feat(i18n): add Brazilian Portuguese (pt-BR) translation and refine pt#1427
Open
mzspicoli wants to merge 1 commit into
Open
feat(i18n): add Brazilian Portuguese (pt-BR) translation and refine pt#1427mzspicoli wants to merge 1 commit into
mzspicoli wants to merge 1 commit into
Conversation
mzspicoli
force-pushed
the
fix/i18n-pt-br-alias
branch
from
4658352 to
983216e
Compare
mzspicoli
changed the title
The strings merged in nielsfaber#1422 under language code `pt` were closer to Brazilian Portuguese than European Portuguese (e.g. `usuário`, `gerenciar`, `monitoradas`, `curinga`, `excluir`, `seu` without article). This commit: - Renames the existing translation to `pt-BR.json` (keeps the strings as authored). - Rewrites `pt.json` in European Portuguese: `utilizador`, `gerir/gestão`, `monitorizadas/monitoriza`, `marcador`, `eliminar`, `o seu`, `num`, `fumo/fuga`, removed `você`, "tem a certeza que pretende...", etc. - Registers `pt-BR` in `localize.ts` so users with profile language `pt-BR` get the dedicated translation (replacing the alias from the previous version of this PR).
mzspicoli
force-pushed
the
fix/i18n-pt-br-alias
branch
from
983216e to
ce4547f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #1422.
On a closer review, the strings I submitted in #1422 under language code
ptare actually closer to Brazilian Portuguese than European Portuguese (terms likeusuário,gerenciar,monitoradas,curinga,excluir, plus thevocêform and missing definite articles before possessives). I'm a native Brazilian Portuguese speaker, so the strings I originally wrote naturally came out in pt-BR — they were just mislabeled aspt. Sorry for the confusion.This PR splits the two variants correctly.
Changes
pt-BR.json(new) — the strings as merged in feat(i18n): add Portuguese (pt) frontend translation #1422 are moved here verbatim under their correct language code. Authored and reviewed by me as a native pt-BR speaker.pt.json(rewritten as European Portuguese) — generated by applying common pt-BR → pt-PT lexical substitutions:usuário/usuários→utilizador/utilizadoresgerenciar→gerir,gerenciamento→gestãomonitoradas/monitora→monitorizadas/monitorizacuringa→marcadorexcluir automação→eliminar automaçãofumaça→fumo,vazamento→fugavocê; added definite articles before possessives (seu→o seu)tem certeza que deseja→tem a certeza que pretendeem um grupo/item→num grupo/itemlocalize.ts— registerspt-BRas a dedicated language entry (replacing the alias from the earlier version of this PR).Result
pt): uses the new pt-PT translation (mechanical adaptation, pending native review).pt-BR): uses the original strings from feat(i18n): add Portuguese (pt) frontend translation #1422 (now correctly labeled).