[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev including/excluding charsets (was: CPU problems connecting
Re: lynx-dev including/excluding charsets (was: CPU problems connecting to a site)
Mon, 30 Aug 1999 10:36:09 -0400 (EDT)
> > > Is the opposite logic possible, include all _but_ the following?
> On Sun, 29 Aug 1999, T.E.Dickey wrote:
> > it's doable - not as written, but making similar logic -
> > but I thought the small-subset was more useful.
> Well, having to list all charsets to be included requires the users
> (installer) to know which are necessary for reasonable operation. A
> lot of folks using this feature may get that wrong. I *think* without
> at least iso-8859-1, us-ascii, utf-8 (maybe also x-transparent) listed
> there will be some "interesting" failure modes (not lynx crashing or
> hanging, but lynx rendering entities etc. in weird ways).
us-ascii is always listed because of the way the ifdef's are constructed.
> Maybe there should be a --with-charsets=minimal, where minmal is
> equivalent to a list of charsets (yet to be determined exactly) that
> are required for minimal "reasonable" behavior.
something like that, perhaps
Thomas E. Dickey
- Re: lynx-dev including/excluding charsets (was: CPU problems connecting to a site),