Versioning
Includes functions of the application up to version | 7.2.4 |
| Current translate5 version | 7.3.2 |
translate5 assigns an auto status to each segment when it is saved. After editing by users, the segment status is again adjusted depending on the type of editing action.
Characteristics of processing status symbols
The processing status symbols are composed of the following parts:
| Status | Icon | Explanation |
|---|---|---|
| Pre-translated |
| The segment was automatically pre-translated based on the associated language resource(s). |
| Blocked |
| This symbol is set if the segment was already marked as locked in the imported .xliff file. This setting can be adjusted for .xliff files in the import settings. |
| Locked |
| The segment has been locked by the project manager and can only be unlocked by them. 100% matches are automatically locked if this setting is activated for the import. |
| Translated |
| The segment has been translated, but has not yet been edited by the reviewer. As a rule, all segments have this status at the beginning of a review task. |
| Not translated |
| The segment has neither been translated nor edited by the reviewer. Segments that are (accidentally) untranslated have this status at the beginning of a review task. In translation tasks, the segments initially either have the status “not translated” or “pre-translated”. |
| Translated, auto-set |
| The segment was auto-propagated due to a repetition with another segment. |
| Saved |
| The segment has been saved. |
| Opened |
| The segment was opened but not edited. |
| Edited |
| The segment was edited. |
| Commented |
| The segment was commented on. |
| Automatically changed |
| The segment was changed automatically and/or auto-propagated due to a repetition. |
Processing status symbols — examples
Below, you will find a selection of processing status symbols with the corresponding explanations:
| Processing status | Icon | Explanation |
|---|---|---|
| Reviewed, unchanged |
| The segment was opened and saved without it being edited. |
| Reviewed, unchanged, commented |
| The segment was opened, commented on and saved without it being edited. |
| Reviewed |
| The segment has been edited and saved by the reviewer. |
| Reviewed and commented |
| The segment has been edited, commented on and saved by the reviewer. |
| Reviewed, untouched, auto-set at finish of workflow step |
| The segment has not been opened or changed by the reviewer. All segments that have not yet been opened automatically receive this status as soon as the entire reviewing process has been completed. |
| Reviewed, unchanged, auto-set |
| After confirmation of the option for automatic adaptation of internal repetitions, the segment was saved without changes because the project manager also saved the first segment (i.e. the first occurrence of the segment content in a file) without changes. |
| Reviewed, auto-set |
| After confirmation of the option for automatic adaptation of internal repetitions, the segment was changed as if the reviewer had edited and saved it manually. |
| 2. Review |
| The segment has been edited and saved by the reviewer. |
| 2. Review, auto |
| After confirmation of the option for automatic adaptation of internal repetitions, the segment was changed as if the 2. reviewer edited it manually and saved it. |
| PM reviewed, M-elected, unchanged |
| The segment was opened and saved by the project manager without it being edited. |
| PM reviewed |
| The segment has been edited and saved by the project manager. |
| PM reviewed-elected, unchanged, auto-set |
| After confirmation of option for automatic adaptation of internal repetitions, the segment has been saved without changes, because the project manager has also saved the first segment (i.e. the first occurrence of the segment content in a file) without changes. |
| PM reviewed, auto-set |
| After confirmation of the option for automatic adaptation of internal repetitions, the segment was changed as if the project manager had edited and saved it manually. |
