Skip navigation

Error 9000

1177 Views 25 Replies Latest reply: Dec 20, 2012 6:00 AM by tkchung RSS
1 2 Previous Next
ralphiedee Level 2 Level 2 (335 points)
Currently Being Moderated
Dec 14, 2012 10:27 AM

I have an Apple Fixed layout book, after trying to upload via ITunes Producer I was first getting Error 5107 ( No Landmarks error )

 

I then got the correct info , removed the guide tags from the .ncx and replaced with my files

 

Now after trying to upload via ITunes Producer I get Error 9000 unable to parse .opf

 

Did I read the instructions for Landmarks wrong?

 

Here is an example from the 5.1 guide

 

<nav epub:type="landmarks">

<ol>

<li><a href="coverpg.xhtml" epub:type="cover">Cover</a></li>

<li><a href="titlepg.xhtml" epub:type="titlepage">Title Page</a></li>

<li><a href="chapter.xhtml" epub:type="bodymatter">Start</a></li>

<li><a href="bibliog.xhtml" epub:type="bibliography">Bibliography</a></li>

</ol>

</nav>

 

Below is my code

 

<nav epub:type="landmarks">

<ol>

<li><a href="cover.html" epub:type="cover">Cover</a></li>

<li><a href="page1.html" epub:type="page1">Page 1</a></li>

<li><a href="page2.html" epub:type="page2">Page 2</a></li>

<li><a href="page3.html" epub:type="page3">Page 3</a></li>

<li><a href="page4.html" epub:type="page4">Page 4</a></li>

<li><a href="page5.html" epub:type="page5">Page 5</a></li>

<li><a href="page6.html" epub:type="page6">Page 6</a></li>

<li><a href="page7.html" epub:type="page7">Page 7</a></li>

<li><a href="page8.html" epub:type="page8">Page 8</a></li>

<li><a href="page9.html" epub:type="page9">Page 9</a></li>

<li><a href="page10.html" epub:type="page10">Page 10</a></li>

<li><a href="page11.html" epub:type="page11">Page 11</a></li>

<li><a href="page12.html" epub:type="page12">Page 12</a></li>

<li><a href="page13.html" epub:type="page13">Page 13</a></li>

<li><a href="page14.html" epub:type="page14">Page 14</a></li>

<li><a href="page15.html" epub:type="page15">Page 15</a></li>

<li><a href="page16.html" epub:type="page16">Page 16</a></li>

<li><a href="page17.html" epub:type="page17">Page 17</a></li>

<li><a href="page18.html" epub:type="page18">Page 18</a></li>

<li><a href="page19.html" epub:type="page19">Page 19</a></li>

<li><a href="page20.html" epub:type="page20">Page 20</a></li>

<li><a href="page21.html" epub:type="page21">Page 21</a></li>

<li><a href="page22.html" epub:type="page22">Page 22</a></li>

<li><a href="page23.html" epub:type="page23">Page 23</a></li>

<li><a href="page24.html" epub:type="page24">Page 24</a></li>

<li><a href="page25.html" epub:type="page25">Page 25</a></li>

<li><a href="page26.html" epub:type="page26">Page 26</a></li>

<li><a href="page27.html" epub:type="page27">Page 27</a></li>

 

 

<li><a href="page28.html" epub:type="page28">Page 28</a></li>

<li><a href="page29.html" epub:type="page29">Page 29</a></li>

<li><a href="page30.html" epub:type="page30">Page 30</a></li>

<li><a href="page31.html" epub:type="page31">Page 31</a></li>

<li><a href="page32.html" epub:type="page32">Page 32</a></li>

<li><a href="page33.html" epub:type="page33">Page 33</a></li>

<li><a href="page34.html" epub:type="page34">Page 34</a></li>

<li><a href="page35.html" epub:type="page35">Page 35</a></li>

<li><a href="page36.html" epub:type="page36">Page 36</a></li>

<li><a href="page37.html" epub:type="page37">Page 37</a></li>

<li><a href="page38.html" epub:type="page38">Page 38</a></li>

<li><a href="page39.html" epub:type="page39">Page 39</a></li>

<li><a href="page40.html" epub:type="page40">Page 40</a></li>

<li><a href="page41.html" epub:type="page41">Page 41</a></li>

<li><a href="page42.html" epub:type="page42">Page 42</a></li>

<li><a href="page43.html" epub:type="page43">Page 43</a></li>

<li><a href="page44.html" epub:type="page44">Page 44</a></li>

<li><a href="page45.html" epub:type="page45">Page 45</a></li>

 

 

<li><a href="page46.html" epub:type="page46">Page 46</a></li>

<li><a href="page47.html" epub:type="page47">Page 47</a></li>

<li><a href="page48.html" epub:type="page48">Page 48</a></li>

<li><a href="page49.html" epub:type="page49">Page 49</a></li>

<li><a href="page50.html" epub:type="page50">Page 50</a></li>

<li><a href="page51.html" epub:type="page51">Page 51</a></li>

<li><a href="page52.html" epub:type="page52">Page 52</a></li>

<li><a href="page53.html" epub:type="page53">Page 53</a></li>

<li><a href="page54.html" epub:type="page54">Page 54</a></li>

<li><a href="page55.html" epub:type="page55">Page 55</a></li>

<li><a href="page56.html" epub:type="page56">Page 56</a></li>

<li><a href="page57.html" epub:type="page57">Page 57</a></li>

<li><a href="page58.html" epub:type="page58">Page 58</a></li>

<li><a href="page59.html" epub:type="page59">Page 59</a></li>

<li><a href="page60.html" epub:type="page60">Page 60</a></li>

 

 

<li><a href="page61.html" epub:type="page61">Page 61</a></li>

<li><a href="page62.html" epub:type="page62">Page 62</a></li>

<li><a href="page63.html" epub:type="page63">Page 63</a></li>

<li><a href="page64.html" epub:type="page64">Page 64</a></li>

<li><a href="page65.html" epub:type="page65">Page 65</a></li>

 

 

<li><a href="page66.html" epub:type="page66">Page 66</a></li>

<li><a href="page67.html" epub:type="page67">Page 67</a></li>

<li><a href="page68.html" epub:type="page68">Page 68</a></li>

<li><a href="page69.html" epub:type="page69">Page 69</a></li>

<li><a href="page70.html" epub:type="page70">Page 70</a></li>

<li><a href="page71.html" epub:type="page71">Page 71</a></li>

<li><a href="page72.html" epub:type="page72">Page 72</a></li>

<li><a href="page73.html" epub:type="page73">Page 73</a></li>

<li><a href="page74.html" epub:type="page74">Page 74</a></li>

<li><a href="page75.html" epub:type="page75">Page 75</a></li>

<li><a href="page76.html" epub:type="page76">Page 76</a></li>

<li><a href="page77.html" epub:type="page77">Page 77</a></li>

<li><a href="page78.html" epub:type="page78">Page 78</a></li>

<li><a href="page79.html" epub:type="page79">Page 79</a></li>

<li><a href="page80.html" epub:type="page80">Page 80</a></li>

<li><a href="page81.html" epub:type="page81">Page 81</a></li>

<li><a href="page82.html" epub:type="page82">Page 82</a></li>

<li><a href="page83.html" epub:type="page83">Page 83</a></li>

<li><a href="page84.html" epub:type="page84">Page 84</a></li>

<li><a href="page85.html" epub:type="page85">Page 85</a></li>

<li><a href="page86.html" epub:type="page86">Page 86</a></li>

</ol>

</nav>


Did I miss something here?

 

????

Mac Pro, Mac OS X (10.7.2), Mac Pro 8 Core
  • tkchung Calculating status...
    Currently Being Moderated
    Dec 15, 2012 1:56 PM (in response to ralphiedee)

    Hi ralphiedee, I've been having the same problem here, been trying to figure out what's wrong all day. Note the sample ePub I cut from the original does not exhibit any problem.

  • tkchung Level 1 Level 1 (0 points)
    Currently Being Moderated
    Dec 15, 2012 7:05 PM (in response to ralphiedee)

    Hi ralphiedee,

     

    Ok, I found a workaround that may help, at least it solved my problem.  Since I had cut a sample from the original that I knew was working, I copied the contents from my original opf into a new version of the sample's opf. Klunky workaround, I know, but it did the job and allowed me to finally upload to the store with no more "Error 9000, unable to parse" errors.

     

    Hope this helps?

    Tim

  • tkchung Level 1 Level 1 (0 points)
    Currently Being Moderated
    Dec 16, 2012 8:00 AM (in response to ralphiedee)

    Hi ralphiedee,

     

    When I say sample, I mean the preview version of the ePub that you need to create for fixed layout books with read aloud content which is what mine is.  Because the error message "unable to parse opf file" doesn't hint at what the actual problem is in the opf, the best way I could tackle that was to create a small ePub from the original, one that I knew would work, and build it back up to the original, adding in small groups of pages at a time, and testing as I went, to see if the error came up again.  Luckily this worked for me.

     

    Before you do all this, best make sure your ePub validates ok using epubcheck: http://code.google.com/p/epubcheck

     

    Hope this helps.

     

    Cheers,

    Tim

  • tkchung Level 1 Level 1 (0 points)
    Currently Being Moderated
    Dec 16, 2012 12:39 PM (in response to ralphiedee)

    Hi ralphiedee,

     

    Yep, I'm referring to taking what you already did, make a copy of that and edit it down to a few pages, and start troubleshooting from that.  This is to address the "unable to parse the opf file" error.

     

    Regarding landmarks, your <manifest> section in your opf should refer to a table of contents file e.g.

     

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

     

    and the toc.xhtml should contain the landmarks code.  Your list of landmarks is meant for ereaders to allow easy navigation to important or highlighted sections of the book, so it does not need to contain all the pages of your book.  For example, this is all I have for the landmarks section in my toc.xhtml for my 57-page book:

    <nav epub:type="landmarks">

                                  <ol>

                                            <li><a href="pg_cover.xhtml" epub:type="cover">Cover</a></li>

                                            <li><a href="pg_fm01.xhtml" epub:type="frontmatter">Copyright &amp; Acknowledgements</a></li>

                                            <li><a href="pg_fm02.xhtml" epub:type="titlepage">Inside Cover</a></li>

                                            <li><a href="pg00l.xhtml" epub:type="bodymatter">Start</a></li>

                                  </ol>

                        </nav>

     

    Lastly, for epub:type attribute, there are standard types you should be referring to, which can be found here:

    http://idpf.org/epub/vocab/structure/

     

    Cheers,

    Tim

  • tkchung Level 1 Level 1 (0 points)
    Currently Being Moderated
    Dec 17, 2012 11:23 AM (in response to ralphiedee)

    Hi RD,

     

    First, I would take out the nav section from the opf.  As mentioned, this needs to go into a separate table of contents file, i.e. either a .ncx or a .xhtml file, depending on what version of epub you are creating.

     

    I notice you have <spine toc="ncx">, this means you should have a node with id="ncx" which is a reference to a table of contents file.  You would define this in your manifest section, like this:

     

    <manifest>

    ...

    <item id="ncx" href="toc.ncx" media-type="application/x-dtbncx+xml"/>

    ...

    </manifest>

     

    toc.ncx is a separate file which will contain your navigation elements. 

     

    For epub 2.0, you should be using <guide> in your opf file instead of landmarks, which is very similar to landmarks in terms of its purpose.  e.g.

    <package>

         ...

         <guide>

              <reference type="cover" title="Cover" href="page000.xhtml"/>

              <reference type="text"  title="Content" href="page003.xhtml"/>

         </guide>

         ...

    </package>

     

    For epub 3.0, <guide> is replaced by <landmarks> but should be located in the toc file instead of the package file, as already mentioned.  I don't believe there's any harm in leaving in the <guide> section for epub 3.0 packages, as epubchecks would simply ignore it.

     

    The rest of your manifest content looks ok from what you've posted.

     

    I recommend checking out the epub fixed format sample from iTunes Connect.  It's located under the Deliver Your Content link when you log into your iTunes Connect account.  It's a great resource for building epub 3.0 file and shows exactly how a landmark code should be set up.

     

     

    Cheers,

    Tim

  • tkchung Level 1 Level 1 (0 points)
    Currently Being Moderated
    Dec 17, 2012 2:55 PM (in response to ralphiedee)

    Hi RD,

     

    It sounds rather odd that the original epub had no .ncx file if the spine referenced one.  Did the original epub validate using epubcheck? I'm curious to know what version of epub the package referenced.

     

    Anyways, you won't need to reference every page in your epub as a navPoint, only the ones you feel are good bookmarks for the publication.  For example, suppose I use page01.xhtml and page03.xhtml as bookmarks, then the <navMap> would look something like this:

     

    <navMap>

        <navPoint id="navPoint-1" playOrder="1">

          <navLabel>

            <text>This is the label for the start of my book.</text>

          </navLabel>

          <content src="page01.xhtml"/>

        </navPoint>

        <navPoint id="navPoint-2" playOrder="2">

          <navLabel>

            <text>This is the label for stop point 2.</text>

          </navLabel>

          <content src="page03.xhtml"/>

        </navPoint>

    </navMap>



     

    Hope this helps?

     

    Cheers,

    Tim

  • tkchung Level 1 Level 1 (0 points)
    Currently Being Moderated
    Dec 18, 2012 7:45 AM (in response to ralphiedee)

    Hi RD,

    I'm not sure I would trust Epubchecker, since you say it points to version 1.0.5 and google's epubcheck is up to version 3.0 now.  I would stick with downloading the tool directly from google and running the tool from Terminal.

     

    Can you paste the top of your package file code here? It will say what version epub, ie 2 or 3, you are trying to make.  This is important because it relates to your landmarks.  If you're doing 2.0 you don't need a landmarks section but you should have a guide section.  Vice versa for 3.0.  .ncx files are used by 2.0.

     

    Again, referring to Apple's sample 3.0 ePub, you'll notice there is no .ncx file and no guide section, and instead there is a toc.xhtml with the landmarks code.

     

    Cheers,

    Tim

  • tkchung Level 1 Level 1 (0 points)
    Currently Being Moderated
    Dec 18, 2012 1:12 PM (in response to ralphiedee)

    Hi RD,

     

    Sure, is there a way to PM on here? Otherwise, DM me on twitter, @cruddog.

     

    Cheers,

    Tim

1 2 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.