cargo-i18n VS Fluent

It recently became possible to set up translation infrastructure in Rust with i18n-embed and Project Fluent. Popsicle is the first project to receive this treatment (https://github.com/pop-os/popsicle/pull/123), and other projects will be following soon. So if you've been interested in translating our software, the chance to do so will be present soon.

> Typical printf usage is imperative and additive:

> if (enter) printf("Hello "); else printf("Goodbye "); printf("World!\n");

And unless you want your translator to hate you, you really, really mustn’t do this in user-facing output.

(OK, you can if you really want to and if you’re ready to give them the same tools[1], but it won’t be simple. Although I’m unaware of any professional translators supporting this either—most use a CAT, and the Fluent approach ignores those.)

[1] https://projectfluent.org/

I wrote one for creating a Fluent library for PHP.

No. fluent-vue uses Fluent syntax from Mozilla https://projectfluent.org/. Which, I would say is just as powerful as ICU but is much more readable.

I think Mozilla's translation system called Fluent can handle that.

https://projectfluent.org/

After few months of frustration with trying to use the "de-facto" internationalization library for Vue.js - vue-i18n, I've decided it is time to replace it. And that is why I have created fluent-vue. I will write more about it and Fluent syntax it uses in my following blog posts.

fluent

> I'm also not sold on the whole "HTML-style error-recovery"

Having used and written a parser for a similar recoverable localization language (https://projectfluent.org/) I'm sold on it.

It makes a lot of things easier. It's kinda like adding trailing comma to lists. It's both boon when writing lists by hand and generating it via code.