Re: [Tools-discuss] UTF-8 box characters with wavy lines in XML2RFC v3 draft

Carsten Bormann <cabo@tzi.org> Wed, 06 November 2019 07:51 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2CD2120C01 for <tools-discuss@ietfa.amsl.com>; Tue, 5 Nov 2019 23:51:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-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 OappA5xEQ11k for <tools-discuss@ietfa.amsl.com>; Tue, 5 Nov 2019 23:51:26 -0800 (PST)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFAA1120BFF for <tools-discuss@ietf.org>; Tue, 5 Nov 2019 23:51:26 -0800 (PST)
Received: from [192.168.2.100] (p548DC893.dip0.t-ipconnect.de [84.141.200.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 477Jd86Pwlz10BC; Wed, 6 Nov 2019 08:51:24 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <8F23347E-D33C-415E-8D0D-EC3AF2017268@nostrum.com>
Date: Wed, 6 Nov 2019 08:51:24 +0100
Cc: Tom Pusateri <pusateri@bangj.com>, "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>, Tom Pusateri <pusateri=40bangj.com@dmarc.ietf.org>, tools-discuss <tools-discuss@ietf.org>
X-Mao-Original-Outgoing-Id: 594719482.478665-41bfa39abc8ce6796f3437d9f2bc9355
Content-Transfer-Encoding: quoted-printable
Message-Id: <32583250-B918-42DD-83D7-A770E6BDB71F@tzi.org>
References: <31468A3A-FF68-4F58-BC89-54B277A423F1@bangj.com> <8F23347E-D33C-415E-8D0D-EC3AF2017268@nostrum.com>
To: Adam Roach <adam@nostrum.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/JZjkmTB_SWzTPNBNugTWJPgDF7o>
Subject: Re: [Tools-discuss] UTF-8 box characters with wavy lines in XML2RFC v3 draft
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Nov 2019 07:51:29 -0000

On Nov 6, 2019, at 07:09, Adam Roach <adam@nostrum.com>; wrote:
> 
>> But we completely control the HTML document and can even embed the font.  This sounds like a solvable problem.
>> 
> 
> 
> Sure, and my take is that your proposed cure would be several orders of magnitude worse than the disease. The prospect of requiring specific fonts for proper HTML rendering is almost certainly not what we want.

We already embed the font (PT Mono).

I’m not very good with the inspector, but Chrome appears to say about this draft [1]:
PT Mono—Local file(2280 glyphs)
Courier—Local file(24 glyphs)
Lucida Grande—Local file(2 glyphs)

I don’t know how to get Chrome to reveal which characters of the HTML source which glyph out of the above list.

Grüße, Carsten

[1]: https://datatracker.ietf.org/doc/html/draft-pusateri-dnsop-update-timeout