Fluent VS json5

> 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.

JSON5 support

Meanwhile, formats have been evolving (JSON5, YAML), config entry points are constantly changing. These fluctuations, fortunately, were covered by tools like the cosmiconfig.

I think JSON5 is fairly close to this: https://json5.org

I reckon the only thing it's missing to be truly accessible to non-techies is that string values still need to be quoted, i.e. you can't have:

key: this is my value

(I'm definitely not saying it would be a good idea to allow quotes to be dropped, just that that's the only potential stumbling block I see for non-techies.)

I believe that's JSON5.

https://github.com/json5/json5

It's my preferred configuration file format, it fixes all the problems I have with JSON (trailing commas, comments) without turning it into a mess full of gotchas like YAML.

JSON 5 support

I would like to see mention of JSON5 which is 11 years its elder. For comments in JSON, JSON5 is a good starting point.