View Single Post
Old 04-23-2010, 08:41 PM   #12
charleski
Wizard
charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.
 
Posts: 1,196
Karma: 1281258
Join Date: Sep 2009
Device: PRS-505
Quote:
Originally Posted by DaleDe View Post
Do you suppose the @page CSS can be used somehow to do this?

Dale
Hmm, can't think of any. For Adobe's method the work, you have to have text somewhere on the page that's being displayed which is tagged with the selector specified in the rules section of the template. That means this text has to be present on every page of the document.

I get the strong feeling that Adobe introduced the page template idea as a preliminary model back when the epub spec was still in flux and decided not to develop it any further when certain people made a big fuss about not wanting any sort of proprietary extensions (and, of course, this was a part of the whole css vs XSL-FO thing). While the idea of keeping the standard completely open is laudable, the standard has languished from neglect, partially as a result.
charleski is offline   Reply With Quote