Skip to content

Conversation

@akatsoulas
Copy link
Collaborator

No description provided.

Copy link
Contributor

@escattone escattone left a comment

Choose a reason for hiding this comment

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

This seems like an improvement on the existing prior-translation-wiki-map, but I don't think it will affect the UI elements, which are covered by the menu, button, and pref tags. I think we'd have to include those tags in the prior-translation-wiki-map in order to improve the handling of the UI elements.

@akatsoulas
Copy link
Collaborator Author

No objections on this. Shall we do this iteratively and merge this improvement?

Copy link
Contributor

@escattone escattone left a comment

Choose a reason for hiding this comment

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

r+wc

- A Python `dict` maps keys to their values.
- Each `wiki-hook`, `wiki-article-link`, and `wiki-external-link` in the {{ source_language }} text of the "prior translation" becomes a key in the `prior-translation-wiki-map`, and each key's value is its corresponding translation found in the {{ target_language }} text of the "prior translation".
- **IMPORTANT**: Extract **ALL** `wiki-hook`, `wiki-article-link`, and `wiki-external-link` elements from the **ENTIRE** {{ source_language }} text of the "prior translation". Each element becomes a key in the `prior-translation-wiki-map`, and each key's value is its corresponding translation found in the {{ target_language }} text of the "prior translation".
- This map preserves human-localized wiki elements, which **must be reused** whenever those elements appear anywhere in your translation, regardless of whether they appear in changed or unchanged sections.
Copy link
Contributor

Choose a reason for hiding this comment

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

I would use "This `prior-translation-wiki-map` ..." instead of "This map ..." just to be crystal clear.

4. For each part that is different, **freshly translate** that part. **Remember to obey the `Rules for translating special strings`**.
4. For each part that is different, **freshly translate** that part:
- **Remember to obey ALL of the `Rules for translating special strings`**.
- **CRITICAL**: Even in different/changed parts, you **MUST** check the `prior-translation-wiki-map` for every wiki element (per Rule #3) before translating. This ensures already-localized UI elements are preserved.
Copy link
Contributor

Choose a reason for hiding this comment

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

I would use wiki elements instead of UI elements.

@akatsoulas akatsoulas merged commit 1447cc7 into mozilla:main Nov 17, 2025
2 checks passed
@akatsoulas akatsoulas deleted the update-l10n-prompt branch November 17, 2025 16:51
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