quote:
Originally posted by KeyStorm
I mean >5 chars for if there are small words/keys that aren't translated, like "OK".
And yeah, it was just me surprised of all those green arrows... so well, not a bug. But still could be inproved comparing the keys .
I dunno... It could be actualy very confusing if this is added...
If this is added you're gonna rely on it and you might miss key's because of the ">5". Then if you don't add the ">5" restriction, false warnings are given, so again confusion...
If this isn't added, the user is forced to look at every key to see if it is translated, this makes that the language file is checked in detail (which is a must I think) and less "hasty" mistakes are being made...
About the "remove comments"-button:
you don't need to rely on the ini-api's for that. Much faster and more reliable would be:
code:
pseudocode:
do while not eof(readfile)
textline = readline(readfile)
if not firstchar(stripleadingspaces(textline)) = ";" then
writeline(writefile)
endif
loop
Related to this... Maybe this could be made into a seperate program (or if Choli has the time in his own program) together with a routine where all the topics and keys are sorted like the DefaultLg.dat. This makes comparing languages files with the original english one very easy in other programs. (because most linecomparing programs are only good at resyncronizing at a certain level). Also, double blank lines can be deleted, a blank line could be added before topics, blank lines between keys can be deleted, etc...