New Crowdin translations by Github Action

[github-actions]

Note

Expands localization coverage for the snap UI and errors.

• Adds new locale files: de_DE, el_GR, en_GB, fr_FR, hi_IN, id_ID, ja_JP, ko_KR, pt_BR, ru_RU, tl_PH, tr_TR, vi_VN
• Updates es_419.json → es locale and minor string adjustments (e.g., "Máx."); adds error.3100
• Extends zh_CN with additional error code messages (error.*)

^{Written by Cursor Bugbot for commit 29bb9ee. This will update automatically on new commits. Configure here.}

[cursor]

Japanese locale file incorrectly identified as English

The ja_JP.json locale file has "locale": "en" instead of "locale": "ja". This causes the Japanese translations to be misidentified as English, which will likely break localization for Japanese users since the internationalization system will treat Japanese content as English content.

 

[cursor]

Japanese locale file declares wrong locale value

The ja_JP.json file contains Japanese translations but incorrectly sets "locale": "en" instead of "locale": "ja". This mismatch between the locale identifier and the actual translation content could cause the application to incorrectly identify or use this locale file, potentially resulting in Japanese users seeing unexpected behavior or the locale not being properly recognized.

 

[cursor]

Japanese locale file has wrong locale identifier

The Japanese locale file ja_JP.json sets "locale": "en" but contains Japanese translations. This causes the system to incorrectly identify this file as English instead of Japanese, preventing Japanese users from seeing the correct translations when using the ja_JP locale variant. The value should be "ja" to match other Japanese locale files.

 

[cursor]

Japanese locale file incorrectly identifies as English

The ja_JP.json translation file has its locale value set to "en" instead of "ja", despite containing Japanese translations. The existing ja.json correctly uses "locale": "ja". This mismatch will cause the localization system to incorrectly identify this file as English, meaning Japanese users would not see these translations.

 

[cursor]

Japanese locale file has wrong locale identifier

The ja_JP.json file contains Japanese translations but has "locale": "en" instead of "locale": "ja". This mismatch between the locale identifier and the actual content (Japanese messages) could cause the application to incorrectly identify this file's language or fail locale-matching logic. The existing ja.json file correctly uses "locale": "ja", so this appears to be an error in the Crowdin translation automation.

 

[cursor]

Japanese locale file has wrong locale identifier

The Japanese translation file ja_JP.json has "locale": "en" instead of "locale": "ja". This mismatch means the localization system will likely identify this file as English rather than Japanese, causing Japanese users to not see the Japanese translations despite the file containing properly translated Japanese text.

 

[cursor]

Japanese locale file incorrectly specifies English locale

Medium Severity

The ja_JP.json file has "locale": "en" but contains Japanese translations. The existing ja.json file correctly uses "locale": "ja". This mismatch could cause the localization system to treat Japanese translations as English, potentially resulting in Japanese users not seeing the correct localized content or causing locale resolution issues.

 

[cursor]

Japanese locale file incorrectly identifies as English

Medium Severity

The ja_JP.json file contains Japanese translations but declares "locale": "en" instead of "locale": "ja". This mismatch causes the Japanese locale file to be incorrectly identified as English, which will break localization for Japanese users. The existing ja.json file correctly uses "locale": "ja".

 

[cursor]

Duplicate locale identifier after Spanish locale change

Medium Severity

The locale value in es_419.json was changed from "es_419" to "es", but es.json already uses "locale": "es". This creates duplicate locale identifiers where two different files both declare themselves as the es locale. This could cause locale resolution conflicts, where the localization system may unpredictably choose between the two files for Spanish speakers, potentially serving the wrong regional variant.

 

[cursor]

Duplicate locale identifier after changing es_419 to es

Medium Severity

The locale identifier in es_419.json was changed from "es_419" to "es", but a separate es.json file already exists with "locale": "es". This creates duplicate locale identifiers, which could cause the localization system to incorrectly select between generic Spanish and Latin American Spanish (the 419 in the filename refers to the UN M.49 code for Latin America). Additionally, the filename es_419.json now mismatches its internal locale value.

 

[cursor]

Latin American Spanish locale identifier incorrectly changed

Low Severity

The locale field in es_419.json was changed from "es_419" to "es", removing the Latin American Spanish regional specificity. This creates an inconsistency since pt_BR.json in the same PR correctly preserves its regional identifier as "pt-BR". If the application uses the locale field to distinguish between Spanish regional variants (e.g., Latin American vs. European Spanish), this change could cause incorrect locale resolution for Latin American Spanish users.

🔬 Verification Test

Why verification test was not possible: This is a data/configuration change in a JSON locale file. The bug is evident from direct inspection of the diff - the locale value was explicitly changed from "es_419" (the IETF language tag for Latin American Spanish) to "es" (generic Spanish), which removes regional specificity that may be needed for proper locale matching.

 

[cursor]

Japanese locale file has wrong locale identifier

High Severity

The ja_JP.json locale file has "locale": "en" instead of "locale": "ja". This causes the Japanese locale to incorrectly identify itself as English. The existing ja.json file correctly uses "locale": "ja". This mismatch could cause the localization system to fail to recognize the file as Japanese, resulting in Japanese users seeing incorrect language content or fallback behavior.

 

[cursor]

Duplicate locale identifier for Spanish locale files

Medium Severity

The es_419.json file had its locale field changed from "es_419" to "es". However, es.json already uses "locale": "es". This creates duplicate locale identifiers, which could cause the localization system to use the wrong file or exhibit undefined behavior when resolving Spanish translations. Latin American Spanish users may not receive the correct regional translations.