Are you a locale leader and want us to include new members in our upcoming reports? Contact us!<\/a><\/p>\n Upcoming deadlines:<\/p>\n As anticipated in the last report, this release cycle is longer than usual<\/b> (6 weeks instead of 4), to accommodate for the end of year holidays in Europe and the US.<\/p>\n The number of new strings remains pretty low, but expect this to change during the first half of 2021, when we should have new content, thanks to a mix of new features and old interfaces revisited. There will also be changes to improve consistency around the use of Title Case<\/i> and Sentence case<\/i> for English. This won\u2019t result in new strings to translate for other locales, but it\u2019s a good reminder that each locale should set and follow its own rules, and they should be documented in style guides<\/a>.<\/p>\n Since we\u2019re at the end of year, here are a few numbers for Firefox:<\/p>\n [1] Disclaimer: other browsers make it quite difficult to understand which languages are effectively supported (there\u2019s no way to switch language, and they don\u2019t necessarily work in the open). Other vendors seem to also have a low entry barrier when it comes to adding a new language, and listing it as available. On the other hand, at Mozilla we require high priority parts to be completely translated, or very close, and a sustainable community before shipping.<\/p>\n <\/p>\n In many regards, you can surely say about 2020 \u201cWhat a year…\u201d – and that also applies to mobile at Mozilla.<\/p>\n We shipped products, dropped some\u2026 Let\u2019s take a closer look at what\u2019s happened over the year.<\/p>\n In 2020, we shipped the all new Firefox for Android browser (\u201cFenix\u201d) in 94 languages<\/a>, which is a great accomplishment. Thank you again to all the localizers who have contributed to this project and its global launch. Your work has ensured that Firefox for Android remains a successful product around the world. We are humbled and grateful for that.<\/p>\n As for the latest release that comes out in December, we will be able to try out a few new features, such as a tab grid view and the ability to delete downloads.<\/p>\n 2020 also brought improvements and cool new features to Firefox for iOS – especially since the iOS update to version 14. To only list a few:<\/p>\n But 2020 has also been a year when we have had to drop some mobile projects, such as Scryer, Firefox Lite and Firefox for Fire TV. We thank you all for the hard work on these products.<\/p>\n Firefox Reality should be available until at least 2021, but not much l10n work is to be expected. We are still figuring things out in regards to Lockwise, we will keep you posted once we know more.<\/p>\n We are looking forwards to 2021 to continue shipping great localized mobile projects. Thank you all for your ongoing work and support!<\/p>\n This year, mozilla.org saw the long awaited migration from .lang to .ftl format. The change gives localizers greater flexibility to localize the site in their language more naturally, and the localized content is pushed to production from once a day manually to a few times in an hour automatically. The new file structure ensures consistency usage in brands and product names across the site. The threshold to activate a locale has lowered, with the hope that it would attract more localizers to participate.<\/p>\n In the past seven months or so, 90+ files have been migrated, added and updated to the new format, and more are still in the work. New pages would be more content heavy and more informational.<\/p>\n Another major change is, instead of creating a new What\u2019s New Page (or WNP) with every Firefox release, the team has decided to promote the evergreen WNP page<\/a> with stable content for an extended period of time. If Firefox desktop is offered in your locale, please make sure this page is fully localized.<\/p>\n The mozilla.org team would like to take the opportunity to express their deep gratitude to all of our community localizers, all over the world. Your work is critical to Mozilla’s global impact and essential for making Mozilla’s products available to the widest possible audience. 61% of 2020 visits were in locales served primarily by community localizers. In those locales, non-Firefox visits to our website grew by 10% this year and downloads increased by 13%! Mozilla’s audience is all over the world, and we couldn’t reach it without you, the localizers who bring www.mozilla.org to your communities. Thank you!<\/p>\n This year, a limited payment feature was added to a few select markets. Next year, the payment feature will be expanded to support PayPal and in more European regions. The team is working on the details and we will learn more soon.<\/p>\n Despite a challenging year, the project saw a significant growth in dataset collection in the past six months: an additional 2,000 hours added, 6 more languages (Hindi, Lithuanian, Luganda, Thai, Finnish, Hungarian) , and over 7 million clips total! Check out which languages have the most hours on Discourse<\/a>.<\/p>\n Given the year 2020 has turned out to be, you may not recall that Mozilla’s strategy for Project WebThings this year was to successfully establish it as an independent, community-led open source project.\u00a0 The important work needed to complete that transition took place in November and December.\u00a0 Through the efforts of community members the project streamlined its name to just “WebThings”, established a new home at webthings.io<\/a>, relocated all the project’s code and assets on GitHub<\/a>, created a new set of backend services to support and maintain the global network of users’ WebThings Gateways, and provided a simple path for transitioning Gateways to the new community infrastructure through the release of WebThings Gateway 1.0.\u00a0 Though a lot changed, Pontoon continues to be our platform for localization and the WebThings team has been continually delighted by the contributions there<\/a>, with teams supporting thirty-four languages.\u00a0 You’ll still find WebThings discussion on Discourse<\/a>, including several more detailed announcements about the community’s newfound independence and plans for 2021.<\/p>\n Wagtail has become the first CMS<\/a> to be fully integrated & automated with Pontoon \u2014 and managing translations doesn\u2019t require writing or manually deploying a single line of code. This will dramatically reduce the amount of time required to make some content localizable and get it published.<\/p>\n Mozilla Foundation worked directly with Torchbox, Wagtail\u2019s editor, and sponsored the development of the Wagtail Localize plugin<\/a>, adding localization support into Wagtail. This solution will not only work for us, but for any organization using this free and open source CMS!<\/p>\n Wagtail is currently used on the Foundation website<\/a>, the Mozilla Festival website<\/a> and on the Donate websites<\/a>. A lot of efforts went into designing a system to manage content at a granular level for each locale, so that you will only translate content that is relevant for your locale. For instance you won\u2019t see in Pontoon content that is used for performing A\/B tests in English, or custom content that is only relevant to other locales. Another nice feature is that your work gets automatically published on production within a few minutes. You can read more about the changes for the Mozilla donate websites here<\/a> and you can expect even more content to be localized via Wagtail Localize in 2021!<\/p>\n We\u2019ve got a few releases including Firefox 83<\/a> in mid-November and Firefox 84<\/a> just this week. Some of the following articles are completely new but most are only updated. You can also keep track of SUMO\u2019s new articles on our sprint wiki page in the above links.<\/p>\n Here are the recent articles that have been translated:<\/p>\n We\u2019ve just landed a new feature on team dashboards – Insights – which shows an overview of the translation and review activity of each team. Stay tuned for more details in a blog post that will be published soon.<\/p>\n In order to simplify adding new editor implementations to Pontoon, Adrian<\/a> refactored the frontend editor code using React hooks. All features should work exactly the same as before, but perform better<\/a>.<\/p>\n Thanks to Philipp<\/a> Pontoon has been upgraded from Django 2.2 to Django 3.1. The process also brought several related library upgrades and new dependency management using pip-compile.<\/p>\n We have moved our test automation fromTravis CI to GitHub Actions. Thanks to Axel<\/a> and Flod<\/a> for taking care of it! We\u2019ve also split automation into multiple tasks, which comes with several benefits<\/a>.<\/p>\n Several frontend bugs have been fixed by our new contributor Mitch<\/a>. Perhaps the most interesting one: changing the text to uppercase directly in JS files instead of using the text-transform property of CSS. Reason? The text-transform property is not reliable<\/a> for some locales. Welcome to the team, Mitch!<\/p>\n Thanks to Jotes<\/a> we\u2019ve landed several improvements and bugfixes for the project config<\/a> support. Jotes also migrated several unit tests from using the Django test framework to pytest.<\/p>\n April<\/a> and Jotes<\/a> have made good progress on the implementation of the Concordance search. It will be added to the Machinery panel and will allow you to search all your past translations without leaving the translate view. Two related changes have already landed – you can now reset custom search with a click of a button, and when you copy custom search result, it gets added to the editor instead of replacing its content.<\/p>\n Image by Elio Qoshi<\/p><\/div>\n <\/p>\n Know someone in your l10n community who\u2019s been doing a great job and should appear here? Contact one of the l10n-drivers and we\u2019ll make sure they get a shout-out (see list at the bottom)!<\/p>\n Did you enjoy reading this report? Let us know how we can improve by reaching out to any one of the l10n-drivers listed above.<\/p>\n","protected":false},"excerpt":{"rendered":" Welcome! New localizers Emmanuel of Basaa Alejandro, Manuel, and Sergio of Galician Are you a locale leader and want us to include new members in our upcoming reports? Contact us! … Read more<\/a><\/p>\n","protected":false},"author":385,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[467028,137],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/posts\/1497"}],"collection":[{"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/users\/385"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/comments?post=1497"}],"version-history":[{"count":0,"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/posts\/1497\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/media?parent=1497"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/categories?post=1497"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/tags?post=1497"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}New community\/locales added<\/h2>\n
\n
New content and projects<\/h2>\n
What\u2019s new or coming up in Firefox desktop<\/h3>\n
\n
\n
What\u2019s new or coming up in mobile<\/h3>\n
\n
What\u2019s new or coming up in web projects<\/h3>\n
mozilla.org<\/h4>\n
Firefox Accounts<\/h4>\n
Common Voice<\/h4>\n
Project WebThings<\/h4>\n
What\u2019s new or coming up in Foundation projects<\/h3>\n
What\u2019s new or coming up in SuMo<\/h3>\n
\n
\n
\n
\n
What\u2019s new or coming up in Pontoon<\/h3>\n
Team insights<\/h4>\n
![\"\"](\"https:\/\/blog.mozilla.org\/l10n\/files\/2020\/12\/ow7TQh7-252x448.png\")
<\/a><\/p>\nEditor refactor<\/h4>\n
Upgraded to Django 3<\/h4>\n
New test automation<\/h4>\n
Front-end bugfixes<\/h4>\n
Project config improvements<\/h4>\n
Upcoming changes to Machinery<\/h4>\n
![\"\"](\"https:\/\/blog.mozilla.org\/l10n\/files\/2020\/12\/FTxIJhl-252x179.png\")
<\/a><\/p>\nFriends of the Lion<\/h2>\n
![\"\"](\"https:\/\/blog.mozilla.org\/l10n\/files\/2017\/07\/2-Lions-01-252x232.png\")
\n
Useful Links<\/h2>\n
\n
Questions? Want to get involved?<\/h2>\n
\n
\n