Quote:
Originally Posted by BetterRed
My reading of your posts seemed to assume that because the books could be accessed by the viewer the DRM must have been removed when the books were added. Just wanted to let you know that is a false assumption.
|
Thanks. I am aware but can see how that might not have been clear.
The assumption I'm making (obviously incorrectly) is that if calibre e-book reader (with assistance of whatever other plugins) has no trouble opening and paginating a book... that count pages plugin, when relying on the calibre e-book viewer "algorithm" would use the same code path and also not have any trouble.
Indeed when it comes to DRM, for certain formats (azw3, etc) count pages plugin does NOT have issue with this method. But for the other formats it does (even though calibre e-book viewer does not have any problem with those other formats).
I agree that if I convert (e.g. to epub stripping DRM in process) that count pages plugin will probably count the epub format fine...since this seems to be a format-specific issue for the count pages plugin (azw, azw4, htmlz, kfx).
Was hoping to resolve the issue so that count pages plugin could use calibre e-book viewer for all supported formats to count pages before needing to do a full library conversion that I will do at some point in the future.
Maybe the answer here is that the formats that don't have a problem DID actually (for unknown reason) have the DRM stripped during library import (could disable the "other plugin" and see if I can still view them). And the second part would be that the count pages plugin does not use the same code path as the calibre e-book viewer does and so does not benefit from the other plugin making the file accessible, meaning count pages plugin really only works on files that already have DRM removed, rather than any files the calibre viewer can access.