View Single Post
Old 10-20-2009, 06:08 PM   #16
Katelyn
Addict
Katelyn has a complete set of Star Wars action figures.Katelyn has a complete set of Star Wars action figures.Katelyn has a complete set of Star Wars action figures.Katelyn has a complete set of Star Wars action figures.
 
Katelyn's Avatar
 
Posts: 225
Karma: 342
Join Date: Jul 2006
Location: Indiana
Device: Pocketbook 360, Iphone 3g, Sony 505, REB1200, GEB1150
I discovered that zipped HTML books work fine in LRF format but as EPUB they no longer play nicely with my Sony reader. No idea why but it doesn't matter since I can convert to LRF. Odd but not worth trying to determine the cause. I'm doing everything the same way I've been doing it for a couple years and the problem suddenly appeared.

Thanks for the suggestions and advice!


Quote:
Originally Posted by charleski View Post
A bad character in the html can cause the reader to crash even though it reads fine on the computer. I've experienced this with some ePubs I made using Atlantis - a manual page-break before an h1 tag leads to it inserting an invalid character code at the start of the chapter title. When I remove the bad characters using Notepad++ the ePub works fine.

Katelyn, the ePub you uploaded has references to 'index2.html' in the toc and several of the html files. Since this file doesn't exist inside the ePub that may be what's causing problems on your reader.

If you have problems reading a certain book, I really recommend checking the ePub with ePubcheck as it's far more likely that it's the code that's at fault rather than your reader. ePubCheck often spits out a load of errors on books that read fine. Basically errors of the type 'attribute "qwert" not allowed at this point; ignored' can be disregarded, but 'could not parse toc.ncx: Invalid path' is more serious as are errors that report an invalid XML character.
Katelyn is offline   Reply With Quote