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

Carsten Bormann <cabo@tzi.org> Sun, 27 October 2019 17:51 UTC

Return-Path: <cabo@tzi.org>
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 EB3641200B2 for <xml2rfc-dev@ietfa.amsl.com>; Sun, 27 Oct 2019 10:51:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 8Xcx_GDsW_Pi for <xml2rfc-dev@ietfa.amsl.com>; Sun, 27 Oct 2019 10:51:35 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E94D120046 for <xml2rfc-dev@ietf.org>; Sun, 27 Oct 2019 10:51:35 -0700 (PDT)
Received: from [192.168.217.110] (p5089AE1C.dip0.t-ipconnect.de [80.137.174.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 471QQF6hsFzymQ; Sun, 27 Oct 2019 18:51:33 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <37D9DCA7-A262-46A6-88C7-369127959164@tzi.org>
Date: Sun, 27 Oct 2019 18:51:31 +0100
X-Mao-Original-Outgoing-Id: 593891489.658808-b94e1383af3f5a69ad6bf7bf699eab94
Content-Transfer-Encoding: quoted-printable
Message-Id: <834E00E6-A39A-4E8C-8AF4-7D2F9B736C74@tzi.org>
References: <37D9DCA7-A262-46A6-88C7-369127959164@tzi.org>
To: xml2rfc-dev@ietf.org
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/PnWCMgXJUStLJ3CgtJPixyc5rTw>
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 17:51:38 -0000

(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.)

Grüße, Carsten


> On Oct 27, 2019, at 18:24, Carsten Bormann <cabo@tzi.org> wrote:
> 
> I’m not quite sure I understand when I have to provide the ascii=“” attribute.
> 
> I can have authors that have umlauts without further ado.
> If I have organizations with umlauts, I need to put in ascii=“”, or I get:
> 
> t2trg-sworn.xml(20): Error: Found non-ascii content without matching ascii attribute in <organization>: Universit?t Bremen TZI
> 
> (Note also that the error message has some mojibake.)
> 
> Grüße, Carsten
>