[Top][All Lists]

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

LYNX-DEV Make 'raw mode' saveable - why I don't, and other 'raw' topics

From: Klaus Weide
Subject: LYNX-DEV Make 'raw mode' saveable - why I don't, and other 'raw' topics of limited interest to , the Latin-1 majority
Date: Sat, 1 Mar 1997 20:58:10 -0600 (CST)

On Fri, 28 Feb 1997, Hynek Med wrote:

> It works fine. After I failed with the cc compilation, as I wrote before,
> though. The only thing it needs now is the raw mode being saveable - many
> documents are still unmarked, and thus thought as being ISO-8859-1.. :-(

Why I don't make 'raw mode' saveable -

frankly, because I don't know how it works.

Each time I looked at the code in LYCharSets.c and LYOptions.c and
LYReadCFG.c etc. I finally gave up with a headache.  Those variables
LYRawMode, LYDefaultRawMode, LYUseRawModeDefault are just not compatible
with my brain.  They look too similar, I cannot tell them apart.  
There you have my confession.

HTPassEightBitRaw, HTPassEightBitNum, HTPassHighCtrlRaw,
HTPassHighCtrlNum, I think I understand.  They should finally be
replaced by a more general chartrans mechanism, but I left them in
place to fall back to the old behaviour.  (You should get all the old
behaviour if you compile Lynx without -DEXP_CHARTRANS, my patches are
trying to be very conservative.  Which makes the whole thing much more
messy than it needs to be.)

I am not sure what the function of 'raw mode' in a fully charset
translating Lynx should be.  Maybe it would not be not needed at all.
What is it supposed to do?  (Assume I am viewing a document labelled
as iso-8859-5, while Display Character Set is KOI8-R.  What's the
meaning of toggling 'raw mode' or '@'?)

The current behaviour (with chartrans enabled) is probably
inconsistent, because I tried to mimick the existing code, but I feel
the semantics of 'raw' don't translate well when you move from (a) a
Lynx which can either interpret characters as iso-8859-1 or leave them
untouched to (b) a Lynx which can (theoretically) translate any
incoming 8bit charset to any Display Character Set.  If we can agree
on a functional definition of '@', I can try to make the code do what
we want.

That still won't make 'raw mode' (whatever it means) saveable, on
which I have admitted defeat.


; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.

reply via email to

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