Thread: Changing legacygetepub… naming conventions
View Single Post
Old 03-19-2021, 02:46 AM   #9
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by kovidgoyal View Post
Note that as per the spec when both are present filename* should be preferred and allows for arbitrary unicode in filenames.
We did discuss this. That's part of the reason I'm expecting a quick fix and maybe the rest addressed later. I think it not using the filename right now was because it was coded without expecting both. But, they might decide not to support filename*. In the context of a dedicated ereader, it just isn't needed. The filenames are not really there to be seen. And it is similar to what calibre does when you do a send-to-device.
davidfor is offline   Reply With Quote