Fluent VS cldr

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

Creating this mapping is a manual process, and the link contains the reference for the mappings. To establish this mapping, you can find the necessary information by visiting the link.

One problem I stumbled upon frequently is codebases that did not support localized formats, but just assumed a certain format to use, for example through concatenation.

There are capabilities built into the programming languages, which allow to format numbers, currencies, etc. with a specific locale. There are also great resources [1] out there that provide all kinds of formats and localized names for countries, currencies, etc.

[1] Unicode CLDR: https://github.com/unicode-org/cldr

Small addition: If you need the characters in machine-readable form, the source is the CLDR project. For Portuguese, the XML file is here on Github: https://github.com/unicode-org/cldr/blob/master/common/main/pt.xml

This information is false. en-150 in CLDR does not use this Euro English variant. It's just world English (en-001) with 3 adjustments: 24 hour time, currency symbol after the number and European time zone codes. Source. That's it.