IETF Logo Mail Archive

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

John R Levine <johnl@taugh.com> Thu, 17 February 2022 19:21 UTC

Return-Path: <johnl@taugh.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 BD9443A1007 for <xml-sg-cmt@ietfa.amsl.com>; Thu, 17 Feb 2022 11:21:47 -0800 (PST)
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=iecc.com header.b=XCclVhQ5; dkim=pass (2048-bit key) header.d=taugh.com header.b=PV6Jx7eR
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 CMm4Z4UZLwHY for <xml-sg-cmt@ietfa.amsl.com>; Thu, 17 Feb 2022 11:21:42 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46B923A0FF5 for <xml-sg-cmt@ietf.org>; Thu, 17 Feb 2022 11:21:41 -0800 (PST)
Received: (qmail 66517 invoked from network); 17 Feb 2022 19:21:40 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding; s=103d3.620ea044.k2202; bh=vyZfH4Y6EBdcM4IhV6sitWP4h8DKc4eCT67bcuxfU0M=; b=XCclVhQ5klZyo9flFWH9mFTb3ylzhwfosW0I9dWdV+Wq/qS5xUdrsbU0+saqZHUmCqiahvTWlvmhjyPQ5c3MIM4vCzcxlppTkN/wnq+Lc1PoHKbLxpGkZEZEpAQ9Hpv1Zf7LPwJ6HR7VKNjvo67Dmc15olmRU9Sxs+ih+CRJNNZXnhMlgwUczDou115PmqbwVoy6/YIYRBg9idj/y8qFqQ1oKEKTy+xvfig/I7j+uF8yVpMaYRSFnye9B4jeafFiEEEtxX2rSfKOE4By/Ae5Ee0so8/8wNy5KyVRbCRJ4gplMNqsukI/0zb7yIYA0zxLDeVnriyHMkzwXc0pLJAGVQ==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding; s=103d3.620ea044.k2202; bh=vyZfH4Y6EBdcM4IhV6sitWP4h8DKc4eCT67bcuxfU0M=; b=PV6Jx7eRTmZ8qt8IlB3mKiIwLRiqXBPwGdMAMHsw6LdiRQ5vH8s4CaJaSs4+MHN0sDF0QnzZlnCcqMciF7EbsUshZiUs8kWjxdt14PMWK7EfKJiREySpgx+mwL/rduqjylwNLviXikB8zm1rUEVBz9gMnqaiZpcdgEjLsubXQC+38CXEyBwDNIW4DswZjNn6EFdmDxLxK2AnUGXWCfF9l7wvYSdtdLKckLiqjUbAp57ojZHDm2oZcrv72uq1BTalQ0qDfOXdLiazsTq95otPQd1T6nydy75VQNUhgsKfDhRvxluZtMjos3p8W7UBAiMzA+WZpDkgxI4paMmAV+PPDA==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 17 Feb 2022 19:21:39 -0000
Received: by ary.qy (Postfix, from userid 501) id 4D863375DB5F; Thu, 17 Feb 2022 14:21:38 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id B0B32375DB41; Thu, 17 Feb 2022 14:21:38 -0500 (EST)
Date: Thu, 17 Feb 2022 14:21:38 -0500
Message-ID: <c5d600ea-bfc1-0412-dbd1-20afb5ae7a48@taugh.com>
From: John R Levine <johnl@taugh.com>
To: Alice Russo <arusso@amsl.com>, "xml-sg-cmt@ietf.org" <xml-sg-cmt@ietf.org>
Cc: RFC Editor <rfc-editor@rfc-editor.org>
X-X-Sender: johnl@ary.qy
In-Reply-To: <9EDE9834-2586-43BA-9681-AC576EFF5C30@amsl.com>
References: <9EDE9834-2586-43BA-9681-AC576EFF5C30@amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml-sg-cmt/qxb7HryxNzTLpphTqOV20RWds4o>
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: Thu, 17 Feb 2022 19:21:48 -0000

> 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

v2.23.0 | Report a Bug | By Email