LocalyzerQAInvalidLocale: Difference between revisions
Jump to navigation
Jump to search
| (17 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
== Error #2: Invalid Locale== | == Error #2: Invalid Locale== | ||
When LocalyzerQA | When LocalyzerQA shows an Invalid Locale error, it means that the locale set up in the Application does not correspond to a locale in Localyzer (LocalyzerExpress or a Jenkins based system). | ||
For example, let's say that | For example, let's say that | ||
* in LocalyzerExpress, the locale for Portuguese is mapped to ''''por'''', so that a translated file will be in the form resources_por.json (the same goes for other file types like .properties, .resx, etc.). | * in LocalyzerExpress, the locale for Portuguese is mapped to ''''por'''', so that a translated file will be in the form resources_por.json (the same goes for other file types like .properties, .resx, etc.). | ||
* In LocalyzerQA, the only locales available are Portuguese (Portugal), or pt-PT, and Portuguese (Brazil) or pt-BR when setting up the Application. The user picked Portuguese (Portugal), or '''pt-PT''' | * In LocalyzerQA, the only locales available are Portuguese (Portugal), or pt-PT, and Portuguese (Brazil) or pt-BR when setting up the Application. The user picked Portuguese (Portugal), or '''pt-PT''' | ||
The LocalyzerExpress '''por''' locale will not match the LocalyzerQA '''pt-PT'''. Hence this error message. | The LocalyzerExpress '''por''' locale will not match the LocalyzerQA '''pt-PT'''. Hence this error message. | ||
You can see the locales handled by Localyzer on the backend (either LocalyzerExpress or a Jenkins based system) as you click on the error in the PostEdit page. It will list the expected locales, for example: | === Checking the locales match === | ||
* You can see the exact locale code (pt-PT in the example above) in the Review for an Application. | |||
* You can see the locales handled by Localyzer on the backend (either LocalyzerExpress or a Jenkins based system) as you click on the error in the PostEdit page. It will list the expected locales, for example: | |||
Target Locales: de-DE,fr,fr-BE,ja,no,por | Target Locales: de-DE,fr,fr-BE,ja,no,por | ||
Watch out for some locales, as their code are more likely to vary from system to system : | |||
* Norwegian: no/NO, nb/NO, nn/NO ... | |||
* Serbian: sr/BA, sr/ME, sr/RS, sr/Latn/BA, sr/Latn/ME, sr/Latn/RS | |||
* Indonesian: in/ID, id/ID | |||
* Hebrew: iw/IL, he/IL | |||
== Possible Corrective Action == | == Possible Corrective Action == | ||
If possible, change the locale in LocalyzerExpress or Localyzer to be a locale supported by LocalyzerQA, here pt, or pt-PT. | If possible, change the locale in LocalyzerExpress or Localyzer to be a locale supported by LocalyzerQA, here '''pt''', or '''pt-PT'''. | ||
Those are the standard locale as per | Those are the standard locale as per [https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html|Standard Locale ISO Codes]. | ||
This may require a change in the code locale framework. | This may require a change in the code locale framework. | ||
== List of Errors == | == List of Errors == | ||
[[ | * [[LocalyzerQA#Handling_Errors|LocalyzerQA Error List]] | ||
Latest revision as of 18:05, 15 March 2021
Error #2: Invalid Locale
When LocalyzerQA shows an Invalid Locale error, it means that the locale set up in the Application does not correspond to a locale in Localyzer (LocalyzerExpress or a Jenkins based system).
For example, let's say that
- in LocalyzerExpress, the locale for Portuguese is mapped to 'por', so that a translated file will be in the form resources_por.json (the same goes for other file types like .properties, .resx, etc.).
- In LocalyzerQA, the only locales available are Portuguese (Portugal), or pt-PT, and Portuguese (Brazil) or pt-BR when setting up the Application. The user picked Portuguese (Portugal), or pt-PT
The LocalyzerExpress por locale will not match the LocalyzerQA pt-PT. Hence this error message.
Checking the locales match
- You can see the exact locale code (pt-PT in the example above) in the Review for an Application.
- You can see the locales handled by Localyzer on the backend (either LocalyzerExpress or a Jenkins based system) as you click on the error in the PostEdit page. It will list the expected locales, for example:
Target Locales: de-DE,fr,fr-BE,ja,no,por
Watch out for some locales, as their code are more likely to vary from system to system :
- Norwegian: no/NO, nb/NO, nn/NO ...
- Serbian: sr/BA, sr/ME, sr/RS, sr/Latn/BA, sr/Latn/ME, sr/Latn/RS
- Indonesian: in/ID, id/ID
- Hebrew: iw/IL, he/IL
Possible Corrective Action
If possible, change the locale in LocalyzerExpress or Localyzer to be a locale supported by LocalyzerQA, here pt, or pt-PT. Those are the standard locale as per Locale ISO Codes.
This may require a change in the code locale framework.