> > I think it is a *bad* idea to make getopt depend on gettext
> > unconditionally.
>
> Is this because groff uses getopt but not gettext?
Exactly. Adding gettext support to groff would be nice, but until now
it hasn't happened.
> What about the other gnulib modules that depend on gettext? He
Werner LEMBERG <[EMAIL PROTECTED]> writes:
> I think it is a *bad* idea to make getopt depend on gettext
> unconditionally.
Is this because groff uses getopt but not gettext?
What about the other gnulib modules that depend on gettext? Here is a
list. Shouldn't they be in the same category as g
I think it is a *bad* idea to make getopt depend on gettext
unconditionally. I suggest a patch similar to the one below.
BTW, Nelson Beebe tested a prerelease of groff 1.19.2 on his zoo of
Unix platforms. He writes:
Builds with C++ compilers fail in compiling getopt.c; it is too bad
that t
