Re: BRF charset support

Samuel Thibault <[email protected]> writes:

> I would expect links to output braille patterns when browsing it, but it
> doesn't recognize the BRF charset (though it is supported by my debian's
> glibc's iconv) and links considers the text to be latin1, hence the
> result is "A B C".

BRF charset support was added to iconv in Debian glibc 2.3.6-11
on 2006-05-30.  So it's rather new.

> When links doesn't know a charset, it should ask iconv in case the latter
> is able to convert into unicode, and then links could display it like any
> unicode text.

That seems like an excellent idea, if the alternative is to treat
the text as ISO-8859-1.  Such a change seems to complex for the
forthcoming ELinks 0.12 branch, however.  It could perhaps get in
0.13 if there is spare time.

I think an enhancement request about this should be added to
bugzilla.elinks.cz.  I can do that if you don't want to.  Are you
requesting conversion of unknown charsets in HTTP documents via
iconv (regardless of whether the charset is BRF) or support for
the BRF charset (regardless of whether iconv supports it)?  If
both, I think they should be separate requests.

Are the charset names of iconv generally consistent with MIME?

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

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

iD8DBQFFfcrJHm9IGt60eMgRArnJAKDb8MeO/Iwp9R19dJgjLjzFWo8vbgCg3QGa
Arq4NplxRyHFBYc6IiSBy78=
=nI6u
-----END PGP SIGNATURE-----