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

Kesara Rathnayake <kesara@staff.ietf.org> Wed, 09 August 2023 21:47 UTC

Return-Path: <kesara@staff.ietf.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 C48ACC1522C2 for <rfc-markdown@ietfa.amsl.com>; Wed, 9 Aug 2023 14:47:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=staff-ietf-org.20221208.gappssmtp.com
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 k-xmqxr_VxRC for <rfc-markdown@ietfa.amsl.com>; Wed, 9 Aug 2023 14:47:48 -0700 (PDT)
Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 01AC3C1522D3 for <rfc-markdown@ietf.org>; Wed, 9 Aug 2023 14:47:17 -0700 (PDT)
Received: by mail-ej1-x636.google.com with SMTP id a640c23a62f3a-99bdf08860dso296391466b.0 for <rfc-markdown@ietf.org>; Wed, 09 Aug 2023 14:47:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20221208.gappssmtp.com; s=20221208; t=1691617636; x=1692222436; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=RgRa5OVZx5INZSIggyhjzwzIxcpGq/hgGX4KUl4nHYU=; b=faIi60z5Csn0e3g195/U7ntox/QyX/So+1A9ihviSBx6ps59S0iPXCJBFQ9X90YwtL Ku1zA4c/HRn0QXyODTOtHGfp7na3KW5dZfqyqFtrA33F7vA9kWKNY9ZgBx1uHAOQS/9E uBCVZ2hJTdaS6iznlpcB2KikXltc4gfU2mVcO/vPU1e8C7/QITD7nq+FsGWhMZbqVoMP yp7e/qkW8aK5Q/7OnacqKqcXxpu5JWzuTGYSOG3v0LswPh9820eQbYtBLIhQR0pvOwYU Jua1prPq757D1I1udxxJnHQ82MAJPIDfmYRGmw+OQqUc1dIbSBdieuVEFPEXO0txnYkE 6WJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691617636; x=1692222436; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=RgRa5OVZx5INZSIggyhjzwzIxcpGq/hgGX4KUl4nHYU=; b=PEssKQF4G1iqHKm6k8Sd4R5yKs/nnyo7ipn/lYz/HFJl1h2saxtYF/a/cVr3+YA2j4 RSw8KOk8q4/F0s6ygn7jYT5N7pBO+6GNN8tfgBjATVtdiXPScyP08nofJwY86o9pA2dE Iza+NbZxI2ACUuohB5p74kqP+3wg2QskEY+i4z/BnJ12UJpbbEsyfuzK8to6nQ/k4xcF HZD8M+wAEVeBBzUSpxVuepZSBZszLhOu3od0J/NJeLl/sPIFEt5HiOgrLTp+aKCjEKeB ZAnV+ILXKvwG1fXUfMfxKFvFZ26iMVzulKxyK1iQtedOjQLuG7Yih5BXyI9vu4WlM+4o 4LEQ==
X-Gm-Message-State: AOJu0YyrngChUwSa0Y7vzo1qLuhW0MY7TzEY1V4B54chFk9xHVvYdrCt Dh1/RarmutYdkFRZ5YCgywb2V2omY/a0nSi4KEeqMscYkMs0avkjjEU=
X-Google-Smtp-Source: AGHT+IG2POiug4teUhQv/Yq2xLM5amL2J7ZkrrCFTEDGRqXokl678xKNpg11yLHUxoGkllf8EdFjOa66jGPk7E1Ldkc=
X-Received: by 2002:a17:906:3101:b0:99b:cb59:79b3 with SMTP id 1-20020a170906310100b0099bcb5979b3mr246266ejx.1.1691617636493; Wed, 09 Aug 2023 14:47:16 -0700 (PDT)
MIME-Version: 1.0
References: <CAD2=Z85hDSHt9gmAz4OGZ3HpYsyY_0tVjUuad7qPOiYFHdEKgA@mail.gmail.com> <0C87712C-4F97-4150-A7ED-F6438B157462@tzi.org> <CAD2=Z84ufaTai-VydeWOEXLr3vBsbv9NE5HXs_NvhQS92AXmwg@mail.gmail.com> <DDD39630-DDE2-46C3-8CF4-5FE27892A370@tzi.org>
In-Reply-To: <DDD39630-DDE2-46C3-8CF4-5FE27892A370@tzi.org>
From: Kesara Rathnayake <kesara@staff.ietf.org>
Date: Thu, 10 Aug 2023 09:47:04 +1200
Message-ID: <CAD2=Z8523sOaRJka6+EggvPY1aybnzX2WKVTWfBWZR-781J4Hg@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: rfc-markdown@ietf.org, XML2RFC Interest Group <xml2rfc@ietf.org>, tools-discuss <tools-discuss@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/TMUOcr4sf8R1W63Z07CxoECnMf0>
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 21:47:48 -0000

On Wed, 9 Aug 2023 at 23:47, Carsten Bormann <cabo@tzi.org> wrote:
>
> 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.
>

Good idea, I'll update the UI to convey that these are just for information.
 --Kesara

> Grüße, Carsten
>


-- 
Kesara Rathnayake
Senior Software Development Engineer - IETF Administration LLC
kesara@staff.ietf.org