[Rfc-markdown] Triple Parentheses vs. Triple Braces

Carsten Bormann <cabo@tzi.org> Tue, 11 August 2020 14:55 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 318FC3A1141; Tue, 11 Aug 2020 07:55:14 -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 l-yAsGRBNb41; Tue, 11 Aug 2020 07:55:11 -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 EE9ED3A111D; Tue, 11 Aug 2020 07:55:09 -0700 (PDT)
Received: from [192.168.217.116] (p5089ae91.dip0.t-ipconnect.de [80.137.174.145]) (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 4BQwqJ1ZpBzytl; Tue, 11 Aug 2020 16:55:08 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
From: Carsten Bormann <cabo@tzi.org>
Date: Tue, 11 Aug 2020 16:55:07 +0200
Cc: rfc-markdown@ietf.org
X-Mao-Original-Outgoing-Id: 618850507.565647-ab3631712c8eda05694664a5c553eeb5
Content-Transfer-Encoding: quoted-printable
Message-Id: <05A1A64E-E8DD-4F05-BD49-6133A1B6A75F@tzi.org>
To: IETF general list <ietf@ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/e9nnRhTVna5zM2wyfa-l-smYUMw>
Subject: [Rfc-markdown] Triple Parentheses vs. Triple Braces
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, 11 Aug 2020 14:55:22 -0000

For those who don’t know what the subject line is talking about, please have a quick look at:

https://en.wikipedia.org/wiki/Triple_parentheses


ASCIIDOC uses (((term))) as the notation to put “term” into the index at its point  (“concealed index term”), a convention that kramdown-rfc copies for its markdown dialect.  
(I’m not planning to fix anything about this until ASCIIDOC offers a replacement that would fit well with markdown; in any case, I’d only add another convention.
Fortunately, the index functionality of RFCXML is rarely used in RFCs.)

With the rise of RFCXMLv3, now I need a more friendly notation for the construct 

	<contact fullName=“Nguyễn Ái Quốc”/>

Am I a complete idiot to think that {{{Nguyễn Ái Quốc}}} is a good way to express this in kramdown-rfc’s markdown dialect, the above notwithstanding?  
It would never be visible as such in published material, only in the markdown source code.

[Searching RFCs, RFC 6386 contains the line
           union mv          chroma_mv[4] = {{{0}}};
in some source code; triple braces are not used anywhere else that I can find.
For another random example, note that Trac's wiki syntax uses {{{…}}} for monospace/code; but there are usually no names of people in those braces.
Since the slur was only invented in 2014, these notations predate that.]

Alternative notations that avoid the obvious trap, are still as easy to read and type, and don’t create new backwards compatibility nightmares, are expressly solicited.  

Sorry for the cross-posting to ietf@; we don’t have a mailing list for this kind of subject yet.  (In case it wasn’t clear, I’m looking for serious opinions here.)

Grüße, Carsten