MobileRead Forums - View Single Post

DNSB · 12-09-2023, 06:26 PM

Given that calibre supports multiple OS, you will find the path truncation on any supported OS. That way if I move my library to a different OS, it will not crash and burn. If calibre and whatever you are reading on supports metadata, the actual file name does not matter.

On Windows, if I enable the LongPathsEnabled registry setting (Windows 10, 1607+), it will make no difference to how calibre stores filenames though a 32,767 character path would be allowed.

12-09-2023, 06:26 PM	#18
DNSB Bibliophagist Posts: 46,471 Karma: 169115146 Join Date: Jul 2010 Location: Vancouver Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos	Given that calibre supports multiple OS, you will find the path truncation on any supported OS. That way if I move my library to a different OS, it will not crash and burn. If calibre and whatever you are reading on supports metadata, the actual file name does not matter. On Windows, if I enable the LongPathsEnabled registry setting (Windows 10, 1607+), it will make no difference to how calibre stores filenames though a 32,767 character path would be allowed. Last edited by DNSB; 12-09-2023 at 06:29 PM. Reason: Added minimum Windows version for LongPathsEnabled