Repository navigation
fix(i18n): complete pt-BR strings and localize relative dates - #1213
felipemontenegro91 wants to merge 3 commits into
Conversation
The English text for settings.gpu.switchToCpu.description changed from "You can re-download CUDA later" to "You can re-download the GPU backend later" when ROCm support landed, but the Brazilian Portuguese string still mentioned CUDA. Translate the current source text. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
getDateLocale() had no case for pt-BR, so relative timestamps in history,
captures and MCP bindings stayed in English ("5 minutes ago") while the rest
of the interface was in Portuguese. Map pt-BR to date-fns ptBR, following the
existing es/fr/ja/zh pattern.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
I tested pt-BR as a backport on the v0.5.0 release. The branch is
Three strings whose English source differs between v0.5.0 and Results on v0.5.0 (macOS 27.2, Apple Silicon). I built the desktop shell from that branch and ran it with the official v0.5.0
What this doesn't cover. The 17 new strings and the Remaining English. What's still in English in the pt-BR UI is hard-coded in components, not missing from the locale file, on both v0.5.0 and
I'm happy to send a separate PR moving these into i18n if that's welcome. Prepared with AI assistance. |
Brazilian Portuguese still falls back to English in a few places. This PR fixes three of them.
1. Missing strings (17 entries). These cover:
All 847 existing strings are preserved. The 18 missing GPU/ROCm entries are intentionally excluded because #919 already proposes them. Interpolation variables, product names, the sample endpoint URL and the English OmniVoice examples required by its fixed vocabulary are kept as they are.
2. Stale GPU string.
settings.gpu.switchToCpu.descriptionstill said "you can re-download CUDA later". The English source changed to "re-download the GPU backend later" when ROCm support landed, and the Portuguese now translates the current text. No open PR touches this key.3. Relative dates.
getDateLocale()inapp/src/lib/utils/format.tshad nopt-BRcase. Timestamps in history, captures and MCP bindings stayed in English ("5 minutes ago") while the rest of the UI was in Portuguese. The fix mapspt-BRto date-fnsptBR, following the existinges/fr/ja/zhpattern.With the fix, the output changes like this:
5 minutes agohá 5 minutos2 hours agohá cerca de 2 horasvisto pela última vez 5 minutes agovisto pela última vez há 5 minutoskoandithave the same gap; I left them out to keep this PR scoped to pt-BR. No open PR mapsptBRinformat.ts. #599 addsruthe same way, which may cause a trivial import-line conflict.Validation on
main(8af7efe + this branch)git diff --checkpass.tsc --noEmitpasses forappandweb, and thewebproduction build passes.en. The only 18 remaining gaps match the GPU strings proposed in fix(i18n): add Cloud login translations for es, it, ko #919.pt-BRwithout fallback.ptBRdirectly, which is where the table above comes from.main.CHANGELOG.mdis intentionally unchanged, because its header marks it as generated and says not to edit it manually. Suggested release note: "Translate custom LLM settings, remote-refinement notices, OmniVoice guidance and the About label into Brazilian Portuguese; localize relative dates for pt-BR."Prepared with AI assistance. Maintainers are welcome to request terminology adjustments.
🤖 Generated with Claude Code