Form feed in Net-UTF8? (Was: FWD: Re: Comments on Unicode Format for Network Interchange

Stephane Bortzmeyer <bortzmeyer@nic.fr> Fri, 05 October 2007 15:12 UTC

Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Idoqu-00074y-7c; Fri, 05 Oct 2007 11:12:32 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1Idoqt-00074t-IN for discuss-confirm+ok@megatron.ietf.org; Fri, 05 Oct 2007 11:12:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Idoqt-00074l-8o for discuss@apps.ietf.org; Fri, 05 Oct 2007 11:12:31 -0400
Received: from mx2.nic.fr ([192.134.4.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Idoqq-0000XV-De for discuss@apps.ietf.org; Fri, 05 Oct 2007 11:12:31 -0400
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id 12C4B1C0100; Fri, 5 Oct 2007 17:12:28 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx2.nic.fr (Postfix) with ESMTP id 0E8141C00F7; Fri, 5 Oct 2007 17:12:28 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.4.69]) by relay2.nic.fr (Postfix) with ESMTP id 00BA158EBBF; Fri, 5 Oct 2007 17:12:28 +0200 (CEST)
Date: Fri, 5 Oct 2007 17:12:27 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: John C Klensin <john-ietf@jck.com>
Subject: Form feed in Net-UTF8? (Was: FWD: Re: Comments on Unicode Format for Network Interchange
Message-ID: <20071005151227.GA31232@nic.fr>
References: <398A6C120C8B166FCBD3BDAF@p3.JCK.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <398A6C120C8B166FCBD3BDAF@p3.JCK.COM>
X-Operating-System: Debian GNU/Linux 4.0
X-Kernel: Linux 2.6.18-4-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: discuss@apps.ietf.org
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

Doug Ewell said:

> > I recommend that the control code FF (form feed, U+000C) be
> > likewise permitted.  The form feed function is well known and well
> > defined in almost all printing functions, and all RFCs issued in
> > modern times use FF to separate pages.  It would ironic indeed for
> > the Internet-Draft to retain the requirement that form feeds
> > "SHOULD NOT be used unless required by exceptional circumstances"
> > while advancing toward publication as an RFC, complete with form
> > feeds!

And I did not see anywhere a discussion of this specific point. I
notice that draft-klensin-net-utf8-04 still disallows (actually, it is
a SHOULD NOT in section 2.1) form feeds and I'm not sure of the
rationale. Why end-of-lines and not end-of-pages?