There are constraints in national language support (NLS) in MCS, which are determined largely by file naming limitations, allowable content in URIs, and certain reserved words.
There are constraints in national language support (NLS) in MCS, which are determined largely by file naming limitations, allowable content in URIs, and certain reserved words.
For example you cannot use NLS characters in the names of policies (policies, layouts, themes, and layout formats).
The table lists MCS user interface controls where you can enter NLS characters.
| Policy | Controls |
|---|---|
| Variants | Literal text values (URIs must be US-ASCII) |
| Layouts | Link Text format attributes on dissecting panes, fragments and form fragments |
| Devices | Text type policy controls on the Policies page. The type can be viewed in the Type control on the Structure page. |
| Name on the Structure page. This is not the Short Name which cannot contain NLS characters. | |
| Help Text on the Structure page |
MCS does not support the use of NLS characters anywhere in the theme editor.
In the policy editors, some words always appear in English rather than in the localized language. These words are not translated because they have special meaning in the context of the processing performed by MCS.
These reserved words include occurrences of or references to:
XDIME or XHTML element names
Most theme style property names, selectors and their values
The names of types of MCS policies or policy objects.
IANA content types, or other names specified in Internet or related standards
The 'Short Name' of any device policy
The text value of any predefined device policy