When you are publishing content that Translations has localized, the Web Help user interface (UI) supports the following languages:
What has been localized in the UI for the supported languages?
- Contents tab name
- Index tab name
- Search field and Match partial words option
- Tooltips for the toolbar buttons
How does it work?
When you have localized your content in Author-it using Translations, the content is assigned a value for the SYS_LOCALE_ABBREVIATION.
When you publish you localized content, the <Templates\Web Help\uilocale folder, then Web Help opens using the localized UI.
However, if you publish content that can't be matched to a supported locale, then the UI defaults to English.
Can I make my own locale files?
The files needed for a locale are the CSS file and the JS file. You need to create a CSS file and a JS file for your locale, and name them using the two letter locale code used in Translations. Store both of your files in the Templates\Web Help\uilocale folder.
- Use the CSS file if you need to overwrite any styling elements. In most files provided the files are empty. Only the Arabic and the Hebrew css files contain styling code.
- The JS file contains the text strings for elements in the UI - including tabs, button names or tooltips, and messages. Each of the text strings are in English in the first column; just add your localized text stings to the second column.