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

Lars Eggert <lars@eggert.org> Mon, 01 February 2021 14:53 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 EDBF23A11EE; Mon, 1 Feb 2021 06:53:45 -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 D4Lg-XD35rpU; Mon, 1 Feb 2021 06:53:44 -0800 (PST)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:4000:400:211:32ff:fe22:186f]) (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 CBA3A3A11ED; Mon, 1 Feb 2021 06:53:43 -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 26F2F600057; Mon, 1 Feb 2021 16:53:34 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1612191214; bh=FEFoWdQZTedqCJULJ1Fa9sk8UH98YULZLT6C4MF3KzM=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=xqdWK1rG9gWO9ugIezOlMzTSnew+FWQ+gnioOL1YSEcLTjYO0agJPNlgOTBijV5/5 rciL4HHreEWkmis6PmlRD0NBcta4llm/qEYAvUCXfG0rTQ1SBJVPXlZw5/iIbWuiyV HzpD0rqkkb1RXHZ0zX4FhR/p3VJ6aK2GlEthWfPM=
From: Lars Eggert <lars@eggert.org>
Message-Id: <450E303F-B4E3-451E-B1BC-FA92DBC29063@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_9EA3E781-9965-4768-B3E3-EDD94B82B541"; 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 16:53:33 +0200
In-Reply-To: <87lfcacstt.fsf@fifthhorseman.net>
Cc: xml2rfc-dev@ietf.org, xml2rfc@ietf.org
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
References: <8735yje4kt.fsf@fifthhorseman.net> <342339E7-A47C-4C51-8852-7FFBB6A8C750@eggert.org> <87lfcacstt.fsf@fifthhorseman.net>
X-MailScanner-ID: 26F2F600057.AF294
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/Yde2l-fnYzIByP3Bo3Enm7WhhuA>
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 14:53:46 -0000

On 2021-1-30, at 18:06, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:
> On Sat 2021-01-30 07:22:43 +0200, Lars Eggert wrote:
>> I think that would be excellent, but AFAIK Unicode can (still) only be
>> used in contact names (see the recent "Unicode in xml2rfc v3" thread
>> over on rfc-interest@). I really hope we can just get to an agreement
>> to allow Unicode anywhere in the document.
> 
> whoops, i've been using unicode (in particular, the box-drawing
> characters and a few fancy arrows) to pretty good effect (imho) in
> several I-Ds already, for example:
> 
>    https://www.ietf.org/archive/id/draft-dkg-lamps-e2e-mail-guidance-00.html#name-multilayer-cryptographic-en

Ah! You're right, in artwork, there is no issue.

I was trying to use Unicode in the text, which has the restriction I mentioned.

Lars