Difference between revisions of "Create a Localyzer only project"
(→Accessors) |
(→Translation Connections and Locales) |
||
| Line 32: | Line 32: | ||
[[File:LzTMS.png|center|600px]] |
[[File:LzTMS.png|center|600px]] |
||
| − | Select the source locale |
+ | Select the source locale and the target locales into which the strings will be translated. Optionally, |
| + | * The pseudo-locale, by default 'eo' (Esperanto). It allows to check if strings have been externalized, the layout for expanded strings, etc. |
||
| + | * The trackback locale, by default 'ia' (Interlingua). This works together with LocalyzerQA to determine what exact strings to modify if necessary |
||
| + | * The InContext locale, by default 'la' (Latin). This works together with the InContext Chrome plugin to easily capture context. |
||
| + | |||
Click ''Next'' |
Click ''Next'' |
||
Revision as of 15:03, 29 October 2025
Data Source Settings
For this example, we are using the GitHub repository. Other Data Source types are similar. Enter the credentials, the repository URL, and the branch that is being used for the project.
Project Name
The values on this page are initially filled in based on the repository and can be changed at creation or later while editing.
- Set the Group Name. Often, this is the same as the Company Name that Command Center was installed with. But it can be almost anything. There is a restriction that it must be the same case. For example, if the Group Name for other projects is ACME (all caps), then another project cannot be created with a group name of 'acme' or 'Acme'.
- Set the Project Name. Project name must be one word and cannot contain any of the following characters: < > : " * / | ? . % --
- Set the Module Name. This is defaulted to the branch that the project is using.
- Tags - tags can be selected from a drop-down list of already created tags or new ones can be created by selecting the plus sign. Projects can have a number of tags associated with them.
- Select the Project Run Type. A project can be a Globalyzer project, a Localyzer project or both. By default these are unselected. The user cannot select Next until at least one option is selected.
Select Next
Accessors
Select the Users and Teams that will have access to this project. Also verify the users that will receive email notifications for this project.
Click Next
Translation Connections and Locales
Select a Machine Translation, an LLM, or a Translation Management System that will be translating the resource files. These need to have been created before attempting to create a Localyzer project.
Select the source locale and the target locales into which the strings will be translated. Optionally,
- The pseudo-locale, by default 'eo' (Esperanto). It allows to check if strings have been externalized, the layout for expanded strings, etc.
- The trackback locale, by default 'ia' (Interlingua). This works together with LocalyzerQA to determine what exact strings to modify if necessary
- The InContext locale, by default 'la' (Latin). This works together with the InContext Chrome plugin to easily capture context.
Click Next
