Thread: Modify ePub plugin dev thread
View Single Post
Old 06-22-2011, 10:34 PM   #152
capnm
Groupie
capnm knows the difference between 'who' and 'whom'capnm knows the difference between 'who' and 'whom'capnm knows the difference between 'who' and 'whom'capnm knows the difference between 'who' and 'whom'capnm knows the difference between 'who' and 'whom'capnm knows the difference between 'who' and 'whom'capnm knows the difference between 'who' and 'whom'capnm knows the difference between 'who' and 'whom'capnm knows the difference between 'who' and 'whom'capnm knows the difference between 'who' and 'whom'capnm knows the difference between 'who' and 'whom'
 
Posts: 156
Karma: 10001
Join Date: Feb 2011
Device: sony
Quote:
Originally Posted by ldolse View Post
@capnm, I'm sorry, but I've got to admit I have no idea what problem you're trying to solve with your description.
Probably because I was thinking in circles ...

If my preferences are all set to 10pt, I assume Quality Check will flag any epubs with an @page other than 10pt.
And probably also flag any epub with any margins in a body statement.
But will it also flag epubs without any @page or body statements? Such as Calibre generated epubs?

Quote:
Regarding jackie_w's and capnm's question about why Calibre specifies @page on a flow by flow level vs css, I recall Kovid mentioning in an old thread that this was in case different margins were required for different flows. That said I'm not sure if Calibre is able to follow through with that logic and set separate margins per flow, maybe someone else can comment....
Supposedly that can all be done in the css like this ...

Code:
@page flow1 {....}
@page flow2 {....}

.txt_flow1 { page: flow1 }
.txt_flow2 { page: flow2 }
but it wouldn't surprise me in the least if it didn't always work, or work as desired
capnm is offline   Reply With Quote