test

Solaris 10 7/07 HW Release Notes

Localization Issues

This section describes localization issues that apply to Solaris 10 OS.

Multiple Input Method Switcher Applications Appear in Trusted Java DS

When you log in to the Trusted Java DS with UTF-8 or Asian locales, the Input Method Switcher application, iiim-panel, appears per label by default. Thus in multiple label environment, multiple iiim-panel appears, which could be confusing to the user.

No error message is displayed.

Workaround: Stop using the iiim-panel. Perform the following steps:

Note –

When Attach to each application is selected, language switcher list will not be displayed for GTK applications. You can switch input language through non-GTK applications or by running GTK applications with X Input Method instead of IIIM. For example:


% env GTK_IM_MODULE=xim gedit

Wnn8 Japanese Input Method

Wnn8 Japanese Input method cannot be used if the Wnn8 servers are not enabled.

Workaround: Enable the Wnn8 servers:


# svcadm enable wnn8/server

In addition, select Wnn8 as the Japanese Language engine by running the iiim-properties command.

Keyboard Shortcuts in Mozilla Ambiguous in Spanish Locale (6288620)

The keyboard shortcuts in Mozilla 1.7 are ambiguous in the Spanish (Es) locale. For example, you can use Ctrl-S to copy or to save. No error message is displayed.

Workaround: Use the shortcut keys assigned to user actions from the product menu.

Uninstaller Displays Strings Incorrectly in Some Locales (6487062)

This bugs affects how you uninstall Solaris Trusted Extensions by using prodreg in locales other than C, POSIX, or any English locale. Strings are not displayed correctly in these locales when you uninstall by using prodreg.

No error message is displayed. The uninstaller shows placeholder strings, and buttons do not display correctly.

Workaround: Before you uninstall with prodreg, run the following commands:


# cd <Solaris_installation_media>/Solaris_10/ExtraValue/CoBundled/Trusted_Extensions
# cp -rp locale /var/sadm/tx

Then uninstall with prodreg.

Input Method Cannot Be Enabled With Primary Administrator Rights (6475081)

A user who has the Primary Administrator right can not use the input method for specific locales which prevents that user from entering characters normally. The input method status is not displayed in the workspace. No error message is displayed.

Workaround: Add the following lines to the /etc/security/exec_attr file:


Primary Administrator:solaris:cmd:::/usr/bin/csh:uid=0;gid=0
Primary Administrator:solaris:cmd:::/usr/bin/ksh:uid=0;gid=0
Primary Administrator:solaris:cmd:::/usr/bin/sh:uid=0;gid=0

For information about the file format, see the exec_attr(4) man page.

New ChuYin Input Method Not Supported in Upgrade to IIIMF rev.12 (6492129)

When you upgrade the OS to the Solaris 10 6/06 or Solaris 10 11/06 release, the input method framework and individual input methods get upgraded from rev.10 to rev.12. However, ChuYin is not in the list of supported input methods. Also, you cannot use the function keys F2 and F3 to switch methods

Workaround: Use PinYin to type traditional Chinese characters with Hanyu PinYin. Use Ctrl+Shift to switch input methods.

AltGr Does Not Work As Mode Switcher in Some Russian Locales (6487712)

The AltGr key does not work as a mode switcher for the Russian Xsun layout inru_RU.KOI8-R and ru_RU.ANSI1251 locales.

Workaround 1: Switch to the ru_RU.UTF-8 or the ru_RU.ISO8859-5 locale.

Workaround 2: Use IIIMFTM instead of the Russian keyboard layout.

Arabic6.kt Keytable Does Not Contain Arabic Symbols (6463576)

The Arabic6.kt keytable does not contain any Arabic symbols.

Workaround: Use IIIMF. Set the Arabic input through the gimlet switcher instead of switching to Arabic by using the Altgr key.

Arabic Text Not Appearing in ar Locales

If your x86 system is using Xorg as the default Xserver, the Arabic font (iso7759-6) does not appear in the ar locale. This error does not occur if you are using XSun instead of XOrg.

Workaround: Follow these steps.

  1. As superuser, edit /usr/dt/config/Xservers.

    • Uncomment or add the following line:


      :0 Local local_uid@console root /usr/openwin/bin/Xsun :0 
-nobanner -defdepth 24

    • Comment out the following line:


      :0 Local local_uid@console root /usr/X11/bin/Xorg :0

  2. Reboot the system.

Alternatively, you can log in to ar_EG.UTF-8 or other UTF-8 locales.

Solaris PDASync Does Not Support Data Exchange With the Multibyte Internationalized PDA Device (4263814)

If you exchange multibyte data between a PDA device and Solaris CDE, the data might be corrupted in both environments.

Workaround: Back up your data on your personal computer with the PDA backup utility before you run the Solaris PDASync application. If you accidentally exchange multibyte data and corrupt that data, restore your data from the backup.

Adding Regions Fails With the localeadm Command (6350486)

The function to add regions in the localeadm command no longer works if you create a new configuration file. The Language CD is not detected when you add the following regions:

The following error message is displayed:


No langcd image has been found in
/cdrom/sol_10_1005_x86_4/Solaris_10/Product

No langcd image has been found in
/cdrom/sol_10_1005_x86_4 /cdrom/sol_10_1005_x86_4
/cdrom/sol_10_1005_x86_4
/cdro m/sol_10_1005_x86_4
/cdrom/sol_10_1005_x86_4

Please enter the path to this image/disk, or enter 'q' to quit:

Workaround: When you are prompted to create a new configuration file, select No. Instead, use the configuration file that was installed in the system.

L10N Messages Missing When Using localeadm Utility to Add Locales (6423974)

When the Locale_config configuration file is created using the DVD/net image, using the Locale_config file to add locales leaves many unlocalized messages on the Gnome Desktop. No error message is displayed.

Workaround 1:

    Login as superuser and do the following:

  1. Change to the location of the localeadm Locale_config file.


    # cd /usr/sadm/lib/localeadm/

  2. Revert to the existing Locale_config file bundled with the localeadm utility. 


    # mv Locale_config_S10.txt.old Locale_config_S10.txt

Workaround 2:

Re-create the Locale_config file by using the CD images.

SPARC: Keycode 50 Does Not Work for European Keyboard Layouts (6387317)

Keycode 50 is not working for European keyboard layouts. This problem occurs with all European *6.kt keytable files. All keytables assign some symbols to keycode 50, but the key does not work. No error message is displayed.

Workaround:

Edit the *6.kt files in the /usr/openwin/share/etc/keytables directory. Duplicate keycode 50 for keycode 49 in the affected *6.kt file. For example, add the following entry for keycode 49 to the affected keytable file:

49 RN XK_numbersign XK_asciitilde

Several Arabic Fonts Do Not Work in GNOME (6384024)

In GNOME when you select certain Arabic fonts, the characters do not display. This problem appears when you select fonts for applications, the desktop, or the window title using the GNOME font properties menu. The affected fonts include:

No error message is displayed.

Workaround:

Use any of the newly delivered Kacst family of fonts to display Arabic characters in GNOME applications.

Unable to Switch Input Language on Session-Saved Applications (6360759)

Multiple language input is supported in UTF-8 locales, but the language switch is not working with session-saved applications where mouse button 1 is clicked first after login. This problem occurs with the Java Desktop System (Java DS). No error message is displayed.

Workaround:

Click mouse button 1 on the backgroundworkspace or Launch Menu before clicking any application.

Keyboard Shortcuts in Mozilla in ES Locale Are Unusual and Ambiguous (6288620)

The keyboard shortcuts in Mozilla 1.7 are unusual, especially in Spanish locale. For example, Ctrl-S is being used for copying as well as for saving. No error message is displayed.

Workaround:

Identify the shortcut keys assigned to user actions from menu in the product.

Migration Note to UTF-8 locales

When migrating to UTF-8 locales, the files affect the method that you use to import or export data.

Microsoft Office Files

Microsoft Office files are encoded in Unicode. StarOffice applications can read and write the Unicode encoded files.

HTML Files

HTML files authored using HTML editors such as Mozilla Composer, or HTML files saved by a web browser, usually contain a charset encoding tag. After exporting or importing, you can browse such HTML files with the Mozilla Navigator web browser, or edit the files with Mozilla Composer, according to the encoding tag in the HTML file.

Fixing Broken HTML File

Some HTML files might be displayed in garbage characters. This problem is typically due to the following reasons:

To find the charset encoding tag in the HTML file, perform the following actions:

  1. Open the file with Mozilla.

  2. Press Ctrl-i, or click View to open the View menu.

  3. Click Page Info.

The charset information is in the bottom of the General tab, for example:


Content-Type text/html; charset=us-ascii

If the string charset=us-ascii does not match the actual encoding of the file, the file might appear broken. To edit the encodings of the HTML file, perform the following actions:

  1. Open the file with Mozilla Composer.

  2. Open the File menu.

  3. Select Save as Charset.

  4. Choose the correct encoding. Mozilla Composer automatically converts the encoding and the charset tag as appropriate.

Emails Saved As Portable Format

Modern mails are tagged with the MIME charset tag. The Email and Calendar application accepts MIME charset tags. You do not need to perform any encoding conversion.

Plain Text Files

Plain text files do not have a charset tag. If the files are not in UTF-8 encoding, encoding conversion is needed. For example, to convert a plain text file encoded in Traditional Chinese big5 to UTF-8, execute the following command:


iconv -f big5 -t UTF-8 inputfilename



 > outputfilename

You can also use the File System Examiner for the encoding conversion.

You can use the Text Editor to read and write character encoding text automatically or by specifying an encoding explicitly when opening or saving a file.

To start Text Editor, click Launch, then choose Applications->Accessories->Text Editor.

File Names and Directory Names

If file names and directory names using multibyte characters are not in UTF-8 encoding, encoding conversion is needed. You can use File System Examiner to convert file and directory names and the contents of plain text files from legacy character encodings to UTF-8 encoding. Refer to the online Help for File System Examiner for more information.

To start File Systems Examiner, click Launch, then choose Applications->Utilities->File System Examiner.

When you access non-UTF-8 file or directory names on Microsoft Windows via SMB using File Manager, you can access the non-UTF-8 file or directory names without encoding conversion.

Launching Legacy Locale Applications

For applications that are not ready to migrate to Unicode UTF-8, you can create a launcher on a front panel to start the application in legacy locales. You can also launch the applications directly from the command line. Perform the following steps to create a launcher for an application.

  1. Right-click on the panel where you want to place the launcher.

  2. Choose Add to Panel->Launcher.

  3. Use the following format to type the entry in the Command field in the Create Launcher dialog:


    env LANG=locale LC_ALL=
locale application name

    For example, if you want to launch an application called motif-app from /usr/dt/bin in the Chinese Big5 locale, enter the following text in the Command field of the Create Launcher:


    env LANG=zh_TW.BIG5 LC_ALL=zh_TW.BIG5 /usr/dt/bin/motif-app

  4. Click OK to create the launcher on the panel.

When you need to run CLI (command line interface) applications which are specific to a legacy locale, open a Terminal window in the legacy locale first and then run the CLI applications in the same Terminal window. To open a Terminal window in a legacy locale, enter the following command:


eng LANG=locale LC_ALL=locale GNOME-TERMINAL –disbable-factory.

Instead of opening a new Terminal window in a legacy locale, you can switch the locale setting from UTF-8 to a legacy locale in the current Terminal window by changing the encoding the Set Character Encoding menu in the Terminal window. Then you must also set the LANG and LANG environment variables to the current shell.

Hardware for Estonian Keyboard Type 6, French Canadian Keyboard Type 6, and Polish Programmers Keyboard Type 5 Not Available

Software support for three additional keyboard layouts has been added to the Solaris OS: Estonian keyboard Type 6, French Canadian keyboard Type 6, and Polish programmers keyboard Type 5.

This software gives users in Estonia, Canada, and Poland greater flexibility for keyboard input by modifying standard U.S. keyboard layouts to their own language needs.

Currently, no hardware is available for the three additional keyboard layout types.

Workaround: To take advantage of this new keyboard software, modify the /usr/openwin/share/etc/keytables/keytable.map file in one of the following ways:

Cannot Print Documents in Portable Document Format (6239307, 6218079)

On all locales, the Document Viewer cannot print localized files that are in Portable Document Format (PDF).

Workaround: Choose one of the following workarounds:

Special Keyboard Keys Do Not Work (5077631)

Special keys on the left of the keyboard do not work on European keyboard mappings. This problem affects all European locales.

Workaround: Use shortcut keys instead of the special keyboard keys. The following example lists shortcut keys and the corresponding functions:

Modifier Keys Do Not Function Correctly (4996542)

On all locales, the Alt key and the Shift key might not function as modifier keys when you use the Internet/Intranet input method. For example, the Shift-arrow key combination might not allow you to select text. Instead, the combination might insert Latin characters.

Workaround: Use a different input method, for example, Default. To switch input methods, right-click on an object and select Input method.

Chinese and Korean Characters Are Printed In a Box (4977300)

The postscript printer does not bundle Chinese or Korean fonts. Consequently, in Chinese or Korean locales, if you attempt to print from the Mozilla browser, the characters are printed within a box. The Common UNIX Printer System (CUPS) needs to convert the Mozilla postscript fonts before a file can be printed.

Workaround: Perform the following steps.

  1. Click Launch => Preferences => Printers.

  2. Right-click the PostScript printer icon, then select Properties.

  3. Click the Advanced tab.

  4. Set the Ghostscript pre-filtering to Convert to PS level 1.

Sort Capability in the European UTF-8 Locales Does Not Function Correctly (4307314)

The sort capability in the European UTF-8 locales does not work properly.

Workaround: Before you attempt to sort in a FIGGS UTF-8 locale, set the LC_COLLATE variable to the ISO–1 equivalent.


# echo $LC_COLLATE
>  es_ES.UTF-8
# LC_COLLATE=es_ES.IS08859-1
# export LC_COLLATE

Then start sorting.