Re: [Tools-discuss] <contact/>: asciiFullname should be latinFullname

Tom Pusateri <pusateri@bangj.com> Wed, 07 October 2020 06:51 UTC

Return-Path: <pusateri@bangj.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 1FFA43A1665 for <tools-discuss@ietfa.amsl.com>; Tue, 6 Oct 2020 23:51:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bangj.com
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 nW4M6OjQGTFt for <tools-discuss@ietfa.amsl.com>; Tue, 6 Oct 2020 23:51:30 -0700 (PDT)
Received: from oj.bangj.com (69-77-154-174.static.skybest.com [69.77.154.174]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BC8A3A11DE for <tools-discuss@ietf.org>; Tue, 6 Oct 2020 23:51:30 -0700 (PDT)
Received: from [172.16.10.184] (mta-107-13-246-59.nc.rr.com [107.13.246.59]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id AD7821DC9F; Wed, 7 Oct 2020 02:51:28 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bangj.com; s=201907; t=1602053488; bh=+OaIWIWwuWBOqYw+4KRw6CH/tJI+hroufQAJRILm09o=; h=From:Subject:Date:References:Cc:In-Reply-To:To:From; b=s7/WZWuRR8SiOnyr96wsctdNoPae3q2aQWl430FRbY5hB9oYMXBLKtMW9dXmH6sQg uqEQ+IJLu04aCUartOhoQntFwy+7wF3ZmEIYqaDPc5RnyFxT57VsS3T2ti5rOtUdOn pQ1whT+1O28rIxEas9wucin6cDD/HoDCWHUT+hhzMfTX5QryjywbqFx375LFIzm4C1 vPEd9sE9/OgyUfEtxAN90rCjnayayr/hqJcLZcHQBxUQk5HY6XSgpKYD42WKk81ZZa XtrDqg8DdGkZYMdP2oi4v81ZlqvJFS9wwB/G/TzgcwccoL6KNM2z3hcY+2wecqXa+7 D6g7bLiuwUlEw==
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Tom Pusateri <pusateri@bangj.com>
Mime-Version: 1.0 (1.0)
Date: Wed, 7 Oct 2020 02:51:27 -0400
Message-Id: <52B934D6-9ABC-4224-BF85-1D323B1AA6A7@bangj.com>
References: <E01F5548-0729-4B27-98F2-CA7C19C37CF1@tzi.org>
Cc: Tools Team Discussion <tools-discuss@ietf.org>
In-Reply-To: <E01F5548-0729-4B27-98F2-CA7C19C37CF1@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: iPad Mail (18A393)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/yCiSRMduEGdLcan9RnMGBtharVc>
Subject: Re: [Tools-discuss] <contact/>: asciiFullname should be latinFullname
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: Wed, 07 Oct 2020 06:51:33 -0000

> On Oct 7, 2020, at 12:20 AM, Carsten Bormann <cabo@tzi.org> wrote:.
> 
> What it really should say:
> 
> <contact fullname="トヨタ自動車株式会社" asciiFullname="Toyota Jidōsha KK"/>
> 
> But that transliteration is not entirely ASCII, so I get this error:
> 
> foo.xml(76): Error: Found non-ascii content in <contact> attribute value asciiFullname="Toyota Jidōsha KK"
> 
> Why do we allow Latin names in contact names, but if we have a non-Latin name, then the transcription suddenly needs to be ASCII, not just Latin?
> 
> Grüße, Carsten

Another related question:

How many times do we have to endure restrictions on UTF-8 characters in a UTF-8 document. Can we please just allow UTF-8 characters anywhere in a document?

It’s not like we don’t have multiple levels of an editor process to resolve any issues with incorrect use.

Tom