Epub validation errors

[JSWolf]

Actually, H1 is not automatically bold. It depends on the settings for H1 in CSS.

[DaleDe]

Originally Posted by JSWolf

Actually, H1 is not automatically bold. It depends on the settings for H1 in CSS.

Yes, it is automatic unless, as you say, overridden by the CSS. The default is bold, no need to specify.

Dale

[JSWolf]

Originally Posted by DaleDe

Yes, it is automatic unless, as you say, overridden by the CSS. The default is bold, no need to specify.

Dale

Yes you are correct about h1 being bold.

[Newauthor]

Hello everyone. After reading back through messages. This is really turning out to be a fun project. How do I go about deleting the internal TOC, to let Sigil create the TOC?

[DaleDe]

Originally Posted by Newauthor

Hello everyone. After reading back through messages. This is really turning out to be a fun project. How do I go about deleting the internal TOC, to let Sigil create the TOC?

You don't have to delete the internal TOC but if you want to you just erase it in the xhtml document that it appears in.

To create and external TOC which is totally independent from the internal one if present, you need only use h1, h2, h3, etc. heading for the titles you want to appear in the TOC and click the TOC menu choice in tools to see what you have done. If the h number is the same then the entries will be on the same level. larger h numbers will appear and lower level toc entries. You can also remove any that show up but you don't want them to be in the TOC. I often use a h1 for the Title but I don't want it in the TOC.

Dale

[Newauthor]

Dale,

The table of contents info shows up in content0002.xhtml. Would it be recommended that I erase all the information there? Then hit the ToC generation button in Sigil?

[Newauthor]

Okay so after much playing around. I ran another epub validation and I'm ending up with the same errors. Shown below.


ERROR: epub/toc.ncx(56): assertion failed: different playOrder values for navPoint/navTarget/pageTarget that refer to same target

ERROR: epub/toc.ncx(74): assertion failed: different playOrder values for navPoint/navTarget/pageTarget that refer to same target

ERROR: epub/toc.ncx(66): 'Chapter9': fragment identifier is not defined in 'tmp_da02e54b013a717f705d92d610839337_GpOkmN.ch.fi xed.fc.tidied.stylehacked.xfixed_split_001.html'

ERROR: epub/toc.ncx(72): 'Chapter10': fragment identifier is not defined in 'tmp_da02e54b013a717f705d92d610839337_GpOkmN.ch.fi xed.fc.tidied.stylehacked.xfixed_split_001.html'

So I looked at the toc.ncx line 56 all it says is </navPoint> but nothing after that.

Line 51 <navPoint id="navPoint-7" playOrder="7">

Line 55 <content src="Text/content0008.xhtml" />

Looking at Content0008.xhtml
Line 13 <h1 class="center" id="heading_id_7"><span class="bold">xxxxx</span></h1>

Looking at Content.Opf
Line 39 <item href="Text/content0008.xhtml" id="content0008.xhtml" media-type="application/xhtml+xml" />


Thanks every one for all the help but I'm having a head to desk moment trying to figure this one out. My conclusion is if I can correct toc.ncx line 56, then I should be able to correct 74.

As for epub/toc.ncx(66): 'Chapter9': fragment identifier is not defined in 'tmp_da02e54b013a717f705d92d610839337_GpOkmN.ch.fi xed.fc.tidied.stylehacked.xfixed_split_001.html'

Anything you can provide to shoot me in the right direction would be greatly appreciated. Thanks a million!

[Newauthor]

Found something here. At the top of my xhtml files I'm noticing there's two different <?xml lines. Does this matter at all?

<?xml version="1.0"?>

<?xml version="1.0" encoding="utf-8" standalone="no"?>

[Newauthor]

Thank you everyone. I'm pleased to announce that I the epub validation has passed!

[DaleDe]

Originally Posted by Newauthor

Dale,

The table of contents info shows up in content0002.xhtml. Would it be recommended that I erase all the information there? Then hit the ToC generation button in Sigil?

As I said, it does not matter! They are independent, not in any way related to each other. They don't even have to have the same data. The links in the xhtml file are just links. You know they are a toc but the program does not.

Dale

[Newauthor]

Originally Posted by DaleDe

As I said, it does not matter! They are independent, not in any way related to each other. They don't even have to have the same data. The links in the xhtml file are just links. You know they are a toc but the program does not.

Dale

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!

[DaleDe]

Originally Posted by Newauthor

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

[Newauthor]

Originally Posted by DaleDe

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

Hi Dale,

Its on the content0001.xhtml. Here is what it says on lines 9 - 15.

<title></title>
</head>

<body>
<p>;</p>
</body>
</html>

Line 13 is the problem. Is there something else that's suppose to be there?

[charleski]

Do you really want a completely blank page? It's always a good idea actually to look at the ePub in something like ADE and make sure it appears the way you want it. Blank pages are common in print as fillers for the printing signatures, but aren't needed (or desirable) in ebooks.

What do you actually want to go on the first page of your book?

[DaleDe]

Originally Posted by Newauthor

Hi Dale,

Its on the content0001.xhtml. Here is what it says on lines 9 - 15.

<title></title>
</head>

<body>
<p>;</p>
</body>
</html>

Line 13 is the problem. Is there something else that's suppose to be there?

There should be something there. If you remove the ; then there is nothing in the whole document, no text, no images, nothing. That is why there is an error. Why would you want an entire page with a ; in the upper left hand corner? Why would you want a blank page. If you really want a blank page consider: <p>This page is intentionally blank</p>

It is likely that this page is an artifact of the fact that Sigil gives you a starting page to begin your book on. In this case you should just remove the whole page. Right click on the entry in the left column of Sigil and delete the file.
Dale