Skip to content

feat: add Brazilian Portuguese localization - #300

Merged
vinzdg merged 2 commits into
vinzdg:mainfrom
dinicleyaguiar:feat/pt-br-localization
Sep 22, 2026
Merged

vinzdg merged 2 commits into
vinzdg:mainfrom
dinicleyaguiar:feat/pt-br-localization

Conversation

@dinicleyaguiar

Copy link
Copy Markdown
Contributor

Summary

Adds Brazilian Portuguese (pt-BR) localization to the Windows version of Codenotch.

Changes

  • detects pt-BR from the Windows locale when using Follow system
  • adds Brazilian Portuguese tray menu strings
  • translates usage windows, reset text, stale-reading text, and provider labels
  • adds Brazilian Portuguese hover-card copy and dynamic patterns
  • adds Brazilian Portuguese settings UI and status text
  • adds localization tests for pt-BR
  • keeps pt-PT separate instead of mapping all Portuguese locales to Brazilian Portuguese

Validation

  • cargo test passes locally on Windows
  • existing localization tests remain passing
  • Brazilian Portuguese locale and tray-menu tests are included

Notes

This change is scoped to the Windows localization system and follows the existing language-table structure.

@dinicleyaguiar

Copy link
Copy Markdown
Contributor Author

I noticed #295 after opening this PR, so I want to avoid duplicating effort.

I reviewed the maintainer feedback there and updated this branch accordingly:

  • uses pt-BR to match the macOS catalog;
  • covers all tray menu strings in i18n.rs;
  • adds the missing raymenu.rs localization;
  • includes the Claude sign-in strings in the usage card;
  • aligns shared Brazilian Portuguese wording with Sources/Localizable.xcstrings;
  • keeps pt-PT separate from Brazilian Portuguese.

All Rust tests and the Windows UI script checks pass locally.

If you would prefer to continue with #295 instead, I am happy to close this one. Otherwise, this PR should now cover the remaining Windows pt-BR gaps mentioned there.

@vinzdg
vinzdg merged commit d9e9bc1 into vinzdg:main Sep 22, 2026
vinzdg added a commit that referenced this pull request Sep 22, 2026
Resolving the notch.html conflict by keeping both sides dropped the closing
brace of TEXT.ko and the closing bracket of PATTERNS.ko, so the pt-BR tables
were nested inside the Korean ones and the page did not parse. A page that
does not parse opens empty with nothing in the log, which is what
check-ui-scripts.mjs exists to catch — and did.

Verified structurally as well as syntactically: TEXT, PATTERNS and UI each
carry ko and pt-BR with their own key counts.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants