It may turn out that automatic translation of everything is a bad idea. Or maybe a good
idea that's untenable.
If that's the case, maybe it's best to admit defeat and say you have to indicate
which elements are translatable in your template's markup.
Sometimes we need switches and knobs, but when one approach is sensible and the other is
not, why clutter things up with a switch? :-)
-Jonathan
On 2013-04-05, at 10:18 AM, Eric Wittmann wrote:
Hey guys. After using this a little bit more I'm wondering if a
"manual" mode should be supported for i18n. I think the automatic
generation of keys is a great feature, and will be much more usable once
we address some of the false-positives (via the strategies we discussed
yesterday). That said, I think as a developer who is writing *both* the
templates and the errai app, I would prefer a fully-manual mode.
In other words, I would like to be able to flip a switch on my template
so that *only* the "data-i18n-key" approach is taken. So I would be
forced to add that attribute to anything I wanted translated.
For those of us who like fine-grained control, it seems like a nice option.
Thoughts?
-Eric
_______________________________________________
errai-dev mailing list
errai-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/errai-dev