Quote:
Originally Posted by ldolse
I've got no idea on this stuff, keep hoping an expert on these nuances will chime in. Does .txt_flow1 need to go into the xhtml somewhere, and are you saying that the epub renderer knows which flow is flow1 vs. flow2 based on the manifest?
|
Sorry for my cryptic brevity & lack of clarity
In a single-css, multiple page definition model, this:
Code:
@page flow1 {....}
@page flow2 {....}
.txt_flow1 { page: flow1; font-family: ....blah..blah.... }
.txt_flow2 { page: flow2; font-family: ....blah..blah.... }
goes in the css.
The xhtml would have something like:
Code:
<body class="txt_flow1" style="">
...
</body>
So flow1 styled blocks in the xhtml refer to the .txt_flow1 class in the css, and thus to flow1 page layout.
Similarly for flow2 styled blocks.
Or you can create different stylesheets for each flow, and each xhtml can link to the appropriate style sheet.
Or you can skin the cat by ......
Having said all that .... I ran across this trivia while trying to do something completely different quite some time ago, and I've never actually used it, or even seen it used
So I'm really not an expert, but hopefully partly correct