You can translate the Composer interface into other languages. Composer supports standard i18n languages. See https://perldoc.perl.org/I18N::LangTags::List#LIST-OF-LANGUAGES.
To translate the interface, you must have a specific supervisor setting switched on. Please contact technical support for information about this setting.
Translation files in the format
vocabulary-<xx>_<YY>.json are used in the translation. The English translation file is provided and is named
- Linux Environments: Located in the
- Windows Environments: Located in the
To translate the Composer interface:
Rename the copy of the file. Be sure to name it in the format
<xx>is a two-character code representing the language you want to use and
<YY>is the dialect. See https://perldoc.perl.org/I18N::LangTags::List#LIST-OF-LANGUAGES.
Translate the JSON values to the right of the JSON keys (after the colon) in the file. All values should be specified in quotes. The JSON keys should not be translated because the keys are used by the Composer code.
Here is an example of part of a translated translation file:
This file is CSS-friendly. For example,
</b>around a JSON value or part of a value indicate that the value should be bold.
Finally, placeholders (variables) are used throughout the file and should not be changed or removed, although they can be relocated within a JSON value, as needed for your translation. Placeholders appear surrounded by
%symbols (for example,
%name%) in the translation file. Composer code inserts a value for these placeholders, based on where the JSON key is used in the product. For example, a dashboard name might be inserted for the placeholder
%name%for one JSON key, but a visual name might be inserted for a different JSON key that also uses the
Save your translated file.
Contact your Composer technical support representative for additional steps.