Property File Editor that stores Property Strings in HTML. Scans Java source for "getString"-calls and assigns them to properties. Scans existing property files and displays overview of translation. All input Strings are converted to HTML.
The editor parses all .java-files in a given directory and its
subdirectories and extracts calls to .getString(String
name)-Methods. I use this Method to get strings from
I18N-property-files via a ResourceBundle in Java. Multiple calls to the
same string in a class are recorded only once.
After all strings are collected, one .property-file must be specified. If there are more property files in the same directory that seem to be translations for other languages, they are also considered. A table is constructed with one property on each line in the first row and all translations in the following rows. When clicking on a cell, the content can be edited and will be saved back as 7-bit-HTML with unicode-characters represented by &\#0000; where 0000 is replaced by the unicode-number for that character. When the table is closed, all not empty cells are written back to the appropriate .property-file for each language. Not translated cells are marked gray. This speeds up translation a lot, since you have all languages and all strings that need to be translated at one place. It even finds strings the programmer didn't record and marks them as not translated.
One great benefit is, that when editing for a language that has not-Latin characters, you can simply switch the keyboard Layout on your Computer to that Language and enter all necessary Strings.
You need Java from java.com installed for this to work. Please make a backup of your property files before you start the application
cvs -d:pserver:firstname.lastname@example.org:/cvsroot/properedit login(no password needed)
cvs -z3 -d:pserver:email@example.com:/cvsroot/properedit co -P properEdit