View Single Post
Old 05-08-2015, 01:57 PM   #6
Phssthpok
Age improves with wine.
Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.
 
Posts: 590
Karma: 95229
Join Date: Nov 2014
Device: Kindle Oasis, Kobo Libra II
Quote:
Originally Posted by odamizu View Post
For "Insert page break before" option, try: //*[name()='h1']

That works for me to limit page breaks to only <h1> and keeps any <h2> subheads on the same page.

@eschwartz: I have a few books that use <h1> for chapter heads and <h2> for subheads. With the above "insert page break before" option it works fine. Why is this improper?
Thanks, I'll give it a try. Meanwhile some other books (with different CSS) don't exhibit this problem, so I'm confused.

I agree with you about heads & subheads. Structurally, the H2s are headings, not just paras with a special appearance. They should be denoted as such in the HTML. However, I then want to use CSS to control the appearance of that structure, and not have the appearance undermined by the conversion tool. Eschwartz's position seems to be that I should destroy the structure to give the correct appearance... in which case I could use nothing but <div> or <span> with CSS to give the appearance of headings, quotations and other structural elements.
Phssthpok is offline   Reply With Quote