IETF Logo Mail Archive

Re: [xml2rfc] [irsg] UPDATE regarding <u> Re: AUTH48: RFC-to-be 9340 <draft-irtf-qirg-principles-11> for your review

John Levine <johnl@taugh.com> Fri, 03 March 2023 19:31 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 8C5DEC14CEE4 for <xml2rfc@ietfa.amsl.com>; Fri, 3 Mar 2023 11:31:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.846
X-Spam-Level:
X-Spam-Status: No, score=-1.846 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_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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="ERxQq4Yh"; dkim=pass (2048-bit key) header.d=taugh.com header.b="IPPuBEhI"
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 tTpTYzmyP3c1 for <xml2rfc@ietfa.amsl.com>; Fri, 3 Mar 2023 11:31:31 -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 95FE6C14CF1D for <xml2rfc@ietf.org>; Fri, 3 Mar 2023 11:31:31 -0800 (PST)
Received: (qmail 85079 invoked from network); 3 Mar 2023 19:31:28 -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=14c53.64024b10.k2303; bh=7Qw1P7Ds6riPpqOmOOAXjj6EEPH31n8DXmcQmsGr2Mo=; b=ERxQq4YhKvy8wB7F2yXhwJyrPycVhmlEn02WpyIrFrAXgif939X2bKl3pVm0FEx4x/+lkg1qCLyMvw7uk9F+V2nqRFpnVM7u6QYqgG9CZD1nuztk92xb82fYN6ZlgMcJI2whs0Fz6iwCSWh0j7QBYeOHSx1/C2u6PvgPtozEIsDuJJ98Z+r98vZcHTfrCvC2Q0Pr2++Wjb2qhrNSw0QSLqZqtxylAAqUja9dI5jtRabAFmWp3H0Mo1btG7h6HWrw9/OXaSPfx40UloB/q7cOFdmIlUqK7GumJ0jLm7lp/gHoLkTXsH4tBv1TYhMw4FWQ4f8Q4VusKPz2oku8AWFFvg==
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=14c53.64024b10.k2303; bh=7Qw1P7Ds6riPpqOmOOAXjj6EEPH31n8DXmcQmsGr2Mo=; b=IPPuBEhIOGDNf4+Srt02MVqz8VrI/SwLH8oD7eL6cItBfDFemreUDteyKsFvYth3PyhmzYISbKlMq8GQybiFwvRQ5BOpPa/XRUWnXDmECmSympH6ND83wX+TJQ1GjLxkNGdjNq5QpfjR4pQq7gu0bK850I0jT8A0nRpN8YT44TsKi0q011Bc/yEtq15r2nS1lNJWG1CUCS3grxHukGBGmAQypfYbkW42GTFBzSs5WlCsfFOis6uCZzfL8d432gkWYwb6Nqv+rhtg45tknI4ZFqbXAqxQi2/WFN9bywUy6AdBQgU2KNeAULtskr4qElii+oeCh037bbDgRqUDb0dNgA==
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; 03 Mar 2023 19:31:28 -0000
Received: by ary.qy (Postfix, from userid 501) id BAAEAA3C41DE; Fri, 3 Mar 2023 14:31:26 -0500 (EST)
Date: Fri, 03 Mar 2023 14:31:26 -0500
Message-Id: <20230303193126.BAAEAA3C41DE@ary.qy>
From: John Levine <johnl@taugh.com>
To: xml2rfc@ietf.org
In-Reply-To: <0DC566C3-F20D-4A4E-8B1F-E5CC11CA6BBF@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/31zz-VDFQ39bjMajxJ0lmYCD4VE>
Subject: Re: [xml2rfc] [irsg] UPDATE regarding <u> Re: AUTH48: RFC-to-be 9340 <draft-irtf-qirg-principles-11> for your review
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: Fri, 03 Mar 2023 19:31:37 -0000

It appears that Carsten Bormann  <cabo@tzi.org> said:
>Hi Sandy,
>
>this is an interesting discussion.
>
>I wasn’t realizing that any specific version of xml2rfc creates a repertoire of characters directly supported in PDF
>generation, and that using characters outside of that repertoire requires some development effort (font
>selection/qualification, font integration, new xml2rfc release). ...

The PDF spec includes a set of standard fonts: Times-Roman, Helvetica,
Courier, Symbol, Times-Bold, Helvetica-Bold, Courier-Bold,
ZapfDingbats, Times-Italic, Helvetica- Oblique, Courier-Oblique,
Times-BoldItalic, Helvetica-BoldOblique, Courier-BoldOblique.

They include a list of characters which appears to be the same as the
list in the 1985 Postscript manual with the addition of a Euro sign.
If you use any other font or any other characters in those fonts, you
are supposed to embed those characters in the document. If you don't,
they'll get rendered in amusing ways you can read about on
Stackoverflow. Fonts are bulky, so you want to avoid embedding more
characters or fonts than you actually use. We use Noto and Roboto
rather than any of the standard fonts so we embed everything.

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.

R's,
John

v2.23.0 | Report a Bug | By Email