Skip to content

Completed translations for pt-PT locate + minor fix in en-US#1145

Merged
amyjko merged 15 commits into
wordplaydev:mainfrom
ETBRamos:main
Jun 4, 2026
Merged

Completed translations for pt-PT locate + minor fix in en-US#1145
amyjko merged 15 commits into
wordplaydev:mainfrom
ETBRamos:main

Conversation

@ETBRamos
Copy link
Copy Markdown
Contributor

Context

Completed portuguese-portugal translations in both tutorial (pt-PT-tutorial.json) and base (pt-PT.json) translation files

Portuguese locale added to SupportedLocales.ts

Minor bugfix line 2359 of en-us.json where "last" object documentation referred to .first() instead.

Fixed formatting issues caused by machine translation within translation text (largely missing spaces, special characters).

Verification

Line-by-line verification of translations, consultation with Portuguese dictionary (priberam.org; utilized by university of lisbon), for verification of vocabulary suitable for the locale.

Selecting established vocabulary for programming concepts by referencing existing translated documentation for programming languages

Verification that the tone and vocabulary used match the context, particularly for shorter translations where words with multiple meanings are frequently mistranslated in context.

…t-PT.json) translation file

Portuguese locale added to SupportedLocales.ts

Minor bugfix line 2359 of en-us.json where "last" object documentation referred to .first() instead.

'$~' removed from edited translations.
Copy link
Copy Markdown
Collaborator

@amyjko amyjko left a comment

Choose a reason for hiding this comment

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

Wonderful, thank you so much for this comprehensive review!

While you were working on it, we changed the template syntax to use named parameters (e.g., $first, $second) instead of numbered parameters (e.g., $1, `$2). That led to some conflicts. Can you review the conflicts and make sure that the named parameters end up in the right place in the text? It should be relatively quick scan to verify.

After the conflicts are resolved, I think this is ready to ship.

@ETBRamos
Copy link
Copy Markdown
Contributor Author

Sounds good, I've reviewed the conflicts and integrated my translation fixes where needed to reflect my previous changes with the new syntax, and reviewed the new additional lines in the file.

Copy link
Copy Markdown
Collaborator

@amyjko amyjko left a comment

Choose a reason for hiding this comment

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

One last question here: many strings still start with $~, meaning they are still annotated as machine translated. Or those strings you didn't review, or did you review them and those annotations should be removed? (If you reviewed everything, we should remove all of them, except for the newest strings that I just added to this PR). You could do a simple search and replace if they're all reviewed.

@ETBRamos
Copy link
Copy Markdown
Contributor Author

ETBRamos commented Jun 3, 2026

I did review everything, will do!

@ETBRamos
Copy link
Copy Markdown
Contributor Author

ETBRamos commented Jun 3, 2026

Alright, I removed the $~ and resolved the new merge conflicts, reviewing the new lines.

Copy link
Copy Markdown
Collaborator

@amyjko amyjko left a comment

Choose a reason for hiding this comment

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

Looks good to go! I will merge and get it live. Thank you so much for the thorough contribution!

@amyjko amyjko merged commit de0b1e4 into wordplaydev:main Jun 4, 2026
2 checks passed
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.

3 participants