Quote:
Originally Posted by icallaci
Yes, and it was getting worse, although even before 4.31 I was having a problem with duplicate books in my Calibre library. I always put my current read into a temporary Calibre library so that I can fix typos, formatting problems, etc. as I read. When I finish the book, I reimport the fixed version back into my permanent Calibre library. Something must have changed the way books were saved, because a book titled (for example) "This Is the Title" would be saved to disk as "This Is the Title: And This is the Subtitle," even though I had "polished" the ebook to update the metadata. So when I reimported the ebook back into my permanent library, it wasn't recognized as a duplicate and was instead added as a new book with the longer title.
|
None of that has anything to do with the device. It is all happening in calibre. If you are getting that title when you do a "Save to disk" (though while you said "saved to disk", I suspect you are either talking about the "Send to device" or what calibre uses internally) then either that is what the title in the library is, or, you have a template that sets the file name as that (for the save-to-disk and send-to-device).
Quote:
Anyway, after I installed firmware 4.31 on my Elipsa, I started experiencing database errors, disk i/o errors, and other fun things. I suspect the two things are related somehow, but I decided to go back to square one. I even created a new Calibre library and copied all the ebooks from the old library into the new one, hoping to standardize the way metadata was displayed and saved.
|
I don't quite understand how that would have worked. Calibre displays the metadata as it displays the metadata. Unless you were removing custom columns when doing this.
Quote:
Then I reset my Elipsa, and reinstalled and reimported everything from the newly created Calibre library. It seems to be working now. But it's only been 3 days, so I'm still hesitant to say it's fixed.
|
As to the issues on the device, I am seeing more occurrences of Windows reporting the filesystem is dirty. But, nowhere near as many as before Kobo updated dosfstools in 4.23 (I think that was the version). I usually do the scan and have not had an issue whether I do or don't. And I haven't had any corrupt databases.