Quote:
Originally Posted by davidfor
@BeckyBooks: If everyone is happy with the change, send a PM to a moderator with asking for the plugin to be updated. But, you need to bump the version number so that calibre will detect and announce the update. It's in __init__.py.
|
Actually, I think I have some beta tweaks (related to formatting) on my test box. They're stable enough to roll out, as I've been using them myself, but they're also minor enough that I didn't want to make a new version for 'em. I wouldn't mind combining those with the new feature while we're operating.
Quote:
Originally Posted by deback
I don't know if I made myself clear enough. When there is a page-map.xml file in the epub, quite often, the page numbers at the top or bottom of ADE, depending on which version of ADE is being used, will be very inaccurate. The total page numbers will not be listed. It could show that there is only one page in the book, or it could say two pages, or maybe 3 pages or more, but it will be way off from the total actual pages in the book.
|
That doesn't really clarify anything, because "actual pages" could refer to several different things. For ebooks where a print edition exists, I tend to define "actual pages" by reference to the print version, which in theory should match a provided page map of either format (NCX or Adobe). It could also relate to the ADE-generated page numbers, which really have nothing to do with a reality-based page count. So, how are you using the term?
Furthermore, your report here is muddy:
Quote:
Let's say you're on page 250 in the epub file. The page number at the top or bottom of ADE might say that you're on page 2. Deleting the page-map.xml file fixes the problem, and then the total correct number of pages will be displayed in ADE. I've seen many page-map.xml files in epub files that messed up the page-numbering in the epub file. I've seen very few page-map.xml files in epub files that did not mess up the page-numbering.
|
In a previous message, you appeared to be saying a double page number would show up, but now it looks like an incorrect one shows up instead of the correct one. Finally, you also acknowledge that sometimes the file causes no such problems.
This is why sample ebooks make all the difference. That's something we can actually examine and test, and we can try different approaches to see what the results are. As it stands, all we have to go on are your reports, with no way to even verify that a problem exists, let alone what else may be contributing to it. It's like telling your mechanic that your car's electrical system is shot without even testing the battery to see if you've got power - maybe that's accurate, but there are other possibilities to consider.