Hi, As the roadmap mentions, you can expect more details on the features in the next release (2.0) once 1.6 has been released. And as the bug details mention, XLIFF support has been accepted for inclusion in 2.0.
In the meantime, have you explored using other tools to convert XLIFF to Java .properties? I found one such tool, however it may be out of date since the spec has evolved since then. http://www.ibm.com/developerworks/xml/library/x-localis2/ -alex On Jan 27, 7:56 pm, jbdhl <[email protected]> wrote: > Betteri18nsupport is the one and only thing keeping us from > converting to GWT. See e.g. > http://code.google.com/p/google-web-toolkit/issues/detail?id=2926 > I wonder why the roadmap > http://code.google.com/webtoolkit/makinggwtbetter.html#roadmap > does not mention a word about betteri18nsupport, especially nothing > about XLIFF, not even for 2.0. It is a very important issue for "i18n > heavy" applications and I guess thei18nsupport is the only really > immature area left in GWT. Is the roadmap incomplete or have the > priorities changed? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
