Re: [XBoard-devel] developer release

[h.g. muller]

> Before that it would be useful to add some translator comments to explain 
> contexts where necessary. There is at least the color button texts ("R", 
> "G", "B", "D") in xoptions.c (What does D stand for? Darken? Decrease? 
> Something else?)

It stood indeed for Darker, as Blacker collided with Bluer.
In fact this whole thing was a poor-man's solution to patch up the lack of 
a good color-picker in Xaw.
In WinBoard you would have a 'Choose' button here that would bring up a 
standard window with a palette where you could pick from.


> The most important missing translations at the moment is the engineNames 
> values. Texts like "%s engine did something" cannot be properly translated 
> as long the words "first" or "second" are inserted untranslated. That 
> should really be fixed.

Can't that be fixed by writing _() around the applicable other arguments of 
(s)printf, as well as around the format. I think we already do that in 
several places (although perhaps not in the XBoard front-end), and I am 
pretty sure "first" and "second" must already be marked for translation 
somewhere.


> args.h also needs to be mentioned in po/potfiles.in as it is now, as it 
> contains several translatable texts. However I really don't understand why 
> there is C functions in a header file. That is bad coding style. Why isn't 
> they in args.c?

That was because it it is an #included file. Wasn't that necessary because 
autoheader needed to see the dependency of xboard.c or winbord.c on it?