calibre

  1. Bug #1317883
  2. Activity log

Activity log for bug #1317883

Date Who What changed Old value New value Message
2014-05-09 12:17:52 Robert Błaut bug added bug
2014-05-09 12:17:52 Robert Błaut attachment added Test case showing problem https://bugs.launchpad.net/bugs/1317883/+attachment/4108648/+files/za%C5%BC%C3%B3%C5%82%C4%87%20ge%C5%9Bl%C4%85%20ja%C5%BA%C5%84.epub
2014-05-09 12:18:15 Robert Błaut attachment added calibre-windows.png https://bugs.launchpad.net/calibre/+bug/1317883/+attachment/4108649/+files/calibre-windows.png
2014-05-09 12:18:30 Robert Błaut attachment added calibre-mac-os-x.png https://bugs.launchpad.net/calibre/+bug/1317883/+attachment/4108650/+files/calibre-mac-os-x.png
2014-05-09 12:19:29 Robert Błaut description Mac OS X uses a sort of 'decomposed UTF-8' for storing filenames. calibre think i'ts 'simple UTF-8'. Details: http://stackoverflow.com/questions/9757843/unicode-encoding-for-filesystem-in-mac-os-x-not-correct-in-python So ebook-edit checking is completely useless if one of filenames has unicode characters. Check attached screenshots and compare Windows and Mac OS X calibre output. I've also attached test case (epub file) demonstrating a problem. Mac OS X uses a sort of 'decomposed UTF-8' for storing filenames. calibre incorrectly "thinks" it's a 'simple UTF-8'. Details: http://stackoverflow.com/questions/9757843/unicode-encoding-for-filesystem-in-mac-os-x-not-correct-in-python So ebook-edit checking is completely useless if one of filenames has unicode characters. Check attached screenshots and compare Windows and Mac OS X calibre output. I've also attached test case (epub file) demonstrating a problem.
2014-05-09 13:27:21 Kovid Goyal calibre: status New Won't Fix
2014-06-22 06:09:16 Kovid Goyal calibre: status Won't Fix Fix Released