Quote:
Originally Posted by davidfor
So, like the page list but no anchors in the book. That sounds like it could be a separate plugin, but the metadata writer is probably sensible. And both also make sense.
And what I find interesting is that it sounds like the page count doesn't have to have any real relationship to the size of the book. If it is a 100,000 word book and someone says it is 10 pages long then the page index would be built that way.
An alternative is to do the page count while doing the conversion. The Count Pages plugin does have a callback for other plugins to use it, but it runs the count in a job, so it probably isn't suitable here. But, it does have sample code for a few algorithms.
|
Where this process is best implemented seems a gray area to me. The number of pages in the book could be considered to be a piece of metadata, but their exact placement seems more like content to me. At the moment I plan to allow page number creation during conversion and allow it to be updated when metadata is embedded.
I plan to allow those users who care about having a specific number of pages to determine it themselves using their preferred method. For everyone else there is already a simple method implemented within the plugin that yields a page count close to the actual number of pages as given by a pre-existing EPUB pagelist in a set of books I tested with.
The exact placement of those pages within the book is already handled using another simple algorithm and I do not plan on changing that.
I am still considering the best approach, but I don't want to spend much more time on this. There aren't that many users of this plugin.
Added: After checking again I was able to find the custom column information in a place accessible during conversion so I will add the ability to configure the lookup name for the custom column containing the page count.