Is it possible to sent books to device with filename in non-ascii characters?

[flyisland]

I have some books, the {title} and {authors} meta-data of my books are in Chinese character, and the save temple of "sending books to devices" is "{title}-{authors}".

After sent the books to my device (iRiver Story), the filename of my books on the storage of IRiver Story turns to "PinYin"(which is ascii).

So it's very inconvenience for me to search books on my reader, is it possible to sent books to device with filename in non-ascii characters?

[Manichean]

From what I know, no. The reason this restriction is in place is because it would take a huge effort to get non-ASCII filenames working across three different OSes with who knows how many different underlying filesystems, so it won't be done.

[flyisland]

Originally Posted by Manichean

From what I know, no. The reason this restriction is in place is because it would take a huge effort to get non-ASCII filenames working across three different OSes with who knows how many different underlying filesystems, so it won't be done.

I know "The filenames in the calibre library will always be ASCII“， but the "save to disk" action can export the books to my disk with filename in Chinese character.

I'm wondering why "sending to device" must be ascii?

[Manichean]

Are you sure that save to disk creates non-ascii files? I think that all disk write operations have the same limitations.
As for the filenames in the Calibre library folder, which I think you're talking about in the first part, you shouldn't go touch them at all.

[flyisland]

Originally Posted by Manichean

Are you sure that save to disk creates non-ascii files? I think that all disk write operations have the same limitations.
As for the filenames in the Calibre library folder, which I think you're talking about in the first part, you shouldn't go touch them at all.

1. Yes, I'm quite sure save to disk creates non-ascii files.

meta-data in Chinese:
save to disk filename in Chinese:

but I also notice that some characters are wrong in converting.

2. Yes, I can accept the Calibre Library as the black-box, what I need is saving book in my reader in Chinese.

I think this is a very important feature, since everyone likes to see and search book's name with their familiar characters, and so many languages in the word use non-ascii characters.

[kovidgoyal]

Sending to device always coerces filenames to ascii. That's because most ebook readers use FAT filesystems and FAT has totally atrocious support for non ascii characters. I have no desire to debug the endless bugs that will result from writing non ascii chars to FAT filesystems, so...

If you really, really need metadata in the filesystem on the device, use save to disk to save books to the device.

[flyisland]

Originally Posted by kovidgoyal

Sending to device always coerces filenames to ascii. That's because most ebook readers use FAT filesystems and FAT has totally atrocious support for non ascii characters. I have no desire to debug the endless bugs that will result from writing non ascii chars to FAT filesystems, so...

If you really, really need metadata in the filesystem on the device, use save to disk to save books to the device.

I think the compromise approach it to let users own the risk, maybe you could add a check box "Convert non-English character to English equivalents" of "Sending books to devices", just like the "save to disk".

I guess all the non-English users will benefit from it.

[Manichean]

Originally Posted by flyisland

I guess all the non-English users will benefit from it.

Let me correct that for you: All the non-English users who speak a language that uses a non-latin alphabet. Personally, I'm doing just fine with only ASCII.

[flyisland]

Originally Posted by Manichean

Let me correct that for you: All the non-English users who speak a language that uses a non-latin alphabet. Personally, I'm doing just fine with only ASCII.

Thanks for the correction