Manage Custom Languages
In 'System Language. Open' (MNS105), you can create custom languages.
In 'Custom Language Constants. Open' (MNS130), you can add custom language constants. This holds the custom translations for existing constant IDs. (MNS130) may be opened directly or through a related option in (MNS105). This is only available for custom languages.
| Program/Panel | Field | The field indicates … |
|---|---|---|
| (MNS105/E) | System language | … the code for the languages that the installation covers and custom languages. Custom languages consist of at least 1 number, for example, B7, 7J, or 13. This format is applied to prevent conflicts when a new standard language with the same code is added. |
| (MNS105/E) | Custom language | … the custom language indicator. This field is automatically set to 1 when a custom language is created. |
| (MNS105/E) | Fallback language | … the standard language to fall back into when the custom language does not
have a corresponding constant ID in 'Custom Language Constants. Open'
(MNS130). Only a standard language can be set as a fallback
language. This field is required for custom languages. |
| (MNS130/E) | System language | ... the custom language where the constant IDs are created. |
| (MNS130/E) | Fallback language | … the standard language to fall back into when the custom language does not have a corresponding constant ID in 'Custom Language Constants. Open' (MNS130). This is set in 'System Language. Open' (MNS105) and only used as reference in (MNS130). |
| (MNS130/E) | Constant ID | … the current constant ID that holds a custom translation. When a constant ID is not added to this list, it uses the standard translation of the fallback language. |
| (MNS130/E) | Value | … the standard translation of the current constant ID for reference. |
| (MNS130/E) | Constant value | … the custom translation of the current constant ID. |
A custom language in (MNS105) may only be copied to another custom language. You cannot copy a custom language to a standard language and vice versa. A custom language may only be deleted when there are no corresponding constant IDs in (MNS130) and if it is not used in 'Language. Open' (CRS010).
Custom languages are only available for document printouts and may only be used as document language if it is retrieved from (CRS010). Custom languages cannot be used as session language and system language.
For STREAM output, the document language should also reflect the custom language. However, the custom translations are not set up in (MNS130) and are handled manually in Exstream.
Custom languages are exported and imported to simplify the migration of setups between environments. Custom languages are exported through the related option Export Configuration (Ctrl + 22) in (MNS105). Application Configuration Management (ACM) is used to allow the users to select and export multiple custom languages in the same configuration file
Custom languages are also exported through the action Export (F17). To export a range of custom languages, enter a custom language in the 'From' (LANC) and 'To' (LANC) fields. You can leave the 'From' field empty to export all the custom languages until the value of the 'To'' custom language or leave the 'To' field empty to export all the custom languages starting with the value of the 'From' custom language. To export all custom languages, leave and 'From' and 'To' fields empty.
You cannot export standard languages. If multiple languages are selected or a range of languages is entered, the standard languages are skipped and only the custom languages are exported. If there is no valid custom language in the selection, an error is prompted.