Difference between revisions of "LocalyzerQAGlobalReplace"
| Line 1: | Line 1: | ||
An application in LocalyzerExpress is made up of a number of repositories. |
An application in LocalyzerExpress is made up of a number of repositories. |
||
| − | When |
+ | When correcting a translation, you can optionally check Global Replace. As opposed to acting solely on the resource strings identified by the LocalyzerID value, a Global Replace will replace all instance of the 'Current' string for all the repositories of the application to the 'New' string. This change takes place for the review locale. |
If Global Replace is checked, then in addition to the change being made to the specified Localyzer ID, |
If Global Replace is checked, then in addition to the change being made to the specified Localyzer ID, |
||
Revision as of 19:26, 28 April 2022
An application in LocalyzerExpress is made up of a number of repositories.
When correcting a translation, you can optionally check Global Replace. As opposed to acting solely on the resource strings identified by the LocalyzerID value, a Global Replace will replace all instance of the 'Current' string for all the repositories of the application to the 'New' string. This change takes place for the review locale.
If Global Replace is checked, then in addition to the change being made to the specified Localyzer ID, the change will be made throughout the application for the locale. So all of the Localyzer IDs (for the locale) within an application that match Current will be replaced by New.
Note that an application is a list of repository/branches defined within Localyzer-Express, and pointed to by LocalyzerQA.
