IETF Logo Mail Archive

Re: [Rfc-markdown] [rfc-i] [Tools-discuss] Tool to convert TXT to RFCXML

Carsten Bormann <cabo@tzi.org> Mon, 17 July 2023 08:40 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 34D91C13AE5A for <rfc-markdown@ietfa.amsl.com>; Mon, 17 Jul 2023 01:40:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZIYl2lS_cheH for <rfc-markdown@ietfa.amsl.com>; Mon, 17 Jul 2023 01:39:57 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07649C1519BE for <rfc-markdown@ietf.org>; Mon, 17 Jul 2023 01:39:55 -0700 (PDT)
Received: from [192.168.217.124] (p548dc15c.dip0.t-ipconnect.de [84.141.193.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4R4FrS6gdVzDCcW; Mon, 17 Jul 2023 10:39:52 +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: <d76f7ddf-46ae-4046-a1e0-9499da86e700@betaapp.fastmail.com>
Date: Mon, 17 Jul 2023 10:39:52 +0200
Cc: "Julian F. Reschke" <julian.reschke@gmx.de>, rfc-markdown@ietf.org, RFC Interest <rfc-interest@rfc-editor.org>
X-Mao-Original-Outgoing-Id: 711275992.4451129-c6fe4784cf53abbc8dd13998307e70f3
Content-Transfer-Encoding: quoted-printable
Message-Id: <37D9635A-D16A-4F04-B8BB-CA275F29119C@tzi.org>
References: <CABXxEz97ZDeHhtMeX6CwX842d=s9CXfUtG5DFWpxNKbtBcoW6Q@mail.gmail.com> <CAD2=Z86=DyfT0Fp23DqdCyz32Od4uhAhA48K=pst64eZ+CS8NA@mail.gmail.com> <CABXxEz-KC5Nayv=KMce9mDi_ngu9J8PY1-pAbMUBypxEX2Pw8Q@mail.gmail.com> <430B62BB-45BB-4ECF-812F-39E84926CFA7@tzi.org> <CABXxEz-_6MV0P9sc=GBJw+eReFpLZC2vDFFvo9katc1ECwpyRw@mail.gmail.com> <9f95474b-c049-2e5a-1cfd-f3e9ebf48e2d@gmx.de> <fe96fb1a-1c56-4416-b937-b0b66c38ae71@betaapp.fastmail.com> <66ef1749-f4b1-51af-8e08-06eb58a9005a@gmx.de> <869922F5-DA96-40DB-A749-32E801A1A632@tzi.org> <d76f7ddf-46ae-4046-a1e0-9499da86e700@betaapp.fastmail.com>
To: Martin Thomson <mt@lowentropy.net>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/_QoP2KLU1NzUn1dzZTZZlnOO3hU>
Subject: Re: [Rfc-markdown] [rfc-i] [Tools-discuss] Tool to convert TXT to RFCXML
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.39
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, 17 Jul 2023 08:40:02 -0000

On 2023-07-17, at 09:58, Martin Thomson <mt@lowentropy.net> wrote:
> 
> For our purposes, it seems like a simple <nobr>...</nobr> element would be fine.  (Which leads me to ponder a new kramdown extension whereby words could be automatically wrapped in various span-level elements to ensure consistent styling for keywords…)

Indeed — the current nobr hack described in

<https://mailarchive.ietf.org/arch/msg/rfc-markdown/umCatJwgKIhYF3yRRGdRhKVSy4U>

...was meant to seamlessly (without source change) transition to a <nobr element, and the same treatment could also be provided for <tt, or even <em, just as it already does for <bcp14.

Grüße, Carsten

PS.: I was contemplating to also provide a fake(*) element for “Spationierung” [1] (Letter spacing), just to add some variety :-)
But Spationierung is maybe too much of a German thing.

(*) fake = leading to character insertion/substitution

[1]: https://de.wikipedia.org/wiki/Spationierung

v2.23.0 | Report a Bug | By Email