New Crowdin translations by Github Action #526
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
github-actions
bot
force-pushed
the
l10n_crowdin_action
branch
4 times, most recently
from
5a6e0f5 to
08378df
Compare
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
Bug: Japanese locale file incorrectly identifies as English
The locale field in ja_JP.json is set to "en" instead of "ja". This causes the Japanese translation file to incorrectly identify itself as English, which could result in the localization system not properly serving Japanese translations to Japanese-speaking users. Comparing with the existing ja.json file confirms it correctly uses "locale": "ja".
github-actions
bot
force-pushed
the
l10n_crowdin_action
branch
from
08378df to
3b9c136
Compare
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
Bug: Japanese locale file declares wrong locale identifier
The ja_JP.json file contains Japanese translations but declares "locale": "en" instead of "locale": "ja". All other locale files in this PR correctly set their locale identifier to match their language (e.g., de_DE.json uses "de", fr_FR.json uses "fr"), and the existing ja.json correctly uses "ja". This mismatch could cause the application to incorrectly identify or select this locale.
github-actions
bot
force-pushed
the
l10n_crowdin_action
branch
from
3b9c136 to
411780f
Compare
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
Bug: Japanese locale file has wrong locale identifier
The Japanese locale file ja_JP.json has "locale": "en" but the file contains Japanese translations. The locale identifier should be "ja" to match the file's purpose and content. This mismatch could cause the application's localization system to incorrectly identify this as an English locale, preventing Japanese translations from being applied correctly for Japanese users.
github-actions
bot
force-pushed
the
l10n_crowdin_action
branch
2 times, most recently
from
276bf1b to
7573ae8
Compare
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
Bug: Japanese locale file has wrong locale identifier
The locale value in ja_JP.json is set to "en" instead of "ja". The file contains Japanese translations but identifies itself as English. This mismatch will cause the localization system to treat this file as English rather than Japanese, potentially breaking language selection for Japanese users. The existing ja.json file correctly uses "locale": "ja".
github-actions
bot
force-pushed
the
l10n_crowdin_action
branch
from
7573ae8 to
7799226
Compare
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
Bug: Japanese locale file incorrectly marked as English
The locale field in packages/snap/locales/ja_JP.json is set to "en", but the file contains Japanese translations. This mismatch can cause the application to misidentify the language, potentially breaking locale detection and translation processing.
github-actions
bot
force-pushed
the
l10n_crowdin_action
branch
from
7799226 to
a8e42dc
Compare
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
Bug: Japanese locale file has incorrect locale identifier
The ja_JP.json file's locale field is set to "en" instead of "ja". This mismatch could lead to incorrect locale resolution or displaying the wrong language.
github-actions
bot
force-pushed
the
l10n_crowdin_action
branch
from
a8e42dc to
f4e620a
Compare
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
Bug: Japanese locale file has wrong locale identifier
The ja_JP.json locale file sets "locale": "en" but contains Japanese translations. This mismatch may cause the localization system to misidentify the file's language, potentially leading to incorrect translations or unexpected English fallbacks for Japanese users.
github-actions
bot
force-pushed
the
l10n_crowdin_action
branch
2 times, most recently
from
2efe1b9 to
ffa67ba
Compare
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
Bug: Japanese locale file has wrong locale identifier
The Japanese locale file ja_JP.json has "locale": "en" instead of "locale": "ja". This causes the localization system to incorrectly identify this file as English rather than Japanese, which means Japanese translations may not be applied properly for Japanese users despite the file containing Japanese text.
github-actions
bot
force-pushed
the
l10n_crowdin_action
branch
from
ffa67ba to
3bf2c39
Compare
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
Bug: Japanese locale file has incorrect locale identifier
The Japanese locale file ja_JP.json has "locale": "en" instead of "locale": "ja". This will cause the localization system to treat this file as English rather than Japanese, potentially serving incorrect language content to Japanese users or causing locale matching failures.
github-actions
bot
force-pushed
the
l10n_crowdin_action
branch
from
3bf2c39 to
873391b
Compare
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
Bug: Japanese locale file has incorrect locale identifier
The ja_JP.json file contains Japanese translations but has "locale": "en" instead of "locale": "ja". This mismatch means the locale system may incorrectly identify this file as English content, causing Japanese users to potentially receive incorrect locale handling. Other Japanese locale files like ja.json correctly use "locale": "ja".
github-actions
bot
force-pushed
the
l10n_crowdin_action
branch
from
873391b to
f0204a4
Compare
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
Bug: Japanese locale file has wrong locale identifier
The ja_JP.json locale file has "locale": "en" but contains Japanese translations. This could cause the localization system to incorrectly identify this file as English content, or fail to properly load Japanese translations when users select Japanese as their language. The locale field value should be "ja" to match the file's contents and the pattern used by other locale files like ja.json.
github-actions
bot
force-pushed
the
l10n_crowdin_action
branch
from
f0204a4 to
cb2ebcc
Compare
| @@ -0,0 +1,218 @@ | |||
| { | |||
| "locale": "en", | |||
There was a problem hiding this comment.
Bug: Japanese locale file incorrectly set to English
The locale field in ja_JP.json is set to "en" but the file contains Japanese translations. This causes a mismatch where the application may fail to correctly identify this as a Japanese locale file, potentially breaking locale detection for Japanese (Japan) users and causing unexpected fallback behavior. The value needs to be "ja" to match other locale files' patterns.
Note
Adds multiple new locale files and updates existing translations (including error codes and minor text fixes).
de_DE.json,el_GR.json,en_GB.json,fr_FR.json,hi_IN.json,id_ID.json,ja_JP.json,ko_KR.json,pt_BR.json,ru_RU.json,tl_PH.json,tr_TR.json,vi_VN.json.es_419.json: setlocaletoes, fix"max"to"Máx.", adderror.3100message.zh_CN.json: add missing error codes (error.0,error.1000…error.9000), retain existing messages.Written by Cursor Bugbot for commit cb2ebcc. This will update automatically on new commits. Configure here.