On Fri, 05 Apr 2002 15:26:46 Guy Harris wrote:
> Unfortunately, it appears that the first step involved in making the
> source support gettext is to convince everybody who uses the CVS version
> either to
>
> 1) install gettext (which may be a pain for some of us; we might
> have to install it in a private directory, *and* arrange that
> autoconf etc. pick stuff up from that private directory)
>
> or
>
> 2) stop using it.
>
> The problem is that once the autoconf scripts start depending on
> something, you can't build them - and thus can't develop from the CVS
> version - without that something.
>
> The fact that they depend on GTK+ has *already* been a problem for some,
> as I remember, as it prevented them from building from CVS on a machine
> that had GLib but not GTK+ installed.
Does this mean that there will be absoluteley no support for other languages?
Are there any other ways to translate interface without gettext support?
Does an option of translatability (to potentially any language)
outweigh the trouble of having to use gettext?
Is it such a pain to install gettext?
Don't get me wrong, I am not trying to impose on anyone.
I am just probing the options of having translations of a great package
without harming anyone's interests.
By the way, isn't it possible to just include the source of gettext into
ethereal? Would this get rid of unwanted dependency? Would this insanely
increase the size of ethereal?
--
Alexander Roitman
Dept. of Neuroscience, Lions Research Building
2001 6th Street SE, Minneapolis, MN 55455
Tel (612) 626-7280 FAX (612) 626-9201
