lynx-dev
[Top][All Lists]
Advanced

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

Re: lynx-dev some proposed nit fixes in lynx.cfg


From: Leonid Pauzner
Subject: Re: lynx-dev some proposed nit fixes in lynx.cfg
Date: Sat, 7 Nov 1998 21:04:43 +0300 (MSK)

Thanks!

The only new problem can be introduced by "raw CJK mode".

Exact meaning should be:
1) when the document's charset specified explicitely -
it always converts to display character set.
2) when the document's charset not specified explicitely
ASSUME_CHARSET get in effect. There is a special case: Asian (CJK)
display character sets, for which the corresponding charset is
assumed in documents, i.e., we introduce `CJK mode' or `raw mode'...
....


> --- lynx.cfg-dist     Fri Nov  6 09:29:41 1998
> +++ lynx.cfg-new      Sat Nov  7 11:07:49 1998
> @@ -175,17 +176,19 @@
>  # language or group of languages besides MIME name).  Not all 
> 'human-readable'
> -# names correspond to exactly one valid MIME charset (example is "Chinese"), 
> in
> -# that case an appropriate valid (and more specific) MIME name should be used
> -# where required.  Well-known synonyms are also processed in the code.
> -#
> -# Lynx normally translates characters from document's charset to display
> -# charset, using ASSUME_CHARSET value (see below) if document's charset is 
> not
> -# specified explicitly.  There is the so called `raw or CJK mode' which is 
> OFF
> -# for this case. (When the document charset specified explicitly
> -# it override any assumption like ASSUME_CHARSET or raw or CJK mode).
> +# names correspond to exactly one valid MIME charset (example is "Chinese");
> +# in that case an appropriate valid (and more specific) MIME name should be
> +# used where required.  Well-known synonyms are also processed in the code.
> +#
> +# Raw (CJK) mode
> +#
> +# Lynx normally translates characters from a document's charset to display
> +# charset, using ASSUME_CHARSET value (see below) if the document's charset
> +# is not specified explicitly.  Raw CJK mode is OFF for this case.
> +# When the document charset is specified explicitly, that charset
> +# overrides any assumption like ASSUME_CHARSET or raw CJK mode.
>  #
> -# For the Asian (CJK) display character sets the corresponding charset is
> -# assumed in documents, i.e., raw or CJK mode is ON by default.  In raw CJK
> +# For the Asian (CJK) display character sets, the corresponding charset is
> +# assumed in documents, i.e., raw CJK mode is ON by default.  In raw CJK
>  # mode, 8-bit characters are not reverse translated in relation to the entity
>  # conversion arrays, i.e., they are assumed to be appropriate for the display
> -# character set.  It should be toggled OFF when an Asian (CJK) display
> +# character set.  The mode should be toggled OFF when an Asian (CJK) display
>  # character set is selected but the document is not CJK and its charset not
> @@ -193,6 +196,6 @@
>  #
> -# The `raw or CJK mode' may be toggled by user via '@' (LYK_RAW_TOGGLE) key,
> -# with -raw command line switch or from 'o'ptions menu.
> +# Raw CJK mode may be toggled by user via '@' (LYK_RAW_TOGGLE) key,
> +# the -raw command line switch or from the 'o'ptions menu.
>  #
> -# Raw mode effectively changes the charset assumption about unlabeled
> +# Raw CJK mode effectively changes the charset assumption about unlabeled
>  # documents.  You can toggle raw mode ON if you believe the document has a



reply via email to

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