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 10:44 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 A9145C151556; Mon, 17 Jul 2023 03:44:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 SyqJVbj6Qqz2; Mon, 17 Jul 2023 03:44:06 -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 DD775C151532; Mon, 17 Jul 2023 03:44:04 -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 4R4Jbk1S7wzDCbg; Mon, 17 Jul 2023 12:44:02 +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: <0f1ee0fa-e65c-097f-73e0-288f279c7c49@gmx.de>
Date: Mon, 17 Jul 2023 12:44:01 +0200
Cc: Jay Daley <exec-director@ietf.org>, Martin Thomson <mt@lowentropy.net>, rfc-markdown@ietf.org, RFC Interest <rfc-interest@rfc-editor.org>
X-Mao-Original-Outgoing-Id: 711283441.777954-e4ad9c87638f6426ed91d78c3ebc6d7b
Content-Transfer-Encoding: quoted-printable
Message-Id: <96E4942B-2DA7-40E9-AD5E-502B26B15934@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> <E960579F-0750-471B-8729-8A59E89735D5@ietf.org> <0f1ee0fa-e65c-097f-73e0-288f279c7c49@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/tPexDehUrjIBZed7J4clNlKI6Bg>
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 10:44:10 -0000

On 2023-07-17, at 11:45, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> The trouble with that is that even a rule like "do not insert LF into
> terms" may not be always desirable. For instance, jn HTTP we have
> several longish header field names, and I would not want them to be not
> broken across lines.

Right.  The question whether something is a term is almost orthogonal to whether it should be line-broken or not.

Grüße, Carsten

PS: I love the line-breaking of references of the form [I-D.ietf-sedate-datetime-extended] right after the [I-.  I have already considered silently changing all I-D in anchors into I‑D…
(The breakage would likely be hilarious.)

v2.23.0 | Report a Bug | By Email