UNPKG

i18next.com

Version:

i18next website

27 lines (19 loc) • 1.21 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
--- title: Translation process order: 2 --- #### 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. <div style="text-align: center; background: #fff; padding: 20px; margin-bottom: 30px"> <a href="http://locize.com"> <img style="max-width: 300px;" src="/img/locize.png" /> </a> <p>locize.com comes to the rescue. It's like a translation service on steroid directly connected to your i18next instrumented webproject. <a href="http://locize.com">Learn More</a></p> </div> Don't miss our article *Translate my website — please!* on [medium](https://medium.com/@jamuhl/translate-my-website-please-732ddb622cba#.f0sai4bfb).