Re: [rfc-i] Unicode in xml2rfc v3
Henrik Levkowetz <henrik@levkowetz.com> Tue, 01 December 2020 17:58 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 7CA243A13F4; Tue, 1 Dec 2020 09:58:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.652
X-Spam-Level:
X-Spam-Status: No, score=-2.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 t3RQrrtJlsAR; Tue, 1 Dec 2020 09:58:23 -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 D13353A13DF; Tue, 1 Dec 2020 09:58:23 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 84077F40714; Tue, 1 Dec 2020 09:58:21 -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 D731DF4070F for <rfc-interest@rfc-editor.org>; Tue, 1 Dec 2020 09:58:19 -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 476QDTOf-cEQ for <rfc-interest@rfc-editor.org>; Tue, 1 Dec 2020 09:58:15 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) by rfc-editor.org (Postfix) with ESMTPS id B3434F40714 for <rfc-interest@rfc-editor.org>; Tue, 1 Dec 2020 09:58:14 -0800 (PST)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:54439 helo=tannat.local) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1kk9uq-0004HM-8f; Tue, 01 Dec 2020 09:58:16 -0800
To: Lars Eggert <lars@eggert.org>, rfc-interest@rfc-editor.org
References: <F2E370D6-BCA9-4902-836E-8C5BADFE5209@eggert.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <4cff4b9c-6464-659d-8b27-32396b59182c@levkowetz.com>
Date: Tue, 01 Dec 2020 18:58:07 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <F2E370D6-BCA9-4902-836E-8C5BADFE5209@eggert.org>
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: rfc-interest@rfc-editor.org, lars@eggert.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
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>
Content-Type: multipart/mixed; boundary="===============6864265088106405931=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>
Hi Lars, The way to go, given the current limitations, is to provide the equations within <artwork>. This would work both for unicode text artwork (with the limitation that it will use a monospaced font) and svg artwork, if you can produce that from the math formula input. I have an idea of how to improve math support substantially, and I strongly believe it's needed and appropriate, but for now the approach above is what is available. Looking to the future, I also mentioned Math support in the new work section of my implementation notes: https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation-notes-11#section-5.1 Best regards, Henrik On 2020-12-01 18:35, Lars Eggert wrote: > Hi, > > we're at the moment revising RFC8312, the CUBIC congestion controller for TCP. > There is quite a bit of math in RFC8312, and even more in the papers that > describe CUBIC, some of which we're planning to roll into RFC8312bis. > > That math uses a bunch of greek letters, which we needed to ASCIIfy for RFC8312. > One thing I was planning to do for the bis was to reduce the difference between > the paper and the RFC, by using the greek letters in the RFC. Since, you know, > xml2rfc v3 is supposed to handle Unicode. > > Except, as most of you probably know but I didn't, you can't just use Unicode. > You need to wrap it in a <u> tag, and it must be rendered with "num" in the format. > > Which means that while I can write a formula in kramdown-rfc2629: > > ~~~ math > W_{est} = W_{est} + α_{aimd} * \frac{segments_{acked}}{cwnd} > ~~~ > > and have it automatically rendered in SVG as (via tex2svg): > > and in ASCII (via asciitex) as > > segments > acked > W = W + α * ------------- > est est aimd cwnd > > but I cannot use "α<sub>aimd</sub>" in the text of the RFC - it gets rendered as > "α_(aimd)". > > And using "<u>α</u><sub>aimd</sub>" gets rendered as the even uglier ""α" (GREEK > SMALL LETTER ALPHA, U+03B1)_(aimd)". I can of course play with the format > string, but since there is no way to not at least use "char", I have basically > no option here. > > I had really been hoping that v3 would enable better math. Unicode is not just > for names... > > Thanks, > Lars > > > > _______________________________________________ > rfc-interest mailing list > rfc-interest@rfc-editor.org > https://www.rfc-editor.org/mailman/listinfo/rfc-interest >
_______________________________________________ rfc-interest mailing list rfc-interest@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-interest
- [rfc-i] Unicode in xml2rfc v3 Lars Eggert
- Re: [rfc-i] Unicode in xml2rfc v3 Henrik Levkowetz
- Re: [rfc-i] Unicode in xml2rfc v3 Lars Eggert
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Lars Eggert
- Re: [rfc-i] Unicode in xml2rfc v3 Lars Eggert
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Julian Reschke
- Re: [rfc-i] Unicode in xml2rfc v3 Julian Reschke
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Julian Reschke
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Michael Richardson
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Lars Eggert
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Lars Eggert
- Re: [rfc-i] Unicode in xml2rfc v3 Julian Reschke
- Re: [rfc-i] Unicode in xml2rfc v3 Martin Thomson
- Re: [rfc-i] Unicode in xml2rfc v3 John R Levine
- Re: [rfc-i] Unicode in xml2rfc v3 Lars Eggert
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 John R Levine
- Re: [rfc-i] Unicode in xml2rfc v3 tom petch
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Brian E Carpenter
- Re: [rfc-i] Unicode in xml2rfc v3 Julian Reschke
- Re: [rfc-i] Unicode in xml2rfc v3 Jay Daley
- Re: [rfc-i] Unicode in xml2rfc v3 Julian Reschke
- Re: [rfc-i] Unicode in xml2rfc v3 Brian E Carpenter
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Eric Rescorla
- Re: [rfc-i] Unicode in xml2rfc v3 Brian E Carpenter
- Re: [rfc-i] Unicode in xml2rfc v3 Martin Thomson
- Re: [rfc-i] Unicode in xml2rfc v3 Brian E Carpenter
- Re: [rfc-i] Unicode in xml2rfc v3 Julian Reschke
- Re: [rfc-i] Unicode in xml2rfc v3 tom petch
- Re: [rfc-i] Unicode in xml2rfc v3 Julian Reschke
- Re: [rfc-i] Unicode in xml2rfc v3 Paul Kyzivat
- Re: [rfc-i] Unicode in xml2rfc v3 Marc Petit-Huguenin
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Joel M. Halpern
- Re: [rfc-i] Unicode in xml2rfc v3 Eric Rescorla
- Re: [rfc-i] Unicode in xml2rfc v3 Marc Petit-Huguenin
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Marc Petit-Huguenin
- Re: [rfc-i] Unicode in xml2rfc v3 John R Levine
- Re: [rfc-i] Unicode in xml2rfc v3 Marc Petit-Huguenin
- Re: [rfc-i] Unicode in xml2rfc v3 John R Levine
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann
- Re: [rfc-i] Unicode in xml2rfc v3 Marc Petit-Huguenin
- Re: [rfc-i] Unicode in xml2rfc v3 John R Levine
- Re: [rfc-i] Unicode in xml2rfc v3 John R Levine
- Re: [rfc-i] Unicode in xml2rfc v3 Salz, Rich
- Re: [rfc-i] Unicode in xml2rfc v3 Marc Petit-Huguenin
- Re: [rfc-i] Unicode in xml2rfc v3 Marc Petit-Huguenin
- Re: [rfc-i] Unicode in xml2rfc v3 Martin J. Dürst
- Re: [rfc-i] Unicode in xml2rfc v3 Lars Eggert
- Re: [rfc-i] Unicode in xml2rfc v3 Paul Kyzivat
- Re: [rfc-i] Unicode in xml2rfc v3 Carsten Bormann