Is i18n enough?
We believe not. The closer the release date of your product gets the more obvious it gets, that instrumenting your code for localization is not enough.
There are more points to address:
- How does the translation process look?
- How do the source files get to the translators and back?
- How you deploy new languages after release?
- How do you handle versioning?
Translation Management Systems are a great help. But still there is a gap between development and translation process. Files need to be exported / imported / merged and all while new keys get added to be translated. The chaos is inevitable.
locize.com comes to the rescue. It's like a translation service on steroid directly connected to your i18next instrumented webproject.
Report
Hunter
Happy we got onto producthunt...
Report
Hunter
We just released an update:
You now can compare a resourcefile with another version and/or language. You can even compare them against currently published versions.
Learn more: http://locize.com/changelog.html
A lot of new stuff landed on our platform - use the new incontext editor, track changes to your translations using our auditing feature, translate your content using machine translations,...
Test it for 14d free - no risk, no obligations
