[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev Re: lynx2.8.4dev.2.patch.gz

From: Henry Nelson
Subject: Re: lynx-dev Re: lynx2.8.4dev.2.patch.gz
Date: Mon, 3 Jul 2000 10:07:44 +0900 (JST)

> It is almost trivial, IMHO.

So you believe the documentation for installing message catalogues by
the autoconf method which is included in the Lynx distribution is adequate?

> for me, it is not an easy method.  It seems to me that you claim
> everyone should follow your method and if so you should explain

I have never "claim[ed that] everyone should follow" the GNU gettext method.
For me it is easier than using the Lynx-specific one.  For example, if I
change two translation strings, I can re-compile and install the .mo file
with one alias, and use the new messages immediately.  How do you do that
with the autoconf method?

> the reason much more explicitly (not only saying you dislike it).

To repeat myself:
 1)  I like to have a gettext/libintl environment that is consistent
     among all programs I use.  Preinstalling the gettext package and
     building all other packages with --without-included-gettext ensures
     that that will be the case.
 2)  I do not want to waste my cpu time rebuilding the gettext tools and
     library every time I build Lynx.
 3)  Not every machine I build Lynx on has enough disk space to waste on
     things I don't need (po files, source code for gettext tools and lib). 
 4)  I do not agree with the philosophy of distributing packages within
     packages when the sub-package is just a clone that can be gotten
     separately from the main package.  I approach gettext exactly the same
     way I approach gcc, zlib, slang, ncurses, libbind and any of the other
     programs/libraries I use to build or enhance Lynx.


; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]