[natty] fontconfig-voodoo -a does not work in Japanese locales

This is a regression bug due to the language-selector solution of bug #693337. A fix is proposed to be uploaded to Oneiric (branch linked), and an updated build is available in my PPA (https://launchpad.net/~gunnarhj/+archive/misc).

Since the fontconfig-voodoo feature is of high importance to CJK users, while it's partly broken for Japanese and Korean users, I would suggest that the fix is uploaded as a Natty SRU as well.

Thanks for reporting this bug, and sorry for the inconvenience.

> A fix is proposed to be uploaded to Oneiric (branch linked), and an updated build is available in my PPA (https://launchpad.net/~gunnarhj/+archive/misc).

ppa packages work fine for my natty environments, thank you for quick fixing.

@Gunnar ,
In the fix of bug #693337, that provides {lucid,maverick}-backports, are they affect too?
If yes (or probably/maybe yes), I(we?) will test with these backports.

I didn't think of the backports, but now when you ask, so yes, they probably have the same bug.

I'd appreciate if you could test them. If you confirm that they too suffer from the bug, I'll propose tomorrow that similar fixes be added to the backports.

Thanks!

@Gunnar,

I check with {lucid, maverick} with backports(0.5.8+langfixes~lucid1 , 0.6.8+langfixes~maverick1), I can reproduce the bug.

Thanks for confirming that, Fumihito.

I propose that equivalent changes are merged into the Lucid and Maverick backports. Branches with the changes (links above) were uploaded to my PPA (https://launchpad.net/~gunnarhj/+archive/lang-backports), and the resulting builds have been installed and run successfully.

When working with the backports, I realized that the changes in the branch intended for Oneiric and Natty were not sufficient; while they addressed the command "fontconfig voodoo -a", the failure to set the configuration by clicking the "Apply System-Wide" button in Language Support hadn't been dealt with. I updated the branch accordingly, so now the merge proposal for Oneiric should be ok. An updated build is available at https://launchpad.net/~gunnarhj/+archive/misc .

@Fumihito
Since the changes will go to lucid-backports, maverick-backports, and - hopefully - natty-proposed, your assistance with testing these new branches would be valuable.

This bug was fixed in the package language-selector - 0.35

---------------
language-selector (0.35) oneiric; urgency=low

  [ Gunnar Hjalmarsson ]
  * LanguageSelector/FontConfig.py:
    - Make the fontconfig-voodoo --auto option work also when the first
      LANGUAGE item is just 'ja' or 'ko', i.e. without country code
      (LP: #778869).
  * dbus_backend/ls-dbus-backend:
    - When applying the language settings system-wide, set the fonts
      configuration also when the first LANGUAGE item is just 'ja' or
      'ko' (LP: #778869).
  * fontconfig-voodoo:
    - Do not require --force when removing the current config using the
      fontconfig-voodoo -r option.
    - Print an exception message if the --auto option fails to find a
      suitable configuration.

  [ Martin Pitt ]
  * tests/test_check_language_support.py: Fix test case for removed
    gnome-user-guide-XX packages.
  * LanguageSelector/gtk/GtkLanguageSelector.py: Stop forcing GTK2, moving to
    GTK 3 now. Update GIR dependencies to the GTK 3 versions.
 -- Martin Pitt <email address hidden> Wed, 18 May 2011 09:35:29 +0200

It's not clear to me that this has been tested in a lucid/maverick environment and it should be before upload to backports, but I'm generally in favor of this.

Thanks, Scott. As regards testing, please see comment #5. The installations and tests I mentioned were in Lucid respective Maverick.

Accepted language-selector into natty-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Successfully installed and run language-selector 0.34.2. In particular:

* When making Japanese the system language, a link to the Japanese
  fontconfig file is added to /etc/fonts/conf.d as expected, even if
  the first item in LANGUAGE is just 'ja', i.e. without country code
  (since there are no country specific Japanese translations on my box).

* Running the command "sudo fontconfig-voodoo -a", when the list in the
  LANGUAGE environment variable begins with 'ja', adds a similar link
  as expected if it wasn't there before.

Realize that I wasn't supposed to set the "verification-done" tag, so changing back to "verification-needed".

Sponsored and accepted into l/m-backports, thanks Gunnar!

This bug was fixed in the package language-selector - 0.34.2

---------------
language-selector (0.34.2) natty-proposed; urgency=low

  [ Gunnar Hjalmarsson ]
  * LanguageSelector/FontConfig.py:
    - Make the fontconfig-voodoo --auto option work also when the first
      LANGUAGE item is just 'ja' or 'ko', i.e. without country code
      (LP: #778869).
  * dbus_backend/ls-dbus-backend:
    - When applying the language settings system-wide, set the fonts
      configuration also when the first LANGUAGE item is just 'ja' or
      'ko' (LP: #778869).
  * fontconfig-voodoo:
    - Do not require --force when removing the current config using the
      fontconfig-voodoo -r option.
    - Print an exception message if the --auto option fails to find a
      suitable configuration.

  [ Martin Pitt ]
  * debian/control: Switch Vcs-Bzr: to natty branch.
 -- Gunnar Hjalmarsson <email address hidden> Wed, 18 May 2011 09:42:00 +0200