IETF Logo Mail Archive

Re: [rfc-i] What are current rules on non-ascii in documents?

Carsten Bormann <cabo@tzi.org> Thu, 15 February 2024 12:21 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: rfc-interest@ietfa.amsl.com
Delivered-To: rfc-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FFABC18DB91 for <rfc-interest@ietfa.amsl.com>; Thu, 15 Feb 2024 04:21:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_TEMPERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jy1T82Ktavji for <rfc-interest@ietfa.amsl.com>; Thu, 15 Feb 2024 04:21:11 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97101C18DB86 for <rfc-interest@rfc-editor.org>; Thu, 15 Feb 2024 04:21:10 -0800 (PST)
Received: from client-0165.vpn.uni-bremen.de (client-0165.vpn.uni-bremen.de [134.102.107.165]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4TbDgR1bLbzDCgQ; Thu, 15 Feb 2024 13:21:07 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <5A441C2B-271B-4220-8817-2C176D7E525E@bangj.com>
Date: Thu, 15 Feb 2024 13:21:06 +0100
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, rfc-interest@rfc-editor.org
X-Mao-Original-Outgoing-Id: 729692466.5257601-859eef5def8e9bc500c347f1574d3b97
Content-Transfer-Encoding: quoted-printable
Message-Id: <57A761F5-F376-45B0-A2DD-813B12582EB8@tzi.org>
References: <2705E5C9-8F1E-4557-88E0-B328CE784EF0@tzi.org> <5A441C2B-271B-4220-8817-2C176D7E525E@bangj.com>
To: Tom Pusateri <pusateri@bangj.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/Q_4U4CoIr8KBSIeyFI9vKFwRvdw>
Subject: Re: [rfc-i] What are current rules on non-ascii in documents?
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Feb 2024 12:21:18 -0000

On 2024-02-15, at 12:46, Tom Pusateri <pusateri@bangj.com> wrote:
> 
> Oooh. Maybe I should change the name to aa2unibox?

Well, renamings are always disruptive.
I think it would be enough to explain that the function of this tool is translating traditional ASCII-only RFC box diagrams into Box drawing characters.

(I need to include this in kramdown-rfc’s easy artwork/sourcecode management…)

Grüße, Carsten

v2.23.0 | Report a Bug | By Email