Re: [xml2rfc] [xml2rfc-dev] Unicode box-drawing for a new --table-borders value?

Lars Eggert <lars@eggert.org> Mon, 01 February 2021 12:40 UTC

Return-Path: <lars@eggert.org>
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 ADB803A10FE for <xml2rfc@ietfa.amsl.com>; Mon, 1 Feb 2021 04:40:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eggert.org
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 eb88YStCZZsV for <xml2rfc@ietfa.amsl.com>; Mon, 1 Feb 2021 04:40:32 -0800 (PST)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2C313A10FC for <xml2rfc@ietf.org>; Mon, 1 Feb 2021 04:40:31 -0800 (PST)
Received: from [IPv6:2a00:ac00:4000:400:acf1:c447:f5f0:6aa9] (unknown [IPv6:2a00:ac00:4000:400:acf1:c447:f5f0:6aa9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id E5FB6600057; Mon, 1 Feb 2021 14:40:23 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1612183223; bh=xrYm/lVqbnVkfn/sVrwDL4QcOYCEdwT6e+L8ygwTtqA=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=kHbB4Zul5CT58HhvCBV8Sntov5mdXFmGCKOhmC90Xmar9CrQk4Thhj3fbRMcPj/Cd NQWBXKQkLrj5m74Anfw8yQtBVwrEk79P9OAePqQjueZfdnwA7VCP+VvKFFm2oXqi1D V9G3a5lWrjzqnVNX3aGR2+RLo50SKcZsQ8sioIbk=
From: Lars Eggert <lars@eggert.org>
Message-Id: <41D0C73A-9A16-4C2A-B535-AE0FFCD4A50B@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_7363A225-C007-483E-A974-D16330BFB9EA"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
Date: Mon, 1 Feb 2021 14:40:23 +0200
In-Reply-To: <20210130191455.169316D02C27@ary.qy>
Cc: xml2rfc@ietf.org
To: John Levine <johnl@taugh.com>
References: <20210130191455.169316D02C27@ary.qy>
X-MailScanner-ID: E5FB6600057.A1E1A
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/ru7U_U9-Yy7kidn4cVgvQ9rCdBk>
Subject: Re: [xml2rfc] [xml2rfc-dev] Unicode box-drawing for a new --table-borders value?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <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: Mon, 01 Feb 2021 12:40:34 -0000

Hi,

On 2021-1-30, at 21:14, John Levine <johnl@taugh.com> wrote:
> The ones that occur to me beyond people's names are math symbols like a≥b and
> words that are sometimes written with accents like coördinate.  For the math
> symbols, I get the impression that people really want TeX style equation typesetting
> which while not impossible, would be a major extension.

not only math symbols, but also greek other letters commonly used in math.

+1 for Latex math stuff. Not sure if you saw https://ntap.github.io/rfc8312bis/draft-eggert-tcpm-rfc8312bis.html, it uses latex-style math and renders it via tex2svg for HTML or (my fork of) asciitex for text.

> There's also typesetting stuff like “quotes” which we decided not to
> do when this came up before but we might revisit.

Yes, and various dashes/spaces would be useful.

Lars