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

John C Klensin <john-ietf@jck.com> Fri, 05 October 2007 15:58 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 1IdpYx-0000dZ-0B; Fri, 05 Oct 2007 11:58:03 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1IdpYw-0000dG-6C for discuss-confirm+ok@megatron.ietf.org; Fri, 05 Oct 2007 11:58:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IdpYv-0000bV-S5 for discuss@apps.ietf.org; Fri, 05 Oct 2007 11:58:01 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IdpYu-0001x8-KU for discuss@apps.ietf.org; Fri, 05 Oct 2007 11:58:01 -0400
Received: from [127.0.0.1] (helo=p3.JCK.COM) by bs.jck.com with esmtp (Exim 4.34) id 1IdpYu-000Ama-A8; Fri, 05 Oct 2007 11:58:00 -0400
Date: Fri, 05 Oct 2007 11:57:59 -0400
From: John C Klensin <john-ietf@jck.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Subject: Re: Form feed in Net-UTF8? (Was: FWD: Re: Comments on Unicode Format for Network Interchange
Message-ID: <E877BB045466189D5B4E287A@p3.JCK.COM>
In-Reply-To: <20071005151227.GA31232@nic.fr>
References: <398A6C120C8B166FCBD3BDAF@p3.JCK.COM> <20071005151227.GA31232@nic.fr>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
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


--On Friday, 05 October, 2007 17:12 +0200 Stephane Bortzmeyer
<bortzmeyer@nic.fr> wrote:

> 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?

Because line breaks are required even for unformatted streams.
FormFeeds are not.  

But I find the above arguments reasonably persuasive and will
put FF back in unless others feel strongly about this.

    john