View Single Post
Old 02-16-2013, 08:27 AM   #2
AlPe
Digital Amanuensis
AlPe ought to be getting tired of karma fortunes by now.AlPe ought to be getting tired of karma fortunes by now.AlPe ought to be getting tired of karma fortunes by now.AlPe ought to be getting tired of karma fortunes by now.AlPe ought to be getting tired of karma fortunes by now.AlPe ought to be getting tired of karma fortunes by now.AlPe ought to be getting tired of karma fortunes by now.AlPe ought to be getting tired of karma fortunes by now.AlPe ought to be getting tired of karma fortunes by now.AlPe ought to be getting tired of karma fortunes by now.AlPe ought to be getting tired of karma fortunes by now.
 
AlPe's Avatar
 
Posts: 727
Karma: 1446357
Join Date: Dec 2011
Location: Turin, Italy
Device: Several eReaders and tablets
Quote:
She uses InDesign CS6 on her Mac to make the books and saves them to EPUB 2.0
Very poor workflow choice. CS is not intended to produce good eBooks. Anyway...

Quote:
Can anyone give me some pointers on where to look on solving this problem.
I suggest to first check whether the produced EPUB files are valid, according to the IDPF specs. There is a free validator at http://code.google.com/p/epubcheck/

Then, try a differential analysis of an EPUB file that works on that device/app and another one that does not work. Check for OPF and NCX structural differences. If even this does not succeed, inspect the XHTML page source code, for "strange" elements (frames? javascript stuff? strange unicode chars?)
AlPe is offline   Reply With Quote