I forgot to mention:
With my suggested technique it would be possible to *drop all the Angular
pluralization and gender directives that already exist*.
All would be reduced to just use the *data-i18n* directive, giving it the
correct property names to adhere to the strings.
Moreover:
I believe it to be quite clumsy for the programmer to explicitly load each
and every string into the model at page load.
Wouldn't it be sufficient to just load the JSON string file object into
some Angular property and have the data-i18n directive fetch its strings
from there?
This would result in just this kind of code
{
locale.ready('common'); // this loads the JSON string file and stores its
content into some Angular private field, where the data-i18n can access it
for string retrieval
}
Regards,
Axel Dahmen
--
You received this message because you are subscribed to the Google Groups
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.
