> 1) GWT's i18n can't be used as is, since the interfaces are meant to
> be used at compile-time and the actual text from the properties files
> gets put into the js/html files.

So there is no way to re-use the plural-technology in the Messages
class on the server side? Are we really forced to use two different
technologies then? E.g. the GWT methods on the client side and gettext
on the server? This is kind of ugly IMHO.

> prop2 = first line of prop2 \n \
> second line of prop2 \n \
> third line of prop2

But then translators (which are non-technicans) have to use \n when
breaking lines? Is that really the only way of doing it?
I look forward to the XLIFF support in GWT as these property files are
very limited in many ways.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to