[WICG/webcomponents] DOM Parts and Localization (Issue #1034)

Hi. Would this be an appropriate forum for discussing the relationship between the DOM Parts proposal and localization? I hosted a breakout session at TPAC on [DOM Localization](https://docs.google.com/presentation/d/1cvvNcC2jMKztYKFIAg1Q5JPWrMCd0q8Ac2m7P1RYhOc/edit?usp=sharing), and unfortunately learned only afterwards that it was at the exact same time as the DOM Parts session.

The core idea of "DOM Localization" is to be able to extract localizable messages from HTML and to provide them separately for inclusion in the DOM, with different contents for each locale. As these messages may include tags, to me this sounds like it might be really close to the templates of DOM Parts, with the caveat that the structure won't always be the same: Even something as simple as `Click <a>here</a> to continue` will in some locales have the link at the start or end of the message, rather than in its middle. Sometimes the message structure will also change within a locale, depending on e.g. whether the count of some items is zero, one, or more.

Work on DOM localization builds on top of prior (and still current) work in TC39 [introducing Intl.MessageFormat](https://github.com/tc39/proposal-intl-messageformat), and in the Unicode Consortium's [MessageFormat WG](https://github.com/unicode-org/message-format-wg), where we're defining "MessageFormat 2" as a new syntax and language for the localizable messages that all of the above requires. We're currently evolving said syntax due to in part feedback we got during TPAC, so everything's a bit in flux.

Would there be interest in considering something like MessageFormat 2 as a syntax for DOM Parts, and/or taking into account in that proposal localization aspects? Or would it be better that DOM Localization be presented as a wholly separate proposal? If there's interest, I'd be happy to participate in a real-time call about all this.

In case it's relevant, DOM localization is structurally very similar to how Firefox and other Mozilla products are currently localized, using [Fluent](https://projectfluent.org/) rather than the technologies mentioned above.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/1034
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/1034@github.com>