Fluent VS hjson-js

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

By the way.. if you use the hjson parser you can add comments to json files :) https://hjson.github.io/

I wish this took off https://hjson.github.io. I like it much more than yaml.

I don't know anything about VueJS either but HJSON is pretty cool in that regard https://hjson.github.io/

> Another difficult problem was checking for correct indentation visually (because the configuration is YAML-based and indentation matters).

why yaml? I hate it so much! my eyes hurt looking at it?

why not using https://hjson.github.io/ ?

HJSON [0] is also another format that tries to make it easier for humans to read / write json.

[0] https://hjson.github.io/

well there are json alternatives which fit this bill, such as HJSON.

https://hjson.github.io/

might not be as "common" but it has good implementations for many languages.

zdpack also pre-processes datapacks, allowing json files to be written in hjson or yaml, in addition to allowing a special extensible super-set of MCFunction I call CommandScript. You can check the github page for a quick overview of CommandScript.