Max two pages per chaper - iPad only

[illustrata]

I've been making good progress getting the hang of things with Sigil and this epub, and pub has been displaying consistently everywhere (ADE, epubreader, iPad). But suddenly, the iPad/iBooks display has totally whacked out.

I have a number of chapters, but the iPad will display a maximum of two pages in each chapter. In fact, it shows only a fraction of the total pages that would normally be displayed. The TOC is fine, but if you click on a item that's beyond the second "page" of the chapter, it sends you to the head of the chapter. ADE, Calibre and Epubreader have no problem displaying the entire pub.

Sigil has crashed a few times today, I don't know if something got corrupted along the way.

I'm totally stumped. And things were going so well... Should I just remove the styling and see if that does anything?

Thanks for any ideas on this odd issue.

[huebi]

Have a look if the chapter is bigger then 300k

[illustrata]

Thanks for your suggestion. Just to clarify, I have been working with this pub from the beginning and have had no problems at all with any chapter. I haven't added any additional content (converting from a paperback). The ipad has always displayed it correctly up until about an hour ago -- now each and every chapter over two pages long (profile or landscape), flips to the head of the next chapter.

Just so I know though, where do I find the chapter size?

[theducks]

Originally Posted by illustrata

Thanks for your suggestion. Just to clarify, I have been working with this pub from the beginning and have had no problems at all with any chapter. I haven't added any additional content (converting from a paperback). The ipad has always displayed it correctly up until about an hour ago -- now each and every chapter over two pages long (profile or landscape), flips to the head of the next chapter.

Just so I know though, where do I find the chapter size?

Did you 'Flightcrew' your work so far?
ADE has a nasty habit of ignoring stuff with errors


Size will not be a Sigil 'feature' (there is no Size limit in the EPUB Spec).
Size is simply a (common) device problem.

(Start to) UNzip the EPUB (Open with:<your unzip program>). You can just review the 'packed size' column, then discard/abort the unzip. and continue the work on the EPUB.

[illustrata]

Well Flightcrew was illuminating.

I had couple of minor errors which I corrected, and then

"filename/OEBPS/Text/"
'This resource is reachable but not present in the OPF <manifest>...'

Something's gunked up, right?

...I see it -- bad formatting of interior links. Coded them like an image...wrong. We'll see if that's the ticket...

[illustrata]

OK, I have a spanking clean pub (according to Flightcrew and Threepress Epub validator)...

...and iBooks on iPad and iPhone (and no where else) still shows me only two 'pages' per chapter.

[theducks]

Originally Posted by illustrata

Well Flightcrew was illuminating.

I had couple of minor errors which I corrected, and then



Something's gunked up, right?

...I see it -- bad formatting of interior links. Coded them like an image...wrong. We'll see if that's the ticket...

"Gunked"?

That error says you have a folder ONLY specified somewhere

You are probably looking for "../Text/#something" in one or more files.

missing is the filename.xhtml before the hashmark

[illustrata]

Thanks a bunch. I found all the errors and my epub validates all over the place and I still get only two pages per chapter.

I went back and got an old version of the CSS, loaded that epub and sure enough, 182 pages.

What can you put in CSS to make a epub show you only two pages per chapter??? Augh...

[Toxaris]

I have heard of this problem before with some epubs I made. Haven't looked at the problem though, I don't have an iPad.

[Jellby]

Originally Posted by illustrata

I went back and got an old version of the CSS, loaded that epub and sure enough, 182 pages.

What can you put in CSS to make a epub show you only two pages per chapter??? Augh...

Post the CSS files here, and we can have a look. If I remember correctly neither epubcheck nor Flightcrew actually validate the CSS files, so you might have some error there without knowing.

[illustrata]

OK, all the CSS I had validates; here's what I took out to get things back to normal:

body {
font-family: Corisande, sans-serif;
font-size: 100%;
line-height: 140%;
margin: 0;
padding: 18em;
}

I also removed some code recommended to center text vertically -- I used another approach.

html, body { height: 100%;
margin: 0;
padding: 0;
}
.wedge {
float: left;
height: 50%;
margin-bottom: -2em;
}
.container {
clear: both;
height: 4em;
position: relative;
}
table, tr, th {
height: 4em;
width: 100%;
text-align: center;
}

Not sure which was the culprit...

[Jellby]

body {
...
padding: 18em;
}

What on earth induced you to add a 18em padding around (and inside) the text body? This goes in all 4 sides, so it's effectively 36em narrower and shorter... I'm not surprised it caused havoc.

html, body { height: 100%;

I don't know what's the purpose of that, it looks redundant at best. It might be expected that the "100%" refers to the screen height, but I don't think it works that way, I've learned that relative heights tend to fall on your head.

[illustrata]

No, that was a typo, 1.8em; I don't know if there 18em would be appropriate anywhere, of course.

There is still a lot I don't seem to be able to predict about cascading in general, and i devices in particular. I was just getting the hang of it on web pages. Meh.

Thanks for your help; until we meet again at my next indiscernible error...

[cybmole]

may not apply in your case but a missing or misplaced full stop or semicolon anywhere in css definitions can invalidate everything that follows it e.g. you had table not .table in your example above

[Jellby]

Originally Posted by illustrata

No, that was a typo, 1.8em; I don't know if there 18em would be appropriate anywhere, of course.

That's better, but it still looks too wide to me. Also note that top/bottom margin/padding in the body element applies only to the first and last "pages" in the flow, the body is the whole text, not each screen. If you want to set a page margin, better use something like:

@page { margin: 1em; } /* or 2mm, or 5px... */
html body { margin: 0; padding: 0; }