[GRASS translations] Not yet gettexted?
neteler at itc.it
Mon Feb 28 16:21:11 EST 2005
On Mon, Feb 28, 2005 at 12:37:52PM -0500, Daniel Calvelo wrote:
> Markus Neteler <neteler at itc.it> on 28 Feb 2005 15:22:00 +0100 wrote:
> > Basically it's a lot of work, help is more than welcome.
> Ok. Have you got a rough idea of the priorities for translation? I reckon d.m,
> g.*, r.* are more used than the rest of commands, but people with more grass
> experience might have other ideas.
In a long morning I have indicated all r.* descriptions (> 1000).
All d.*, g.* etc are missing, many v.* as well. Just go ahead!
> > It might also be a good opportunity to write the paragraph on fprintf vs.
> > G_message in SUBMITTING.
> > Good point.
> > Someone knowing better than me may give us a hint when to use
> > G_message().
> locale/README states that both fprintf(stderr...) and fprintf(stdout...)
> should be changed to G_message. I find that quite surprising: it seems to
> erase the distinction between "normal" output and "warning-like" output.
> Shouldn't fprintf(stderr...) become G_warning()?
You are right, it's badly explained.
Radim: what's the policy for G_message?
More information about the grass-translations