Github messages for mblaze
 help / color / mirror / Atom feed
Subject: Re: Problems with special characters using mencrypt and mmime
Date: Thu, 05 Sep 2019 12:43:28 +0200	[thread overview]
Message-ID: <20190905104328.QuRCiOzmybg6rOQTGJG46uv48_aNHHA5kBGs41YRyUY@z> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 369 bytes --]

New comment by Duncaen on mblaze repository

The mail client should decode it, the rfc for mails only allows ascii.

$ echo "\n\naccents: à é" | mmime | mshow /dev/stdin

--- 1: multipart/mixed size=259 ---
--- --- 2: text/plain size=16 ---

accents: à é

  reply	other threads:[~2019-09-05 10:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-05 10:30 [ISSUE] " mblaze-github
2019-09-05 10:43 ` mblaze-github [this message]
2019-09-05 10:58 ` mblaze-github
2019-09-05 10:58 ` mblaze-github
2019-09-05 12:02 ` [ISSUE] [CLOSED] " mblaze-github
2019-09-05 12:02 ` mblaze-github

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190905104328.QuRCiOzmybg6rOQTGJG46uv48_aNHHA5kBGs41YRyUY@z \ \ \

* 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).