opening epub 3 on sigil

C-novice · 05-02-2018, 11:38 PM

I tried to open an epub 3 file in the latest Sigil version 0.9.9 and got this

Code:

The OPF file did not identify the NCX file correctly.
 - Sigil has used the following file as the NCX: toc.ncx

and the text appears with a bunch of tags in Book View.

What does that message mean and can this be fixed?

Doitsu · 05-03-2018, 01:34 AM

Quote:

Originally Posted by C-novice

What does that message mean and can this be fixed?

Most likely toc.ncx wasn't manifested in content.opf. Check the original epub with the IDPF validator and post the results here.

KevinH · 05-03-2018, 09:21 AM

Alternatively, if it was an epub3 but had version="2.0" in the OPF package tag, it would be treated like an epub2 and then a toc.ncx would be needed. The OPF package tag version attribute determines how the epub will be treated (as an epub2 or an epub3).

Yes, what does epubcheck return for this epub?

DiapDealer · 05-03-2018, 09:45 AM

I'm concerned with the statement "text appears with a bunch of tags in Book View." I'm hoping the user is merely confusing Code View with Book View. If the tags are truly appearing in Book View, then the epub in question surely has enormous issues to begin with.

C-novice · 05-03-2018, 09:43 PM

No, it is the Book View here's a sample of how it looks.

'. . .he had always done. 
<!DOCTYPE html>

The validation list is quite long but this this the repeating pattern.

It's no biggie now as we were able to use another document.

KevinH · 05-03-2018, 10:27 PM

Wow, certainly not a valid epub3! What generated it?

Hitch · 05-04-2018, 04:27 PM

Quote:

Originally Posted by C-novice

No, it is the Book View here's a sample of how it looks.

'. . .he had always done. 
<!DOCTYPE html>

The validation list is quite long but this this the repeating pattern.

It's no biggie now as we were able to use another document.

No, no...if this is right:

Quote:

There are much bigger issues. Something is dreadfully wrong here.

Hitch

slowsmile · 05-04-2018, 09:32 PM

@C-novice...Whenever you get xmlns declaration errors all over the place in your html code, this usually indicates that there is an xmlns attribute declaration missing from within the <html> tag in the headers at the top of your html files.

In Book View you said your ebook text looks like this:

'. . .he had always done. tag at the top of the file:

'. . .he had always done. beyond to the woods. tag line from any epub xhtml file in your next post so we can see it? The <html> tag line occurs directly after the <!DOCTYPE> line in at the top of your html files. As a reference for you, the headers at the top of your epub 3 xhtml files should all start like this:

Spoiler:

You also have a bunch of errors in your opf and toc.ncx file. It would also really help tremendously if you posted the code from the <manifest> section in the content.opf file and also posted the code from the toc.ncx file from your epub into your next post. Your toc.ncx might be using a nav map that uses <navpoint> tags which is only relevant for epub 2 format. For epub 3 you should be using a nav map that uses an ordered list within <nav> tags only. This is another wild guess on my part since I really don't know that much about epub 3 format.

A proper epub 3 toc.ncx looks something like this:

Spoiler:

Code:

<?xml version="1.0" encoding="UTF-8"?>
<html  xmlns:epub="http://www.idpf.org/2007/ops">
  <head>
    <meta http-equiv="default-style" content="text/html; charset=utf-8"/>
    <title>Contents</title>
    <link rel="stylesheet" href="css/siddhartha.css" type="text/css"/>
  </head>
  <body>
<!-- Start of Nav Structures -->
<!-- Main Contents -->    
<nav epub:type="toc">
  <h2>Contents</h2>
  <ol>
    <li><a href="s001-BookTitlePage-01.xhtml">SIDDHARTHA</a></li>
    <li><a href="s002-Copyright-01.xhtml">Copyright</a></li>
    <li><a href="s003-Dedication-01.xhtml">Dedication</a></li>
    <li><a href="s004-Epigraph-01.xhtml">Epigraph</a></li>
    <li><a href="s005-AboutTheAuthor-01.xhtml">Herman Hesse</a></li>
    <li><a href="s006-AboutThisBook-01.xhtml">Siddhartha—The book</a></li>
    <li><a href="s007-Part-001.xhtml">First Part</a>
      <ol>
        <li><a href="s008-Chapter-001.xhtml">The Son of the Brahman</a></li>
        <li><a href="s009-Chapter-002.xhtml">With the Samanas</a></li>
        <li><a href="s010-Chapter-003.xhtml">Gotama</a></li>
        <li><a href="s011-Chapter-004.xhtml">Awakening</a></li>
      </ol>
    </li>
    <li><a href="s012-Part-002.xhtml">Second Part</a>
      <ol>
        <li><a href="s013-Chapter-005.xhtml">Kamala</a></li>
        <li><a href="s014-Chapter-006.xhtml">With the Childlike People</a></li>
        <li><a href="s015-Chapter-007.xhtml">Sansara</a></li>
        <li><a href="s016-Chapter-008.xhtml">By the River</a></li>
        <li> <a href="s017-Chapter-009.xhtml">The Ferryman</a></li>
        <li><a href="s018-Chapter-010.xhtml">The Son</a></li>
        <li><a href="s019-Chapter-011.xhtml">Om</a></li>
        <li><a href="s020-Chapter-012.xhtml">Govinda</a></li>
      </ol>
    </li>
    <li><a href="s021-Appendix-01.xhtml">Appendix 1: Dharmmapada</a></li>
  </ol>
</nav>
<!-- Landmarks --> 
<nav epub:type="landmarks">
  <h2>Landmarks</h2>
  <ol>
    <li><a epub:type="bodymatter" href="s008-Chapter-001.xhtml">Begin Reading</a></li>
    <li><a epub:type="titlepage" href="s001-BookTitlePage-01.xhtml">Title Page</a></li>
    <li><a epub:type="copyright-page" href="s002-Copyright-01.xhtml">Copyright Page</a></li>
    <li><a epub:type="frontmatter" href="s004-Epigraph-01.xhtml">Epigraph</a></li>
    <li><a epub:type="frontmatter" href="s005-AboutTheAuthor-01.xhtml">Herman Hesse</a></li>
    <li><a epub:type="backmatter" href="s021-Appendix-01.xhtml">Dharmmapada</a></li>
  </ol>
</nav>
<!-- Other TOC elements --> 
<!-- End of Nav Structures -->
  </body>
</html>

Did you use another application to convert your doc to Epub 3 ? If so, what is the name of the app ? Or did you code your epub manually ?

DNSB · 05-04-2018, 11:07 PM

Quote:

Originally Posted by slowsmile

A proper epub 3 toc.ncx looks something like this:

Spoiler:

Code:

<?xml version="1.0" encoding="UTF-8"?>
<html  xmlns:epub="http://www.idpf.org/2007/ops">
  <head>
    <meta http-equiv="default-style" content="text/html; charset=utf-8"/>
    <title>Contents</title>
    <link rel="stylesheet" href="css/siddhartha.css" type="text/css"/>
  </head>
  <body>
<!-- Start of Nav Structures -->
<!-- Main Contents -->    
<nav epub:type="toc">
  <h2>Contents</h2>
  <ol>
    <li><a href="s001-BookTitlePage-01.xhtml">SIDDHARTHA</a></li>
    <li><a href="s002-Copyright-01.xhtml">Copyright</a></li>
    <li><a href="s003-Dedication-01.xhtml">Dedication</a></li>
    <li><a href="s004-Epigraph-01.xhtml">Epigraph</a></li>
    <li><a href="s005-AboutTheAuthor-01.xhtml">Herman Hesse</a></li>
    <li><a href="s006-AboutThisBook-01.xhtml">Siddhartha—The book</a></li>
    <li><a href="s007-Part-001.xhtml">First Part</a>
      <ol>
        <li><a href="s008-Chapter-001.xhtml">The Son of the Brahman</a></li>
        <li><a href="s009-Chapter-002.xhtml">With the Samanas</a></li>
        <li><a href="s010-Chapter-003.xhtml">Gotama</a></li>
        <li><a href="s011-Chapter-004.xhtml">Awakening</a></li>
      </ol>
    </li>
    <li><a href="s012-Part-002.xhtml">Second Part</a>
      <ol>
        <li><a href="s013-Chapter-005.xhtml">Kamala</a></li>
        <li><a href="s014-Chapter-006.xhtml">With the Childlike People</a></li>
        <li><a href="s015-Chapter-007.xhtml">Sansara</a></li>
        <li><a href="s016-Chapter-008.xhtml">By the River</a></li>
        <li> <a href="s017-Chapter-009.xhtml">The Ferryman</a></li>
        <li><a href="s018-Chapter-010.xhtml">The Son</a></li>
        <li><a href="s019-Chapter-011.xhtml">Om</a></li>
        <li><a href="s020-Chapter-012.xhtml">Govinda</a></li>
      </ol>
    </li>
    <li><a href="s021-Appendix-01.xhtml">Appendix 1: Dharmmapada</a></li>
  </ol>
</nav>
<!-- Landmarks --> 
<nav epub:type="landmarks">
  <h2>Landmarks</h2>
  <ol>
    <li><a epub:type="bodymatter" href="s008-Chapter-001.xhtml">Begin Reading</a></li>
    <li><a epub:type="titlepage" href="s001-BookTitlePage-01.xhtml">Title Page</a></li>
    <li><a epub:type="copyright-page" href="s002-Copyright-01.xhtml">Copyright Page</a></li>
    <li><a epub:type="frontmatter" href="s004-Epigraph-01.xhtml">Epigraph</a></li>
    <li><a epub:type="frontmatter" href="s005-AboutTheAuthor-01.xhtml">Herman Hesse</a></li>
    <li><a epub:type="backmatter" href="s021-Appendix-01.xhtml">Dharmmapada</a></li>
  </ol>
</nav>
<!-- Other TOC elements --> 
<!-- End of Nav Structures -->
  </body>
</html>

There no such animal as a proper epub3 toc.ncx. What your spoiler shows is an epub3 navigation document which should show in the text files. nav.xhtml or toc.xhtml seem to be common names but check in content.opf for the nav property to identify the navigation document. Epub3 allows for a toc.ncx for backwards compatibility and Sigil will create a template toc.ncx if the epub3 did not include one or it wasn't identified properly.

Sample navigation document line in content.opf:

Code:

<item id="toc" href="Text/nav.xhtml" media-type="application/xhtml+xml" properties="nav"/>

As for the mess posted by the OP, the last time I saw something like that was when the author copied and pasted from a code view to a book view. On his only bloody copy of the file.

C-novice · 05-04-2018, 11:31 PM

Quote:

Can you please copy and paste the <html> tag line from any epub xhtml file in your next post so we can see it? The <html> tag line occurs directly after the <!DOCTYPE> line in at the top of your html files.

<html xmlns="http://www.w3.org/1999/xhtml">

Oh yeah, this toc.ncx looks nothing like your sample. I truncate the list -it's quite long.

Quote:

the code from the toc.ncx file

<?xml version="1.0" encoding="utf-8" ?>
<ncx version="2005-1" xmlns="http://www.daisy.org/z3986/2005/ncx/">
<head>
<docTitle>
<text>The Healers Bush</text>
</docTitle>
<navMap>
<navPoint id="title-page-xhtml">
<navLabel>
<text>Title Page</text>
</navLabel>
<content src="Text/title-page.xhtml"/>
</navPoint>
<navPoint id="contents-xhtml">
<navLabel>
<text>Contents</text>
</navLabel>
<content src="Text/contents.xhtml"/>
</navPoint>
<navPoint id="chapter-001-xhtml">
<navLabel>
<text>1. Sage</text>
</navLabel>
<content src="Text/chapter-001.xhtml"/>
</navLabel>
<content src="Text/also-by-leebet-aldaxi.xhtml"/>
</navPoint>
</navMap>
</ncx>

Quote:

the <manifest> section

</manifest>
<spine toc="toc.ncx">
<itemref idref="Cover"/>
<itemref idref="title-page-xhtml"/>
<itemref idref="contents-xhtml"/>
<itemref idref="chapter-001-xhtml"/>
<itemref idref="chapter-002-xhtml"/>
<itemref idref="chapter-003-xhtml"/>
<itemref idref="about-the-authors-xhtml"/>
</spine>
<guide>
<reference type="cover" title="Cover" href="Text/cover.xhtml"/>
</guide>
</package>

The conversion was done with Libre Office. We are a bunch of Sigil novices so since we can't figure out what the dickens is going on, we are ditching both the old .odt and epub file and start over.

If the toc.ncx and manifest I post offer any insight into what we did incorrectly, please do say so we can avoid those errors in future.

Thanks for helping.

C-novice · 05-04-2018, 11:33 PM

Quote:

As for the mess posted by the OP, the last time I saw something like that was when the author copied and pasted from a code view to a book view. On his only bloody copy of the file.

We are Sigil idiots and novices but we did no such thing.

Hitch · 05-04-2018, 11:48 PM

Quote:

Originally Posted by C-novice

We are Sigil idiots and novices but we did no such thing.

Would you mind dreadfully sharing how that ePUB was made? Or anything else you can share? Trying to understand what's happened here.

Hitch

slowsmile · 05-05-2018, 12:36 AM

@C-novice...Since you are a novice with Sigil(and html coding) the best I can suggest is that you start from scratch again using your LibreOffice doc. This method to obtain an epub 3 version of your ebook wont take long, only involves a few steps and does not involve any coding in HTML.

Here's my suggestion:

* Download and install the HTML2Epub Sigil plugin from here. Read the release notes for this plugin!!

* Download and install the ePub3-itizer Sigil plugin from here. Read the release notes for this plugin!!

* If you haven't already done so, download and install the Epubcheck Sigil plugin from here.

* Export your doc from LibreOffce as HTML(Writer) + images into a new folder on your desktop. See the HTML2Epub release notes for more details.

* In Sigil go to Plugins > Input and click on HTML2Epub. This plugin will automatically convert your html doc to full epub 2 format and import it into Sigil.

* After running the plugin, check the epub in Sigil using the FlightCrew or Epubcheck plugin to make sure that you have a valid epub 2 file.

* If everything is OK, then select Plugins > Output > ePub3-itizer and run it. This plugin will convert a valid epub 2 file to valid epub 3 format and save it to your desktop.

* After conversion run Epubcheck on your new epub 3 file to be sure.

Also be aware that the HTML2Epub plugin will remove any blank lines caused by the enter key. So make sure that your headings, text and all spacing(space before, space after etc) in your LO doc have been properly styled using paragraph styles only. Unfortunately, since you cannot code in html, if you spot any formatting errors in your epub 3 file, however trivial, then you will have to go right back to your LO doc to correct it and then run the above process all over again.

I'm also guessing that you probably used the eLAIX extension for LibreOffice to convert your LO doc to epub 3. I tried using it once -- very complicated -- I dumped it after only 5 minutes. I mean what can you say about a LibreOffice add-in that has 35 toolbar buttons? That's even more toolbar buttons than LO has on its default toolbars!!..

C-novice · 05-05-2018, 09:30 AM

Quote:

Originally Posted by Hitch

Would you mind dreadfully sharing how that ePUB was made? Or anything else you can share? Trying to understand what's happened here.

Hitch

Oh nothing complexed, just Export As> Epub 3.0 > Split at: Heading.

When we first encounter the issue, we took the epub doc to Calibre and it opened okay there. But we did a convert from epub to epub in Calibre anyway and took it back to Sigil but it was the same. Then we asked you guys for help.

C-novice · 05-05-2018, 09:42 AM

Quote:

Originally Posted by slowsmile

@C-novice...Since you are a novice with Sigil(and html coding) the best I can suggest is that you start from scratch again using your LibreOffice doc. This method to obtain an epub 3 version of your ebook wont take long, only involves a few steps and does not involve any coding in HTML.

slowsmile, what was the problem? how come our toc.ncx was different from yours and what of the manifest code? What do they tell?

Regardless though,

and everyone on this thread for taking their time to help. This is really kind of you to take the time to write this down for us. We most definitely will try it out with our next LO epub conversion.

05-02-2018, 11:38 PM	#1
C-novice ReadingZealot Posts: 164 Karma: 11818 Join Date: Oct 2014 Device: kobo ARC, Samsung Tab4	opening epub 3 on sigil I tried to open an epub 3 file in the latest Sigil version 0.9.9 and got this Code: The OPF file did not identify the NCX file correctly. - Sigil has used the following file as the NCX: toc.ncx and the text appears with a bunch of tags in Book View. What does that message mean and can this be fixed?

05-03-2018, 09:43 PM	#5
C-novice ReadingZealot Posts: 164 Karma: 11818 Join Date: Oct 2014 Device: kobo ARC, Samsung Tab4	No, it is the Book View here's a sample of how it looks. '. . .he had always done.</span></p> <p class="subsq"><span xmlns=beyond to the woods. </span><span xmlns= This is Code View <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE html> The validation list is quite long but this this the repeating pattern. It's no biggie now as we were able to use another document. Last edited by C-novice; 05-03-2018 at 09:46 PM.

05-05-2018, 12:36 AM	#13
slowsmile Witchman Posts: 628 Karma: 788808 Join Date: May 2013 Location: Philippines Device: Android S5	@C-novice...Since you are a novice with Sigil(and html coding) the best I can suggest is that you start from scratch again using your LibreOffice doc. This method to obtain an epub 3 version of your ebook wont take long, only involves a few steps and does not involve any coding in HTML. Here's my suggestion: * Download and install the HTML2Epub Sigil plugin from here. Read the release notes for this plugin!! * Download and install the ePub3-itizer Sigil plugin from here. Read the release notes for this plugin!! * If you haven't already done so, download and install the Epubcheck Sigil plugin from here. * Export your doc from LibreOffce as HTML(Writer) + images into a new folder on your desktop. See the HTML2Epub release notes for more details. * In Sigil go to Plugins > Input and click on HTML2Epub. This plugin will automatically convert your html doc to full epub 2 format and import it into Sigil. * After running the plugin, check the epub in Sigil using the FlightCrew or Epubcheck plugin to make sure that you have a valid epub 2 file. * If everything is OK, then select Plugins > Output > ePub3-itizer and run it. This plugin will convert a valid epub 2 file to valid epub 3 format and save it to your desktop. * After conversion run Epubcheck on your new epub 3 file to be sure. Also be aware that the HTML2Epub plugin will remove any blank lines caused by the enter key. So make sure that your headings, text and all spacing(space before, space after etc) in your LO doc have been properly styled using paragraph styles only. Unfortunately, since you cannot code in html, if you spot any formatting errors in your epub 3 file, however trivial, then you will have to go right back to your LO doc to correct it and then run the above process all over again. I'm also guessing that you probably used the eLAIX extension for LibreOffice to convert your LO doc to epub 3. I tried using it once -- very complicated -- I dumped it after only 5 minutes. I mean what can you say about a LibreOffice add-in that has 35 toolbar buttons? That's even more toolbar buttons than LO has on its default toolbars!!.. Last edited by slowsmile; 05-05-2018 at 03:03 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
opening and saving unzipped epub files in Sigil	blackest	Sigil	27	01-05-2018 04:00 PM
Page error msg on opening Sigil	C-novice	Sigil	17	11-19-2017 06:45 PM
Error when opening file with Sigil	Kayam	Sigil	7	04-23-2015 03:41 PM
Sigil crashed on opening file ?	rbay	Sigil	7	06-06-2013 04:42 PM
Opening ePub in Sigil breaks TOC and loses italics	PatNY	Sigil	15	08-25-2010 07:05 PM

05-03-2018, 09:21 AM	#3
KevinH Sigil Developer Posts: 7,644 Karma: 5433388 Join Date: Nov 2009 Device: many	Alternatively, if it was an epub3 but had version="2.0" in the OPF package tag, it would be treated like an epub2 and then a toc.ncx would be needed. The OPF package tag version attribute determines how the epub will be treated (as an epub2 or an epub3). Yes, what does epubcheck return for this epub?

05-03-2018, 09:45 AM	#4
DiapDealer Grand Sorcerer Posts: 27,549 Karma: 193191846 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	I'm concerned with the statement "text appears with a bunch of tags in Book View." I'm hoping the user is merely confusing Code View with Book View. If the tags are truly appearing in Book View, then the epub in question surely has enormous issues to begin with.

05-03-2018, 10:27 PM	#6
KevinH Sigil Developer Posts: 7,644 Karma: 5433388 Join Date: Nov 2009 Device: many	Wow, certainly not a valid epub3! What generated it?

Advert

Advert