[mozilla.org]: Switch to Fluent has completed

10 views
Skip to first unread message

Peiying Mo

unread,
May 22, 2020, 11:57:57 AM5/22/20
to localization, Mozilla
*tl;dr:*

- Switch to Fluent has completed.
- Review of migrated files should start as soon as possible; start with
*brands.ftl*, follow brand and trademark guidelines
<https://mozilla-l10n.github.io/styleguides/mozilla_general/index.html#brands-copyright-and-trademark>
.
- File bugs to report issues.

-----------
Hello Localizer,

We just made the switch a few hours ago, thanks to Matjaž and Axel! Please
go ahead and check out your mozilla.org project dashboard on Pontoon. You
will notice a significantly smaller set of files.

I would like to share a few more things as we are at the beginning of this
transition.

*What are the remaining milestones?*

- 22 - 26 May: Communities review migrated files, update if necessary;
New and updated localized content is pushed to production daily; testing
the new flow. Troubleshoot issues if any surface.
- 26 May - 19 June: more content to localize in the new format,
including WNP78. More migrations from .lang to .ftl.
- 19 June: Localized WNP78 ready for release

*What are areas of my immediate focus after the migration?*

*Go over brands.ftl:* This new file captures all the brand and product
names that appear in all the pages on mozilla.org as of now. As a general
rule, brands and product names remain unchanged. The exceptions are:

- Account/Accounts in Firefox Account/Accounts
- Sync in Firefox Sync
- Browser in Firefox Browser

If your community decides to translate any of these products or feature
names, translate it once and translate it in this file. Be sure to have a
consensus among active contributors what the translation should be before
updating this file. This practice will ensure term use consistency across
all pages.

Please refer to the guidelines for brands and trademark
<https://mozilla-l10n.github.io/styleguides/mozilla_general/index.html#brands-copyright-and-trademark>
when reviewing and updating the brands.ftl.

*Then go over the rest of the files* that are available on the dashboard.
This list will grow over time as the mozilla.org team continues migrating
from .lang to Fluent. Keep track of what is reviewed and what is pending
for a review. Here are a few things to check:

- On the project dashboard, if there is orange color in the status
progress bar, click on the file. Check the strings with the orange
color indicator first. If the localized string is absent of a variable,
chances are, the product or brand name is translated, transliterated or
declensed. Insert the variable to replace the
translated/transliterated/declensed term.
- Do not translate words in a variable.
- If there is enough bandwidth within a team, work in pairs, one updates
the string as a suggestion, another reviews and approves it.
- Review your changes on production, especially those with brand and
product names.

*How to report technical issues?*

- Report issues that can’t be resolved in Pontoon by
- Filing a bug in Buzilla and file under your locale.
- Adding my name for NI.
- Including the file name plus a screenshot and/or URL

*When can I see the localized page on production?*

Updated translations are pushed to the production server regularly
throughout the day.

- Pontoon syncs every 20 minutes to the repository.
- GitHub update is pushed to production every 5 minutes.

There are a few changes in the way a localized page is activated:

- When a brand new page is available for localization, it won’t be
enabled on production until it’s at least 80% complete. This means, after
it reaches the threshold, the page will be on production in English and
target language.
- When an activated page gets an update with new strings, these new
strings may or may not have fallback strings. For a page that is completely
translated, depending on the rule set for the page, the change may appear
once the updated strings are fully localized. Otherwise, the update will be
in English.
- An activated page falling far behind from multiple updates for an
extended period of time will create bad user experience with mixed
languages. The page will risk being disabled but deactivation will be done
manually.
- In some cases, pages with major updates require a complete rewrite of
the template. If this happens, the old template is kept on production only
for a defined period of time. When removed, it will cause the URL to
redirect users to the English version if the intended localized page is not
ready.

Have a wonderful weekend!
Peiying
Reply all
Reply to author
Forward
0 new messages