IETF Logo Mail Archive

Re: [Rfc-markdown] [Tools-discuss] New xml2rfc release: v3.18.0

Carsten Bormann <cabo@tzi.org> Wed, 09 August 2023 11:48 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 C38D4C15171B; Wed, 9 Aug 2023 04:48:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.207
X-Spam-Level:
X-Spam-Status: No, score=-4.207 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, T_SCC_BODY_TEXT_LINE=-0.01, 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 i2qjFvC6i7lH; Wed, 9 Aug 2023 04:48: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 18DCDC14CE39; Wed, 9 Aug 2023 04:47:59 -0700 (PDT)
Received: from smtpclient.apple (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 4RLSwr55QZzDCdy; Wed, 9 Aug 2023 13:47:56 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAD2=Z84ufaTai-VydeWOEXLr3vBsbv9NE5HXs_NvhQS92AXmwg@mail.gmail.com>
Date: Wed, 09 Aug 2023 13:47:45 +0200
Cc: rfc-markdown@ietf.org, XML2RFC Interest Group <xml2rfc@ietf.org>, tools-discuss <tools-discuss@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DDD39630-DDE2-46C3-8CF4-5FE27892A370@tzi.org>
References: <CAD2=Z85hDSHt9gmAz4OGZ3HpYsyY_0tVjUuad7qPOiYFHdEKgA@mail.gmail.com> <0C87712C-4F97-4150-A7ED-F6438B157462@tzi.org> <CAD2=Z84ufaTai-VydeWOEXLr3vBsbv9NE5HXs_NvhQS92AXmwg@mail.gmail.com>
To: Kesara Rathnayake <kesara@staff.ietf.org>
X-Mailer: Apple Mail (2.3731.700.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/HYZd1kY4-8V5qrDuF247oeyw3ho>
Subject: Re: [Rfc-markdown] [Tools-discuss] New xml2rfc release: v3.18.0
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: Wed, 09 Aug 2023 11:48:10 -0000

Hi Kesara,

> On 9. Aug 2023, at 13:26, Kesara Rathnayake <kesara@staff.ietf.org> wrote:
> 
> Output from kramdown-rfc's echars and `xml2rfc --warn-bare-unicode`
> option is now listed as separate sections in the validation report on
> https://author-tools.ietf.org/
> Select the file and click on the "Validate (idnits)" button for this.

This is a great feature; I just tried it out.  Thank you!

Looking at the results page, I’m just wondering if putting the echars output uncommented under what could be validation errors isn’t a bit confusing.
This list is just for information, not indicative of a problem if the characters are as expected.
(E.g., I will always have an “ä” from Universität in my drafts — --warn-bare-unicode of course knows that this is fine as it occurs in an address, but echars will dutifully report it.)
We have seen too many people warp their documents just to remove an idnits message; I wouldn’t want to repeat this mistake.

So something like “for information: …” might help confusing the users of this feature a little less.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email