committed at tmccarron-i18n@5070 bulk of VASSAL.build.module dir
committed at tmccarron-i18n@5110 remainder of VASSAL.build.module dir
ok what directory I need to do next? and should I wait for that stuff to go in before I merge my local working project with trunk, or should I do that anyway every once in a while?
I would look at VASSAL.build.module.map and evything below it.
After that, stuff is spread all over the place, it will just be a matter of checking every String without a // NON-NLS-n$ tag.
When the source is changing often and in big ways, you should merge fairly often. Now that only the odd bug fix is going in, you can get away with less.
Joel is trying to get the new site and 3.1 out the door, so will probably be more responsive once that’s sorted.
I made one small change. I have added a generic label
Editor.report_format=Report Format:
and replaced the various instances that had their own versions with this one. In general, we don’t want the translators to have to translate the same string multiple times.
Cheers,
Brent.
*********** REPLY SEPARATOR ***********
On 18/06/2009 at 5:35 PM Tim McCarron wrote:
[quote]
I18n keys added for Layer control, GPL and LOS thread
Tmccarron-i18n-2@5740
Remaining keys for this sub directory committed to
Tmccarron-i18n-2@5749
Please check Zoomer.java
First key in getAttributeDescriptions() (ZOOM_START) was “” and says it is
handled (further down in getAttributeTypes) by LevelConfigurer. Didn’t know
how this key is supposed to be entered but added empty key in editor?