View Single Post
Old 10-13-2023, 03:35 PM   #10
firsikov
Junior Member
firsikov began at the beginning.
 
Posts: 9
Karma: 10
Join Date: Oct 2021
Device: Kindle Voyager
Quote:
Originally Posted by kovidgoyal View Post
doing that with sending to device causes major problems because different devices have different levels on filesystem unicode support (it depends on the file system and the kernel). Why do you care about filenames on the device in any case? the Kindle lists the books by their metadata not their filenames (except PDF)
Hello, Kovid.

I really love your program. Very powerful library manager. And the book editor is beyond praise. Much better than Sigyl.

As you know, many people jailbreak their Kindle. And they use formats other than .mobi or .azw. For example, .epub or .fb2.

And then in the library, such books are displayed not by their internal titles, but by file names. It is very inconvenient when book titles consist entirely of non-Latin letters. Cyrillic, Hangul, Japanese hieroglyphs, or, as mentioned above, Chinese. I'm sure Indian users have the same problems.

If it is possible to add the option "convert non-English characters to English equivalents" to the device settings and make it enabled by default, it would be very convenient for advanced users who really understand what they are doing.

And for users who stumbled upon this option unexpectedly, make a warning about the dangers of such changes.
firsikov is offline   Reply With Quote