[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev chartrans question
|
From: |
Klaus Weide |
|
Subject: |
Re: lynx-dev chartrans question |
|
Date: |
Fri, 12 Feb 1999 05:50:46 -0600 (CST) |
On Thu, 11 Feb 1999, Leonid Pauzner wrote:
> docs/README.chartrans:
> [...]
> - The "Raw" toggle (from -raw flag, '@' key, or Options screen)
> o toggles the assumption "Default remote charset is same as Display
> Character Set" on or off.
> Toggling of the assumed charset is between Display Character Set and
> the specified ASSUME_CHARSET or, if they are the same, between the
> specified ASSUME_CHARSET and ISO-8859-1.
> o The default for raw mode now depends on the Display Character Set as
> well as on the specified ASSUME_CHARSET value.
> o should work as before for CJK charsets (turning CJK-mode on or off).
> o If the effective ASSUME_CHARSET and the Display Character Set are
> unchanged from the ISO-8859-1 default, toggling "Raw" may have some
> additional effect for characters that can't be translated.
> ^^^^^^^^^^^^^^^^^???
> (Try the "Transparent" Display Character Set for more "rawness".)
> [...]
>
> What is the "additional effect" of toggling Raw mode
> when both display charset and assume_charset are iso-8859-1 ?
Good question. If I remember right, it had something to do with
one or more of the global flags HTPassEightBitRaw etc. It may not
apply any more. Maybe I can find some old examples.
Klaus