[Rfc-markdown] 1.3.13: Triple brace syntax 🡡 <contact/>, warning for missing brace

Carsten Bormann <cabo@tzi.org> Tue, 06 October 2020 15:47 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98A063A146B for <rfc-markdown@ietfa.amsl.com>; Tue, 6 Oct 2020 08:47:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IUsmfFqd24b5 for <rfc-markdown@ietfa.amsl.com>; Tue, 6 Oct 2020 08:47:21 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A36293A1453 for <rfc-markdown@ietf.org>; Tue, 6 Oct 2020 08:47:21 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc60.dip0.t-ipconnect.de [84.141.204.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4C5MKf6fndzyRG; Tue, 6 Oct 2020 17:47:18 +0200 (CEST)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mao-Original-Outgoing-Id: 623692038.4452749-cca8a1819b322310f32672ba678466dd
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Tue, 6 Oct 2020 17:47:18 +0200
Message-Id: <1632E59F-231E-4FD1-8182-284FC1449903@tzi.org>
To: rfc-markdown@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/7spMIPZdz6S8_NbZZ2WcSB-ScPY>
Subject: [Rfc-markdown] =?utf-8?q?1=2E3=2E13=3A_Triple_brace_syntax_?= =?utf-8?q?=F0=9F=A1=A1_=3Ccontact/=3E=2C_warning_for_missing_brace?=
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Oct 2020 15:47:26 -0000

1.3.13:

{{foo}
(missing final brace) now elicits a warning and is processed like 
{{foo}}

(Thanks to Julian Reschke for pointing me to https://www.ietf.org/id/draft-ietf-quic-http-31.html#section-4.3 as another example why this might be useful; I’ve seen several before.)

Note that the authors of RFC1436, RFC3951, and RFC8569 might now need to add a backslash (if they use {{foo} outside <sourcecode/>); I considered this slight incursion into potentially existing markdown to be acceptable.  Feedback welcome.


While I was fooling around with braces, I also put in some basic syntax for <contact/> in text:

{{{Jürgen Möllemann}}}
and
{{{トヨタ自動車株式会社}{Toyota Jidosha}}}
create contact elements with fullname and optionally asciiFullname attributes:

<contact fullname="Jürgen Möllemann"/>
<contact fullname="トヨタ自動車株式会社" asciiFullname="Toyota Jidosha"/></t>

N.B. I know that the transliteration is wrong, but we don’t have latinFullname, just asciiFullname; I have enquired on rfc-interest why this is so.

(And please note the discussion in <https://mailarchive.ietf.org/arch/msg/rfc-markdown/e9nnRhTVna5zM2wyfa-l-smYUMw> for why I ultimately did go ahead with syntax that remotely reminds one of triple parentheses.)


Update as usual with

	gem update
or just
	gem update kramdown-rfc2629

Grüße, Carsten