[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Translator comments and other extensions to genparse

From: Jim Meyering
Subject: Re: Translator comments and other extensions to genparse
Date: Mon, 15 Oct 2007 13:43:11 +0200

address@hidden (Michael Geng) wrote:
> On Sat, Oct 13, 2007 at 04:01:09PM +0200, Bruno Haible wrote:
>> Michael Geng wrote:
>> > I released genparse version 0.7.2 which addresses some issues which we
>> > recently discussed in the mailing list.
>> Thank you very much!
>> The only remaining question is: Why is --manyprints not implied by
>> --internationalize? Or why does the doc of --internationalize not say:
>> "When you use this option, the option --manyprints is also recommended."?
> Is there really consensus that in future every command line parameter shall
> be output in a seperate print command?

Not here.
I've tended to divide --help output them into groups of lines
totaling 200-400 bytes.  No one has complained about that for coreutils.
While I find it slightly more readable not to insert

"), stdout);
      fputs (_("\

between every pair of adjacent option descriptions, I can understand how
it would be better for a translator if each option-description message
were in a separate diagnostic.

If I were to change all of coreutils' diagnostics as suggested,
it would cause a lot of trouble for only minimal gain.  IMHO,
it's not worthwhile for an established project that already
has many translations.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]