This section describes localization issues that apply to Solaris 10 OS.
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:
Right-click on iiim-panel and select Preference. The Input Method Preference Editor, iiim-properties, is displayed.
Select None or Attach to Each Application from the Input Method Status and Switcher Placement list in the General tab.
Press Apply or Click the OK button.
To switch the input language, you can also use Hotkey. To enable Hotkey, perform the following steps:
Go to Misc tab in the iiim-properties.
Select the Enable Language/Script choice window using Hotkey option.
Press Apply or Click the OK button.
Note - When Attach to each application is selected, the language switcher list will not be displayed for GTK applications. You can switch input language by using Hotkey.
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.
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.
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.
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 IIIMF instead of the Russian keyboard layout.
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.
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
Reboot the system.
Alternatively, you can log in to ar_EG.UTF-8 or other UTF-8 locales.
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.
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:
Akhbar MT (Regular, Bold)
Shayyal MT (Regular, Bold)
Naskh MT (Regular, Bold)
No error message is displayed.
Use any of the newly delivered Kacst family of fonts to display Arabic characters in GNOME applications.
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.
Click mouse button 1 on the background workspace or Launch Menu before clicking any application.
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.
Identify the shortcut keys assigned to user actions from menu in the product.
When migrating to UTF-8 locales, the files affect the method that you use to import or export data.
Microsoft Office files are encoded in Unicode. StarOffice applications can read and write the Unicode encoded 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.
Some HTML files might be displayed in garbage characters. This problem is typically due to the following reasons:
The charset encoding tag is incorrect.
The charset encoding tag is missing.
To find the charset encoding tag in the HTML file, perform the following actions:
Open the file with Mozilla.
Press Ctrl-i, or click View to open the View menu.
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:
Open the file with Mozilla Composer.
Open the File menu.
Select Save as Charset.
Choose the correct encoding. Mozilla Composer automatically converts the encoding and the charset tag as appropriate.
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 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.
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.
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.
Right-click on the panel where you want to place the launcher.
Choose Add to Panel->Launcher.
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
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.
Software support for some keyboard layouts has been added to the Solaris OS. This software gives users greater flexibility for keyboard input by modifying standard U.S. keyboard layouts to their own language needs.
Currently, no hardware is available for the following keyboard layout types:
Workaround: Choose one of the following workarounds:
Workaround 1: To take advantage of this keyboard software, set up keyboard input using the kbd -s command line utility. For desktop sessions with the UTF-8 locale environment, use Input Method Preference Editor. If the required keyboard layout is not included in the kbd -s utility, use Workaround 2.
Workaround 2: Modify the /usr/openwin/share/etc/keytables/keytable.map file. For example, for the Canadian Type 6 keyboard, make the following changes:
Change the US6.kt entry to Canada6.kt in the /usr/openwin/share/etc/keytables/keytable.map file. The modified entry should read as follows:
6 0 Canada6.kt
Reboot the system for the changes to take effect.
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.