Re:MessageFormat: Unicode standard for localizable message s...
by Vinnl on Monday February 16, 2026 @07:25AM
(#47034163)
Yes, Fluent informed much of the design of MessageFormat. See this FOSDEM talk: https://archive.fosdem.org/2023/schedule/event/mozilla_intme...
Re:MessageFormat: Unicode standard for localizable message s...
by xeeeeeeeeeeenu on Monday February 16, 2026 @07:08AM
(#47034038)
Here's a comparison between the two on Fluent's wiki: https://github.com/projectfluent/fluent/wiki/Fluent-and-ICU-...
It seems the last edit of the page was in 2019, so I'm not sure how up to date it is.
Re:MessageFormat: Unicode standard for localizable message s...
by Vinnl on Monday February 16, 2026 @08:13AM
(#47034561)
Yeah it's actually MessageFormat 2 [1] that's very informed by Fluent's design I believe; I think that comparison is to "normal" MessageFormat.
Re:MessageFormat: Unicode standard for localizable message s...
by zbraniecki on Monday February 16, 2026 @01:52PM
(#47038697)
Correct. MF2.0 addresses all the challenges we identified during design of Fluent.
Re:MessageFormat: Unicode standard for localizable message s...
by hobofan on Monday February 16, 2026 @06:47AM
(#47033898)
They seems to be a strong overlap of people behind both projects, so that likely explains the similarities.
Re:MessageFormat: Unicode standard for localizable message s...
by xnorswap on Monday February 16, 2026 @06:28AM
(#47033773)
I often wonder this myself, this really should be a standard by now.
Re:MessageFormat: Unicode standard for localizable message s...
by hobofan on Monday February 16, 2026 @06:43AM
(#47033873)
I can't speak for the status quo, but for at least the first ~5 years (so until 3 years ago when I last attempted to use it), the JS implementation of Fluent was a mess. Constant issues with incomplete API, wrong TS typings (which at that point were external) and build/bundling issues to the point where we opted for a homebrew solution.
I imagine that I probably wasn't the only one driven away by that (and I gave it many attempts!).
Re:MessageFormat: Unicode standard for localizable message s...
by creshal on Monday February 16, 2026 @07:32AM
(#47034226)
The standard is, for better or worse, gettext; it's good enough that any attempt to replace it runs into the problem that people can't agree on how much better an alternative needs to be to be worth migrating to; so you get a constant churn that so far hasn't seen any clear winner.
Re:MessageFormat: Unicode standard for localizable message s...
by Cthulhu_ on Monday February 16, 2026 @09:38AM
(#47035543)
Feels like it's That XKCD page; there were standards like gettext, then web development came along and a load of people (...present company included) rediscovered localization and pluralization through trial, error, half-building one's own localization library, then the JS world reinvented it, etc etc etc.
Re:MessageFormat: Unicode standard for localizable message s...
by zbraniecki on Monday February 16, 2026 @01:53PM
(#47038714)
We are targeting MF2.0 for inclusion in JavaEcript stdlib (ECMA-402).
And later maybe with its own format into DOM for DOM L10n.
Re:MessageFormat: Unicode standard for localizable message s...
by ComputerGuru on Monday February 16, 2026 @01:59PM
(#47038810)
Wow, the in-browser preview is excellent. I first assumed it was just a demonstration and appreciated it very much, but then I realized it was live-editable and was blown away.
https://projectfluent.org/
I wonder why it hasn't been adopted more widely.