Bug#271834: lynx: mailcap text-formatting entry neither honors file charset nor recognizes locale
On 2004-09-15 Ilya Anfimov <tzirechnoy@hotpop.com> wrote:
[...]
> grotty:<standard input>:5: character above first line discarded
> Current lynx mailcap entry doesn't take info on charset of the
> document when it is possible. It leads to weird results when
> charset is specified only in MIME message headers, and not in the
> html file itself.
> Better strings could be:
> text/html; /usr/bin/lynx -dump -force_html %s -display_charset "`locale charmap`" -assume_charset %{charset}; copiousoutput; description=HTML Text; nametemplate=%s.html
> text/html; /usr/bin/lynx -force_html %s -assume_charset %{charset}; needsterminal; description=HTML Text; nametemplate=%s.html
Hello,
Afaict that would break if there was no charset specified in the MIME
message headers.
> grotty:<standard input>:5: character above first line discarded
> Also note, that option LOCALE_CHARSET:TRUE would be better than
> -display_charset "`locale charset`", but i didn't found it in
> command line parameters of lynx, and it is not turned on by de-
> fault, unfortunately.
[...]
LOCALE_CHARSET is nowadays enabled by default, so at least this part
of the report is fixed.
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
Reply to: