IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Sun, 27 October 2019 19:20 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 8C2F51200B1 for <xml2rfc-dev@ietfa.amsl.com>; Sun, 27 Oct 2019 12:20:48 -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 RBVXvjsYdREP for <xml2rfc-dev@ietfa.amsl.com>; Sun, 27 Oct 2019 12:20:47 -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 625CB120024 for <xml2rfc-dev@ietf.org>; Sun, 27 Oct 2019 12:20:47 -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 471SP96njzzyPp; Sun, 27 Oct 2019 20:20:45 +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: <9079ee9c-3f9c-74bc-9e84-fff223056ab9@levkowetz.com>
Date: Sun, 27 Oct 2019 20:20:45 +0100
Cc: xml2rfc-dev@ietf.org
X-Mao-Original-Outgoing-Id: 593896842.928763-0da680507af8fc53628b44fae3ae7568
Content-Transfer-Encoding: quoted-printable
Message-Id: <C1B5F114-C4D9-4713-A902-794551702092@tzi.org>
References: <37D9DCA7-A262-46A6-88C7-369127959164@tzi.org> <834E00E6-A39A-4E8C-8AF4-7D2F9B736C74@tzi.org> <9079ee9c-3f9c-74bc-9e84-fff223056ab9@levkowetz.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/ZQIm6Fd6m5H11EjVkdGimfCk1nc>
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:20:48 -0000

On Oct 27, 2019, at 19:50, Henrik Levkowetz <henrik@levkowetz.com> wrote:
> 
> 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. 

Do you remember whether it contained non-ASCII characters themselves (which should already fail in the parser) or character-references to beyond-ASCII characters?  Or maybe entity references?

Grüße, Carsten

v2.23.0 | Report a Bug | By Email