Re: [Tools-discuss] [Cellar] non-ascii characters (fwd) Dave Rice: non-ascii characters

Henrik Levkowetz <henrik@levkowetz.com> Tue, 27 August 2019 20:10 UTC

Return-Path: <henrik@levkowetz.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 899361200FF; Tue, 27 Aug 2019 13:10:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UGA47kUMEuOt; Tue, 27 Aug 2019 13:10:48 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C8BA1200DE; Tue, 27 Aug 2019 13:10:48 -0700 (PDT)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:53639 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1i2hnj-0008Cq-8D; Tue, 27 Aug 2019 13:10:47 -0700
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <31591.1566930552@localhost> <c9f67a76-c0ae-6d3e-2bad-47dfdda85df6@levkowetz.com> <16112.1566934510@localhost>
Cc: tools-discuss@ietf.org, cellar@ietf.org
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <73ea49ee-c173-33f5-6fa1-031f1599434a@levkowetz.com>
Date: Tue, 27 Aug 2019 22:10:39 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <16112.1566934510@localhost>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="xAw9eGSGTUvPpX7r6Ko9LI1mfWo3rS6Q2"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: cellar@ietf.org, tools-discuss@ietf.org, mcr+ietf@sandelman.ca
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/eZbDIkwCqMnvmg-JNoNED-96-3A>
Subject: Re: [Tools-discuss] [Cellar] non-ascii characters (fwd) Dave Rice: non-ascii characters
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2019 20:10:50 -0000

Hi Michael,

On 2019-08-27 21:35, Michael Richardson wrote:
> 
> Henrik Levkowetz <henrik@levkowetz.com> wrote:
>     > Hi Michael,
> 
>     > Here's my take on this:
> 
>     > A number of people has highlighted the desirability of using math
>     > symbols in text.  However, this is not currently supported by xml2rfc
>     > v3, and will make idnits unhappy.  Putting math in SVG is currently the
>     > supported approach.
> 
> Yes, and we are using SVG. But we can't do it with XML yet (now Sept. 16).

That's when the RFC-Editor intends to start publishing xml, I believe?

But you should already be able to post drafts using v3 XML -- any reason not
to do so?  (It doesn't affect your primary question, but I'm curious.)

> So we format a txt version for submission to post to the datatracker,
> and it has some UTF-8 in it.
> 
> Are you agreeing that idnits is in error?

For publication purposes, the final arbiter isn't idnits, and the idnits
message for non-ascii characters has been downgraded from error to warning,
since it's not sufficiently sophisticated to clearly tell what's acceptable
and what's not, based on RFC 7997.  I think it's right to emit a warning,
in order to have both authors, shepherd and ADs consider the case, but
can't make any further judgement.


	Henrik