[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [help-gengetopt] Feature requests: gettext
From: |
Tim Post |
Subject: |
Re: [help-gengetopt] Feature requests: gettext |
Date: |
Mon, 01 Sep 2008 02:27:32 +0800 |
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.
Cheers,
--Tim
--
Monkey + Typewriter = Echoreply ( http://echoreply.us )