| Re: [e4-dev] Eclipse Internationalization with the new message extension and the Eclipse translation pattern |
Hi Dirk, hi Tom, I did some experiments following your blog lately. I think it’s a great solution! The only thing missing to make it usable for us in our production environment is the IDE-Integration (see attached screenshot): · Display of the message itself, when you hover over the accessor field · And the possibility to jump to the properties entry from this tooltip. So +1 for including the new message extension in the platform. Having “Externalize Strings…” work with the new type of accessor classes would be nice too, but as you described in your blog, the migration is easy enough. Keep up the great work! Smile Christoph Von: e4-dev-bounces@xxxxxxxxxxx [mailto:e4-dev-bounces@xxxxxxxxxxx] Im Auftrag von Dirk Fauth Hi everybody, I would say it is an evolution of the existing internationalization stuff in Eclipse, that introduces a lot more flexibility. Currently it is contributed to the e4.tools.services plugin, but IMHO this is the way internationalization should look like in future releases of Eclipse. So it should be included into the platform itself. The current code is a summary of workarounds that were necessary because of missing features in Java 1.4. But with Java 1.6, these workarounds can be solved elegantly (loading of ResourceBundles). Using the new message extension it even becomes possible to change the locale at runtime, using OSGi services and the dynamic injection in E4. We would like to see this solution in the Eclipse Platform itself. So with this mail we want to start the discussion if there is anything that speaks against that. Greez, |
Attachment:
2013-08-12_112603.png
Description: 2013-08-12_112603.png
