From: Lars Ingebrigtsen <larsi@corrigan.gnus.org>
To: f.nikolakopoulos@gmail.com
Cc: info-gnus-english@gnu.org
Subject: Re: gnus eml attach
Date: Wed, 11 Apr 2018 00:12:34 +0200 [thread overview]
Message-ID: <878t9u678t.fsf@mouse.gnus.org> (raw)
In-Reply-To: <ovlp4c$i6s$1@blaine.gmane.org> (f. nikolakopoulos's message of "Wed, 29 Nov 2017 09:55:02 +0200")
f.nikolakopoulos@gmail.com writes:
> On mml definitions when I add an attachment with C-c C-a I will need
> also to add the charset like
>
> Now the output of C-c C-a is:
> <#part type="application/pdf" filename="~/foo.pdf" disposition=attachment>
> <#/part>
>
> I will need when I press C-c C-a:
> <#part charset="utf-8" type="application/pdf" filename="~/foo.pdf"
> disposition=attachment>
> <#/part>
Non-text parts are binary (i.e., octet streams) and don't have a
charset, so I don't think this would be correct...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2018-04-10 22:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 7:55 f.nikolakopoulos
2018-04-10 22:12 ` Lars Ingebrigtsen [this message]
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=878t9u678t.fsf@mouse.gnus.org \
--to=larsi@corrigan.gnus.org \
--cc=f.nikolakopoulos@gmail.com \
--cc=info-gnus-english@gnu.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).