[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:10:38 PDT 2014

Being able to put two bits of connected text together on one page is an essential feature in some cases, but agreed, here it's only a nice to have

Being able to avoid destructive page breaks (*) is more than that.

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

(For example, three ways - I'm sure there are more - to keep two paragraphs together - assuming possible - is to tag the first, tag the second, and wrap both in something. There would have to be a better reason than I can see to require one of these. Rather it would be what fits the model.)

(*) Where of course not impossible. If someone creates a 200 line table, I'm not very sympathetic.

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: rfc-interest [mailto:rfc-interest-bounces at rfc-editor.org] On Behalf Of Julian Reschke
Sent: 27 June 2014 15:56
To: John Levine; 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.

On 2014-06-27 16:32, John Levine wrote:
> In article <53AD62D2.9000009 at gmx.de> you write:
>> On 2014-06-27 14:12, Dearlove, Christopher (UK) wrote:
>>> Does the current version allow breaking tables with heading rows 
>>> repeated, but only at certain points, and
>> keeping two independent things, of any types, together on one page?
>> No.

The "No" was about "keeping two independent things together".

> You can do running heads with "running" elements, although it appears 
> you have to duplicate the text you want to put into the header in a 
> paragraph in a class that will be moved to the page header or footer.

Not necessary. Just use <thead> and <tbody> properly.

Again: this is old stuff, and we've been doing this for ages. Just test it.

> There's some examples here:
> http://www.w3.org/TR/css3-gcpm/#running-elements
> To keep text together, there's "page-break-inside: avoid".
> I'd think it wouldn't be too hard to add an attribute to <preamble> to 
> say that it would be nice to repeat its contents if the figure or 
> table spills across a printed page boundary.  In antique (but very 
> useful) tools like tbl, there's a tag that says to do that.

Yes, that's possible, but I'm not convinced that you actually want this all the time.

Which brings us to the fact that optimizing vertical space is really nice if you produce books, but it simply might be overkill for occasional printouts.

Best regards, Julian

rfc-interest mailing list
rfc-interest at rfc-editor.org

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