MobileRead Forums - View Single Post - Why two separate page break xpaths in 0.6.x?

ldolse · 08-11-2009, 11:27 PM

This is with regard to bug #2718, which was about page breaks being inserted.

I understand now why the bug is invalid, I wasn't aware that an additional xpath had been intentionally added to insert more page breaks in final release. I'm just wondering why? It seems like a fair number of books could have a chapter headings that look like the following:

Code:

<h1>CHAPTER X</h1>
<h2>chapter title</h2>
<p>beginning of chapter text</p>

Which all displays on a single page at the beginning of the chapter. This additional xpath will now cause <h1>Chapter X</h1> to appear on a page all by itself.

I can see the benefit of having an additional xpath available to detect page breaks in some other fashion, but I'm not sure that it makes sense to have both the chapter detection xpath AND this one enabled by default....

08-11-2009, 11:27 PM	#1
ldolse Wizard Posts: 1,337 Karma: 123455 Join Date: Apr 2009 Location: Malaysia Device: PRS-650, iPhone	Why two separate page break xpaths in 0.6.x? This is with regard to bug #2718, which was about page breaks being inserted. I understand now why the bug is invalid, I wasn't aware that an additional xpath had been intentionally added to insert more page breaks in final release. I'm just wondering why? It seems like a fair number of books could have a chapter headings that look like the following: Code: <h1>CHAPTER X</h1> <h2>chapter title</h2> <p>beginning of chapter text</p> Which all displays on a single page at the beginning of the chapter. This additional xpath will now cause <h1>Chapter X</h1> to appear on a page all by itself. I can see the benefit of having an additional xpath available to detect page breaks in some other fashion, but I'm not sure that it makes sense to have both the chapter detection xpath AND this one enabled by default.... Last edited by ldolse; 08-11-2009 at 11:43 PM.