From: ashiire <ashiire@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] mshow: unknown charset of extracted attachments
Date: Fri, 18 Aug 2023 21:17:06 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-248@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 923 bytes --]
New issue by ashiire on mblaze repository
https://github.com/leahneukirchen/mblaze/issues/248
Description:
When extracting attachments via `mshow`'s `-x` or `-O` flags, any present charset information is lost. This is troublesome, as charset information is difficult to infer from file contents alone.
`mshow` does explicitly mention attachment charset in render mode if a filter is used to render the attachment, like so:
`--- --- --- 3: text/plain size=235 charset="iso-8859-2" render="mshow-plaintext" ---`
However, this seems like the wrong (and inconvenient) place to recover the information from.
I have a two ideas that might help:
* (Add an option to) explicitly state charset information in list mode, if available.
* Add an option to automatically re-encode extracted attachments to UTF-8, same as in render mode.
I think that either one would be sufficient on its own, but both may be desirable.
next reply other threads:[~2023-08-18 19:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 19:17 ashiire [this message]
2023-08-21 15:47 ` leahneukirchen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-248@inbox.vuxu.org \
--to=ashiire@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).