New Crowdin translations by Github Action#526
New Crowdin translations by Github Action#526github-actions[bot] wants to merge 1 commit intomainfrom
Conversation
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
github-actions
bot
force-pushed
the
l10n_crowdin_action
branch
from
fa831d7 to
8bf31a0
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
github-actions
bot
force-pushed
the
l10n_crowdin_action
branch
11 times, most recently
from
0485788 to
dce42f2
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
github-actions
bot
force-pushed
the
l10n_crowdin_action
branch
14 times, most recently
from
2cdaccc to
9714208
Compare
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
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.
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
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.
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
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.
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
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.
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
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.
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
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".
| @@ -1,5 +1,5 @@ | |||
| { | |||
| "locale": "es_419", | |||
| "locale": "es", | |||
There was a problem hiding this comment.
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.
| @@ -1,5 +1,5 @@ | |||
| { | |||
| "locale": "es_419", | |||
| "locale": "es", | |||
There was a problem hiding this comment.
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.
| @@ -1,5 +1,5 @@ | |||
| { | |||
| "locale": "es_419", | |||
| "locale": "es", | |||
There was a problem hiding this comment.
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.
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
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.
| @@ -1,5 +1,5 @@ | |||
| { | |||
| "locale": "es_419", | |||
| "locale": "es", | |||
There was a problem hiding this comment.
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.
| }, | ||
| "MmssingNonWitnessUtxo": { | ||
| "message": "Transaktion konnte nicht erstellt werden: fehlender Non-Witness UTXO" | ||
| }, |
There was a problem hiding this comment.
Typo in translation key name
Low Severity
The translation key is misspelled as MmssingNonWitnessUtxo (double 'm') instead of MissingNonWitnessUtxo across all newly added locale files. This typo is copied from the source English file but introduces the error into all new translation files, potentially causing lookup failures if the application code uses the correct spelling.
Additional Locations (1)
| }, | ||
| "MmssingNonWitnessUtxo": { | ||
| "message": "Transaktion konnte nicht erstellt werden: fehlender Non-Witness UTXO" | ||
| }, |
There was a problem hiding this comment.
Typo in translation key name across files
Medium Severity
The translation key MmssingNonWitnessUtxo contains a typo with double 'm' instead of MissingNonWitnessUtxo. This misspelled key appears in all newly added locale files. If application code references this error with the correct spelling, the translation lookup fails and users see a missing translation or fallback text instead of the proper error message.
Additional Locations (2)
| "message": "Ζητήθηκε από" | ||
| } | ||
| } | ||
| } |
There was a problem hiding this comment.
New locale files not registered in snap manifest
Medium Severity
Translation files for Greek (el_GR.json), Hindi (hi_IN.json), Indonesian (id_ID.json), Korean (ko_KR.json), and Portuguese-BR (pt_BR.json) are added but not registered in snap.manifest.json. The snap only loads locales explicitly listed in the manifest's source.locales array. Since no base files (e.g., el.json, hi.json) exist either, users with these locales will receive no translations at all.
Additional Locations (2)
| }, | ||
| "send": { | ||
| "message": "Εστάλη" | ||
| }, |
There was a problem hiding this comment.
Greek "send" button label uses wrong tense
Medium Severity
The send key in el_GR.json is translated as "Εστάλη" (Greek past tense passive, meaning "Was Sent"), while the existing base el.json correctly translates it as "Αποστολή" (imperative/noun meaning "Send"). This would cause the Send button to display incorrect text to Greek-speaking users, showing a completed action label instead of an actionable one.
| }, | ||
| "send": { | ||
| "message": "Εστάλη" | ||
| }, |
There was a problem hiding this comment.
Greek "send" translation uses wrong verb tense
Medium Severity
The Greek translation for send is "Εστάλη", which means "was sent" (aorist passive tense). Every other locale correctly uses the imperative or action form for this button label (e.g., "Send", "Enviar", "Envoyer", "Gönder"). Greek users would see a past-tense label on the Send button, which is semantically incorrect and confusing.
| }, | ||
| "send": { | ||
| "message": "Εστάλη" | ||
| }, |
There was a problem hiding this comment.
Greek "send" mistranslated as past tense "Was sent"
Medium Severity
The send key in el_GR.json is translated as "Εστάλη" (past tense: "Was sent"), but the correct imperative translation is "Αποστολή" ("Send"), which is what the existing el.json already uses. This would cause the Send button in the Greek UI to display a past-tense status label instead of an action verb, confusing Greek-speaking users.
| @@ -1,5 +1,5 @@ | |||
| { | |||
| "locale": "es_419", | |||
| "locale": "es", | |||
There was a problem hiding this comment.
Regional locale identifiers are incorrect
Medium Severity
The regional files use mismatched locale values: es_419.json now declares es, and ja_JP.json declares en. If locale resolution or tooling reads the file’s locale field, these bundles can be misidentified, collide with base locales, or be skipped, causing incorrect language fallback for region-specific users.
Additional Locations (1)
| }, | ||
| "send": { | ||
| "message": "Εστάλη" | ||
| }, |
There was a problem hiding this comment.
Greek "send" button mistranslated as past tense
Medium Severity
The Greek translation for the send key is "Εστάλη" which means "was sent" (past tense passive), not "Send" (action/imperative). Every other locale correctly translates this as an action verb for a button label. Curiously, the sending key uses "Αποστολή" which would actually be a more appropriate translation for the send button itself. Greek users will see a confusingly past-tense label on the send action button.
| }, | ||
| "send": { | ||
| "message": "Εστάλη" | ||
| }, |
There was a problem hiding this comment.
Greek send translated as past tense "Was sent"
Medium Severity
The send key in el_GR.json is translated as "Εστάλη" (past tense, "Was sent"), while the base el.json correctly uses "Αποστολή" (the action "Send"). This is a semantic error — a button meant to initiate sending would instead read as a completed-action label, which is confusing for Greek-speaking users.
| }, | ||
| "send": { | ||
| "message": "Εστάλη" | ||
| }, |
There was a problem hiding this comment.
Greek "send" button mistranslated as past tense
Medium Severity
The send key in el_GR.json is translated as "Εστάλη" which means "Was sent" (past tense passive), not "Send" (an action). The base el.json file correctly uses "Αποστολή" for this same key. Every other locale translates this as an imperative/action form (e.g., "Senden", "Envoyer", "Enviar"). A primary action button labeled "Was sent" instead of "Send" will confuse Greek-speaking users in a financial context.
| }, | ||
| "send": { | ||
| "message": "Εστάλη" | ||
| }, |
There was a problem hiding this comment.
Greek "send" button mistranslated as past-tense "sent"
Medium Severity
The send key in el_GR.json is translated as "Εστάλη" which means "was sent" (past tense/passive), while the existing el.json correctly uses "Αποστολή" ("Send"/"Dispatch"). This means Greek users would see a button labeled "Was sent" instead of "Send" — a semantic error on a critical transaction action button that could cause confusion about whether the transaction has already been submitted.
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
Japanese locale file declares wrong locale as "en"
High Severity
The ja_JP.json file has "locale": "en" instead of "locale": "ja". Every other regional locale file uses the correct language code (e.g., de_DE.json → "de", ko_KR.json → "ko"), and the companion ja.json file correctly declares "locale": "ja". This mismatch means the i18n system will treat the Japanese regional file as English, potentially overriding actual English translations or preventing Japanese users from seeing translated content.
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
Japanese locale file has wrong locale identifier
High Severity
The ja_JP.json file sets "locale": "en" instead of "locale": "ja". The companion ja.json file correctly uses "ja". This means the i18n system will treat Japanese translations as English, so Japanese users won't see localized content or—worse—the Japanese strings could override the real English locale.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
Japanese locale file has wrong locale identifier
High Severity
The ja_JP.json file sets "locale": "en" instead of "locale": "ja". This means the i18n framework will treat this Japanese translation file as English, causing it to either not load for Japanese users or override the actual English locale with Japanese strings. The sibling file ja.json correctly uses "locale": "ja".
| }, | ||
| "send": { | ||
| "message": "Εστάλη" | ||
| }, |
There was a problem hiding this comment.
Greek send mistranslated as past tense
Medium Severity
The send key in el_GR.json is translated as "Εστάλη" which means "was sent" (past tense). The existing el.json correctly uses "Αποστολή" ("Send" as an action). This will display incorrect text on the Send button for Greek users.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
Japanese locale file has wrong locale identifier
High Severity
The ja_JP.json file sets "locale": "en" instead of "locale": "ja". Every other regional variant file correctly uses its base language code (e.g., de_DE.json → "de", fr_FR.json → "fr", ko_KR.json → "ko"), and the companion ja.json file correctly uses "ja". This will cause the Japanese regional translations to be misidentified as English, likely preventing Japanese users from seeing localized strings or creating a conflict with the actual English locale files.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
Japanese locale file has wrong locale identifier
High Severity
The ja_JP.json file has "locale": "en" instead of "locale": "ja". This causes the Japanese translation file to identify itself as English, which likely means the localization framework will treat it as an English locale and not apply the Japanese translations for users expecting them. The companion ja.json file correctly uses "locale": "ja".
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
Japanese locale file incorrectly set to "en"
High Severity
The locale field in ja_JP.json is set to "en" instead of "ja". Every other locale file correctly maps to its language code (e.g., de_DE.json → "de", ko_KR.json → "ko"), and the existing ja.json correctly uses "ja". This will cause the i18n system to either treat these Japanese translations as English (potentially conflicting with en.json/en_GB.json) or fail to serve them to Japanese users entirely.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
Japanese locale file has wrong locale identifier
High Severity
The ja_JP.json file has "locale": "en" instead of "locale": "ja". The companion ja.json file correctly uses "ja", and every other regional locale file in this PR uses the correct language code (e.g., de_DE.json → "de", fr_FR.json → "fr", ko_KR.json → "ko"). This will cause the i18n system to treat the Japanese translation file as English, so Japanese users won't see Japanese translations.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
Japanese locale file incorrectly sets locale to English
High Severity
The ja_JP.json file has "locale": "en" instead of "locale": "ja". The companion ja.json file correctly uses "ja". This means the Japanese regional locale file identifies itself as English, which will cause the i18n system to either ignore the Japanese translations or serve English content to Japanese users.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
Japanese locale file has wrong locale identifier
High Severity
The ja_JP.json file has "locale": "en" instead of "locale": "ja". Every other regional locale file correctly matches its language code (e.g., de_DE.json → "de", fr_FR.json → "fr", ko_KR.json → "ko"), and the existing ja.json correctly uses "ja". This will cause the Japanese translation file to be identified as English, so Japanese users will likely see English (or wrong-language) strings instead of the Japanese translations.
2 participants
Note
Low Risk
Low risk localization-only changes; main risk is mismatched locale codes/strings causing certain translations not to load or to fall back to English.
Overview
Adds multiple new
packages/snap/locales/*translation files (e.g.,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) expanding localized UI strings.Updates existing locales to align keys and error messaging:
es_419.jsonswitches itslocaletoes, tweaks themaxlabel punctuation, and addserror.3100;zh_CN.jsonadds the missingerror.*message set (includingerror.3100).Written by Cursor Bugbot for commit 4444175. This will update automatically on new commits. Configure here.