Database rebuild

[DNSB]

Originally Posted by Jellby

After a few tries (communication failures, sqlitebrowser crashes, device resetting to "welcome to Kobo" status, etc.) I think I managed to do it.

Checking cover directories, I found a few *.parsed file that should not be there (the books had been moved to the SD card). It looks like the device (or calibre) didn't remove them automatically, and the common feature I see is all of them have an apostrophe in the filename. Of course, an apostrope or quote is probably more dangerous than spaces in filenames, so I wonder:

a. Why doesn't calibre avoid them?

b. Was I just unlucky or is this maybe a sign of a bug in the firmwar (3.5.0) or in calibre?

I did notice what may have been database issues with 3.5.0 and there were a thread started in this forum about database issues in 3.5.0. So far in the few days that I've had 3.8.0, I haven't seen any issues.

The apostrophe in the file name could be worse. In the original firmware for the Kobo ereader (mark 1), an apostrophe in the file name triggered ""The content you are trying to view is locked. Please use your Adobe ID to authorize etc." error. Download A Connecticut Yankee in King Arthur's Court from Gutenberg, copy it to your Kobo, can't be read. Rename the file to ACYiKAC.epub and it read with no problems. I had a lovely email discussion with Kobo's support staff over that issue before they admitted that yes, it was a bug. It appeared that I was being a bad boy for not using ADE to copy books to my Kobo as Calibre was not a supported option.

Regards,
David

[davidfor]

Originally Posted by Jellby

After a few tries (communication failures, sqlitebrowser crashes, device resetting to "welcome to Kobo" status, etc.) I think I managed to do it.

Checking cover directories, I found a few *.parsed file that should not be there (the books had been moved to the SD card). It looks like the device (or calibre) didn't remove them automatically, and the common feature I see is all of them have an apostrophe in the filename. Of course, an apostrope or quote is probably more dangerous than spaces in filenames, so I wonder:

a. Why doesn't calibre avoid them?

b. Was I just unlucky or is this maybe a sign of a bug in the firmwar (3.5.0) or in calibre?

I've done some testing. It seems that the device has only one problem with an apostrophe in the file name. It can load the book ok and generate and use the cover image. But when I deleted the book using the device, the cover images were not deleted. Calibre had no problem doing this.

The drivers in calibre handle file names. There is a default set of character to replace, but the drivers can override this. I'll add the apostrophe to ones that get changed.

[Jellby]

Good to know, that's another bug to test with future firmwares then.

If you change the filename handling, could you warn in big red letters first? Otherwise, sending an updated version of a book would generate a duplicate of the same book with a different filename.