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

Alice Russo <arusso@amsl.com> Fri, 18 February 2022 17:20 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 2F3B73A120E for <xml-sg-cmt@ietfa.amsl.com>; Fri, 18 Feb 2022 09:20:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 GFOkAVKStF_1 for <xml-sg-cmt@ietfa.amsl.com>; Fri, 18 Feb 2022 09:20:33 -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 C21253A1222 for <xml-sg-cmt@ietf.org>; Fri, 18 Feb 2022 09:20:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id B2991425C356; Fri, 18 Feb 2022 09:20:33 -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 Twe7bQADUl4t; Fri, 18 Feb 2022 09:20:33 -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 88012425C195; Fri, 18 Feb 2022 09:20:33 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Alice Russo <arusso@amsl.com>
In-Reply-To: <c5d600ea-bfc1-0412-dbd1-20afb5ae7a48@taugh.com>
Date: Fri, 18 Feb 2022 09:20:31 -0800
Cc: "xml-sg-cmt@ietf.org" <xml-sg-cmt@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <4230FFCD-F08E-45FB-AF90-595F9DD6AEC7@amsl.com>
References: <9EDE9834-2586-43BA-9681-AC576EFF5C30@amsl.com> <c5d600ea-bfc1-0412-dbd1-20afb5ae7a48@taugh.com>
To: John R Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml-sg-cmt/QjBUDsUJ4XICAKLg1deMmVd8h3o>
Subject: Re: [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: Fri, 18 Feb 2022 17:20:38 -0000

Hi John,
Ack on the outcome (simply leave it written out).

Re:
> I realize this is quite the corner case.

Hm, I see it as a common case in that the I-Ds we receive contain the data about the code point (e.g., the name and U+ notation) more commonly than the character itself, presumably because that was not possible before the format change.

For example, draft-faltstrom-unicode12-07 contains 30 instances of U+ notation.

Thanks,
Alice

On Feb 17, 2022, at 11:21 AM, John R Levine <johnl@taugh.com> wrote:

>> 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?
> 
> In this case I think not.  Patrik is using the character as an example without any plan to render it.  I realize this is quite the corner case.
> 
> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail. https://jl.ly
>