View Single Post
Old 01-11-2013, 10:43 AM   #12
chaley
"chaley", not "charley"
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 5,925
Karma: 1673776
Join Date: Jan 2010
Location: France
Device: Many android devices
Quote:
Originally Posted by kovidgoyal View Post
@chaley: Why not maintain a uuid->filename map on the device? That way if a file already exists, the filename to be used could be looked up from the map.
This doesn't solve half the problem, having different names on different devices for the same book. As far as I can tell, in general syncing reading positions requires the file names to be identical on each device; this is certainly true for moon+. Each device can get the file from a different path, so name generation for new books on all paths must result in the same value.

FWIW: we actually built what you are suggesting, then took it out because it invisibly changed fundamental calibre/device/template behavior. It would be easy to put it back, this time as an option, but as I said it doesn't solve the multiple-device problem.
chaley is offline   Reply With Quote