What is the best way to fix bug 777 (UTF-8-encoded control sequences)?

Bug 777 - UTF-8 should be parsed before control sequences
http://bugzilla.elinks.cz/show_bug.cgi?id=777

I have listed there three ways to fix the bug:

> (a) Decode both the UTF-8 and the control sequences in the slave
>     process.  The master would then have to tell the slave
>     whether to expect UTF-8 or not.
> (b) Decode both the UTF-8 and the control sequences in the
>     master process.
> (c) Decode the UTF-8 in the slave process and the control
>     sequences in the master process.  (This is the opposite of
>     the current scheme.)

Which of them would you prefer?  Please comment.

I would also like to have unicode_val_T in struct
term_event_keyboard.  This would make it possible to bind actions
to arbitrary Unicode characters.  Functions like kbd_field() that
store user input into a character array would then convert to
UTF-8 and insert only if all bytes fit.  The values of KBD_ENTER
and other such macros would have to be changed.  I think this
part could be implemented before changing the control sequence
parser.

_______________________________________________
elinks-dev mailing list
[email protected]
http://linuxfromscratch.org/mailman/listinfo/elinks-dev

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFEzKfmHm9IGt60eMgRAt+6AKDh1dZpSxaj34Nz9a6vm2OjyPX5OACeOCXF
WlM0D0MHoEXxutGimZ7tgFc=
=4UBc
-----END PGP SIGNATURE-----