IETF Logo Mail Archive

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

Tom Pusateri <pusateri@bangj.com> Thu, 15 February 2024 11:46 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 82FDAC14CF1F for <rfc-interest@ietfa.amsl.com>; Thu, 15 Feb 2024 03:46:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.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_DNSWL_HI=-5, 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 8RitD80a32iA for <rfc-interest@ietfa.amsl.com>; Thu, 15 Feb 2024 03:46:42 -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 53EB0C14F6ED for <rfc-interest@rfc-editor.org>; Thu, 15 Feb 2024 03:46:41 -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 558F52CC6F; Thu, 15 Feb 2024 06:46:40 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bangj.com; s=201907; t=1707997600; bh=jnZIsyCeIj+ssi3vObprNF3Zihxwy4PtopaVeDf3NEg=; h=From:Subject:Date:References:Cc:In-Reply-To:To:From; b=sJJkaYi/Q6bak+koTqffFdVJ2ghUXYKGR3fuimrkCEr9slpGxCKJ417mEpiZWvR84 PAfy50W0hUsUI6B8yAtCNvJvZ3Eb30hkt3Zyba16xUf82MkL33sS+ILq7oUM/mS36m WgqIjLjANyxvp6G9w5kpsTjDe6jM7Ir2hnCyrq/OUsAz77VIMvf2ZjXtdPSze1EW7y iywFmUdSoS+RrEfDFdDGNNXoS8DKiKJimT/HJ1DhVRR7iEiKDgbQ5t1EaBr/Vop67k rfmV31s1xpwxy/AGqgCB1QW1EWq6T8d3HHFwVR8hFdB62cqGa0jADsP5+KAlOK7KUs ap26RWtQN2mwg==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
From: Tom Pusateri <pusateri@bangj.com>
Mime-Version: 1.0 (1.0)
Date: Thu, 15 Feb 2024 06:46:39 -0500
Message-Id: <5A441C2B-271B-4220-8817-2C176D7E525E@bangj.com>
References: <2705E5C9-8F1E-4557-88E0-B328CE784EF0@tzi.org>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, rfc-interest@rfc-editor.org
In-Reply-To: <2705E5C9-8F1E-4557-88E0-B328CE784EF0@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: iPad Mail (21D61)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/VVTsznihkQYmD9QVLPTvtJ0RPbM>
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 11:46:46 -0000

Oooh. Maybe I should change the name to aa2unibox?

Tom

> On Feb 15, 2024, at 12:25 AM, Carsten Bormann <cabo@tzi.org> wrote:
> 
> 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:
> 
> <PastedGraphic-1.png>
> 
> 
> 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