IETF Logo Mail Archive

Re: [Rfc-markdown] Trying to mitigate "Re: The <tt> train wreck"

Carsten Bormann <cabo@tzi.org> Mon, 25 April 2022 13:14 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 C4B443A1720; Mon, 25 Apr 2022 06:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 2HMPuQdyeeT8; Mon, 25 Apr 2022 06:14:29 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8628B3A1924; Mon, 25 Apr 2022 06:14:27 -0700 (PDT)
Received: from [192.168.217.118] (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Kn5801l3PzDCcc; Mon, 25 Apr 2022 15:14:24 +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: <YmaPcb7r/2DTto20@miek.nl>
Date: Mon, 25 Apr 2022 15:14:23 +0200
Cc: Jay Daley <exec-director@ietf.org>, rfc-markdown@ietf.org
X-Mao-Original-Outgoing-Id: 672585263.834312-3033b5cfe48c616998edb07d5fb7845f
Content-Transfer-Encoding: quoted-printable
Message-Id: <160373EF-D93E-4FDB-B555-5EB7931430B8@tzi.org>
References: <04BFB6A7-7601-409D-8101-237242F6F38A@tzi.org> <F4C29CED-87A8-40B8-BE28-4EF54CEA3A8B@tzi.org> <834B1392-281F-4F60-A05B-AC49D8FF208F@ietf.org> <YmaPcb7r/2DTto20@miek.nl>
To: Miek Gieben <miek@miek.nl>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/n7xhKXEccfvdQknVOnvZ3-f2ECY>
Subject: Re: [Rfc-markdown] Trying to mitigate "Re: The <tt> train wreck"
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: Mon, 25 Apr 2022 13:14:34 -0000

On 2022-04-25, at 14:09, Miek Gieben <miek@miek.nl> wrote:
> 
> Of course if we get a <term type="xxx"> sort of element, setting the type from markdown
> will be difficult.

Are you trying to say “will not be difficult”?

I’m not sure I understand the <term proposal, but it seems to be another span element, like I discussed in https://github.com/ietf-tools/xml2rfc/discussions/753#discussioncomment-2473180

The ``` code in my proposal (which is not about line breaking, but about decorative vs. semantic) would set the right type for the common case of semantic code spans, and other types can be selected via IAL (“hard things should be possible”).

Of course, finding a way to encode all the other columns in my original mail into the number of backticks is not going to work that well :-)

So for line breaking, I think new syntax would be needed to express the nowrap span (which I would put into its own element, maybe <nobr> :-).

Grüße, Carsten

v2.23.0 | Report a Bug | By Email