On 15.03.2010 22:19, Martin Rex wrote:
...
It needs a painful lot of work to make free-floating formating
not come out with poor results. When I do the above, an ascii
arts with 3 lines of text and a box around is broken over from
page8->page9 for http://greenbytes.de/tech/webdav/rfc2616.html
...
Yes. (And thanks for retrying).
What you are observing is missing support for CSS3 paged media hints in
most browsers. It would be great if the UAs would get better on that.
(PrinceXML (<http://www.princexml.com/>) is a great program that gets
this right).
In order to support free-float formatting, you will have to
tag *ALL* paragraphs, bullet points, drawings, sections and
what have you with "non-breakability" information
(in TeX it is called "badness") so that formatting doesn't
"break" badly as it currently will do. HTML may be ok for
screen rendering, but it is very poor at printing.
HTML has nothing to do with that; CSS does. The necessary specs are
there, but implementations lag behind. Probably because fewer and fewer
people actually care about printing stuff (sic).
This particular free-float HTML-version of rfc2616 also creates
some close-to "intentionally left blank" pages (and the purpose
of page 120 in the above document is a mystery to me).
I have no idea what page 120 is for you (that's the point of a
reflowable format ;-). If you get me some more details (what's on 119
and on 121?), I may be able to offer a theory :-).
And while the Headers&Footers that a browser puts on a printout
might make sense for printing web pages, I strongly prefer the
original headers and footers on RFCs and I-Ds!
Again, something that is specified in the CSS paged media spec, and at
least one implementation gets it right already.
Best regards, Julian
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf