IETF Logo Mail Archive

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

Tom Pusateri <pusateri@bangj.com> Wed, 14 February 2024 23:05 UTC

Return-Path: <pusateri@bangj.com>
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 D4330C151099 for <rfc-interest@ietfa.amsl.com>; Wed, 14 Feb 2024 15:05:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bangj.com
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 h3m_xucFDdZ3 for <rfc-interest@ietfa.amsl.com>; Wed, 14 Feb 2024 15:05:05 -0800 (PST)
Received: from oj.bangj.com (69-77-154-174.static.skybest.com [69.77.154.174]) (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 A8144C14CF15 for <rfc-interest@rfc-editor.org>; Wed, 14 Feb 2024 15:05:05 -0800 (PST)
Received: from smtpclient.apple (69-77-155-156.static.skybest.com [69.77.155.156]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id 3E0D82CCD2; Wed, 14 Feb 2024 18:05:04 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bangj.com; s=201907; t=1707951904; bh=5YmreI8W8nkxpBtcOqWPOhDb9wUDOxhRglmzMl4rR0M=; h=From:Subject:Date:References:Cc:In-Reply-To:To:From; b=A7Zi7lGy2aYye5mUBkJ8uREcWBPhM1pKs1S2f52XMNI+24b3vF2UJWXKeHyTp55Mw hKRso0UEQ8DwmOHECvI/7eQ7ZzlYDThdaoe04ZbJaPPgYw2C38Jif3uBUu7TUwjmXm cTIhR4FKvRKUlDq4/sSTnFUG7fTlV0Pwi1BgdyniynNF+yu//W/y5DC0rtG3zG+GgI MK7mkRBabb+s2AW9EcwPdcBcfZsu4MGa6c4ixq2mCQDv/5Na2kvfx4xFUlEc+ddJZh xx5yreBsw0dtDg8t/BIBcM970mbPxa7Zhela1FhgHDb3irOJ2r7ZKuSf32/TA5Tfbu DXtGWmd51i8Mw==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Tom Pusateri <pusateri@bangj.com>
Mime-Version: 1.0 (1.0)
Date: Wed, 14 Feb 2024 18:05:03 -0500
Message-Id: <883024E7-ECFE-483E-AAC5-B08BBFB75DA2@bangj.com>
References: <3C54D12E-89E0-43BF-ADBB-26F66081E55A@tzi.org>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, rfc-interest@rfc-editor.org
In-Reply-To: <3C54D12E-89E0-43BF-ADBB-26F66081E55A@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: iPad Mail (21D61)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/XYSQ9rq1ec_9vi7L-tLD0C2iVno>
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 23:05:09 -0000


> On Feb 14, 2024, at 3:40 PM, Carsten Bormann <cabo@tzi.org> wrote:
> 
> 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
> 

Haha. Sorry. I meant “try” multiple versions. You could write it ascii art and see how that looked or run aa2unicode on it and see if you liked unicode better.

Tom

v2.23.0 | Report a Bug | By Email