Difference between revisions of "LocalyzerQAGlobalReplace"
| Line 1: | Line 1: | ||
| − | An application in |
+ | An application in <code>Localyzer Express</code> 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 string identified by the <code>LocalyzerID</code> value, a ''Global Replace'' will replace all instances of the ''Current'' string to the ''New'' string. This change takes place for the review locale for all the repositories of the application. |
When correcting a translation, you can optionally check ''Global Replace''. As opposed to acting solely on the resource string identified by the <code>LocalyzerID</code> value, a ''Global Replace'' will replace all instances of the ''Current'' string to the ''New'' string. This change takes place for the review locale for all the repositories of the application. |
||
| − | Note that an application is a list of repository/branches defined within <code> |
+ | Note that an application is a list of repository/branches defined within <code>Localyzer Express</code>, and pointed to by <code>LocalyzerQA</code>. |
Revision as of 19:31, 28 April 2022
An application in Localyzer Express 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 string identified by the LocalyzerID value, a Global Replace will replace all instances of the Current string to the New string. This change takes place for the review locale for all the repositories of the application.
Note that an application is a list of repository/branches defined within Localyzer Express, and pointed to by LocalyzerQA.
