Re: Translation assessment tool (part 1)

[Alexandre Julliard]

Vincent Béron  writes:
> Here we go again after a couple of months...
>
> Changelog:
> Adds a new dump flag to wrc, to be used to assess translations
> advancement.

OK, I put that one in with a few changes, but it would be really nice
if it could be print something understandable, instead of just random
characters that require an external parser to interpret. It wouldn't
be much harder for the parser to check for specific strings instead of
'+' or '-', and it would make that mode useful by itself, for instance
to check translations of a single file. Also, this thing should be
driven by make instead of having a shell script parse the makefiles by
hand.

Translation assessment tool (part 1)

[Vincent Béron]

Le dim 18/01/2004 à 18:30, Alexandre Julliard a écrit :
> Vincent Béron  writes:
> > Here we go again after a couple of months...
> >
> > Changelog:
> > Adds a new dump flag to wrc, to be used to assess translations
> > advancement.
>
> OK, I put that one in with a few changes, but it would be really nice
> if it could be print something understandable, instead of just random
> characters that require an external parser to interpret. It wouldn't
> be much harder for the parser to check for specific strings instead of
> '+' or '-', and it would make that mode useful by itself, for instance
> to check translations of a single file.

Ok, I'll make it emit something more meaningful by itself. Just give me
a couple of days. Probably something along the lines of only outputting
the meaningful data, and not the rest.
> Also, this thing should be
> driven by make instead of having a shell script parse the makefiles by
> hand.

Right. I just wanted to have a working something before mixing it with
make. Still unsure how to get a single file for all dlls at the end (as
was asked by a couple people back in October) with a recursive make run.

Maybe with two commands, one to start it (will cleanup any leftovers
from a previous run) and another one for the recursive part... Or if
it's possible to know how deep the makefile is located (during
recursivity), do something special when coming back to level==1...
(Just thinking out loud)

Vincent