IETF Logo Mail Archive

Re: [rfc-i] Unicode in xml2rfc v3

Carsten Bormann <cabo@tzi.org> Sat, 19 December 2020 06:41 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FE273A0844; Fri, 18 Dec 2020 22:41:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.65
X-Spam-Level:
X-Spam-Status: No, score=-2.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_BLOCKED=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 Nd9Kp2mCMngY; Fri, 18 Dec 2020 22:41:24 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DAC53A083E; Fri, 18 Dec 2020 22:41:24 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id B9F68F4074D; Fri, 18 Dec 2020 22:41:12 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 04065F4074D for <rfc-interest@rfc-editor.org>; Fri, 18 Dec 2020 22:41:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HEIgQlCQVBVa for <rfc-interest@rfc-editor.org>; Fri, 18 Dec 2020 22:41:08 -0800 (PST)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) by rfc-editor.org (Postfix) with ESMTPS id 040E9F40741 for <rfc-interest@rfc-editor.org>; Fri, 18 Dec 2020 22:41:07 -0800 (PST)
Received: from [192.168.217.118] (p548dca87.dip0.t-ipconnect.de [84.141.202.135]) (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 4CybjR1rNLzyVd; Sat, 19 Dec 2020 07:41:15 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <1ff2777e-92a3-2d50-0363-a397800319ed@petit-huguenin.org>
Date: Sat, 19 Dec 2020 07:41:14 +0100
X-Mao-Original-Outgoing-Id: 630052874.657493-b1b3214b45f4e63f510d33a1aef7687b
Message-Id: <B74913D5-164D-4987-919A-E9A77B082B14@tzi.org>
References: <20201216184835.CE1CA2ABC7A1@ary.qy> <AF7F0885-2D39-4F8D-A43B-E1D015146EAE@eggert.org> <72467617-6ca7-b2af-b826-d264c6b6380e@gmail.com> <D8AC8FA8-74DC-4B93-AB5B-73FBE1880F26@ietf.org> <162b0211-bc98-d0c8-b67f-c3068664b9f9@petit-huguenin.org> <CABcZeBPghk2uDJcAHWw6ZaWhnthmCBCpL_28-FQyUOZ4-it3CA@mail.gmail.com> <1ff2777e-92a3-2d50-0363-a397800319ed@petit-huguenin.org>
To: Marc Petit-Huguenin <marc@petit-huguenin.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Subject: Re: [rfc-i] Unicode in xml2rfc v3
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: RFC Interest <rfc-interest@rfc-editor.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On 2020-12-19, at 00:56, Marc Petit-Huguenin <marc@petit-huguenin.org> wrote:
> 
> CLDR short names, prefixed in a similar way than Unicode codepoints (e.g. <N+ROMAN NUMERAL NINE> for <U+2178>) could still be translated to their graphical equivalent in HTML and PDF, but will not make me want to gouge my eyes when implementing from the text format.

That’s what <u> would be good for.

But if I have, say, a formal notation that uses ⅸ as a normal part of writing, just as people talking about congestion control are likely to use α and β, the text must not be littered with explanations any more than it would be when using seriously weird characters such as *, @, or #.

That would also enable RFCs to exhibit typographic normalcy e.g. in the use of dashes and minus signs, which need to be distinct from hyphens in the non-monospace fonts used now for RFCs in their HTML and PDF forms.

Grüße, Carsten

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email