View Single Post
Old 07-28-2011, 12:03 PM   #27
DaleDe
Grand Sorcerer
DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.
 
DaleDe's Avatar
 
Posts: 11,470
Karma: 13095790
Join Date: Aug 2007
Location: Grass Valley, CA
Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7
Quote:
Originally Posted by Newauthor View Post
Thanks Dale, I took it right out and then it passed! I uploaded to lulu and it excepted but then it was rejected by one of their QA specialist because of a little semi colon. So I removed the semi colon, saved, ran another epub validation just to make sure it was clear and received this error.

/OEBPS/Text/content0001.xhtml(13): element "body" incomplete; expected element "address", "blockquote", "del", "div", "dl", "h1", "h2", "h3", "h4", "h5", "h6", "hr", "ins", "noscript", "ns:svg", "ol", "p", "pre", "script", "table" or "ul" (with xmlns:ns="http://www.w3.org/2000/svg")

Now if I put the semi colon back it passes no problem. What is this all about if you can help me to understand. Thanks!
Well, taking it out may have let it pass but only if there were errors in the TOC code. This is nothing wrong with an inline TOC. As a matter of fact this is going to be the rule for ePub version 3. The toc.ncx file will be history.

Again it would be helpful to see the line containing the simicolon to see what is going on, but I suspect the tech support guy was wrong.

Dale
DaleDe is offline   Reply With Quote