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

Carsten Bormann <cabo@tzi.org> Mon, 01 February 2021 21:18 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65FE83A14B5 for <xml2rfc-dev@ietfa.amsl.com>; Mon, 1 Feb 2021 13:18:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=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 paWu3dFDnTcB for <xml2rfc-dev@ietfa.amsl.com>; Mon, 1 Feb 2021 13:18:33 -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 7B57F3A14B4 for <xml2rfc-dev@ietf.org>; Mon, 1 Feb 2021 13:18:32 -0800 (PST)
Received: from [192.168.217.118] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (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 4DV15L3D46zyWc; Mon, 1 Feb 2021 22:18:30 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <ff3f3ea3-5bf8-61cc-ef3b-e08c434ebd9b@gmx.de>
Date: Mon, 01 Feb 2021 22:18:30 +0100
Cc: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, xml2rfc-dev@ietf.org
X-Mao-Original-Outgoing-Id: 633907109.971806-b704a5796117ffb9c720ab00128ef33c
Content-Transfer-Encoding: quoted-printable
Message-Id: <E1A5D3A8-39E7-48D3-AF55-D250400CB239@tzi.org>
References: <8735yje4kt.fsf@fifthhorseman.net> <342339E7-A47C-4C51-8852-7FFBB6A8C750@eggert.org> <87lfcacstt.fsf@fifthhorseman.net> <078f11bc-2adf-5126-a9b6-20cf3167d554@gmx.de> <87zh0nbl6u.fsf@fifthhorseman.net> <ff3f3ea3-5bf8-61cc-ef3b-e08c434ebd9b@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/CMpC-hoqyDjA1l3RT0KZdGUzxMs>
Subject: Re: [xml2rfc-dev] Unicode box-drawing for a new --table-borders value?
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Feb 2021 21:18:37 -0000

On 2021-02-01, at 22:03, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
>> It sounds to me like you're saying the existing drafts i've been working
>> on (like [0]) are somehow skirting the IETF consensus on what makes a
>> legitimate document by "abusing" the artwork mechanism.
> 
> IMHO: non-ASCII characters in artwork were allowed to express examples
> where non-ASCII characters are *required*. This does not seem to be the
> case here. See the rules in
> <https://greenbytes.de/tech/webdav/rfc7997.html#n-rules-for-the-use-of-non-ascii-characters>.
> 
> (These are not my rules, and I might not even support them, but these
> are the rules currently).

One of the qualifications for a German professor is that you need to be able to make up a valid argument for anything, in particular when talking to university administration (which is trained in making up arguments *against* anything).

In this case, of course, RFC 7997 does support this usage as it makes an allowance for the rules of a programming language [1].  The author clearly has defined a new (visual) programming language here and uses that in his artwork.

Grüße, Carsten

[1]: 3.6 code components:
https://tools.ietf.org/html/rfc7997#section-3.6