View Single Post
Old 02-03-2025, 06:12 PM   #6
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,600
Karma: 169712392
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by C08 View Post
i'm sorry to necro this thread, but has there been any updates on this issue? i couldn't get the proposed solution to work on the newest version of calibre. currently i'm adding japanese books to calibre and eeeverything is in romaji when converted. it shouldn't be necessary to manually fix the file names back to the original japanese - just keep everything, even the file paths and folders, in the original language! how do i do that?
If you mean the names of the files in the library directories? That is by design. calibre works on multiple OS and file systems and some of them do not support Unicode. In the calibre GUI, you should be able to see the original title, author, etc. which are stored in the database. Manually modifying the filenames in the calibre library is an easy route to a corrupted library.

Simply put, treat the calibre library as a black box and use calibre to manage it. Stop trying to peek under the skirts!

To quote Microsoft's documentation:

Quote:
NTFS stores file names in Unicode. In contrast, the older FAT12, FAT16, and FAT32 file systems use the OEM character set.
DNSB is offline   Reply With Quote