The project localization function allows you to adapt projects for use by a foreign audience by replacing the information text fields of the project with translations specified in a special file.
Creating a translation file
The file itself is a .csv table with comma as a separator and can be opened by any spreadsheet editor. Also, the translation file can be added to the project as a static “Spreadsheet” or “Google Spreadsheet” block by performing a preliminary import in Google Docs.
One of the translation options can be a project that automatically translates the text of a table using the "Text Processing - Text Translation" action.
You can create a table using the main ProjectMaker menu: File → Create localisation file:
When you click this button, the following text fields of the project will be collected and written to the file:
Action message text "Waiting for user action"
Alert Action Text
Action group comments
Localized alerts and messages will also be translated during the ZennoPoster project.
Thus, for the following project:
The following translation table will be compiled:
The current values of the project will be recorded in the column corresponding to the current localization of the program.
Modifying a table
The table consists of 5 columns:
The ID of the element to be translated, used to apply the translation
The status of the translation element used to control the relevance of the data.
The “Need update” status is set:
By default, all elements have;
In the absence of texts from third-party localizations;
When the file is updated for the first time after changing the text in the project;
The “Ok” status is set:
If there is at least one third-party localization text;
The “Not found” status is set:
If there is no element with the specified id in the project.
Russian localization text of the element
English localization text of the element
Chinese element localization text
Columns of text of third-party localizations of the project, as well as an item status column, are available for free editing.
File changes are applied instantly without the need to reload the project or program.
When the ID column is changed, the element will not be found in the project and will receive the “Not found” status, which is also set when the element is deleted in the project, therefore it is not recommended to change this parameter.
If you change the column of the current localization in the table, and not in the project, the file will lose its relevance and the element will not be considered translated, so when you try to view the translation of another localization, you will be prompted to update the file.
To avoid errors in loading the translation file, it is recommended to perform all table changes using spreadsheet editors.
Updating the translation file
The file update function is necessary to write new values to the file, as well as to update the text of the current localization of elements.
If there is a translation file next to the project, the Localization section will be available in the menu, containing buttons for updating localisation file and viewing other project localizations:
When you click the "Update localization file" button, the current values of the project text fields will be collected with subsequent matching with the file fields. For existing elements, the text of the current localization will be updated, as well as the status. New elements will be added with the “Need update” status, and the elements not found in the project, but existing in the file, will receive the “Not found” status.
The translation of a project is carried out by replacing the text of the translated elements with those specified in the text localization file when viewing the localization, as well as when directly opening a project created in a localization different from the current localization of the program.
When replacing, the id of the elements is compared, as well as the comparison of the current value of the element in the project and the value of the localization text of the element in the file. Thus, if the text was changed in the project and the file was not updated, then this element is considered irrelevant and will not be translated when the project is opened in a program of another localization. However, in the case of viewing localization, a file update will be offered, without which the viewing will not be available. This logic allows you to prevent disagreements between the source text of the project and the text of the original localization of the file when viewing the translation, and at the same time translate the maximum number of translated elements when directly opening the project in a program of a different localization.
If an item does not have translation text for the localization being viewed, the item text will not be changed and will remain as it is in the original project localization.
The translation preview function performs the translation of the project exactly according to the translation when the project is opened in a program of another localization.
In the translation view mode, the execution and recording of the project, as well as its saving and modification, are not available.
To exit the localization view mode, press the “Back to editing” button on the information panel, or select the current program localization in the “Translation view” menu.
If, while viewing the translation, the table file was damaged or deleted, the project will return to its original state and display an error message.
It is also worth considering that, unlike the comments of the action groups and the actions themselves, the notes do not adapt their size depending on the text.