From 8ac7a240edeb28229cb5afe722484462703f9b4e Mon Sep 17 00:00:00 2001 From: Andre Heinecke Date: Fri, 7 Sep 2018 15:44:33 +0200 Subject: [PATCH] Add optional charset specification --- middle.mkd | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/middle.mkd b/middle.mkd index 9e5bb58..1347aea 100644 --- a/middle.mkd +++ b/middle.mkd @@ -3074,6 +3074,9 @@ The cleartext signed message consists of: - Exactly one blank line not included into the message digest, + - Optionally a "Charset" Armor Header followed by one blank line, + both included in the message digest, + - The dash-escaped cleartext that is included into the message digest, @@ -3090,6 +3093,15 @@ contains a comma-delimited list of used message digests. Current message digest names are described below with the algorithm IDs. +If the "Charset" Armor Header is given, the specified message is +to be expected in that encoding. If the Header is omitted an +implementation SHOULD try to guess the charset from the context +of the message. For example by using the systems local 8 bit +charset or checking for the content-type in a MIME context. + +An implementation MAY assume UTF-8 encoding in case the "Charset" +Header is omitted. + An implementation SHOULD add a line break after the cleartext, but MAY omit it if the cleartext ends with a line break. This is for visual clarity. -- 2.11.0