Re: Feature requests: gettext

Tim Post wrote:
> Hi,
> 
> Just to clarify, this is from NBSD getopt:
> 
> static const char recargchar[] = "option requires an argument -- %c";
> static const char recargstring[] = "option requires an argument -- %s";
> static const char ambig[] = "ambiguous option -- %.*sn";
> static const char noarg[] = "option doesn't take an argument -- %.*sn";
> static const char illoptchar[] = "unknown option -- %cn";
> static const char illoptstring[] = "unknown option -- %sn";
> 
> FBSD, OBSD are similar, just longer to account for various GNU getopt
> compatibility.
> 
> This is why I say the output would be (at best) mixed on many systems
> when adding gettext. The above strings are expanded by warnx(), which
> does not use gettext.
> 
> I really think this could introduce more porting headaches for
> gengetopt, without much of a pay off.
> 

 From what I understand, it's better not to add this feature, isn't it? :-)

-- 
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134     (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com  http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net