[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev [PATCH 2.8.3.dev6] patch that allows user to define what
Re: lynx-dev [PATCH 2.8.3.dev6] patch that allows user to define what charsets will appear in "assumed doc chset" and "display chset" popups
Sat, 14 Aug 1999 11:37:32 +0500 (SAMST)
On Sun, 15 Aug 1999, Leonid Pauzner wrote:
> 12-Aug-99 06:01 Vlad Harchev wrote:
> Do you say several ASSUMED_..._CHOICE lines possible? Why not a list?
> Would this be resetted with reload_read_cfg() ?
Yes, several ASSUMED_ ... _CHOICE are allowed. This approach simplifies
parsing (so now I rely on parsing by LYReadCFG.c) and allows choices to be
added in the INCLUDEd files.
This won't work with reload_.. (I mean all new changes to lynx.cfg will be
lost) - but this is easy to fix. Currently new changes will be ignored (the
info will be gathered, but final routine won't be called).
I will fix it in the end of August (Now I have only hyphenation on my TODO
> > +# or lines with full names of charsets.
> > +# * litteral string '<ALL>' (without quotes) will enable all charset
> > choices in
> > +# corresponding field. This is useful for overriding site defaults in
> > private
> > +# pieces of lynx.cfg included via INCLUDE directive.
> > +# Default values for both settings are <ALL>, but any occurance of
> > settings with
> > +# values that denote any charsets will make only listed choices available
> > for
> > +# corresponding field.
> > +#ASSUMED_DOC_CHSET_CHOICE:<ALL>
> > +#DISPLAY_CHSET_CHOICE:<ALL>
> Display charsets list may need "us-ascii" as a special case;
> both Display charsets list and assumed charsets list may need "x-transparent"
> also. (few users will be aware of it but this is a key in case of problems).
We can advice including them in the lynx.cfg comment, rather then including