[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
lynx-dev x-transparent (was Re: CJK broken in Lynx 2.8.2dev.17)
From: |
Klaus Weide |
Subject: |
lynx-dev x-transparent (was Re: CJK broken in Lynx 2.8.2dev.17) |
Date: |
Wed, 10 Mar 1999 09:20:25 -0600 (CST) |
On Tue, 9 Mar 1999, Leonid Pauzner wrote:
> 9-Mar-99 20:40 Nelson Henry Eric wrote:
>
> > I have no recollection of when or why "Transparent" got into my
> > lynx.cfg file. "x-transparent" does not work, either, however.
"Transparent" probably acts like "Blahblah" when used as an
ASSUME_CHARSET, it's unrecognized as a MIME charset name, in contrast
to "x-transparent". None of them are really registered charsets of
course.
> IMO, x-transparent may be useful for "display charset" to see everything
> "raw",
> but seems useless for "document charset" of any kind. No?
The idea was that translating x-transparent -> any-display-charset
should more or less have the same effect as any-MIME-charset ->
"Transparent". Not that I thought this very useful, but the
simplifying assumption that every possibly display character sets
(even a pseudo one like "Transparent") corresponds to one MIME charset
made it necessary to have *some* behavior if this pairing occurs, and
this seemed to be the most logical choice.
Klaus