> > Is there any way to have it use the system's native gettext libraries
> > instead of building and using the src/intl included with the source?
>
> Not at the moment, and it is certainly not planned. Gettext has been
> changed to integrate better with ELinks: it uses the ELinks memory
> functions, has some specific wrappers etc.
>
> There is a bugzilla entry which is currently marked WONTFIX. Pasky's
> last remarks are:
>
> Our instance of libgettext is *heavily* customized and it is
> expected to get even more customized by the time, so using
> system gettext routines is not really feasible.
>
> - http://bugzilla.elinks.or.cz/show_bug.cgi?id=537
>
> > Any patches to check for adequate gettext and use it if available?
>
> I do not know of such patches.
>
> > If not, would you be interested if used commonly-used autoconf to check
> > this?
>
> Patches are always welcome, but I do not really see a reason. Is gettext
> really that big?
>
> > (I also found that the Makefile system used in buildling elinks is
> > different than I am used to when using autoconf configure.)
>
> Yes, we changed to using a GNU make based build system instead of
> automake, since ELinks has a lot of build-time options that caused
> automake to generate huge makefiles because conditional are badly
> implemented. Sad, but having a Makefile taking several megabytes of
> storage is crazy.
Thank you for the information.
I didn't realize that your gettext was heavily customized. I only thought
it was provided just in case some platforms didn't have any adequate
gettext/libintl.
My problem is that it installs or modifies
${PREFIX}/share/locale/locale.alias.
Does it really need this locale alias mapping file? Can't it just use what
is provided by native system?
As far as I can tell with building and installing hundreds of programs
from source (and many that use gettext / libintl) nothing else on my
system create or modify this ${PREFIX}/share/locale/locale.alias. Note I
have a system /usr/share/locale/locale.alias that is used.
So I now see the only difference is that elinks provides its own gettext.
Since elinks provides its own maybe it can be have "elinks" as part of the
name. Or maybe it can be coded to just use the systems' own version.
Either way, this could be changed in read_alias_file() in
src/intl/gettext/localealias.c.
Probably not very important now that I understand some background on this.
Thanks again, Jonas, for the info.
_______________________________________________
elinks-dev mailing list
[email protected]
http://linuxfromscratch.org/mailman/listinfo/elinks-dev
