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

Julian Reschke <julian.reschke@gmx.de> Mon, 17 July 2023 09:45 UTC

Return-Path: <julian.reschke@gmx.de>
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 098E9C15256B; Mon, 17 Jul 2023 02:45:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, 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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmx.de
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 NufUBSlNxaRw; Mon, 17 Jul 2023 02:45:19 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95C88C1522CB; Mon, 17 Jul 2023 02:45:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.de; s=s31663417; t=1689587106; x=1690191906; i=julian.reschke@gmx.de; bh=P+8h2Il/RgFsdlcvvcSJbMLXuuYusmDqcpDDGY8HleM=; h=X-UI-Sender-Class:Date:Subject:To:Cc:References:From:In-Reply-To; b=Gr5i3VR9Zvmu6kwQI2vvCBni0iERv6OgpNTD+zd4fbguyAK4hHtPNqfsUNlH+qvPCLSwcHk SezOcvIltoAS95ba66ycehvqXDUkFNC7c9f1dAmUxLFEnJ0xB7S+4BGuAWqVlNSA/ksLjROAr TIN5Mhq6AiLSV2dDyZHX+Tsp8RV2fz4C/YOEUUJ/wzs7cza9gC7Ex0KtajaT61APs6cCMKyTG WOBLoDAIfmq5UvHAAx27mi3AuKV1EFU4Nrf4zrFz9DOGodoH4TmQtlyf7+VHLzm1hKWLaEHZ3 GdDhIP/UJlQyieAq/Z1wg9Yv492V4X22ad/UE+OPyBi1pTClIQwA==
X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a
Received: from [192.168.1.145] ([217.91.35.233]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1N7iCW-1prLVI1qwU-014gQI; Mon, 17 Jul 2023 11:45:06 +0200
Message-ID: <0f1ee0fa-e65c-097f-73e0-288f279c7c49@gmx.de>
Date: Mon, 17 Jul 2023 11:45:06 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0
To: Jay Daley <exec-director@ietf.org>, Martin Thomson <mt@lowentropy.net>
Cc: Carsten Bormann <cabo@tzi.org>, rfc-markdown@ietf.org, RFC Interest <rfc-interest@rfc-editor.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>
Content-Language: en-US
From: Julian Reschke <julian.reschke@gmx.de>
In-Reply-To: <E960579F-0750-471B-8729-8A59E89735D5@ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:26rXeL9v8RCx35jpqRSpZEhJfiZPAdudQZRoj98GkTZMyLfO2jm KNaeLLrOXEmIagJss3L9pQauByGncuVAuecNBlkiaqlat7BNV6hPE8ciQfT7Hf1qcDY/bjM eqLbgW5eIzXG6Q7LaDIsOudulcgYK1oT0YWClDQMvdBhHIKG/Gv1LdJIQLiUcDNoLx57AIi sEC6pZ5VVnnLaxt89fy+g==
UI-OutboundReport: notjunk:1;M01:P0:wlOWJ2jIlro=;IVWjekK6qQTbflE2rPZbr1uSFRb t03r7srOLT/F/+WvCrrBtmh/lYfiFMuoqCHuocgUlNCfFPuIzkVIANNYlH6cEN6RF4ymJ+UoI +84dvrhvF6mCv3jBEPG5RjsWIhbi5vtawcnFQGNYQBJ7m/HzIdAma0h6mjv73w+z+CNhBqNXI pVLCmyyO06tPTwjI8kF4R6uX6Y6kBjcCWTRfteo92PesYqbUl2fuWTaChDhiQH6QmgHsyp8oM V3Z4Vb3U0WXm6N4Hz/afCBk8LRni5WEJS9tcCR0Qo3vJ6tkpPE8OxqIcZFGAPrNVdpi9K8+Tc ++WdGeowgiOFWMn/3Q56lC9jLwATVFlhQFMRUNTr9lpl/PRQdhXtsHr8ryNKnB9m0TKjFw9qz hGA9G27QoX/+SILheAv8+CRSBZzd0WfoGJMVN9sO9KAZK/qy8wha2gkCitZhddG4uSHFj/VaO H18saSs6RFnqzJY9l4uLgixMzgez34I2uQyfQMJivL9rMalTKAN7n6Q8pr9bG7fdzlB9BzSbg 6nskNzgeNGHGwYxjVX+LRrOvI+3WC9yKCUf2lwsm2pS1aZUcVARiFUrUiTUJBT9KMRb1YGhiv UuDGCPac5/pYBBEVCAFR0T2e+OVN982ZHhwgSBUegQxYZPIvgn4xMTalq84vlJZ4tEFrs9o9V kY91NVLMY2n8pACuNy+fQDFJeQU0VjRXJV/0mj/M48OC4BQax3ontelmaskntHZkffnb9/ohh WyP/9i43KomeaJmxR4jccA2y1gcFyG3L/q9iFhFJmfSNx64Jp8m3n+BJB9M3k01huzc0o2iPh g672YtKL54BppYWpSl1y4a7zw3QeGfyBXciaifNFKzcH6SOigB6TkkmQkAB7AY24tK6LmpxgW l+Va3FPc7IKQLvc6zu27Wf/69c0C4J4Wblo2JHTkI2ubM4cJeOKVvM79bdNSJwrVghEjEuSuw t4H5gfrwUA/tg5Cqmf72mWzp9Yg=
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/jSyEuAw26hnX69RN1kbRh9YQk0E>
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 09:45:24 -0000

On 17.07.2023 11:35, Jay Daley wrote:
>
>
>> On 17 Jul 2023, at 08:58, Martin Thomson <mt@lowentropy.net> wrote:
>>
>> On Mon, Jul 17, 2023, at 16:47, Carsten Bormann wrote:
>>> * add <nobr or similar to RFCXML, so we don’t have to play the
>>> character substitution games.
>>
>> This.  The way HTML does it is with CSS directives[1].  There is a lot
>> of control over this through CSS, though for annoying reasons wrapping
>> is still not fully specified.
>>Trouble
>> 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...)
>
> A word of caution.  The authoring markup languages are being pulled in
> two different directions and if that is not well managed then I fear we
> will end up with an even more complex way of working than exists now.
>   Those two directions are - does the markup represent formatting or
> does the markup represent semantics.  As I understand it, the original
> consensus design goal was to prioritise the representation of semantics.
>   i.e. not to prevent the formatting, but to capture the semantics first
> and then add finer grained formatting to that,
>
> If we approach this specific issue from the semantic perspective then
> that would better be served by adding a new element, such as <term> …
> </term> that is intended to represent a technical term used inline in
> any body text and which therefore must remain as an atomic whole.
> ...

I agree partly.

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.

Remember, the alternative is that lines, in particular in narrow
displays or in plain text, will have lots of horizontal space instead.

Best regards, Julian