View Single Post
Old 10-09-2013, 07:18 AM   #25
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 45,424
Karma: 27757236
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
Sigh, how many times do I need to say the same things.

Yes, the file name truncation logic has changed in 1.x. File names are now truncated a little more strictly than before, this was because of a bug in the old logic that could, in some corner cases, cause file paths to become longer than 265 characters.

The length at which filenames are truncated has nothing to do with the location of the library. If it did, it would be a recipe for disaster. Suppose you create a library at c:\library and tomorrow decide to move it to c:\users\me\my documents\my school library. Boom, your files would become inaccessible. calibre allows for ~70 characters for the path to the library and truncates the file/folder names so that any library path upto 70 characters will work. And no those numbers are not exact, if you want the exact calculation, use the source, Luke.

And yes, I know that you can use UNC style paths to access paths longer than 265 characters on windows, however, while calibre itself could do that, lots of other tools would choke and be unable to even see the files, including Windows Explorer itself.
kovidgoyal is offline   Reply With Quote