IETF Logo Mail Archive

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

"Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org> Thu, 14 September 2017 21:07 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 E7492132199 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 14 Sep 2017 14:07:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 cKCnqoULWnca for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 14 Sep 2017 14:07:09 -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 AFD7F120724 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Thu, 14 Sep 2017 14:07:09 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 92DE9B812BA; Thu, 14 Sep 2017 14:06:55 -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 DD61EB812BA for <rfc-interest@rfc-editor.org>; Thu, 14 Sep 2017 14:06:53 -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 HmtrYLA5JfDf for <rfc-interest@rfc-editor.org>; Thu, 14 Sep 2017 14:06:53 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) by rfc-editor.org (Postfix) with ESMTPS id 0A5ADB812B9 for <rfc-interest@rfc-editor.org>; Thu, 14 Sep 2017 14:06:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 3EDCA1C2CBA; Thu, 14 Sep 2017 14:06:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xGwXBXBEZniK; Thu, 14 Sep 2017 14:06:46 -0700 (PDT)
Received: from Heathers-MacBook-Pro.local (c-73-181-135-61.hsd1.wa.comcast.net [73.181.135.61]) by c8a.amsl.com (Postfix) with ESMTPSA id 0D4761C1D11; Thu, 14 Sep 2017 14:06:46 -0700 (PDT)
From: "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
To: ietf@ietf.org, rfc-interest@rfc-editor.org
Message-ID: <09b0ed8b-c47a-83c3-9174-cce990bdb145@rfc-editor.org>
Date: Thu, 14 Sep 2017 14:07:05 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
Content-Language: en-US
Subject: [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>

Hello all,

RFC 8187, "Indicating Character Encoding and Language for HTTP Header
Field Parameters", is the first RFC to be published with UTF-8 encoding
and include characters not in the basic ASCII character set. This
document has been, with the author's consent, patience, and support,
used to test the existing tool chain to produce RFCs to see where the
environment has difficulty in handling non-ASCII characters. The RPC is
continues this testing with the PRECIS document cluster (C326), which is
currently in AUTH48.

The RPC and the Tools Team has identified several areas that need to be
modified to support these characters. Some of those areas will
ultimately be handled with the new format tools; others have been
modified as part of the more general work to prepare for the new RFC
format. For the documents being used to test the toolchain, a
significant amount of manual processing is required to publish the
RFCs with non-ASCII characters in the final text. In order to keep
overall processing times down, leave staff enough time to test
the other tools that are being developed as part of the RFC format
project, and allow the editors time to create and/or update new
procedures as the v3 tools are released, no additional non-ASCII
documents outside of RFC 8187 and the PRECIS cluster will be published
until the new format tools are in production.

Many thanks go out to Julian Reschke and Peter Saint-Andre for their
support, the Tools Team for answering a variety of technical questions,
and to the RPC staff who worked to ensure that the RFC
publication process resulted in readable RFCs.


Heather Flanagan, RSE

_______________________________________________
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