Re: [xml2rfc-dev] When is @ascii required?

Julian Reschke <julian.reschke@gmx.de> Sun, 27 October 2019 19:52 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFA19120052 for <xml2rfc-dev@ietfa.amsl.com>; Sun, 27 Oct 2019 12:52:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 G_sxVwK7TANq for <xml2rfc-dev@ietfa.amsl.com>; Sun, 27 Oct 2019 12:52:21 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6D58120046 for <xml2rfc-dev@ietf.org>; Sun, 27 Oct 2019 12:52:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1572205910; bh=YQkZYUr2LgiOcgMhTkRRJ8OztFZKATDERvS11M5CclE=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=kUhwfhB4uf5iIxN4au1x+DfUugU1ezfHCOzt35RSds9f2mChfCuWDvCPhGuM2XPsI I4WWHZi56nC34dbzxFy6owUW7z5LWAHCu0UrI26BKBMKdzYK0edyQbjwLMKgAQB/RY UoAfeaaoNXkuUT3A3GRZRFv2O+yMsKqeARlFLlSs=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([217.251.129.19]) by mail.gmx.com (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1N4hvb-1hxLdq3W6B-011jp1; Sun, 27 Oct 2019 20:51:49 +0100
To: Henrik Levkowetz <henrik@levkowetz.com>, Carsten Bormann <cabo@tzi.org>, xml2rfc-dev@ietf.org
References: <37D9DCA7-A262-46A6-88C7-369127959164@tzi.org> <834E00E6-A39A-4E8C-8AF4-7D2F9B736C74@tzi.org> <9079ee9c-3f9c-74bc-9e84-fff223056ab9@levkowetz.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <80322414-4318-1cf9-3781-48651a07ed19@gmx.de>
Date: Sun, 27 Oct 2019 20:51:46 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <9079ee9c-3f9c-74bc-9e84-fff223056ab9@levkowetz.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:OL2W8D7JpXUBsOSbdZQYvGFaR4p9G0aEBaPbN2OrYaUyD+mvsNC U1Ht/U/OmyNTq7mexKSfTCjc3VzVAO5MuOyOK3k7SAGXm6b2jilquYFuoNSRMqXfugH9DY9 TKroHf66picmRfTw563Mt9rCdSj+E19qabOZs3vWT5z6P35lIq2lsa9hw6eq99UxlitDw2o YPsM/CcO14USdoYu1kKiQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:qO6AGScu0Zc=:fSGvYRZ2DZ0rNHc/ubw7++ vUkqEC6hQuAAlLGuAuyZ5lqzJonmwOBrAM18fnHUfo8WZSlQDD9uP268xR1HboRHlCer6cUI8 zRIaO5iRsnrTpAWpzr1h9WMvKWhdudMR5POdDTQNp0CGluAx5QSsuP9NOiKz33BYu5/JwWLDm SGhvv8spjwRDPIeQv50kq88k1ws/fWh9gZKf54totS4zmnEZKbRkCDoZ7jTSaJD2R68yFSf3C K9DrBkpcq47JYBBJofp7WKzVE4otaZmLT5dKiupkYAp/ygKTGX0BJXoEwZbqklDq/HZLxPEL0 2QlN1ThHQSJBMvxzOXXfFGyt96Hup3/04W4LbKPk5NcICY5sL5UYCGa9lBvCgMFM3dIWt/gR7 Nd51l7hoO9dUG9zlDW1zqkBVKn0W6JKilwFQUA9P+WkUCEpLdWpuFLNB11bbSsSLQmjsYPN1c CM2Ec2hUPlgrSEiEnycNOHQ0pjn5xV0u5iVWD5YOTdwHke/5sthZohTxxdfvh7vIxoQ88dTby MOlL69DiVMXZIj1PluVNf1ubQRPkhY94GXvJnd4+VWfPawFzPuG0C7YA64h4UOQRkq7BKmw+e mlsw4eG2gskOxX2dQF2JbLDRvb0UABROdJWamGQYSZy5xHQrUogMmyRkOrYg6ZR4xvAfS5lDm bdDic3p2qoL3ujGGnyejEjZYLC9UOca4Q9FkXr6TzorJCMx5ctyhL9ywAJE5oRxgG3SELwl7g UX3ebpH/xhuero7FQ/WVLVyTPV6ckQp+6b0e0BDAqLIcW70Iqip9YKKjFIIy5MTmR361VjV/p Y14dfbcl7hCf06RfXklTnG31ME6r8qIkLFDZMOj+pTJrf2tctipOtzGz4MVkkHn5h4QJfOoI9 JJdDqtm85l2LADAiqDdRjqbRKBbolYP/2MdD+lk4j+6GK0rp2F38xnDp7W9LSJCV0hnR6SgFT FXXbHBtpfX9jFEPiFoj9CtkxAq7n0cqbXBZTQe5fEsNI+6L1X3XYDDhDURSIpTBQShJZSw1OG OJT0jcEAwSoqULJ37EAhgGNmLvAMx7lLtw/FvAUePbEiW5wwlvckvxQPhVJcgClwKXBUTY03E Hf8QTbv3sYw3gkUL/9HJ5GzqDjDR/D30AFOps7/hsTQaryxFDH4ehShDxjWA6/PfFtIxnW+8C 20ltoS0v4Qz+qv5J3ijyj4p8GMK/k8zSF86j6axAbxhW2XXarJN9U+LOcofNMAf0utTQakxLH bX0d3/4FIwXudznBKvxDr1ZvAjiZ0dZbgbUWYJ67qWB7f9kWVLipLRB6blQ4=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/VilrP97_myEPGkLEM7Vw87jYRig>
Subject: Re: [xml2rfc-dev] When is @ascii required?
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Oct 2019 19:52:24 -0000

On 27.10.2019 19:50, Henrik Levkowetz wrote:
> Hi Carsten,
>
> On 2019-10-27 18:51, Carsten Bormann wrote:
>> (Looking at the source of the message in preptool.py/check_ascii_text, I also don’t understand this:
>>
>>                  if self.tree.docinfo.encoding.lower() in ['us-ascii', ]:
>>                      self.die(c, “Found non-ascii content in a document with xml encoding declared as %s” % self.tree.docinfo.encoding)
>>
>> I don’t understand what the source encoding has to do with this; XML
>> allows me to have beyond-ascii characters in documents the xml
>> encoding of which uses us-ascii (or koi8-r, for that matter).  I
>> think that any access to self.tree.docinfo.encoding at this point in
>> processing is a layer violation.)
>
> It may very well be that the test can be improved, but it was triggered
> by a hard-to-diagnose failure where an XML file had us-ascii encoding
> declared, but contained non-ascii characters.  The RPC didn't manage to
> get a handle on what the problem was that triggered the failures, and it
> also took me a while to understand what was going on.
> ...

That should be an error reported at the time of XML parsing...

Best regards, Julian