Re: [l10n-dev] a localization tool.

Maxym Mykhalchuk wrote:

> So, Milos,
>
>> no actually, it compares the server version of original bundle and 
>> the server version of your russian bundle and will tell you that the 
>> original bundle was changed after you translated it.
>
>
> If so, you may easily strip our algorithm (as long, as you keep SPL & 
> Copyrights, but there's no problem, I suppose).
>
> What about your algorithm? Where're the sources, I'd like to look at 
> them and see if I can incorporate them in t13s/tools. I see only one 
> major difference: translator can do no checkout, but compare the files 
> on a server.

javacvs/libsrc/org/netbeans/lib/cvsclient/commandLine/command/locbundlecheck.java

the algorithm is fllowing:
1. do cvs annotate (can be also rannotate actually, if you don't have 
the sources checked out, but that's not done yet)
2. the output for both files will contains a date of last modification 
for each line.. I take out the lines that contain the <key>=<value> 
stuff and look for those that are modified later in the original file.


>
>> true, however with the cvs tool you can easily figure out which file 
>> was not changed at all. 
>
>
> The one that doesn't contain "# NEW|MODIFIED !!!". grep forever! ;-)


:))

>
>> and in our project we didn't use the netbeans tools for translating 
>> bundles so I came up with this.
>
>
> Why didn't you? What a shame ;-)
> We may cooperate and get a mutual benefit

dunno, was not really my responsibility and since the amount of loc. 
bundles was rather small we didn't care (time schedules etc) lately i 
realized that the bundles  that I modified lately were probably not 
translated, only the new added ones were, so I wrote this tool to figure 
out what's to be translated for the next release..

since I'm quite familiar with the cvslibrary I hacked together this tool..


Milos