Re: lynx-dev 8-bit chars and LYgetstr

[Leonid Pauzner]

14-Feb-99 00:29 Laura Eaves wrote:
> Sifting through the ifdef soup in LYStrings.c and the line edit bindings in
> LYEditmap.c, it appears lynx is hardcoded to recognize only ISO-8859-1 on
> input strings.  (This includes WHEREIS strings, goto buffer input, and form
> text entry.)
> This explains why my alt135 example doesn't work.  My display charset is 
> cp437,
> not ISO-8859-1.

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.

> This is wrong and should really be fixed before 2.8.2.
> The question is, what should the behavior be?
> How should lynx edit bindings respond to different display charsets?
> Should commands for actions such as erase, enter, etc, have the same key
> bindings for all charsets (like it is now)?  What about chars >= 128?

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.

> Comments welcome.
> --le