MobileRead Forums - View Single Post

DNSB · 05-07-2025, 01:30 PM

Some people are still using systems that do not support UTF-8 or even a small chunk of it. Using the limited ASCII character set for the filenames in the library where the user should not be digging around in the files simply ensures that cross-platform compatibility works. The calibre GUI will happily show the accented characters or basically any UTF-8 character as part of the book title or the author name or other fields.

Save to disk or send to device can use the full UTF-8 character set. Though I've seen multiple posts where the complaint is made that the book title, author name or even the contents of the book are filled with the unknown character glyph since the font used does not support that glyph.

Out of curiosity, since this is your first post on MobileRead, where did you raise the question?

05-07-2025, 01:30 PM	#12
DNSB Bibliophagist Posts: 47,260 Karma: 171291590 Join Date: Jul 2010 Location: Vancouver Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos	Some people are still using systems that do not support UTF-8 or even a small chunk of it. Using the limited ASCII character set for the filenames in the library where the user should not be digging around in the files simply ensures that cross-platform compatibility works. The calibre GUI will happily show the accented characters or basically any UTF-8 character as part of the book title or the author name or other fields. Save to disk or send to device can use the full UTF-8 character set. Though I've seen multiple posts where the complaint is made that the book title, author name or even the contents of the book are filled with the unknown character glyph since the font used does not support that glyph. Out of curiosity, since this is your first post on MobileRead, where did you raise the question? Last edited by DNSB; 05-07-2025 at 01:32 PM.