...

• Application texts. These are used for various function and menues in the Web Viewer and are based in Signifikant’s translations. Currently supported languages are found here: Custom texts and available languages

• Custom application texts. This is when an application text does not fit customer’s needs. Custom texts will override the application texts. It is also for some functions possible to define keytexts in profile.config, and such keytexts shall be defined as a custom text. See here for more information: Custom texts and available languages

• Data texts. These texts are name of parts, specifications on parts, name of kits, products and selected lead texts as the text in the start page. These texts are updated in the Manager application. See this article.

• Texts from API. Eg error messages from integrations come as a part of an API resonse. In this case Web Viewer simply show what is returned. See here for a description of options: https://signifikant.atlassian.net/wiki/spaces/ASKB/pages/974585868/General+objects+and+attributes#Texts-returned-in-calls

Fallback handling

When presenting a text in Web Viewer, Web Viewer will try to present the text in the language the user has selected. If no translation of the text in selected language exist, Web Viewer will check if text has an invariant translation and use that translation. If no invariant translation exist, Web Viewer will fall back to default language. Default language is defined in profile.config and is typically set to an english language variant as en, en-GB or en-US.

This strategy is applied to all texts.

Adding languages

Available languages are defined in the language storage. Languages may be

...

When new texts are created manually no persistent id is added. This must be done manually or in an external translations database.

Text storage

All texts are available as a table in the text storage. The text repository may be used to

...