stale ppi entry in _meta.xml causes deriver to fail
Bug #346017 reported by
samuel-archive
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Deriver |
In Progress
|
Medium
|
Hank Bromley | ||
Bug Description
see end of:
http://
I fixed this by removing the ppi tag from the _meta.xml and trying again.
can we have the deriver basically ignore old ppi values in the non-ia-book case?
(s3 connector here...)
Revision history for this message
| Hank Bromley (hank-archive) wrote | #1 |
| Changed in deriver: | |
| assignee: | nobody → hank-archive |
| importance: | Undecided → Medium |
| status: | New → In Progress |
To post a comment you must log in.
Yes, I was already planning to fix this. We don't want to just ignore old ppi values, because there's some page sampling involved in guessing the ppi, and in case of a conflict the old one might well be correct, with the new one simply having missed the pages that require a higher ppi.
In general, the max value is usually the right one, but not necessarily, as the pdf may have been replaced between runs. So I was thinking when there's a conflict I'd do a "best of 3" or some such.