Translating Pentaho
As part of our fun week this year, I began work on a tool to make it easier to contribute translations of all Pentaho projects (There are over 100!) . Since then, I’ve been working in my spare time to get to an initial release of the project. I now have a first cut available, and I’m looking for feedback on the tool. I haven’t yet invested much in the UI, but now that all the plumbing is working well, we can start discussing what capabilities would be the most beneficial to folks who might want to contribute a translation. You can download the latest here on our continuious integration server:
http://ci.pentaho.com/job/pentaho-i18n-tool/
Please check it out and let me know what you think!
The tools seems great, but the stucture of the directories seems différent with the realities.
I mean if we translate the mantle:org/pentaho/mantle/public/messages/messages and save it, we also want to put it directly in the corresponding directory in the server so we can use it right away (and of course share it with the community.)
The folder structure maps to the source project paths. Unfortunately there is a compilation step before the message bundles are really useful. For the java based bundles, you’d need to crack open a JAR and place it in there, for GWT you’d need to rebuild the project. I agree being able to drop in the bundles into a running environment would be ideal, so I’ve created the following JIRA case:
http://jira.pentaho.com/browse/COMMONS-94
Please comment and vote on the case. Thanks!
Will