{"id":1639,"date":"2024-01-18T07:33:03","date_gmt":"2024-01-18T07:33:03","guid":{"rendered":"https:\/\/blog.mozilla.org\/l10n\/?p=1639"},"modified":"2024-01-18T07:33:03","modified_gmt":"2024-01-18T07:33:03","slug":"advancing-mozillas-mission-through-our-work-on-localization-standards","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/l10n\/2024\/01\/18\/advancing-mozillas-mission-through-our-work-on-localization-standards\/","title":{"rendered":"Advancing Mozilla&#8217;s mission through our work on localization standards"},"content":{"rendered":"<p>After the previous post highlighting <a href=\"https:\/\/blog.mozilla.org\/l10n\/2024\/01\/15\/mozilla-localization-in-2023\/\">what the Mozilla community and Localization Team achieved in 2023<\/a>, it&#8217;s time to dive deeper on the work the team does in the area of localization technologies and standards.<\/p>\n<p>A significant part of our work on localization at Mozilla happens within the space of Internet standards. We take seriously our commitments that stem from the <a href=\"https:\/\/www.mozilla.org\/about\/manifesto\/\">Mozilla Manifesto<\/a>:<\/p>\n<blockquote><p>We are committed to an internet that includes all the peoples of the earth \u2014 where a person\u2019s demographic characteristics do not determine their online access, opportunities, or quality of experience.<\/p><\/blockquote>\n<p>To us, this means that it\u2019s not enough to strive to improve the localization of our products, but that we need to improve the <i>localizability<\/i> of the Internet as a whole. We need to take the lessons we are learning from our work on Firefox, Thunderbird, websites, and all our other projects, and make them available to everyone, everywhere.<\/p>\n<p>That\u2019s a pretty lofty goal we\u2019ve set ourselves, but to be fair it\u2019s not just about altruism. With our work on <a href=\"https:\/\/projectfluent.org\/\">Fluent<\/a> and <a href=\"https:\/\/projectfluent.org\/dom-l10n-documentation\/\">DOM Localization<\/a>, we\u2019re in a position where it would be far too easy to rest on our laurels, and to consider what we have \u201cgood enough\u201d. To keep going forward and to keep improving the experiences of our developers and localizers, we need input from the outside that questions our premises and challenges us. One way for us to do that is to work on Internet standards, presenting our case to other experts in the field.<\/p>\n<p>In 2023, a large part of our work on localization standards has been focused on <a href=\"https:\/\/github.com\/unicode-org\/message-format-wg\">Unicode MessageFormat 2<\/a> (aka \u201cMF2\u201d), an upcoming message formatting specification, as well as other specifications building on top of it. Work on this has been ongoing since late 2019, and Mozilla has been one of the core participants from the start. The base MF2 spec is now slated for an initial \u201ctechnology preview\u201d release as a part of the 2024 Spring\u2019s <a href=\"https:\/\/cldr.unicode.org\/\">Unicode CLDR<\/a> release.<\/p>\n<p>Compared to Fluent, MF2 corresponds to the syntax and formatting of a single message pattern. Separately, we\u2019ve also been working on the syntax and representation of a <a href=\"https:\/\/github.com\/eemeli\/message-resource-wg\">resource format<\/a> for messages (corresponding to Fluent\u2019s FTL files), as well as championing JavaScript language proposals for <a href=\"https:\/\/github.com\/tc39\/proposal-intl-messageformat\">formatting messages<\/a> and <a href=\"https:\/\/github.com\/tc39\/proposal-intl-message-resource\">parsing resources<\/a>. Work on standardizing DOM localization (as in, being able to use just HTML to localize a website) is also getting started in <a href=\"https:\/\/www.w3.org\/blog\/2019\/w3c-and-whatwg-to-work-together-to-advance-the-open-web-platform\/\">W3C\/WHATWG<\/a>, but its development is contingent on all the preceding specifications reaching a more stable stage.<\/p>\n<p>So, besides the long term goal of improving localization everywhere, what are the practical results of these efforts? The nature of this work is exploratory, so predicting results has not and will not be completely possible. One tangible benefit that we\u2019ve been able to already identify and deploy is a reconsideration of how Fluent messages with internal selectors \u2014 like <a href=\"https:\/\/projectfluent.org\/fluent\/guide\/selectors.html\">plurals<\/a> \u2014 are presented to localizers: Rather than showing a message in pieces, we\u2019ve adopted the MF2 approach of presenting a message with its selectors (possibly <a href=\"https:\/\/pontoon.mozilla.org\/fr\/firefox-profiler\/app.ftl\/?string=224370\">more than one<\/a>) applying to the whole message. This duplicates some parts of the message, but it also makes it easier to read and to translate via machine translation, as well as ensuring that it is internally consistent across all languages.<\/p>\n<p>Another byproduct of this work is MF2\u2019s <a href=\"https:\/\/github.com\/unicode-org\/message-format-wg\/tree\/main\/spec\/data-model\">message data model<\/a>: Unlike anything before it, it is capable of representing all messages in all languages in all formats. We are currently refactoring our tools and internal systems around this data model, allowing us to deduplicate file format-specific tooling, making it easier to add new features and support new syntaxes. In Pontoon, this approach already made it easier to introduce syntax highlighting and improve the editing experience for right-to-left scripts. To hear more, you can join us at FOSDEM next month, where we\u2019ll be <a href=\"https:\/\/fosdem.org\/2024\/schedule\/event\/fosdem-2024-1759-a-universal-data-model-for-localizable-messages\/\">presenting on this<\/a> in more detail!<\/p>\n<p>At Mozilla, we do not presume to have all the answers, or to always be right. Instead, we try to share what we have, and to learn from others. With many points of view, we gain greater insights \u2013 and we help make the world a better place for all peoples of all demographic characteristics.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>After the previous post highlighting what the Mozilla community and Localization Team achieved in 2023, it&#8217;s time to dive deeper on the work the team does in the area of &hellip; <a class=\"go\" href=\"https:\/\/blog.mozilla.org\/l10n\/2024\/01\/18\/advancing-mozillas-mission-through-our-work-on-localization-standards\/\">Read more<\/a><\/p>\n","protected":false},"author":663,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[12694,12691,137],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/posts\/1639"}],"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\/663"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/comments?post=1639"}],"version-history":[{"count":0,"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/posts\/1639\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/media?parent=1639"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/categories?post=1639"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/tags?post=1639"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}