IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Wed, 14 February 2024 20:09 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 71CADC151520 for <rfc-interest@ietfa.amsl.com>; Wed, 14 Feb 2024 12:09:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-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 PqR1r9ejT4bl for <rfc-interest@ietfa.amsl.com>; Wed, 14 Feb 2024 12:09:56 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::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 AC878C15154D for <rfc-interest@rfc-editor.org>; Wed, 14 Feb 2024 12:09:55 -0800 (PST)
Received: from smtpclient.apple (p548dcbf2.dip0.t-ipconnect.de [84.141.203.242]) (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 4TZq6n2pQ9zDCcL; Wed, 14 Feb 2024 21:09:53 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <B831D08A-B030-4D68-9F96-0F1024C2DB5B@bangj.com>
Date: Wed, 14 Feb 2024 21:09:42 +0100
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, rfc-interest@rfc-editor.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <3C54D12E-89E0-43BF-ADBB-26F66081E55A@tzi.org>
References: <8d32c491-fff0-4a3e-9a39-d5bb6c3d930e@alum.mit.edu> <B831D08A-B030-4D68-9F96-0F1024C2DB5B@bangj.com>
To: Tom Pusateri <pusateri@bangj.com>
X-Mailer: Apple Mail (2.3774.400.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/a6kX0m720LHxPH-t991_rQcYcAg>
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: Wed, 14 Feb 2024 20:09:59 -0000

On Feb 14, 2024, at 21:08, Tom Pusateri <pusateri@bangj.com> wrote:
> 
> FYI, I wrote a tool to convert from ascii art to unicode so you could have multiple versions. You might find it useful.

How would you use these multiple versions in one RFC?

Grüße, Carsten

v2.23.0 | Report a Bug | By Email