View Single Post
Old 09-10-2010, 02:11 AM   #4
DoctorOhh
US Navy, Retired
DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.
 
DoctorOhh's Avatar
 
Posts: 9,897
Karma: 13806776
Join Date: Feb 2009
Location: North Carolina
Device: Icarus Illumina XL HD, Kindle PaperWhite SE 11th Gen
Quote:
Originally Posted by mrbillb View Post
That being said, you missed the point of the post. I was more interested in the bogus code Calibre inserted in the file, since it is the cause of the error messages. If I use Sigil to remove the Calibre-inserted code from the epub file, the errors go away.
I didn't see any bogus code, what code are you removing? Obviously removing the <br> codes should prevent this error but <br> codes by themselves are not bogus code and you did have a <br> code in the original html.

What did you convert from?

It was my impression that as long as the encoding was correct, that the html input and the Calibre Debug Input directory would contain the same code. Since this isn't correct what does the the html code look like inside the zip file in the calibre directory for this book. There is encoding that takes place when adding a html book prior to any conversions.

Last edited by DoctorOhh; 09-10-2010 at 02:26 AM.
DoctorOhh is offline   Reply With Quote