IETF Logo Mail Archive

Re: [rfc-i] RFC Series publishes first RFC with non-ASCII characters

Toerless Eckert <tte@cs.fau.de> Thu, 21 September 2017 15:01 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA2E512ECEC for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 21 Sep 2017 08:01:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.713
X-Spam-Level:
X-Spam-Status: No, score=-2.713 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FAKE_REPLY_C=1.486, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FeFNqSQidCED for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 21 Sep 2017 08:01:58 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78D94134B71 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Thu, 21 Sep 2017 08:01:37 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 781AEB81531; Thu, 21 Sep 2017 08:01:16 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 2B5B8B8123F; Tue, 19 Sep 2017 13:47:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rvNvfCZIqpIs; Tue, 19 Sep 2017 13:47:48 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) by rfc-editor.org (Postfix) with ESMTPS id 68947B8123E; Tue, 19 Sep 2017 13:47:48 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 4F32958C4F8; Tue, 19 Sep 2017 22:48:02 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 373E2B0CC2F; Tue, 19 Sep 2017 22:48:02 +0200 (CEST)
Date: Tue, 19 Sep 2017 22:48:02 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>, rfc-interest@rfc-editor.org
Message-ID: <20170919204802.GB20344@faui40p.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Mailman-Approved-At: Thu, 21 Sep 2017 08:01:15 -0700
Subject: Re: [rfc-i] RFC Series publishes first RFC with non-ASCII characters
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

One usability comment:

As a frequent reader of RFC, primarily using the text format, it would be
great if there was a human readable tag, eg: as another header line indicating
enough about the format used by the document to quickly know what the
minimum required viewer is to get a guaranteed correct display
- ASCII, UTF8, HTML (when graphics are needed), ...

Eg:


Internet Engineering Task Force (IETF)                        J. Reschke
Request for Comments: 8187                                    greenbytes
Obsoletes: 5987                                           September 2017
Category: Standards Track
Format: ASCII / UTF8 / "graphics" / ...

Cheers
    Toerless
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email