🌍 Do you use i18n in your Angular apps? 🌏 Read @petebd's blog post to dive into $localize and learn what new features and build time improvements it introduces to Angular internationalization! blog.angular.io/angular-locali…

@angular @petebd The new i18n story is great and the reduced compilation times were life changing; thanks! It would be great to publish a guide on how to do the localization step on apps using webpack directly as ng-tools plugin only works with View Engine enabled.

@angular @petebd After working with ngx-translate the last years, tried Angular i18n now and I like it much more. The 10.1.0 --ivy xi18n flag works well (just often missing location info) + xliffmerge + Poedit

@angular @petebd No way, too much complex => Ngx-translate

@angular @petebd Ngx-translate 🤘🏻

@angular @petebd Finally! We hope to replace all impure pipes from external libraries with more efficient $localize approach!

@angular @petebd Too complex -> ngx-translate

@angular @petebd We have started using $localize but it is still super limited, really hoping for some localize$ love in future versions such as late loading of translations and support for dynamically generated translation keys

@angular @brandontroberts @petebd After using $localize we have to create multiple builds. How to call these builds from server-side or what are some best practices to load those builds when a user requests a specific language???

@angular @petebd The ngx-translate syntax is simpler and more intuitive.. A demo to see it in action would be great with an example of a template i18n and a code localization.

@angular @petebd nope

@angular @petebd Unfortunately, this isn't the i18n direction I need. Do what transloco does