InContext Locale: Difference between revisions
Jump to navigation
Jump to search
Created page with "= Prerequisites == To set the special Context Locale, the Localyzer project must be configured with a TMS with an InContext Server and a valid Context License. = Setting th..." |
|||
| Line 1: | Line 1: | ||
= Prerequisites == | = Prerequisites == | ||
To set the special Context Locale, the Localyzer project must be configured with a TMS with an InContext Server and a valid Context License. | To set the special Context Locale, the Localyzer project must be configured with a TMS with an InContext Server and a valid Context License. | ||
[[File:Localyzer Project with InContext.png|600px|center]] | |||
= Setting the Context Locale = | = Setting the Context Locale = | ||
Either during the project creation or when editing a Localyzer project, set the Context Locale checkbox and pick a locale. By default, we use 'la' (Latin) as it is found in most browser settings and it is not a locale likely to be a target for most commercial applications. | Either during the project creation or when editing a Localyzer project, set the Context Locale checkbox and pick a locale. By default, we use 'la' (Latin) as it is found in most browser settings and it is not a locale likely to be a target for most commercial applications. | ||
Revision as of 20:29, 2 June 2025
Prerequisites =
To set the special Context Locale, the Localyzer project must be configured with a TMS with an InContext Server and a valid Context License.
Setting the Context Locale
Either during the project creation or when editing a Localyzer project, set the Context Locale checkbox and pick a locale. By default, we use 'la' (Latin) as it is found in most browser settings and it is not a locale likely to be a target for most commercial applications.