Use this sheet to configure how the status values are changed when project is edited.
Use these combo boxes to specify how the translation status changes after certain actions. Possible actions are:
|When modifying||If enabled Sisulizer changes the translation status automatically to the selected status after a translation has been modified.|
|When selecting||If enabled Sisulizer changes the translation status automatically to the selected status after a translation has been selected.
This feature is for a QA persons that can just click translations to set the status for a desired status.
|When loading||If enabled Sisulizer changes the translation statuses of all translations automatically to the selected status after the project has been loaded.
Be careful with this feature. If this feature enabled Sisulizer will set every single status value to the specific value after the project has been loaded.
|When importing||Specifies the default translation status value that Sisulizer sets in the Import Wizard.|
Use these check boxes to specify if row status, comments and translations are automatically changed after certain actions.
|Change row status from New to In use automatically before scanning||If checked Sisulizer automatically changes row status from New to In use when rescanning the project.|
|Change row status from Changed to In use automatically before scanning||If checked Sisulizer automatically changes row status from Changed to In use when rescanning the project.|
|Clear translation comments automatically||If checked Sisulizer automatically clears translation comments when rescanning the project. Turn this on if you want automatically clear the translation comments written by translators.
Note! When this is turned on application clear all translation comments when performing scanning.
|Enable automatic update of binary translations||
Some projects have binary rows. Such rows usually contain custom data that user translates by loading data from a file. Updating these translations manually may be laborious. To make it easier you can turn on automatic translation update. When it is turned on Sisulizer remembers the file name and the next time the project is opened Sisulizer compares the translated data to the data in the file. If data in the file differs from the current data Sisulizer automatically loads new data from the file to the project. To turn automatic translation update on click Yes when Sisulizer prompts it after you have selected the file for the first time.
|Retranslate automatically translated items if original value changes||If the row has been translated automatically (auto translated status is on) and the original value of the row will be modified in the source file. Then during the next scanning process the row will get a new original value, but the translations keep same. After scanning the translations will not match to the original value any more.
If checked all such automatically translated rows where the original values changes during the scan process will be retranslated and the existing value will be overwritten.
Use these check boxes to specify if untranslated rows should be translated using existing translations. If either check box is checked Sisulizer translates untranslated rows. The check boxes specify the source where existing translations are looked from. Possible values are:
|Globally within the whole project||Existing translations will be searched from the whole project.|
|Locally within the row's node||Existing translations will be searched only from the same node.|
Specifies if and how the translations of duplicate strings are updates after the translation of one of the strings has been changed.
|Prompt first||Select rows dialog is shown that contains list of all duplicate strings. The user can select which one to update. If a row does not already have a value Sisulizer does not show that row on the list but automatically sets the translation value.|
|Automatically||Sisulizer automatically updates the translations of all duplicate strings.|
|No||No action is done.|
Specifies if and how the statuses of duplicate strings are updates after the status of one of the strings has been changed.
|Prompt first||A select rows dialog is shown that contains list of all duplicate strings. the user can select which one to update.|
|Automatically||Sisulizer automatically updates the statuses of all duplicate strings.|
|No||No action is done.|
If checked Sisulizer writes log an entry for each row it translates using exiting duplicates.
If checked Sisulizer applies the smart duplicate translation that ignores character case and some punctuation marks.
Specifies how to select duplicate strings.
|By Original||All strings that have same original value are treated as duplicate strings.|
|By Original and Context||Only strings that have same context and same original value are treated as duplicate strings.|
If this is defined then only strings that are longer than the given value will be
candidates when translating duplicate string. For example if the value is 2.
Only strings longer than 2 characters will be auto translated.
When Sisulizer translates duplicate strings or translates using translation engines it add certain characters to the translations if original string contains them but the existing translations do not. For example if the project contains two similar rows that differ only by punctuation marks:
Hello World Hello World!
If the project already contains Finnish translation for the first one (Moi maailma) and we translate duplicates Sisulizer add the exclamation character to the translation of the second row
Moi maailma Moi maailma!
If you want to disable adding of these punctuation marks when translating duplicates or using translation engines add the characters that you want to exclude to this field.