Localization Issues

This section describes issues encountered when using the Sun N1 Service Provisioning System 6.0 in locales other than the English locale.

Cannot Import Variable Sets That Include Non-ASCII Characters(6576425)

If you try to import a variable set that includes non-ASCII characters in the set name or details, the import fails.

Workaround: None.

Cannot Save or Check Out Plans or Components That Contain Non-ASCII Characters (6565638, 6576430)

If you use the browser user interface to try to save or download the XML file of a plan or component that includes non-ASCII characters, the operation fails.

Workaround: Use the command line interface to save or checkout plan or component XML that includes non-ASCII characters.

Search Pattern With Non-ASCII Latin-1 Characters Does Not Work Correctly (6302462)

In the Latin-1 locale environment, non-ASCII characters should not be used in the search pattern. For example, umlauts in German and accents in French. The desired match might not be in the returned set when the find operation is executed.

Workaround: Latin-1 locale users should not use non-ASCII characters as the input to the find command. Using non-ASCII characters might not return the desired result. Use only ASCII characters in these locales.

Locale Sensitive Sorting Is Not Supported

String–based data within the Sun N1 Service Provisioning System is sorted using the standard dictionary lexicon. Locale-specific collation is not performed. Consequently, accented versions of characters appear in a different position than the same unaccented characters.