non-ascii filename txt files sent to device get converted to ascii

Bug #812321 reported by Neil Gordon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
calibre
Won't Fix
Undecided
Unassigned

Bug Description

I unchecked the preference to convert non-ascii filenames to ascii, and:
1) It is still converted to ascii in the library file (I don't care about this)
2) It is still converted to ascii when sent to the device (in this case a kindle 3 - and I REALLY CARE ABOUT THIS)
I understand maybe your library will not deal with UTF-8 filenames, and to be honest it doesn't bother me. BUT please!! please put the proper filename back when sendinf to devices which support it!

With mobi files etc the meta data exists, so the name shows correctly from the kindle interface. But .txt files do not seem to do this! So I get these bullcr*p converted filenames showing on the kindle menu and can't tell what file is what!

This is a serious issue which makes your software pretty much unusable in this situation.

Tags: filenames utf8
Revision history for this message
Kovid Goyal (kovid) wrote : Re: calibre bug 812321

I have no interest in dealing with all the issues that creating non ascii
filenames on devices will create.

 status wontfix

Changed in calibre:
status: New → Won't Fix
Revision history for this message
Neil Gordon (norgus) wrote :

Thank you for considering the issue anyway.
I would appreciate it if you would look at the issue some time in the future. I know for a fact UTF-8 filenames work perfectly well on at least the kindle 3.
It makes the software very inpractical for users of non English languages to use if the document titles end up unreadable on their devices.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.