React Intl VS i18n-js

You can use a third-party library, which is a bunch of code that someone else wrote for you. Many awesome third-party libraries can format numbers with commas in JavaScript. For example, you can try Numeral.js, Accounting.js, or Format.js.

react-intl

Looks like react has an npm package for internationalizing too. https://www.npmjs.com/package/react-intl

Format.JS

React i18n: Documentation: https://formatjs.io/docs/react-intl/ Source Code: https://github.com/formatjs/formatjs

de { key1 { "Deutsche Sprache " "schwere Sprache" } key2 { "Düsseldorf" }} I've found this library http://formatjs.io/react/. http://formatjs.io/ supports ICU, however I can't find any good example how to wire my language files with my app.

As we mentioned earlier, the Next.js works well with existing i18n libraries (react-intl, lingui, next-intl, and similar). In this tutorial, we will use the react-intl.

The second format is the ICU Message Format. There are multiple JavaScript modules implementing the ICU message syntax. One of the most used is intl-messageformat by Format.js. It is used behind the scenes also in react-intl.

I'm using expo-localization, which uses i18n-js to localise my app fully except for the app name.

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.

In most packages (i18next, i18n-js), the approach used to access translations is as follows:

I was working on an app built with React on Rails. Most of the pages were written in React, but some pages were written in and rendered from the Rails views. This meant that I needed to figure out a way to provide translations on both the backend and the frontend. I searched for articles and tutorials, but I couldn’t find one that was solving the same problem I had. I found a lot of tutorials on “i18n-ing” Rails apps, and some on Rails and Javascript, but not on Rails and React. After spending some time researching, I decided to try rails-i18n and i18n-js gems.