Hi, Concerning the first question, the solution is simple. I developed a tool class to use on server side. The class GWTI18N permits to obtain dynamically an implementation of the XXXMessage interface (sub interface of gwt Message interface). Here is a link to the class : http://code.google.com/p/gwt-fusionchart/source/browse/trunk/fusionchart_server/src/com/raisepartner/chartfusion/web/server/gwti18n/GWTI18N.java To use it you have to put the i18n interfaces and properties files in your classpath whereas in your code you simple call GWTI18N.create(TotoMessages.class); This class is based on the use of the annotation com.google.gwt.i18n.client.LocalizableResource.Key on methods. This class could be improved to support plural mode.
About the second question I think you could use html tag in order to structure your message in several paragraphs. This means your email will be write in HTML, not a simple text. Regards, Seb On 26 fév, 02:52, jbdhl <[email protected]> wrote: > Consider a case where some RPCs in a GWT application will trigger the > server to send an email to the user where the email should be sent in > the language used at the requesting client. > > 1) How should I approach this server-side internationalization (i18n)? > Can GWTs i18n be used in this situation? > > 2) The email will have multiple paragraphs of text, not just one-line > messages as the property files are limited to (as far as I know). > Similarly, our help-page and about-page have many large paragraphs of > text. How can I translate these multi-line texts? > > Thanks --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
