On Sun, 11 Jan 2026, Andreas Mohr wrote:
>On Sun, Jan 11, 2026 at 08:35:13PM +0100, Thorsten Glaser wrote:
>> On Sun, 11 Jan 2026, Andreas Mohr via Lynx-dev wrote:
>>
>> >- "outer-scope" MIME multi-part attribution is utf-8
>>
>> You can ignore that.
>
>For purposes of document scope, indeed.
>
>One could argue that
>a MIME attribution could be made to
Yes, but not the attribute on the multipart/ object itself
(which should not have one), only the one on the part.
>The only complaint remaining might be that lynx perhaps is not flexible
>enough to offer applying trainwreck post-mortem workaround/bending.
This, yes.
>> For your scenario of…
>>
>> >- mailcap entry
>> > text/html; lynx -assume_charset=%{charset} -display_charset=utf-8
>> > -collapse_br_tags -dump %s; nametemplate=andi_%s.html; copiousoutput
>>
>> … you could do something like…
>>
>> text/html; <%s perl -0pe
>> 's!<meta\s+http-equiv="Content-Type"\s+content="[^"]*"\s*/?>!!ig;' | lynx
>> -assume_charset=%{charset} -display_charset=utf-8 -collapse_br_tags -dump
>> -stdin; nametemplate=andi_%s.html; copiousoutput
>>
>> … to automatically remove such charset declaration.
>
>Ah, right, or possibly some sed -e 's/...' alter{c|n}ation...
That is basically sed but multiline-capable (some authors like
to put newlines in the midst of tags, e.g. Frontpage Expreß;
don’t ask me how I know), and perl is in base anyway, so it’s
a good tool to do this.
The RE I used won’t catch if the user uses a different order
or adds extra attributes, but it’ll match case-insensitively
at least, and I suspect your broken files come from only one
sender software anyway, which is unlikely to deviate from
this template.
>> (EN: “[…]uhr.gz is a reason to install mksh on every system.”)
>
>Oh wow indeed!
You’re welcome :þ
bye,
//mirabilos
--
"Using Lynx is like wearing a really good pair of shades: cuts out
the glare and harmful UV (ultra-vanity), and you feel so-o-o COOL."
-- Henry Nelson, March 1999
