Skip to content

Implementation of the Portuguese (Brazil) Language#229

Open
vedned wants to merge 3 commits into
FirestormViewer:masterfrom
vedned:Allef
Open

Implementation of the Portuguese (Brazil) Language#229
vedned wants to merge 3 commits into
FirestormViewer:masterfrom
vedned:Allef

Conversation

@vedned
Copy link
Copy Markdown

@vedned vedned commented May 8, 2026

Overview

This pull request updates and expands the existing Portuguese (pt) localization for Firestorm Viewer using Brazilian Portuguese terminology and phrasing.

Following review feedback and clarification regarding the localization structure used by Second Life and Firestorm, the implementation keeps the existing pt locale instead of introducing a separate pt_BR locale.

The translation work was therefore consolidated directly into the existing /xui/pt/ structure to preserve compatibility with upstream localization handling, future merges, and the language conventions used by the viewer and simulator infrastructure.

Changes Included

Localization Updates

  • updated Portuguese interface translations using Brazilian Portuguese wording
  • expanded translation coverage across viewer interface components
  • localized additional floaters, panels, dialogs, notifications, and menus
  • improved consistency of terminology across the UI

Locale Structure Preservation

  • preserved the existing pt locale structure
  • avoided introducing a separate pt_BR XUI resource tree
  • maintained compatibility with existing upstream localization workflows
  • preserved file history and reduced future merge conflicts with Linden Lab updates

Technical Notes

  • kept the existing /xui/pt/ resource structure
  • maintained the pt language identifier used by the viewer
  • aligned with the current localization conventions used by Second Life and Firestorm

Notes

Although the translation wording is primarily Brazilian Portuguese, the localization continues to use the existing pt locale for compatibility and upstream consistency reasons.

@@ -0,0 +1,9 @@
<?xml version='1.0' encoding='utf-8'?>
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After reviewing several of the translation files like this one, I've noticed that many include unnecessary attributes which make tracking changes and modifications more difficult. To streamline our process, could we please ensure we are following the structure outlined in the Wiki and this JIRA issue? For the best examples of a clean and organized structure, the /de/ and /pl/ folders serve as excellent references for which files require translation.

Copy link
Copy Markdown
Author

@vedned vedned May 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the clarification. I understand the issue now.

I'll review the translation files again and remove the unnecessary attributes to better match the minimal structure used in /de/ and /pl/.

I'll also make the necessary changes as quickly as possible.

Thanks for the guidance.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any updates? ~

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, i have made some progress. i was traveling, but i will be finishing it soon....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants