Re: w3m -> standard, lynx -> optional

[Andreas Metzler <ametzler@downhill.at.eu.org>]

Petr Baudis <pasky@ucw.cz> wrote:
>  regarding UTF8 support in ELinks, it's not so well but neither so
>  bad.  ELinks can chew pages in Unicode - it recodes them to the
>  terminal charset. It can also handle UTF8 terminals - go to
>  Terminal options and enable UTF8 I/O (it's not very well tested as
>  I personally do not use it but a report comes time by time that it
>  is working).
[...]
>  So, UTF8 I/O outputs stuff in UTF8, but only the subset contained in
> Terminal charset, which is the charset in which the document is kept
> rendered.

I see, that explains it, why there is a dropdown list that allows me to
select any terminal charset but UTF-8 and an additional [ ] enable
UTF8 I/O button. The latter toggles enabling the second iconv in
iconv -f 'webpage-charset' -t 'termcharset' | \
iconv -f 'termcharset' -t UTF-8
                 cu andreas
-- 
Hey, da ist ein Ballonautomat auf der Toilette!
Unofficial _Debian-packages_ of latest unstable _tin_
http://www.logic.univie.ac.at/~ametzler/debian/tin-snapshot/