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

Carsten Bormann <cabo@tzi.org> Thu, 13 July 2023 08:47 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 B1041C151061; Thu, 13 Jul 2023 01:47:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FFxiv6ZQC9_6; Thu, 13 Jul 2023 01:47:46 -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 B9135C14CE33; Thu, 13 Jul 2023 01:47:43 -0700 (PDT)
Received: from client-0227.vpn.uni-bremen.de (client-0227.vpn.uni-bremen.de [134.102.107.227]) (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 4R1pCJ4wVdzDCbV; Thu, 13 Jul 2023 10:47:40 +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: <CABXxEz-KC5Nayv=KMce9mDi_ngu9J8PY1-pAbMUBypxEX2Pw8Q@mail.gmail.com>
Date: Thu, 13 Jul 2023 10:47:40 +0200
Cc: Kesara Rathnayake <kesara@staff.ietf.org>, rfc-markdown@ietf.org, tools-discuss <tools-discuss@ietf.org>
X-Mao-Original-Outgoing-Id: 710930860.2100821-d42f0c432d2ea692feba11d529e391c2
Content-Transfer-Encoding: quoted-printable
Message-Id: <430B62BB-45BB-4ECF-812F-39E84926CFA7@tzi.org>
References: <CABXxEz97ZDeHhtMeX6CwX842d=s9CXfUtG5DFWpxNKbtBcoW6Q@mail.gmail.com> <CAD2=Z86=DyfT0Fp23DqdCyz32Od4uhAhA48K=pst64eZ+CS8NA@mail.gmail.com> <CABXxEz-KC5Nayv=KMce9mDi_ngu9J8PY1-pAbMUBypxEX2Pw8Q@mail.gmail.com>
To: Oleg Pekar <oleg.pekar.2017@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/KWV6Mz_RhLLZGH9JPwE3teNJoog>
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: Thu, 13 Jul 2023 08:47:49 -0000

Hi Oleg,

I’d like to see the source to give a specific recommendation, but I can point out a recent feature that we have added to kramdown-rfc:

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

This means that by adding one line somewhere, you declare once and for all that you don’t want specific words broken, as in:

*[XXX-YYY-ZZZ]: <nobr>

Please tell us whether this works for you.

Grüße, Carsten



Grüße, Carsten

On 2023-07-13, at 10:37, Oleg Pekar <oleg.pekar.2017@gmail.com> wrote:
> 
> Thanks Kesara, Carsten, Rich, it worked!
> 
> One more small question: how could I prevent rfc2xml from breaking the terms in the text with '-' inside. I.e. words like XXX-YYY-ZZZ are broken by the hyphen sign and I want to prevent it. Including every time such a word in CDATA may not be an easy option.