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. You could reuse the properties files though if you ship them with your war/ear file, and on the server side, just use old ResourceBoundle.
2) properties files are not limited to one-line messages. These are both valid entries: prop1 = first part of prop1 \ second part of prop1 \ third part of prop1 prop2 = first line of prop2 \n \ second line of prop2 \n \ third line of prop2 On Feb 25, 8:52 pm, 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 -~----------~----~----~----~------~----~------~--~---
