Tool for finding missing translations in properties.xml
Hi all, in my Wicket app I'm using properties.xml files for my i18n texts, like described in the wiki[1]. The problem I have is that the files are differently up to date, depending on the language and how important it was for somebody to translate one exact key for one special language etc. the only thing I really know is that English is up to date... So, does anyone knows a tool which expects translation files in a dir structure and compares all found to their English base file? In the end it should simply print which file in which dir is missing which key compared to the English base. Such a problem sounds common to me, but I couldn't find any good software dealing with it yet. Thanks! [1]: https://ci.apache.org/projects/wicket/guide/6.x/guide/i18n.html#i18n_2 Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...05151- 9468- 55 Fax...05151- 9468- 88 Mobil..0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Tool for finding missing translations in properties.xml
I wrote my own tool as my search wasn't successful. But it is simply a main method loading the files and compares keys. Cheers Per Am 07.07.2016 um 16:48 schrieb Thorsten Schöning: Hi all, in my Wicket app I'm using properties.xml files for my i18n texts, like described in the wiki[1]. The problem I have is that the files are differently up to date, depending on the language and how important it was for somebody to translate one exact key for one special language etc. the only thing I really know is that English is up to date... So, does anyone knows a tool which expects translation files in a dir structure and compares all found to their English base file? In the end it should simply print which file in which dir is missing which key compared to the English base. Such a problem sounds common to me, but I couldn't find any good software dealing with it yet. Thanks! [1]: https://ci.apache.org/projects/wicket/guide/6.x/guide/i18n.html#i18n_2 Mit freundlichen Grüßen, Thorsten Schöning - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Tool for finding missing translations in properties.xml
Guten Tag Per Newgro, am Freitag, 8. Juli 2016 um 16:37 schrieben Sie: > I wrote my own tool as my search wasn't successful. But it is simply a > main method loading the files and compares keys. Thanks, I had the same approach in my mind. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...05151- 9468- 55 Fax...05151- 9468- 88 Mobil..0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Tool for finding missing translations in properties.xml
Hi, In Eclipse MarketPlace, you may find Eclipse ResourceBundle Editor https://marketplace.eclipse.org/content/eclipse-resourcebundle-editor I guess it works with .properties.xml too... Best regards, Sebastien
Re: Tool for finding missing translations in properties.xml
We faced the ame problem and created a small maven plugin. Now that i heard that others might need this too, i uploaded our solution to github: https://github.com/pingunaut/wicketmessages-maven-p lugin It's a small maven plugin available from maven central which generates an excel file from your properties.xml files, so you can easily sort, filter, ... To test it you can simply type: mvn com.pingunaut.maven.plugin:wicketmessages-maven-plugin:generateXls This will generate a file called messages.xlsx in your project's root folder. Don't expect to much we just started to use it by ourselves so this still in development... Hope it helps, Best regards Martin On Sun, 2016-07-10 at 11:58 +0200, Thorsten Schöning wrote: > Guten Tag Per Newgro, > am Freitag, 8. Juli 2016 um 16:37 schrieben Sie: > > > > > I wrote my own tool as my search wasn't successful. But it is > > simply a > > main method loading the files and compares keys. > > Thanks, I had the same approach in my mind. > > Mit freundlichen Grüßen, > > Thorsten Schöning > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Tool for finding missing translations in properties.xml
On Wed, Jul 20, 2016 at 9:57 PM, Martin Spielmann < martin.spielm...@pingunaut.com> wrote: > We faced the ame problem and created a small maven plugin. > Now that i heard that others might need this too, i uploaded our > solution to github: https://github.com/pingunaut/wicketmessages-maven-p > lugin > > It's a small maven plugin available from maven central which generates > an excel file from your properties.xml files, so you can easily sort, > filter, ... > > To test it you can simply type: > > mvn com.pingunaut.maven.plugin:wicketmessages-maven-plugin:generateXls > > This will generate a file called messages.xlsx in your project's root > folder. > > > Don't expect to much we just started to use it by ourselves so this > still in development... > > Hope it helps, > Thanks for sharing, Martin! > > Best regards > Martin > > On Sun, 2016-07-10 at 11:58 +0200, Thorsten Schöning wrote: > > Guten Tag Per Newgro, > > am Freitag, 8. Juli 2016 um 16:37 schrieben Sie: > > > > > > > > I wrote my own tool as my search wasn't successful. But it is > > > simply a > > > main method loading the files and compares keys. > > > > Thanks, I had the same approach in my mind. > > > > Mit freundlichen Grüßen, > > > > Thorsten Schöning > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
