Hi, Kalle Olavi Niemitalo, le Mon 11 Dec 2006 23:16:40 +0200, a écrit : > 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.
Yes. > > 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. > > I think an enhancement request about this should be added to > bugzilla.elinks.cz. Ah, the http://links.sourceforge.net/#dev page said to send it to the Links mailing list. > Are you > requesting conversion of unknown charsets in HTTP documents via > iconv (regardless of whether the charset is BRF) That should be the simplest way. Particular support of the BRF charset shouldn't be needed. I submitted the bug. > Are the charset names of iconv generally consistent with MIME? Yes, or at least iconv seems to always recognize MIME charsets. Samuel _______________________________________________ elinks-dev mailing list [email protected] http://linuxfromscratch.org/mailman/listinfo/elinks-dev
