feat: Add Portuguese (Brazil) language support with complete translations. #726
Conversation
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
Add Portuguese (Brazil) translation file.
magisph
added a commit
to magisph/note-gen
that referenced
this pull request
Oct 31, 2025
🎯 Goal Ensure complete and accurate localization for Portuguese (Brazil) (pt-BR), resolving translation gaps from the initial implementation. ✅ Changes Made * Updated `messages/pt-BR.json` to be fully synchronized with the `en.json` source file. * Translated all missing keys, including critical sections that were previously untranslated (e.g., `settings.audio`, `recording`, `editor`, `footer`, and `article.editor.toolbar`). * Ensured 100% key-for-key parity with the source language file to prevent UI fallbacks. 🔍 Context The initial Portuguese translation (PR codexu#726) was incomplete. This caused the UI to fall back to other languages (like Chinese Traditional) or display raw translation keys for Brazilian users. This PR provides the correct and complete translations to ensure a fully native experience. 🧪 Ready for Testing All translation keys are properly mapped and ready for integration. Thank you for reviewing this contribution! 🚀
codexu
pushed a commit
that referenced
this pull request
Nov 15, 2025
🎯 Goal Ensure complete and accurate localization for Portuguese (Brazil) (pt-BR), resolving translation gaps from the initial implementation. ✅ Changes Made * Updated `messages/pt-BR.json` to be fully synchronized with the `en.json` source file. * Translated all missing keys, including critical sections that were previously untranslated (e.g., `settings.audio`, `recording`, `editor`, `footer`, and `article.editor.toolbar`). * Ensured 100% key-for-key parity with the source language file to prevent UI fallbacks. 🔍 Context The initial Portuguese translation (PR #726) was incomplete. This caused the UI to fall back to other languages (like Chinese Traditional) or display raw translation keys for Brazilian users. This PR provides the correct and complete translations to ensure a fully native experience. 🧪 Ready for Testing All translation keys are properly mapped and ready for integration. Thank you for reviewing this contribution! 🚀
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
🎯 Goal
Add complete and accurate Portuguese (Brazil) language support to NoteGen application.
📋 Description
This PR addresses the issue reported in PR #526, where the Portuguese translation file contained English text instead of proper Portuguese translations.
This submission provides a fully translated Portuguese (Brazil) file with all interface elements correctly translated.
✅ Changes Made
messages/pt-BR.jsonwith complete Portuguese (Brazil) translations🔍 Context
The maintainer (@codexu) correctly identified in PR #526 that the previous submission contained English text. This PR provides the correct, complete Portuguese translations.
🧪 Ready for Testing
All translation keys are properly mapped and ready for integration.
Thank you for reviewing this contribution! 🚀