GNOME Bugzilla – Bug 231311
I18n Problems -- Launching Evo in Japanese Gnome 2 session still faulty
Last modified: 2002-09-26 21:59:43 UTC
Package: Evolution Priority: Major Version: GNOME2.1.0 1.1.1 Synopsis: I18n Problems -- Launching Evo in Japanese Gnome 2 session still faulty Bugzilla-Product: Evolution Bugzilla-Component: Miscellaneous Description: Description of Problem: Japanese support in Gnome 2 seems to have gone mostly out of the window with the Red Carpet updates of 9/16. The 9/26 snapshots are a bit better, but there are still some flaws. Launching Evo in a Japanese session first only launches Evo with everything set to English. Manually launching from a terminal to force the Japanese yields the following: [$HOME]$ env LC_ALL=ja_JP.eucJP evolution ** WARNING **: Invalid UTF-8 sequence ** WARNING **: Invalid UTF-8 sequence Unlike the 9/16 snapshots, my message list window showing the "From" and "Subject" headings now properly renders Japanese. Also unlike the 9/16 snapshots, I can now access Kinput2 for message composition, but once I hit return to enter the Kinput2 entry, the text displayed on the screen turns from legible Japanese in Kinput2 to ascii garbage in the composer window. This turns out to be the same for regular email message display -- the fonts default to English settings, making it impossible to read any Japanese messages. However, testing Japanese message composition, I discovered that the Japanese text I entered is still there by emailing myself a message in Japanese to my Yahoo account, and then reading that message online using Galeon. Furthermore, launching Bug Buddy from the Help menu gave me the following: ** (bug-buddy:1799): CRITICAL **: file bug-buddy.c: line 293 (on_product_toggle_clicked): assertion `druid_data.state == STATE_PRODUCT' failed This may have something to do with other bugs I've reported, # 30601 and # 30977. I also ran across reference to i18n problems in libzvt that may be relevant, but I can't find the bug number right now. Steps to reproduce the problem: 1. Update Gnome 2 using Red Carpet on 9/26/02 2. Launch Evo in a Japanese Gnome session 3. Try to read a Japanese email Actual Results: Evo launches using English menus and fonts. Even when forcing the environment variable to Japanese, Japanese messages are still rendered as ascii garbage. Playing with the HTML display fonts option doesn't help - you either get more ascii garbage, or mysteriously Chinese ideograph garbage. Expected Results: Evo launched in a Japanese session should automatically make use of Japanese fonts for display in all subwindows and menus. How often does this happen? Every time. Additional Information: Unknown reporter: erikanderson3@yahoo.com, changed to bugbuddy-import@ximian.com. Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
*** This bug has been marked as a duplicate of 230870 ***
I have Japanese fonts for X installed, and I still can't get Evo to display Japanese mail. In the past, I discovered that running Evo in a Japanese Gnome session would do the trick, but ever since updating my Gnome 2 with the Red Carpet snapshots on 9/16, Evo won't do the trick, even in a Japanese Gnome session and even after launching it from a term with $ env LC_ALL=ja_JP.eucJP evolution Changing fonts with gtkHTML won't work either (I've tried), as the encodings for Japanese fonts are too complicated. gtkHTML insists that you also choose the encoding, which bolloxes things up as Japanese uses at least two different encodings, afaict -- one for the Roman alphabet, one for Chinese ideographs, and one for the native Japanese syllabaries. Some font settings seem to lump the Roman and syllabaries together, but any Japanese message is bound to have some combination of all three. Having to futz with font encodings to read half the message simply isn't acceptible. Running Evo under a Japanese Gnome session (prior to the 9/16 Red Carpet snapshots) seemed somehow to get around this problem by using totally different fonts than the ones I can manually select using gtkHTML, but sadly I am not (yet) a programmer and I don't know why this was so. All of this seems to suggest that the problem is not with Evo but with something in the underlying Gnome framework.