[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
|
From: |
Leonid Pauzner |
|
Subject: |
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 |
|
Date: |
Sun, 15 Aug 1999 22:43:51 +0400 (MSD) |
12-Aug-99 06:01 Vlad Harchev wrote:
> See diffs for lynx.cfg (5 lines lower than this) for more description.
> Seems this is useful for not-only-English-speaking people, that use
> documents in languages for which several encodings exist - they have to
> change "assumed doc chset" 'O'ption's field very often (since not all page
> authors are worried about inserting proper charset info in the <HEAD>).
> Primitive pattern matching will make the things even better (like
> ASSUMED_DOC_CHSET_CHOICE:arabic* - only all arabic encodings - that have full
> name begining with "arabic" - will be selected).
The implementation looks rather dirty. But see below.
> PS: Tested with '-form-options-' too. All wrapped in conditionals. No
> commandling equivalent exists.
> Best regards,
> -Vlad
> diff -ru lynx2-8-3dev6-orig/lynx.cfg lynx2-8-3dev6/lynx.cfg
> --- lynx2-8-3dev6-orig/lynx.cfg Wed Aug 11 19:07:40 1999
> +++ lynx2-8-3dev6/lynx.cfg Thu Aug 12 05:46:03 1999
> @@ -340,6 +340,35 @@
> #
> #ASSUME_CHARSET:iso-8859-1
> +# It's possible to reduce the number of charset choices in the 'O'ptions menu
> +# for "display charset" and "assumed document charset" fields via
> +# DISPLAY_CHSET_CHOICE and ASSUMED_DOC_CHSET_CHOICE settings correspondingly.
> +# Each of these settings can be used several times to define the set of
> possible
> +# choices for corresponding field. The syntax for the values is
> +# string | prefix* | <ALL>
> +# Where
> +# * 'string' is either the MIME name of charset or it's full name (listed
> +# either in the left or in the right column of table of recognized charsets),
> +# case-insensitive - e.g. 'Koi8-R' or 'Cyrillic (KOI8-R)' (both without
> quotes),
> +# * 'prefix' is any string, and such value will select all charsets having
> the
> +# name with prefix matching given (case insensitive), ie for the charsets
> +# listed in the table of recognized charsets,
> +# ASSUMED_DOC_CHSET_CHOICE:cyrillic*
> +# will be equal to specifying
> +# ASSUMED_DOC_CHSET_CHOICE:cp866
> +# ASSUMED_DOC_CHSET_CHOICE:windows-1251
> +# ASSUMED_DOC_CHSET_CHOICE:koi8-r
> +# ASSUMED_DOC_CHSET_CHOICE:iso-8859-5
Do you say several ASSUMED_..._CHOICE lines possible? Why not a list?
Would this be resetted with reload_read_cfg() ?
> +# 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).