View Single Post
Old 01-27-2012, 11:50 AM   #80
jackie_w
Wizard
jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.
 
Posts: 2,909
Karma: 4329387
Join Date: Sep 2009
Location: UK
Device: Sony PRS-350, PB360, Kobo Glo/AuraHD/Aura6"/AuraH2O
Quote:
Originally Posted by Yoths View Post
After installing your modified EbookReader, some of my epubs couldn't be opened any more. I compared these epubs to those which work and found out that the *.opf and *.ncx files in the 'bad' epubs were saved as UTF-8 without BOM and using Unix line break style (LF only) and in the 'good' epubs - as UTF-8 with BOM and using Windows line break style (CR+LF). I re-saved the *.opf and *.ncx files of one 'bad' epub using the "right' format, and it could be opened well again.
This is not really a bug, but maybe it would be possible for you to fix them...
I can't say I've had any problems with .opf and .ncx files myself but I do remember someone saying that their older Sony model had a problem when the .css file was written as UTF-8 (with BOM). I don't remember linebreaks (LF vs CRLF) being an issue, though.

They eventually tracked the problem down to the DRM-stripping tool they were using.
jackie_w is offline   Reply With Quote