title: Angular Internationalization ( ngx-translate/ i18n OR i18next )
body: <p>I need to implement internationalization in a large scale project in Angular. From what I have found, there are two main choices : Angular's official <strong>i18n</strong> OR <strong>ngx-translate</strong>.</p>
  
  <p>To understand advantages and disadvantages of both, I have gone through a lot of discussions : </p>
  
  <p><a href="https://github.com/angular/angular/issues/16477" rel="nofollow noreferrer">https://github.com/angular/angular/issues/16477</a></p>
  
  <p><a href="https://github.com/ngx-translate/core/issues/495" rel="nofollow noreferrer">https://github.com/ngx-translate/core/issues/495</a></p>
  
  <p><a href="https://github.com/ngx-translate/core/issues/783" rel="nofollow noreferrer">https://github.com/ngx-translate/core/issues/783</a></p>
  
  <p><a href="https://stackoverflow.com/questions/44923138/differences-ngx-translate-vs-i18n?rq=1">Differences ngx-translate vs i18n</a></p>
  
  <p>Now, the 3rd option is "<strong>angular-i18next</strong>". There's not a lot of documentation on this. I understand it's a wrapper over i18next. But does it overcome any shortcomings like:</p>
  
  <ul>
  <li><p>Translating non template text.</p></li>
  <li><p>Dynamic translations without reloading the page.</p></li>
  <li><p>Having single build with AOT compilation.</p></li>
  </ul>
  
  <p>Or, my best bet is to choose between <strong>i18n</strong> and <strong>ngx-translate</strong>?
  Also, is anyone using "<strong>angular-i18next</strong>"?</p>