typesafe-i18n VS tolgee-platform

inlang: localization infrastructure for software and the next git (made by the inlang team and same author of the amazing typesafe-i18n library)

So I went to search and found https://github.com/ivanhofer/typesafe-i18n (1.6k stars). Seems great so far.

As far as I know `typesafe-i18n` works similiar to other solutions. The only difference is, that it does not include `next` in its package name ^^. There is an example in the docs that should cover the basic setup: https://github.com/ivanhofer/typesafe-i18n/tree/main/packages/adapter-react/examples/nextjs

You could try https://github.com/ivanhofer/typesafe-i18n, but I never tried it with "next export", so maybe you need to make additional adjustments.

Fully type-safe support with typesafe-i18n.

Maybe you can find an answer in this discussion: https://github.com/ivanhofer/typesafe-i18n/discussions/130

Is TypealizR solving a similar problem like [typesafe-i18n](https://github.com/ivanhofer/typesafe-i18n) in the JS ecosystem?

Typesafe-i18n

shameless plug: sounds like you are looking for https://github.com/ivanhofer/typesafe-i18n

If you want to get really good `TypeScript` support for i18n, you should check out https://github.com/ivanhofer/typesafe-i18n :)

You can learn more do about this platform on their website Tolgee.

Puedes saber más hacer de esta plataforma en su web Tolgee

Well, some tools can help you do something similar with localized texts and one I found recently is Tolgee (which by the way is also Open Source ⭐️, bonus points for that!)

Tolgee- Software localization from A to Z made really easy.

Website: https://github.com/tolgee/tolgee-platform

There's also GitHub repo. Stars are very appreciated. 🤓

We are developing this platform https://tolgee.io/ with our own integrations, which can also work with next.js (https://tolgee.io/integrations/next).

We use Tolgee and it has been great for us and our clients.

Or you can try Tolgee. It doesn't have Android SDK yet, but it has a pretty nice REST API and it can export to .json or .xliff. Definitely better workflow than Excel. And it open-source. (Disclaimer, I am the founder of it. haha.)

Hey, identifying of the keys is pain. That was one of the reasons why I founded Tolgee. Using that you can not only identify the keys byt also modify the keys directly in the web application you are working on. 🙂 We don't have a Ruby integration, but it few folks already required it. It would be great to find somebody interested who would help us to create such integration.