handling time and date differences between different locales

[jonator]

https://github.com/osmosis-labs/osmosis-frontend/blob/b4f3655a506f3a884a9c7cb7943d425466ae3b95/packages/web/localizations/dayjs-locale-ar.js

In the Osmosis frontend, we use locale files per language to define how dates/times are displayed. How will Inlang handle this? Could they be provided by Inlang for common libs, like our dayjs?

[samuelstroschein]

Datetime formatting is part of an i18n library (see i18n-next), or a programming language itself. JavaScript, for example, has the Intl object that provides what you seemed to have built yourself.

The Intl object takes care of formatting and contains the translations themselves. See the example below

In the future, inlang will most likely provide i18n libraries and deep integrations with frameworks like Next.js to take care of everything for you under the hood.

Did I answer your question?

[jonator]

Yeah. Perhaps you could wrap the next config, as many utilities do for Next.js. (Next config is basically a wrapper around WebPack config).

Then you could check for some libs and add locale stuff in the build step?

https://github.com/osmosis-labs/osmosis-frontend/blob/1a787d982deb92c59edb8671e9f75234f0b99e9a/packages/web/next.config.js#L3

[samuelstroschein]

Yep, that's a good idea. Combined with the inlang.config.js file building such framework-specific i18n libraries should become a breeze. For now, we are focused on building dev tools and the editor to manage translations and leverage existing i18n libraries.

[jonator]

osmosis-labs/osmosis-frontend#1243 (comment)

Good comment on possibly using a hooks-based system to let developers write custom code (as a method of supporting locales).