[Xml-sg-cmt] question: use of <u> element

Alice Russo <arusso@amsl.com> Thu, 17 February 2022 18:50 UTC

Return-Path: <arusso@amsl.com>
X-Original-To: xml-sg-cmt@ietfa.amsl.com
Delivered-To: xml-sg-cmt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 084753A0F0F for <xml-sg-cmt@ietfa.amsl.com>; Thu, 17 Feb 2022 10:50:01 -0800 (PST)
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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 Hi7u8rsYx2Ui for <xml-sg-cmt@ietfa.amsl.com>; Thu, 17 Feb 2022 10:49:55 -0800 (PST)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2173A3A0490 for <xml-sg-cmt@ietf.org>; Thu, 17 Feb 2022 10:49:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 10AE3425C194; Thu, 17 Feb 2022 10:49:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SlMIERkF657E; Thu, 17 Feb 2022 10:49:55 -0800 (PST)
Received: from [192.168.4.33] (c-24-17-19-210.hsd1.wa.comcast.net [24.17.19.210]) by c8a.amsl.com (Postfix) with ESMTPSA id E3FEA425A344; Thu, 17 Feb 2022 10:49:54 -0800 (PST)
From: Alice Russo <arusso@amsl.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Message-Id: <9EDE9834-2586-43BA-9681-AC576EFF5C30@amsl.com>
Date: Thu, 17 Feb 2022 10:49:54 -0800
Cc: RFC Editor <rfc-editor@rfc-editor.org>
To: "xml-sg-cmt@ietf.org" <xml-sg-cmt@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml-sg-cmt/mtWf1thtRCGE0EPEZFbQDEVmDDE>
Subject: [Xml-sg-cmt] question: use of <u> element
X-BeenThere: xml-sg-cmt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working list for the xml and style guide change management team <xml-sg-cmt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml-sg-cmt>, <mailto:xml-sg-cmt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml-sg-cmt/>
List-Post: <mailto:xml-sg-cmt@ietf.org>
List-Help: <mailto:xml-sg-cmt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml-sg-cmt>, <mailto:xml-sg-cmt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Feb 2022 18:50:01 -0000

Greetings,

Should the <u> element be used to get the desired output even when it doesn't include the character itself? The <u> can be used to render the "U+" notation or name of a Unicode code point. For example (from draft-faltstrom-unicode12-07):

This output:
 SPHERICAL ANGLE OPENING UP (U+29A1) existed before IDNA2008 was ...

could be rendered w/ this XML:

A)  <t> <u format="name-num">⦡</u> existed before IDNA2008 was ... </t>

instead of 

B)  <t> SPHERICAL ANGLE OPENING UP (U+29A1) existed before IDNA2008 was ...</t>


Should the RPC be using A? 
It would mean a programmatic check (in addition to a manual check) of whether the submitted text is accurate. (i.e., the author submits a long name and "U+" notation, RPC looks it up and puts the actual char in <u> in the source file, renders output, then checks if it matches what was submitted.) 
 
Thanks,
Alice