Angular-translate 2.0 released

Almost a year ago when this project was announced on angular google group I was looking for a i18n solution for my app, I tried it but the negative performance impact made me discard it. Its approach of implement i18n through filters and directives relying on angular dirty checking make your app really slow If you have a regular amount of i18n strings. I ended up generating different templates for each language with grunt and using a simple i18n function mapping a dictionary for strings on js code. I see that it hit 2.0 now, its evolution make it usable without a notable performance penalty?

Had a look but couldn&#x27;t quickly see if this supports Gettext? As you build out an increasingly large app and i8n is important to you, using a standardized i8n process makes your life significantly easier than managing lists of strings.<p>We&#x27;ve been using angular-gettext[1] along with Transifex and it&#x27;s made a significant impact our development and translation management.<p>[1] <a href="http://angular-gettext.rocketeer.be/" rel="nofollow">http:&#x2F;&#x2F;angular-gettext.rocketeer.be&#x2F;</a>

Minor nitpick: The english &quot;paragraph&quot; is better translated as &quot;Absatz&quot;. &quot;Paragraph&quot; has a very narrow meaning in german (a section of a legal code, e.g. §1 BGB).

I looked at the changelog on Github, and while there is certainly a lot of good stuff in there, for such a big release I would expect more information on some points, such as &#x27;determinePreferredLanguage&#x27; or &#x27;teaches directive custom translate-value-* attr&#x27;. Or link the commit ids to the commits (and link to relevant issues).

More information about the release can be found here: <a href="https://plus.google.com/+PascalPrecht/posts/V5GtNp1tU27" rel="nofollow">https:&#x2F;&#x2F;plus.google.com&#x2F;+PascalPrecht&#x2F;posts&#x2F;V5GtNp1tU27</a>