fluent.js VS i18next

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.

For this article, we'll leverage the 'Simple CRM' project from our previous list of projects. We'll integrate and utilize the i18n library to internationalize our application.

When starting a new project with Next.js these days, next-intl and zod are my go to libraries for internationalization and schema validation, respectively. Of course, when using zod for client-facing validations I would like to translate potential error messages. The package zod-i18n can be used to achieve this for i18next, a popular alternative internationalization library. This means that by using this library as starting point one can quickly achieve zod translation with next-intl.

The best way to implement internationalization is to use an internationalization framework library, such as i18next. With this kind of library, you can easily handle translations and automatically display your frontend labels in the user's language. The frontend application also needs to be flexible and easily configurable so that its layout can change accordingly, reading from left to right or right to left. CSS allows this with the rtl and ltr CSS direction property.

For reference, I am using i18next for providing translations, which is configured to use the english message string as a key for the translations and fallback to it if no translation is found in the chosen language. I also use the official svelte-i18next integration. It wraps the i18next object in a Svelte store and, among other things, provides reactivity when the language is changed.

// app/components/BuiltInFormatsDemo.tsx 'use client'; import React from 'react'; import {useTranslation} from '../i18n/client'; import type {LocaleTypes} from '../i18n/settings'; import {useParams} from 'next/navigation'; const BuiltInFormatsDemo = () => { let locale = useParams()?.locale as LocaleTypes; const {t} = useTranslation(locale, 'built-in-demo'); return (

{/* "number": "Number: {{val, number}}", */} {t('number', { val: 123456789.0123, })} p>

{/* "currency": "Currency: {{val, currency}}", */} {t('currency', { val: 123456789.0123, style: 'currency', currency: 'USD', })} p>

{/* "dateTime": "Date/Time: {{val, datetime}}", */} {t('dateTime', { val: new Date(1234567890123), formatParams: { val: { weekday: 'long', year: 'numeric', month: 'long', day: 'numeric', }, }, })} p>

{/* "relativeTime": "Relative Time: {{val, relativetime}}", */} {t('relativeTime', { val: 12, style: 'long', })} p>

{/* "list": "List: {{val, list}}", */} {t('list', { // https://www.i18next.com/translation-function/objects-and-arrays#objects // Check the link for more details on `returnObjects` val: t('weekdays', {returnObjects: true}), })} p> div> ); }; export default BuiltInFormatsDemo;

As our world becomes increasingly interconnected, the development of web applications that cater to a global audience takes precedence among developers. If you're a TypeScript developer, you're likely acquainted with the advantages of static typing and the assurance it provides in your codebase. When it comes to internationalization (i18n) and localization (l10n), maintaining the same level of type safety becomes crucial. This is precisely where i18next, an influential i18n framework, enters the picture.

check i18next

In this article, we will go over how to perform internationalisation in our react app using the i18next framework. I18next is an internationalisation framework written in JavaScript. It comes with everything you need to localise your web, desktop or mobile product such as user language detection, loading and caching translations, and file conversion etc More features can be found in their documentation. (https://www.i18next.com/)

Luckily this is a well-solved problem: https://www.i18next.com/

I am so sorry for all the people using https://www.i18next.com/ and manually defining string ids. Fuck that. I will never write another message id in my life.