Re: lynx-dev 8-bit chars and LYgetstr

[Laura Eaves]

> From: "Leonid Pauzner" <address@hidden>
> Date: Sun, 14 Feb 1999 14:22:59 +0300 (MSK)
>...
> I still do not understand _why_ you have the problem,
> I have no problem with cp866 display charset which is not iso-8859-1.
> Supposedly the problem outside of Lynx.

As far as I can tell the problem is in lynx...
To test this I tried planting some CTRACE statements in LYStrings.c.
I then ran lynx, typed / then alt231 space alt135 ENTER.
The trace output showed:

                Lynx Trace Log (2.8.2dev.16)

User message: Trace ON!
LYEdit1(): ch=231 action=1
LYEdit1:adding ch=231 Pos=0 StrLen=0 MaxLen=511
LYEdit1(): ch=32 action=1
LYEdit1:adding ch=32 Pos=1 StrLen=1 MaxLen=511
LYEdit1(): ch=271 action=0
LYEdit1(): default: ch=271
User message: 'ç ' not found!
...

When and where is the char 135 getting translated to 271?
I'll continue poking...

> Extremely bad idea to have default mapping for any actions from 128..256 
> range,
> we will fall into all kind of incompatibility between ~40 lynx recognized
> charsets.  Aside from "actions" mapping, text input should be 8bit clean
> for all valid characters as it is believed implemented now.

I agree.
--le