Re: [Tools-discuss] what revision of markdown for IETF?

Carsten Bormann <cabo@tzi.org> Tue, 22 June 2021 19:15 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABF1D3A13A4 for <tools-discuss@ietfa.amsl.com>; Tue, 22 Jun 2021 12:15:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_FAIL=0.001, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 YynBVbCTmc47 for <tools-discuss@ietfa.amsl.com>; Tue, 22 Jun 2021 12:15:31 -0700 (PDT)
Received: from gabriel-2.zfn.uni-bremen.de (gabriel-2.zfn.uni-bremen.de [IPv6:2001:638:708:32::19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 394553A13A2 for <tools-discuss@ietf.org>; Tue, 22 Jun 2021 12:15:31 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4G8bhH0m3Vz2xJ9; Tue, 22 Jun 2021 21:15:27 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <25460.1624388436@localhost>
Date: Tue, 22 Jun 2021 21:15:26 +0200
Cc: tools-discuss@ietf.org
X-Mao-Original-Outgoing-Id: 646082126.481926-3b9cb92e19a1ebdd293c7f8f63b695ec
Content-Transfer-Encoding: quoted-printable
Message-Id: <B9FABF7B-55CD-4C63-97E1-6B39E285E1EE@tzi.org>
References: <25460.1624388436@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/aTKGKKkfZpAGuL9QfrnclF0shY0>
Subject: Re: [Tools-discuss] what revision of markdown for IETF?
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jun 2021 19:15:37 -0000

Revision is a word that can be used to describe steps in an orderly, linear editing process.
I don’t know how that word got into the same mail as the word markdown…

Tables weren’t part of the original markdown spec.
This was quickly fixed in the then dominant PHP markdown implementation (the name of which I forget), but other tools have implemented deviant versions of that.
Most notorious is github, which requires all-pipe vertical lines for detection (no plus signs as with everyone else).
John Gruber abandoned markdown, and commonmark came a bit late.
The rest is history.

I don’t think we should try to be the guy that cleans up all the kids’ rooms in the whole neighborhood.

But here the problem is a different one:

> On 2021-06-22, at 21:00, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> Signed PGP part
> 
> I know that markdown has many flavours/versions. I have no idea how to name
> them.
> 
> Comparing:
>        https://datatracker.ietf.org/doc/agenda-interim-2021-cellar-06-cellar-01/
> 
> and:
>        https://codimd.ietf.org/notes-ietf-interim-2021-cellar-06-cellar
> 
> you'll see that our nice table is not rendered as such on the DT.

Because the thing isn’t rendering markdown at all!

(Oh, and looking at the uploaded media type is a procedure that may seem justifiable from the letter of the standards but given the reality of browser implementations really is just torturing the user base.  In this century, we have file name endings (“extensions”) for that.)

Grüße, Carsten