Closed Bug 1510065 Opened 6 years ago Closed 6 years ago

[mozilla.org]: WNP 64

Categories

(Mozilla Localizations :: Other, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: CocoMo, Assigned: corneliu)

References

Details

Due to PR not ready within the time frame agreed upon, this project will be localized by an agency. Here is the summary of the discussions through email thread and Slack so everyone is on the same page with the necessary actions in order to meet the RelEng schedule.

*Project*: Firefox WNP 64 page
*Languages*: de, es, fr, pl, pt-BR, ru, zh-TW
*Source*: Pages 3-4 https://docs.google.com/document/d/1w_FtATgfnf1TVWnwz5RAfr-S5p-gJ0oME9lXjpVNbsI/edit (Clay had cleaned it up so context is now marked with [brackets])
*Mockup*: https://drive.google.com/drive/folders/1HLeIVWi_7h1LtMkS8eg6xM540tFaILJN
*Deadline*: Thursday (11/29) or Friday (11/30) at the latest.

NOTE: 
- The agency will deliver in Google doc the way the file is received (pages 3-4 content only).
- Webdev will be tasked to copy and paste localized content in the template according to the locales listed above.
- Amy is preparing the PR https://github.com/mozilla/bedrock/pull/6513 but strings will **not** be extracted and made available on Pontoon. 
- L10n communities would not be involved in this project at all.
- Only if time permitted, an in context review on staging will be done by the agency.
- Peiying will share the PR with the agency and explore solutions to deliver localized html file. This is NOT the expected delivery for this project.
Hi Peiying,

Regarding your question about localizing the HTML file directly, not in Google Docs, we could work with HTMLs directly and it's generally preferable, but in this particular case, the condition that the HTML was in did not match the DOCX, i.e. not all translatable text from the DOCX actually exists in the HTML (for example, the entire page 3), and not all text that exists in the HTML and matches the text in DOCX was marked as translatable. Only one paragraph had a L10N tag:

<p>{% trans login='#' %}Have an account? <a href="{{ login }}">Log in</a>{% endtrans %}</p>
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.