IETF Logo Mail Archive

Re: [xml2rfc] [irsg] character sets, was UPDATE regarding <u>

Carsten Bormann <cabo@tzi.org> Sat, 04 March 2023 08:39 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F9C4C151520 for <xml2rfc@ietfa.amsl.com>; Sat, 4 Mar 2023 00:39:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.188
X-Spam-Level:
X-Spam-Status: No, score=-4.188 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hFAF0JHSkpnm for <xml2rfc@ietfa.amsl.com>; Sat, 4 Mar 2023 00:39:15 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE0EAC151549 for <xml2rfc@ietf.org>; Sat, 4 Mar 2023 00:39:14 -0800 (PST)
Received: from smtpclient.apple (p548dc9a4.dip0.t-ipconnect.de [84.141.201.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4PTJCz6n0DzDCbG; Sat, 4 Mar 2023 09:39:11 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20230304041905.DA71BA438468@ary.qy>
Date: Sat, 04 Mar 2023 09:39:01 +0100
Cc: xml2rfc@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <5E205D41-48AD-4CEB-A867-E893D7B33CAC@tzi.org>
References: <20230304041905.DA71BA438468@ary.qy>
To: "John R. Levine" <johnl@taugh.com>
X-Mailer: Apple Mail (2.3731.400.51.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/pMk1uHtyQfNdQgSjKGppMZnrmYY>
Subject: Re: [xml2rfc] [irsg] character sets, was UPDATE regarding <u>
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Mar 2023 08:39:21 -0000

On 4. Mar 2023, at 05:19, John Levine <johnl@taugh.com> wrote:
> 
> I think the most likely reasons to want characters they don't include
> is if there are strings in languages that are written with different
> characters, like Hebrew, Arabic, Chinese, or Japanese.

I would expect we will need to support the letters within the human names that we want to present.
The Noto family of fonts is a very good choice to make this possible.

This discussion came up for ➔ (U+2794) though, and at least to me it was a total surprise that this isn’t in the current repertoire.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email