View Single Post
Old 02-17-2014, 11:47 PM   #26
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
The temporary folders issue (when deleting a book) only happened on unusual filesystem mounts, like when I reported this using a school computer. It is a fat client running LTSP, so the filesystem is I believe mounted from the server computer. And it only kicked in after the book gets deleted, which if I understand correctly should be after the copy was made. Something to do with the new database backend having a new method of sending files to the trash.

The filename truncation was an issue involving a lack of proper support for long filenames (a Windows problem) and it meant that people expected to find their books under the usual {author}\{title} - {author}.{format} location, but didn't, since the unusually long field was given to the filesystem in shortened form. calibre kept perfect track of it, it just didn't play nice with people "looking under calibre's skirt" due to a Windows limitation.

As far as I am aware, neither should cause any problems with the books disappearing.
eschwartz is offline   Reply With Quote