I'm at my wit's end with internationalization (i18n) for my app. I'm a solo developer really invested in creating a quality product, but managing i18n has become a huge headache. I've tried using libraries like i18next and react-intl, but they fall short when it comes to handling nested keys, fallback chains, and formatting for different locales. I'm on the brink of creating my own i18n solution in a fictional language just to escape this madness! Has anyone here tackled similar challenges? Have you tried tools like General Translation or Phrase? I'm looking for any advice or experiences you can share!
2 Answers
Hey! It sounds like you're feeling pretty overwhelmed. What specific issues are you dealing with? If you share some code examples, the community might help you avoid some common pitfalls. I see you've gotten some replies that hint at possible library issues; let’s clear those up!
I went through a similar transition with i18next and react-i18n, and honestly, while it can be tedious, it's manageable. If you can pinpoint the issues you’re facing, I could give you some specific pointers!
Thanks! One specific issue I have is with loading examples from General Translation. I cloned their repo but got stuck on setting up the environment variable file. Any advice on using their example app?
I agree, it would help to see some code! I've found that understanding the documentation thoroughly can also ease things a lot.