Quote:
Originally Posted by JvdW
Now I should tell you that I use Calibre on more than one computer to sync news, books etc. The first example is from a system at home (0.7.2?) and the second is from Calibre at work (0.7.2). I Think that might complicate things since at work I can plugin my Reader and have Calibre detect it, unplug it and it scans rather quickly then (10secs). Only the first time it took a long time and only then are the dates changed.
The problem is I can't figure out where those dates are coming from since those books are on my Reader, not in the library at work but in my library at home. (which on second thoughts my not be true, will check and report if relevant)
|
The dates come from the books on the device. Calibre's library is irrelevant.
The dates are checked (and possibly changed) on the first scan, whenever a book is added or deleted, or whenever collections are changed. In these cases, calibre scans the books folders on the device for files (books), gets the 'ctime' date from the file, breaks it into components (year, month, etc) using the local timezone (required by FAT file systems), then creates a date string using the format
Code:
"%w, %d %m %Y %H:%M:%S GMT"
It appears that one of your machines is reporting an incorrect ctime for the books. It isn't reasonable that all were created on 1 Jan 2008 at noon. That looks like someone's idea of a good default date.
What OS are you running at work and at home? Are both of them locale-aware and do both have valid locales? From what you say, it appears that the work machine is doing it right, but the home machine is not.