Re: BRF charset support

Kalle Olavi Niemitalo, le Tue 12 Dec 2006 09:53:18 +0200, a écrit :
> This elinks-dev mailing list is for the ELinks variant.  I don't
> know whether the developers of the original Links read this list.

Ah. So I don't know how to report bugs to Links people :)

> It is good to discuss changes, but if they are not going to be
> made immediately, I find it is easier to keep track of them and
> schedule them for releases if they are in the Bugzilla as well.

As I said, I submitted it in the bugzilla.

> Am I correct in assuming you don't need ELinks to support using
> iconv-based charsets for:
> - I/O with the user's terminal.

This is transparently handled by the brltty daemon.

> (Using BRF like this would require binding ELinks actions to Unicode
> Braille characters, and you'd be unable to type slashes in file names
> and URIs.)

This is transparently handled by the brltty daemon (it synthesizes key
presses at the kernel level).

> - encoding form data in HTTP POST requests.

I'm not sure what you mean by this.  I guess you're talking about the
data that a blind user would type in forms.  This is transparently
handled by the brltty daemon (just like above).

You _don't_ need to have to care about braille terminals yourself. Just
use iconv for converting from BRF to whatever you prefer for your own
internal stuff (wchar_t for instance), and then output UTF-8 braille
patterns.  That will be just fine.

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