fluent.js VS rails-i18n

Want to quick internationalize your app? You can use com.hydroper.ftl from NPM, which uses Fluent. Should work for browser (if you use Webpack targetting "browser") and NodeJS. It uses Intl from ECMA-402 and @fluent/bundle.

Fluent is a localization system with more flexibility for translators. FTL means to Fluent Translation List. It seems to refer to the syntax used to define resources, which are (roughly) collections of messages.

In general though, translation is very hard. There are more exceptions than rules, and a lot of work has gone into the libraries to support all languages. consider using something like https://projectfluent.org/ if this isn't just a learning exercise.

Working on a personal project that needed localization I decided to use fluent from Mozilla. It already exists an excellent crate to use fluent in Rust which is fluent-bundle (and others fluent crates) but now that I'm used to "If it compiles, it works" I wanted to have a macro that checked that the "localization messages" I'm using existed and had all the required arguments, not finding what I was looking for I decided to write this crate for my needs and share it with the community.

Even if you're not planning to translate your game into other languages, it might be worth looking into one of the localisation systems. For example, Mozilla's Fluent handles pluralisation, gender, etc..

It's a tempting argument. By interviewing hundreds of people a different pattern emerged though. Translators don't know how to code. Some companies manually removed quotation marks (") from strings because they confused translators.

What do you think about Mozilla's Fluent format/syntax https://projectfluent.org/?

BTW feel free to reach out via email to me. Look at my profile to find it.

The last format in this multiverse trip is Fluent a Mozilla project. The Fluent format shares a lot of philosophy that drove the design of ICU Message Format.

My Elm code generator for i18n files Travelm-Agency has just reached a critical milestone: supporting all of projectfluents constructs. Yes, that means even locale specific constructs like matching on PluralRules (zero, one, few, many, other) or formatting dates and numbers based on the current locale! As far as I'm aware that is something that no other i18n solution for Elm can do so far.

As an example, there is a really good localisation framework called Project Fluent where you write your translatable expressions in a text file that later gets parsed. The resulting parse tree borrows entirely from the original text and doesn't make any allocations other than the occasional Vec for sequences.

Note that if you are using rails-i18n, configuration is automatically available for many locales.

And this example of translation for Rails defaults: https://github.com/svenfuchs/rails-i18n/blob/master/rails/locale/en.yml

Also, download ja.yml from rails-i18n and place it in config/locales.

Everything else is set up like site/welcome, but here, we introduce pluralization for countable things. I18n is able to select the appropriate translation based on the variable passed to it. If you see that pluralization is not working well for your locale, it's a good idea to enhance your Rails app with the rails-i18n gem.

rails-i18n

No. That does not contain time only no date i cannot use that without also geting date output also: https://github.com/svenfuchs/rails-i18n/blob/62ffdacdf52e2895715c9d708118bd5ffc320f6a/rails/locale/es-ES.yml. See? This is why I pose question in this reddit.

The origin of this format start Ruby. The i18n-js format is a direct export of translations defined by Ruby on Rails. To export the translations, a Ruby gem can be used, that's completely disconnected from Rails and that can be used for the solely purpose of exporting the translations, even if your project is written in a different language. For JavaScript there's a companion JavaScript package. It comes bundled with all base translations made available by rails-i18n. Base translations allow formatting date, numbers, and sentence connectors, among other things.

The translations are accquired from rails-i18n project -- which is one of the first modules that does things like this.

The Rails Locale Data Repository seems to be the only comprehensive collection of formats but unfortunately I have not seen a single date/time format it uses that is an actual date time format used in the given locale.

The cherry on top was that Comfy gem depended on rails-i18n, which overwrote date I18n translations coming from russian gem, breaking translations on some of the pages. Surely enough, this resulted in another hour or so of debugging and fixing.