Quote:
Originally Posted by ChaJudLeoBit
I used headers, but I may have chosen H2 instead of H1 because they came out SO BIG. I will go check right now.
I take that back. All chapter headings are H1.
I'll include a screen shot of the chapter list and my TOC.
|
Actually, I was talking, or recalling, Charlene's post in this:
https://www.mobileread.com/forums/sho...22&postcount=3 in which she'd used a paragraph class for chapterheads. My bad.
Vis-a-vis this:
Quote:
|
I sent an e-mail to the person who attempted the upload to find out if this was an option. If she chose the second, this would cause the program to be unable to detect chapters?
|
Allowing Nook to make changes to the book allows it to override the CSS, so, yes: it could. Not necessarily will, but could. Why don't you just use your own test account at NookPress and test it yourself? That's what I do when I have a client doing the driving, and I'm not there to see what's happening.
I don't see any immediate reason that your book's chapters shouldn't be detected, except one hairball possibility, which I'd love to say is nuts, but: is it possible that NookPress now also looks for an HTML TOC? Which you don't appear to have in your ePUB? Yes, yes, I know: not needed for ePUB2, and preferably, not used, but I wonder if NookPress is now looking at Word-generated TOC's, which are inline TOC's, for chapters? Just a ponderment.
Also, vis-a-vis this:
Quote:
|
I used headers, but I may have chosen H2 instead of H1 because they came out SO BIG.
|
That's what CSS is for. Fix them there, rather than then choosing a different heading.
Without seeing more, it's very difficult to know what's going on there.
ETA: I see Toxaris got to this post first. What he said.
Hitch