View Single Post
Old 06-23-2011, 08:35 PM   #4
pholy
Booklegger
pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.
 
pholy's Avatar
 
Posts: 1,801
Karma: 7999816
Join Date: Jun 2009
Location: Toronto, Ontario, Canada
Device: BeBook(1 & 2010), PEZ, PRS-505, Kobo BT, PRS-T1, Playbook, Kobo Touch
I can think of two possibilities:
1 - You may have very long lines which get split into multiple lines by iTunes Producer. This might happen if your originating software makes each paragraph a single line, as most word processors do. I hate this because I use simple minded text editors like vim or gedit which don't wrap lines, forcing me to scroll sideways when I fix up html code. Html parsers don't generally care about white space, so they can use smaller read buffers than word processors.
2 - Have you tried using an xml verifier on the xhtml file? It should use the xml schema specified in the file and point you to the problem. It sounds sort of like a prematurely terminated body, to me. Sorry I can't think of a verifier for you to use.
pholy is offline   Reply With Quote