IETF Logo Mail Archive

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

Jean Mahoney <jmahoney@amsl.com> Mon, 17 July 2023 14:17 UTC

Return-Path: <jmahoney@amsl.com>
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 568FBC151AEB for <rfc-markdown@ietfa.amsl.com>; Mon, 17 Jul 2023 07:17:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 kMkk4akBFkTC for <rfc-markdown@ietfa.amsl.com>; Mon, 17 Jul 2023 07:17:35 -0700 (PDT)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (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 D95E2C151AE6 for <rfc-markdown@ietf.org>; Mon, 17 Jul 2023 07:17:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 88A7F424B435; Mon, 17 Jul 2023 07:17:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RU3TMxihHtse; Mon, 17 Jul 2023 07:17:35 -0700 (PDT)
Received: from [192.168.1.203] (unknown [47.186.48.51]) by c8a.amsl.com (Postfix) with ESMTPSA id 5C546424B432; Mon, 17 Jul 2023 07:17:35 -0700 (PDT)
Message-ID: <c62feb69-9544-ad7c-dfe7-6f084458ba8d@amsl.com>
Date: Mon, 17 Jul 2023 09:17:34 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.13.0
Content-Language: en-US
To: Julian Reschke <julian.reschke@gmx.de>, rfc-markdown@ietf.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>
From: Jean Mahoney <jmahoney@amsl.com>
In-Reply-To: <66ef1749-f4b1-51af-8e08-06eb58a9005a@gmx.de>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/EKqQULlMt3LyYDf2GtxW9WR541c>
Subject: Re: [Rfc-markdown] [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 14:17:40 -0000

Hi all,

On 7/17/23 12:13 AM, Julian Reschke wrote:
> On 17.07.2023 03:24, Martin Thomson wrote:
>> On Thu, Jul 13, 2023, at 20:38, Julian Reschke wrote:
>>> What *should* work is replacing "-" by a non-breaking hyphen
>>> (<https://www.fileformat.info/info/unicode/char/2011/index.htm>).
>>
>> Am I the only person who finds this recommendation a little bit less 
>> than satisfactory?  A literal search for XXX-YYY-ZZZZ will fail in 
>> that case.  XXX‑YYY‑ZZZZ is not the same string.
>
> I agree that this is a problem. But that's also what the RFC Editor has
> been doing in the past (AFAIR).
[JM] Yes, to ensure that XXX‑YYY‑ZZZZ doesn't break, we would use 
non-breaking hyphen entities at the author's request.

We prefer to limit the use of entities to control line breaks, such as 
non-breaking space, non-breaking hyphen, word joiner, and zero-width 
space, and use them only if the line breaks are really bad (in tables 
with many columns, for instance).

Best regards,
Jean

>
>> ...
>
> Best regards, Julian
>
> _______________________________________________
> Rfc-markdown mailing list
> Rfc-markdown@ietf.org
> https://www.ietf.org/mailman/listinfo/rfc-markdown

v2.23.0 | Report a Bug | By Email