[rfc-i] use cases for page breaking hints, Re: Update on the plain text thread(s)

Dearlove, Christopher (UK) chris.dearlove at baesystems.com
Fri Jun 27 08:54:44 PDT 2014

Frankly, I'm already spending more time on this than I should. That's how things are.

I tripped over this mostly by accident, I subscribed to this list for some specific purpose I've now forgotten, and then didn't unsubscribe (though mostly I don't read most of it). So I'm effectively just a random author off the street here.

Am I unique? I tend to assume that in regards like this, that would be surprising. So why no one else? Well, not quite no one else. But not many. (Though not that many people here at all.) Maybe not many random authors - or actually, more important, readers - wander in here. OK, decisions were made some time back, and I can appreciate that people have moved on. But mostly random authors/readers tend not to read every RFC published, especially on what appear minutae of document formats.

Christopher Dearlove
Senior Principal Engineer, Information Assurance Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194 |  Fax: +44 1245 242124
chris.dearlove at baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687

-----Original Message-----
From: John R Levine [mailto:johnl at taugh.com] 
Sent: 27 June 2014 16:19
To: Dearlove, Christopher (UK)
Cc: rfc-interest at rfc-editor.org
Subject: RE: [rfc-i] use cases for page breaking hints, Re: Update on the plain text thread(s)

----------------------! WARNING ! ---------------------- This message originates from outside our organisation, either from an external partner or from the internet.
Consider carefully whether you should click on any links, open any attachments or reply.
Follow the 'Report Suspicious Emails' link on IT matters for instructions on reporting suspicious email messages.

> I suspect that what's really wanted is to stand back and say, OK, authors want some pagination control. What works?

I don't recall anyone else asking for this.  If you think it's important, why don't you mock something up and propose it?

John Levine, johnl at taugh.com, Taughannock Networks, Trumansburg NY Please consider the environment before reading this e-mail.

This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.

More information about the rfc-interest mailing list