GNOME 2.0 Desktop for the Solaris Operating Environment Troubleshooting Guide

Chapter 9 Localization and Internationalization Problems

This section provides information about how to deal with localization- and internationalization-related problems in the GNOME 2.0 Desktop.

9.1 Localized Locales


Note –

Arabic and Hebrew are not fully supported locales.


The GNOME 2.0 Desktop supports the locales listed in the following table.

Language 

Locale 

Arabic 

ar 

ar_EG.UTF-8 

Brazilian Portuguese 

pt_BR.ISO8859-1 

pt_BR.UTF-8 

Chinese, Simplified 

zh 

zh.GBK 

zh.UTF-8 

zh_CN.EUC 

zh_CN.GB18030 

zh_CN.GBK 

zh_CN.UTF-8 

Chinese, Traditional 

zh_HK.BIG5HK 

zh_HK.UTF-8 

zh_TW 

zh_TW.BIG5 

zh_TW.EUC 

zh_TW.UTF-8 

English 

Posix (C) 

en_AU.ISO8859-1 

en_CA.ISO8859-1 

en_GB.ISO8859-1 

en_GB.ISO8859-15 

en_IE.ISO8859-1 

en_IE.ISO8859-15 

en_NZ.ISO8859-1 

en_US.ISO8859-1 

en_US.ISO8859-15 

en_US.UTF-8 

French 

fr_FR.ISO8859-1 

fr_FR.ISO8859-15 

fr_FR.UTF-8 

German 

de_DE.ISO8859-1 

de_DE.ISO8859-15 

de_DE.UTF-8 

Hebrew 

he 

he_IL.UTF-8 

Italian 

it_IT.ISO8859-1 

it_IT.ISO8859-15 

it_IT.UTF-8 

Japanese 

ja 

ja_JP.eucJP 

ja_JP.PCK 

ja_JP.UTF-8 

Korean 

ko 

ko_KR.EUC 

ko.UTF-8 

ko_KR.UTF-8 

Polish 

pl_PL.ISO8859-2 

pl_PL.UTF-8 

Russian 

ru_RU.ANSI1251 

ru_RU.ISO8859-5 

ru_RU.KOI8-R 

ru_RU.UTF-8 

Spanish 

es_ES.ISO8859-1 

es_ES.ISO8859-15 

es_ES.UTF-8 

Swedish 

sv_SE.ISO8859-1 

sv_SE.ISO8859-15 

sv_SE.UTF-8 


Note –

Some locales provide limited support, as follows:


9.2 Problems That Affect All Locales

The following problems affect all locales:

9.2.1 Unlocalized Menu Items

Problem  

Affects all locales. 

The following menu items are unlocalized across all locales: 

  • Audio Control

  • Media Player

Solution  

This problem will be fixed in a future release. 

9.2.2 Warning Messages to Console

Problem  

Bug ID 4818711, affects all locales. 

When you launch GNOME applications from a terminal, you might occasionally see warning messages in the terminal window. 

Solution  

These warnings do not appear if you launch applications from the desktop environment menus. These warnings do not affect the functionality of the application.  

This bug will be fixed in a future release of the GNOME Desktop. 

9.2.3 Obsolete Topics In Online Help

Problem  

Affects all locales. 

Obsolete applications such as gweather and Stock Ticker are included in online Help.

Solution  

Ignore Help for obsolete applications. 

9.2.4 Multiple Trash Icons

Problem  

Affects all locales. 

When you switch languages using dtlogin, and you log in remotely, multiple Trash icons are shown on the desktop.

Solution  

Perform the following steps: 

  • Open a terminal.

  • Change to the .gnome-desktop directory:

    cd .gnome-desktop

  • Remove unnecessary Trash files.

9.2.5 Dialogs and Panels Are Not Localized

Problem  

Affects all locales. 

A number of applications display unlocalized dialogs and panels.  

Solution  

This problem will be fixed in a future release of the GNOME Desktop. 

9.2.6 Cannot Open a File Created in a Different Locale

Problem  

Bug ID 4824884, affects all locales. 

Nautilus may not open a file that was created in a different locale.  

Solution  

Log in to the locale in which the file was created, then open the file. 

9.2.7 Launching gmines Causes a Segmentation Fault

Problem  

Affects the gmines game in all locales.

If you install a language package, then gmines causes a segmentation fault the next time you try to launch the game.

Solution  

Remove the following file to stop the game from freezing: /usr/share/locale/[your-locale]/LC_MESSAGES/gnome-games.mo.

This action also removes the localization support for all games.  

This problem will be fixed in a future release. 

9.3 Problems That Affect European Locales

The following problems affect European locales:

9.3.1 OpenWindows Login Option Is Missing

Problem  

Affects all European locales in the Solaris 8 operating environment. This is not a problem for the Solaris 9 operatinig environment. 

When you install the GNOME 2.0 Desktop you might notice that OpenWindows is no longer present as a session option in the login screen.  

Solution  

Perform the following steps to restore the OpenWindows option to the login screen: 

  1. Log in as root.

  2. Run the following command:

    cp /usr/dt/config/C/Xresources.d/Xresources.ow /usr/dt/config/locale/Xresources.d/Xresources.ow

Where locale corresponds to the locale for which you wish to restore the OpenWindows login option.

9.3.2 Start Menu Is Not Localized

Problem  

Affects the pt_BR.ISO8859-1 locale. 

The Start menu is not localized.  

Solution  

This problem will be fixed in a future release. 

9.3.3 Characters Are Displayed Incorrectly in the XScreenSaver Properties Dialog

Problem  

Affects the pt_BR.ISO8859-1 and pt_BR.UTF-8 locales. 

In the XScreenSaver Properties dialog, localization characters are missing, In the pt_BR.UTF-8 locale incorrect characters are displayed, for example Cryllic characters.

Solution  

This problem will be fixed in a future release. 

9.3.4 Keyboard Shortcut Does Not Change Input Method Window

Problem  

Affects Russian locales. 

The keyboard shortcut Ctrl+Spacebar to select and change the input method window does not work on the x86 architecture edition of the Solaris operating environment.

Solution  

Use the mouse to select and change the input method window. 

9.3.5 Poor Font Quality in Terminal

Problem  

Affects Russian locales. 

The font quality is low for the Terminal application.

Solution  

Perform the following steps:  

  1. Open a terminal, then choose Edit -> Profiles.

  2. Click on the Edit icon.

  3. In the General tabbed section, deselect the check box Use the same font as other applications.

  4. Click on the font selection bar.

  5. Choose a suitable font from the Choose a terminal font dialog.

9.3.6 No Support for CP1251 and ANSI1251 Encoding

Problem 

Affects Russian locales. 

The pango X11 shaper in this release of the GNOME Desktop does not support CP1251 encoding. As a result, CP1251 or ANSI1251 encoded characters are displayed as zero-width or blank characters.  

Solution 

Use the following locales, which are supported by the pango X11 shaper, until CP1251 support is available:  

  • ru_RU.KOI8-R

  • ru_RU.ISO8859-5

  • ru_RU.UTF-8

You can use iconv conversion tables to re-encode CP1251 and ANSI1251 files. To encode a CP1251 or ANSI1251 file into a UTF-8 encoded file, in a terminal run the following command:  

/usr/bin/iconv -f CP1251 -t UTF-8 CP1251 filename > UTF-8 filename. (man iconv)

9.3.7 Rasterization Problems in Russian Locale

Problem  

Affects the ru_RU.KOI8-R locale. 

In the Solaris 8 operating environment, x86 architecture edition, you might experience rasterization problems regarding the following Russian glyphs: 

  • 00F1

  • 00FF

  • 00DC

This problem affects both the Common Desktop Environment (CDE) and the GNOME Desktop. 

Solution  

You need to select specific fonts for use within the GNOME Desktop. Perform the following steps:

  • Open a terminal and run the following command:

    gnome-font-properties

  • Click on the Desktop font button in the Font Preferences dialog.

  • In the Pick a Font dialog, specify a font from the following list:

    • application: medium, medium italic, bold, bold italic

    • arial: italic, bold, bold-italic

    • courier: italic, bold italic

    • fixed: medium

    • interface system: medium

    • monospace: normal

    • sans: italic, bold italic

    • times: italic, bold italic

This problem will be fixed in a future release. 

9.3.8 Help Appears Only in English

Problem  

Bug id 4921134, affects the following locales: 

  • fr_BE.UTF-8

  • es_AR.ISO8859-1

  • es_BO.ISO8859-1

  • es_CL.ISO8859-1

  • es_CO.ISO8859-1

  • es_CR.ISO8859-1

  • es_EC.ISO8859-1

  • es_GT.ISO8859-1

  • es_MX.ISO8859-1

  • es_NI.ISO8859-1

  • es_PA.ISO8859-1

  • es_PE.ISO8859-1

  • es_PY.ISO8859-1

  • es_SV.ISO8859-1

  • es_UY.ISO8859-1

  • es_VE.ISO8859-1

Solution  

Perform the following actions to resolve this issue: 

  • su passward

  • cd /usr/share/locale

  • ln -s parent locale target locale

  • Log out of your session.

  • Log in again.

Applications should now appear in the target locale. 

9.4 Problems That Affect Asian Locales

The following problems affect Asian locales:

9.4.1 Default Desktop Font Is Too Small Or Blank

Problem  

For example: bug ID 4805328, affects some locales, including Chinese locales. 

Currently, you cannot set the default font for the GNOME Desktop for each locale. As a result, particularly if you are switching between locales, you might find that the default desktop font is either too small or is rendered blank. 

Solution  

To change the default desktop font, perform the following steps:  

  • Open a terminal and run the following command:

    gnome-font-properties

  • Use the Font Preferences dialog to change font size to appropriate values. For example, in Chinese locales, you can set both Application font and Desktop font to Sans 13.

9.4.2 Special Fonts Are Missing in Chinese Locales

Problem  

Bug ID 4821955, affects Traditional Chinese locales. 

You cannot see the characters displayed with some special fonts such as bold fonts. As a result, some characters in the Yelp window appear to be missing.  

Solution  

You must change the pangox.alias file in /etc/{zh_TW.EUC,zh_TW.BIG5,zh_TW.UTF-8,zh_HK.BIG5HK,zh_HK.UTF-8}. Perform the following steps:

  1. Log in as root.

  2. Change to the directory where thepangox.alias file is located for your locale. For example, for the zh_TW.BIG5 locale, run the following command:

    cd /etc/pango/zh_TW.BIG5

  3. Run the following command:

    cat pangox.alias | tr [A-Z] [a-z] > /tmp/pango

  4. Run the following command:

    mv /tmp/pango pangox.alias

  5. If the directory /etc/pango/sparcv9/pango is on your system, change the pangox.alias files. in the locale subdirectories in that directory, in the same way as for /etc/pango.

9.4.3 GNOME Ghostscript Display

Problem  

Affects Asian and Japanese locales.  

Characters with the Japanese Postscript font name are garbled when displayed in GNOME Ghostscript. 

Solution  

Perform the following steps:  

  1. Log in as root.

  2. Run the following command: cd /

  3. Run the following command: mkdir /Resource

  4. Depending on the locale, run one of the following commands:

    Simplified Chinese

    ln -s /usr/openwin/lib/locale/zh/X11/Resource/CMap /Resource/CMap

    Traditional Chinese

    ln -s /usr/openwin/lib/locale/zh_TW/X11/Resource/CMap /Resource/CMap

    Japanese

    ln -s /usr/openwin/lib/locale/ja/X11/Resource/CMap /Resource/CMap

    Korean

    ln -s /usr/openwin/lib/locale/ko/X11/Resource/CMap /Resource/CMap

9.4.4 Different Date Format in the Solaris Operating Environment

Problem  

Affects Japanese locales. 

The date format is different in the Solaris operating environment. There is no '(' and ')' on the weekday format in the following locales: 

  • Solaris 8 operating environment: ja_JP.UTF-8

  • Solaris 9 operating environment: ja_JP.eucJP, ja_JP.UTF-8

Solution  

Not applicable. 

9.4.5 Character Display Problem in GTK2+ Applications

Problem  

Bug ID 4785550, affects the gedit application and other GTK2+ applications in Japanese locales.

Part of the IBM/NEC extended character and special characters are not displayed. 

Solution  

Known limitation. 

9.4.6 Printing Out From gedit in the Solaris 8 Operating Environment

Problem  

Affects Japanese locales. 

You can preview JISX0212 in the gedit application, but you cannot print out JISX0212.

Solution  

Solaris 8 operating environment: Known limitation. 

Solaris 9 operating environment: Perform the following steps:  

  • Open the gedit application.

  • Choose Edit -> Preferences.

  • Select Fonts from the Print category, in the Categories panel.

  • For each print item, specify either of the following fonts:

    • HG-GothicB-Sun

    • HG-MinchoL-Sun

9.4.7 Cannot Print Japanese Characters With Default Font in gedit

Problem  

Bug 4861491, affects Japanese locales. 

When you use the default printer font in the gedit application, Japanese characters are not displayed in Print Preview and are not printed by printers.

Solution  

Perform the following steps:  

  • Open the gedit application.

  • Choose Edit -> Preferences.

  • Select Fonts from the Print category, in the Categories panel.

  • For each print item, specify the HG-GothicB-Sun font.

9.4.8 Cannot Open ISO–2022–JP Encoded File

Problem  

Bug ID 4826184, affects Japanese locales. 

You cannot open ISO-2022–JP encoded files in the gedit application.

Solution  

This problem will be fixed in a future release. 

9.4.9 Localized Characters Do Not Display in gedit

Problem  

For example: bug ID 4785550, affects Japanese locales. 

Japanese characters do not display in the gedit application, when you select Courier as the default font.

Solution  

Perform the following steps:  

  • Open the gedit application.

  • Choose Edit -> Preferences.

  • Select Font & Colors in the Categories panel.

  • Select the option Use default theme font.

This solution does not fix the problem that IBC/NEC extended character and special characters are not displayed in the Solaris 8 operating environment. 

9.4.10 Character Display Problem in Terminal

Problem  

Affects Japanese locales. 

In the Terminal application Preferences dialog, IBM/NEC extended character and special characters are not displayed when you select the option Use the same font as other applications.

Solution  

Perform the following steps: 

  • Open a terminal.

  • Choose Edit -> Current Profiles.

  • In the Editing Profiles dialog, deselect the option Use the same font as other applications.

  • Specify the font to be interface user.

9.4.11 Core Dump When Copy or Link to File

Problem  

Bug ID 4824884, affects Japanese locales. 

A core dump sometimes occurs when you use Nautilus to copy or link to a file that was created in a different locale.  

Solution  

Log in to the locale in which the file was created, then copy the file or create a link to the file. 

9.4.12 Input Method Window Repeatedly Flushed

Problem  

Bug ID 4781611, affects the ja_JP.UTF–8 locale. 

When there are multiple input contexts on the same top-level application window, the input method window is repeatedly flushed. 

Solution  

This problem will be fixed in a future release. 

9.4.13 Japanese Locale Core Dump

Problem  

Bug ID 4808468, affects the ja_JP.UTF–8 locale. 

An application core dump occurs when you do the following:  

  1. Choose Unicode List -> HIRAGANA from the IM status.

  2. Close the application window.

Solution  

This problem will be fixed in a future release. 

9.4.14 GTK2+ Applications Freeze

Problem  

Bug ID 4820426, affects the ja_JP.UTF–8 locale. 

GTK2+ applications freeze when you do the following:  

  1. Open a Lookup Choice window.

  2. Press and hold the space key.

Solution  

This problem will be fixed in a future release. 

9.5 Problems That Affect Complex-Text Locales

The following problems affect complex—text locales:

9.5.1 Incomplete Support for Right-to-Left Languages

Problem  

Affects Arabic and Hebrew. 

Only partial support is available in the GNOME Desktop for right-to-left languages. Full support for right-to-left language printing and GUI widget mirroring is currently under development in the GNOME Desktop.  

Solution  

Arabic and Hebrew text input is supported in the GNOME 2.0 globalization release, with the exception of the Terminal application. If you have not installed any other language pack, and you want text input support, then install the following patches:

 

SPARC Architecture Edition 

x86 Architecture Edition 

Solaris 8 Operating Environment: 

114485-01 

114486-01 

Solaris 9 Operating Environment: 

114274-02 

114275-02