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

John Levine <johnl@taugh.com> Sat, 04 March 2023 04:19 UTC

Return-Path: <johnl@iecc.com>
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 3CF62C151AE2 for <xml2rfc@ietfa.amsl.com>; Fri, 3 Mar 2023 20:19:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.148
X-Spam-Level:
X-Spam-Status: No, score=-4.148 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, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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="MEK/P6a0"; dkim=pass (2048-bit key) header.d=taugh.com header.b="cceAKs8K"
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 OmMpVruSZuIC for <xml2rfc@ietfa.amsl.com>; Fri, 3 Mar 2023 20:19:11 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 5AC7DC15171E for <xml2rfc@ietf.org>; Fri, 3 Mar 2023 20:19:10 -0800 (PST)
Received: (qmail 7051 invoked from network); 4 Mar 2023 04:19:07 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=1b87.6402c6bb.k2303; bh=SiFXuPug/SxAC2myAb/2fgQIUxh3ADATG8nlmRazIbA=; b=MEK/P6a0gB/6aZey+cbsRg+pOhQ1Erjo/5oxULhjK4wxy+CJ15ei8koGCLV7XTuknPBtMLo7fWQaloUjWMfDf+YejgAa+XnxXs8Hc3xftOwUzTPs/WIGUEqz4cttZlBAv8uZM9F9ZLtx5Iqjuu9AQT2ZhHM1p89oyC/IhWF4VJtEfy1Mxqe/zJd/oc8cLqshXk4LvsvvZP8ZTtv0NlhXifcSXHIh9uWbbQjPqRQ1fyNqruD/osVBn0ddN65bIQQvnzNQY76vAfT3xNHKyDoR5kn6TbLAVUb7Tx5rJZok5vk1OELOsgsZpJtVlK/WE97iU8l6tRtWX2dfsiBrE6SAqQ==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=1b87.6402c6bb.k2303; bh=SiFXuPug/SxAC2myAb/2fgQIUxh3ADATG8nlmRazIbA=; b=cceAKs8KEgawAIDdxgzf+BwfSGEgwxWiL7hNly+V7oE3Oqo85E1ZJJn6VZg25Cr6WzhxpljtYuipWFluEd4SN5L1aSj/9OKcxVEt6KzUvhymknL65WccH5UjhhtzNTrBZr4uJbSAVllkaAQUv67YtuLFa2HTIhj+83TFnNmxMRHmkDG4bIKdfBwFsvFzRGQvgK2VcDdz2b95VLbIot9KT/toZlJjYGE8j91xg6smb7x6hzfyCnRsmjHIxYlIpo9GLDdMFilUTH1klesDuiB0ojfNBQvQBZgRbnZOVQFyhE26yE0OEcpFFZuSA24qT8H68Ggqmr+s3AkHorGFW8v4Cw==
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.3 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 04 Mar 2023 04:19:07 -0000
Received: by ary.qy (Postfix, from userid 501) id DA71BA438468; Fri, 3 Mar 2023 23:19:05 -0500 (EST)
Date: Fri, 03 Mar 2023 23:19:05 -0500
Message-Id: <20230304041905.DA71BA438468@ary.qy>
From: John Levine <johnl@taugh.com>
To: xml2rfc@ietf.org
In-Reply-To: <E28A3A7E-10C5-452F-9442-C979551EFAF1@tzi.org>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/_syESGWJOuh1uowIOxd6NEJP0S4>
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 04:19:16 -0000

It appears that Carsten Bormann  <cabo@tzi.org> said:
>On 3. Mar 2023, at 20:31, John Levine <johnl@taugh.com> wrote:
>> 
>> Getting the fonts right is surprisingly tricky. If you look at the
>> earler PDF RFCs, you'll see junk fonts SourceCodePro and
>> TimesNewRomanPSMT which I think were installed on the machine used to
>> make the PDFs so Weasyprint included them just in case.
>
>Right.  That is a (rather pesky!) implementation problem that I was hoping we are already addressing.

Once I noted it and pointed it out, they fixed it.

>Extracting the repertoire resulting from the fonts that we do want to have appears to me to be just a SMOP (small matter of
>programming).
>Making the process explicit of expanding this repertoire is probably a sane way to handle the requirement for this process now
>that we have drawn it into the light.

Our main font is Noto Serif and our fixed pitch font is Roboto Mono.
Both include Latin, Greek, and Cyrillic letters and a wide range of
punctuaton and other stuff:

https://fonts.google.com/noto/specimen/Noto+Serif/glyphs
https://fonts.google.com/specimen/Roboto+Mono/glyphs?query=roboto+mono

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.

R's,
John