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 20:08 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 83E04C15154D for <rfc-interest@ietfa.amsl.com>; Wed, 14 Feb 2024 12:08:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, 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 84ElslzoCgYN for <rfc-interest@ietfa.amsl.com>; Wed, 14 Feb 2024 12:08:04 -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 2B4B7C151547 for <rfc-interest@rfc-editor.org>; Wed, 14 Feb 2024 12:08:03 -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 6F99A2CCC6; Wed, 14 Feb 2024 15:08:02 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bangj.com; s=201907; t=1707941282; bh=VyHjUQRchPt8fhAKEEDfcyuNz08zE8cr1S4jkr3sAs8=; h=From:Subject:Date:References:Cc:In-Reply-To:To:From; b=A7Zz4G03G1x/HYqo5LrOLbeFn+ZsvfT1iBAQLadhG6TJw2QE8PwB2eyo4G7JSwFKT x0Mju9zNd6V9Vd0JR+k17OjInseYxrTTU8LkQjrSgbWUrxnk6FZ89GwmtfTntGDf/F gxfJe+57vyhXE3aOff/rRmcizq/FYF42+7nlwZZ748TQV19I7UF0QbfPDuqf/ZmFqP QibGmOL5O6IsdrweGK9gjhsJcuJ1fRdYz9Mux4Kano7gGLXtPRJcL9dhaNb2bQ61as Gu2gB7JDwKrFEPzMmer7LPWK4DGRkxJZ/PG8dk9tWMjQDMO9LryMpasRqLkMck1WCb /TT9GvMj1EJ0Q==
Content-Type: multipart/alternative; boundary="Apple-Mail-BB899603-6106-4D97-9643-3B601D7BAEF0"
Content-Transfer-Encoding: 7bit
From: Tom Pusateri <pusateri@bangj.com>
Mime-Version: 1.0 (1.0)
Date: Wed, 14 Feb 2024 15:08:01 -0500
Message-Id: <B831D08A-B030-4D68-9F96-0F1024C2DB5B@bangj.com>
References: <8d32c491-fff0-4a3e-9a39-d5bb6c3d930e@alum.mit.edu>
Cc: rfc-interest@rfc-editor.org
In-Reply-To: <8d32c491-fff0-4a3e-9a39-d5bb6c3d930e@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: iPad Mail (21D61)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/2gu3grn6Z8Dq8mijXBOAdRo2jNQ>
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:08:08 -0000

FYI, I wrote a tool to convert from ascii art to unicode so you could have multiple versions. You might find it useful.

$ pip install aa2unicode

https://pypi.org/project/aa2unicode/

Tom

> On Feb 14, 2024, at 2:42 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> 
> I'm doing a genart review of draft-ietf-lamps-e2e-mail-guidance-14.
> As usual I checked for nits using https://author-tools.ietf.org/idnits.
> 
> Typically this turns up a few non-ascii warnings due to author names, which I ignore. But this doc has bigger issues. It has many examples containing stuff like:
> 
> └┬╴multipart/signed; protocol="application/pkcs7-signature"
> ├─╴[protected part]
> └─╴application/pkcs7-signature
> 
> It certainly looks prettier than doing something similar with ascii characters, but making that change wouldn't harm the readability of the document.
> 
> Is this sort of usage now allowed?
> 
>    Thanks,
>    Paul
> 
> _______________________________________________
> rfc-interest mailing list
> rfc-interest@rfc-editor.org
> https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email