We're using it in Matific on a not-yet-deployed site. Currently, there is no programmatic access to text resources. To bypass that, I've created a template in which all strings that need to be accessed programmatically will reside, and then we load the relevant XLF file and parse it in our code to extract the translated messages. This isn't great, but it works.
On Thursday, January 5, 2017 at 8:50:23 AM UTC+2, Martin Kuhn wrote: > > Hi, > > does anybody of you has real world experience with i18n? > > I have the impression that this stuff is not really useful at this time.... > > e.g. is there a way to handle programmatic access to text resources (and > so on)? > > Regards > > Martin > -- You received this message because you are subscribed to the Google Groups "Angular" group. To unsubscribe from this group and stop receiving emails from it, send an email to angular+unsubscr...@googlegroups.com. To post to this group, send email to angular@googlegroups.com. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
