Update source files after linguistic corrections
Sometimes, source strings require corrections or need to be reviewed by a UX writer, for example, when a new feature is being added to the application. Developers have the choice to overwrite the resource files in their development repository with the corrected files or to define a new set of source strings as the master language. We recommend overwriting the source files with the corrected texts to ensure uniform style and terminology.
Developers can overwrite the source files with the files that contain the corrections. In this case, developers will see the correct terminology and style, which can be helpful when introducing new UI texts and allows them to spot correction mistakes.
When developers upload the next drop of resource files to the Rigi workspace (for details, see the Upload files to the workspace guide), Rigi will detect new and modified texts and update the status of the translated texts accordingly.
Technical implementation
A source string in Rigi stores texts uploaded by developers as well as the master text. During a source text upload, Rigi compares the new text with existing texts and The actions are summarized in the following table.
Developer text | Master text | Effect on the translated text |
|---|---|---|
Changed | Changed | The status will be degraded |
Changed | Same | No change |
Same | Changed | No change |
Same | Same | No change |
Developers can keep the files that contain corrections defined as a separate language and make this new language the main language. Therefore, it will not use the resource files containing the 'raw' source texts.
The update mechanism is the same as in option 1. When the developers upload the next drop of resource files to the Rigi workspace, Rigi will detect the new and modified texts and update the status of the translated texts accordingly.