Quote:
Originally Posted by chaley
I strongly suspect that you did not delete the books off the device between test 1 and test 2. This means that when you sent the book from calibre using the wireless device, calibre reused the file name from the first test. CC sees a file name that exists and is identical to what is there, so it is happy to use it. In other words, the calibre template was ignored.
|
Actually, no. For all the tests I've done so far I've always deleted the book before trying to resend. Even though I've checked
Settings - Filenames - Replace existing book files, I haven't tried to test this option yet.
Quote:
Originally Posted by chaley
When you pulled a book using the content server via book details, CC generates a file name. I see that there is a very longstanding bug here in that CC ignored the "calibre template" option you set. Because "Replace" was checked, CC's generated file name replaced the previous name. Had you pulled the book by long-pressing (which you couldn't because the book was already on the device), the option would have been respected and the calibre-generated name would have replaced the CC name. Given the behavior of the wireless device, it is not clear that this is good behavior.
|
Hmmm. I've just done Content Server downloads for 2 books which have never previously been on the phone - one with long-press and one with standard-press-plus-DOWNLOAD-button. Both of them incorrectly transferred with a {title} - {authors} filename.
ETA: Mea maxima culpa. I really need to remember that when alpha/beta-testing I must revert to using the official SmartDevice App Interface 0.0.1 driver, not the subclassed personal one I've been using for ages to force a small CSS change during book transfer. I've redone the Content Server tests (long-press and short-press) for 2 not-on-device-books. Filenaming is working correctly in 5.0.0.4 for the 'Use calibre's file names' setting.
I realise it is not reasonable for me to pursue why my personalised driver fails to rename correctly at this time. Maybe later (much later) when you have some free time after the v5 production release.
Quote:
Originally Posted by chaley
My head hurts when trying to work through all of this.
|
You're not wrong about that
No need to reply until it's convenient.