Re: document writing/editing tools used by IETF

Carsten Bormann <cabo@tzi.org> Sat, 27 February 2021 20:13 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 277CC3A13AC for <ietf@ietfa.amsl.com>; Sat, 27 Feb 2021 12:13:34 -0800 (PST)
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_H3=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 OBjfMbUsPFkW for <ietf@ietfa.amsl.com>; Sat, 27 Feb 2021 12:13:31 -0800 (PST)
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 5B12B3A13AA for <ietf@ietf.org>; Sat, 27 Feb 2021 12:13:31 -0800 (PST)
Received: from [192.168.217.123] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (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 4DnyQK6KnNz105M; Sat, 27 Feb 2021 21:13:29 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Subject: Re: document writing/editing tools used by IETF
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAMm+LwhXzcPVwtYNk5R3k_=r6gP04dg+pgxZ0VLmBiDHYvqXOA@mail.gmail.com>
Date: Sat, 27 Feb 2021 21:13:29 +0100
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-Mao-Original-Outgoing-Id: 636149608.442373-c7388001445a53f86356fca6ea40de22
Content-Transfer-Encoding: quoted-printable
Message-Id: <3AFC2824-25AB-4472-90C5-4695FD61CD34@tzi.org>
References: <37eecb9b-f0eb-e21c-b162-b1f0339e4981@si6networks.com> <3c2d646d-f18d-4d88-b458-29dbd486432b@beta.fastmail.com> <446A8D6B-E624-49E0-B67E-D1F8AFC794E2@lastpresslabel.com> <28ac1e86-f641-b9e8-0f61-6ff442feaa90@si6networks.com> <LO2P265MB057322BA95B1B44D4175356BC29E9@LO2P265MB0573.GBRP265.PROD.OUTLOOK.COM> <089096b1-10d2-3eac-d37c-f040a1930061@network-heretics.com> <37142313-C251-40DC-9336-D3A2F0FB69AD@tzi.org> <001d01d70be3$ff0972d0$fd1c5870$@acm.org> <CAMm+LwhkLTKkp3q4s97TBA-=WpJPof861mygPSjJttowpDjGuw@mail.gmail.com> <8b42a18a-181e-cad7-7333-3e950e643665@gmx.de> <C51C3823-59DA-4E61-B3A9-968BA355EEE2@depht.com> <DM6PR02MB692412D75E013F8EC314DAC6C39D9@DM6PR02MB6924.namprd02.prod.outlook.com> <CAMm+LwhOqy2MCmAY5eO2OcpkM99UOS7A5hJaj+thA3SuO+g8FA@mail.gmail.com> <48263A88-E146-4484-8031-BE410C146EE0@tzi.org> <CAMm+LwhXzcPVwtYNk5R3k_=r6gP04dg+pgxZ0VLmBiDHYvqXOA@mail.gmail.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/msV7rpSFJedwOYLfa0WjaW_yH6M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Feb 2021 20:13:40 -0000

>> > 
>> > pandoc markdown used by Carsten's tool
>> 
>> That would be a different tool.
>> 
>> Kramdown-rfc is based on kramdown, one of the longstanding well-established markdown parsers.
>> (Its github history reaches back 12 years to 2008, and it already was an established project by then.  
>> By the way, kramdown is a Patreon creator — if you like kramdown-rfc, you may want to consider becoming a patron to its parent project.)
>> 
> With respect, we are both mistaken on this.

???

You Keep Using That Word “pandoc", I Do Not Think It Means What You Think It Means

> The plaintext escape on github is ''''
> The plaintext escape in pandoc is ~~~~

The pandoc markdown support took the tilde style from the then prevalent way of writing fenced code blocks, which was introduced as an alternative to indicating code blocks by simply indenting them at least 4 spaces in the original markdown spec [1].

[1]: https://daringfireball.net/projects/markdown/syntax#precode

Github flavored markdown introduced code blocks fenced with three (!) backticks (!); I don’t know why they saw a need to change the custom(*); maybe they couldn’t be motivated to keep holding the shift key for three key presses, or nobody at github took the effort to study the current custom.

Grüße, Carsten

(*) I’m saying “custom”, but really it was the “standard”, except that we are using this word in a different meaning.