The table below summarizes actions that need to be completed before saving and publishing draft content:
Item |
Comments |
Titles |
Titles should be provided for all available translations of the content. This ensures that content in all available languages appears in Search.
|
Statements |
Content must be entered for each statement in every language translation of a procedure. In other words, each statement should have content in its specific language translation. |
Variable values: single-use and reusable variables |
Define variable values in each language, as the values defined in one language are not automatically defined in the other language. If variable names are different in translated text, before publishing, switch between languages used in the content and check for undefined variables.
Understanding Variable Consistency in Translations Sometimes, when translating a statement in different languages, the variables used in those translations might not be consistent, which can cause errors. Imagine you have a statement translated in two languages: English and Spanish. In the English version, the statement might use the variable "[Name]", while in the Spanish version, it might use "[Nombre]". If you use this statement in your content but only provide a translation for the English version, the tool will still expect to find values for both "[Name]" and "[Nombre]". This can result in errors as your content doesn't provide both values.
|
In templates, reusable variables cannot be translated. This is important to remember when reusing statements in multilanguage procedures.
|
|
Reference links |
Target values defined for one language are automatically applied to other languages. |
Data collection/Scan codes |
Data collection key values and scan code values must be defined in all available languages. |
Dynamic table |
Dynamic table elements must be defined in all available languages. |