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 05:25 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 E8CD4C151062 for <rfc-interest@ietfa.amsl.com>; Wed, 14 Feb 2024 21:25:19 -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 rxMYshkP0_RL for <rfc-interest@ietfa.amsl.com>; Wed, 14 Feb 2024 21:25:16 -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 32CBCC14F6FB for <rfc-interest@rfc-editor.org>; Wed, 14 Feb 2024 21:25:13 -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 4Tb3RS39VpzDCbT; Thu, 15 Feb 2024 06:25:08 +0100 (CET)
Content-Type: multipart/mixed; boundary="Apple-Mail=_54C037DD-9725-4B78-A7AF-E42E311A1465"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <883024E7-ECFE-483E-AAC5-B08BBFB75DA2@bangj.com>
Date: Thu, 15 Feb 2024 06:24:57 +0100
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, rfc-interest@rfc-editor.org
Message-Id: <2705E5C9-8F1E-4557-88E0-B328CE784EF0@tzi.org>
References: <3C54D12E-89E0-43BF-ADBB-26F66081E55A@tzi.org> <883024E7-ECFE-483E-AAC5-B08BBFB75DA2@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/YotIH8ll3t3DXysI7BBsA6F1h_8>
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 05:25:20 -0000

On Feb 15, 2024, at 00:05, Tom Pusateri <pusateri@bangj.com> wrote:
> 
> You could write it ascii art and see how that looked or run aa2unicode on it and see if you liked unicode better.

➔
You could write it traditional ascii-only art with -+| and see how that looked or run aa2unicode on it and see if you liked box drawing characters better.

FTFY.

(Its Unicode in both cases.)

Grüße, Carsten

PS. Now if I knew why my (chromium-based) browser does this:



Looks fine in emacs (using “Hack” font):

% aa2unicode ip.txt
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
┌───────┬───────┬───────────────┬───────────────────────────────┐
│Version│  IHL  │Type of Service│          Total Length         │
├───────┴───────┴───────────────┼─────┬─────────────────────────┤
│         Identification        │Flags│     Fragment Offset     │
├───────────────┬───────────────┼─────┴─────────────────────────┤
│  Time to Live │    Protocol   │        Header Checksum        │
├───────────────┴───────────────┴───────────────────────────────┤
│                         Source Address                        │
├───────────────────────────────────────────────────────────────┤
│                      Destination Address                      │
├───────────────────────────────────────────────┬───────────────┤
│                    Options                    │    Padding    │
└───────────────────────────────────────────────┴───────────────┘

v2.23.0 | Report a Bug | By Email