Toc.ncx question

skypilotpete · 07-09-2011, 04:44 AM

I'm in the process of trying to understand the whole process of creating epub files. I'm reading online tutorials, but also unpacking ebooks that I have in my collection, to see if I can understand what they have done.

I'm trying to understand toc.ncx files at the moment, and I'm curious as to why the ones I have opened up contain incredibly complex id entries. One example that I've just copied at random is:

<navPoint class="chapter" id="4e02a154-acca-4e58-908f-db2a4938277d" playOrder="18">

Nothing in the tutorials I've read so far explains why such complex numbers are there in the toc.ncx. Can anyone help me with this?

wannabee · 07-09-2011, 08:51 AM

just a guess, computers like very random names so I guess a computer provided the complex name.

I think the same result may have been accomplished with:

<navPoint class="chapter" id="who-loves-you" playOrder="18">

as long as it it defined in the corresponding file.

now, supposing the computer exports from whatever program you were using, and generates random text, its only a problem if you contradict it in the file the index points to.

ie. it doesn't matter if it's supercallafrajalisticexpealodosis or 123. They just have to be the same as the pointer in the index and the receiver in the file it points to.

pholy · 07-09-2011, 09:13 AM

Quote:

ie. it doesn't matter if it's supercallafrajalisticexpealodosis or 123. They just have to be the same as the pointer in the index and the receiver in the file it points to.

Well, except that a proper id can't start with a numeric character

- But you knew that, didn't you. Let's not confuse the beginners here. (like me)

DaleDe · 07-09-2011, 07:10 PM

Quote:

Originally Posted by pholy

Well, except that a proper id can't start with a numeric character

- But you knew that, didn't you. Let's not confuse the beginners here. (like me)

Actually the original example also started with a number. ncx files are described in the wiki. They are not html but rather dtbook files so the id rule does not apply. The id's in the first example were obviously made up by a computer and not entered by a human. It is better to have human entries I think.

07-09-2011, 04:44 AM	#1
skypilotpete Member Posts: 24 Karma: 590 Join Date: Oct 2010 Location: Adelaide, South Australia Device: Prs 350	Toc.ncx question I'm in the process of trying to understand the whole process of creating epub files. I'm reading online tutorials, but also unpacking ebooks that I have in my collection, to see if I can understand what they have done. I'm trying to understand toc.ncx files at the moment, and I'm curious as to why the ones I have opened up contain incredibly complex id entries. One example that I've just copied at random is: <navPoint class="chapter" id="4e02a154-acca-4e58-908f-db2a4938277d" playOrder="18"> Nothing in the tutorials I've read so far explains why such complex numbers are there in the toc.ncx. Can anyone help me with this?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Is there a size limit for TOC.ncx?	osnova	Kindle Formats	10	10-21-2011 01:41 AM
NCX From Html TOC	Unno	Kindle Formats	20	09-16-2011 09:31 AM
Inline TOC from toc.ncx	elmago79	Kindle Formats	38	03-25-2011 12:56 PM
Can you bypass first two items in TOC.ncx?	sueneu	Kindle Formats	4	07-14-2010 08:36 AM
toc.ncx playOrder question	aarcane	ePub	8	05-25-2010 05:00 AM

07-09-2011, 08:51 AM	#2
wannabee Media Bloke Posts: 2,381 Karma: 113956855 Join Date: Sep 2010 Location: NSW - Australia Device: iOS	just a guess, computers like very random names so I guess a computer provided the complex name. I think the same result may have been accomplished with: <navPoint class="chapter" id="who-loves-you" playOrder="18"> as long as it it defined in the corresponding file. now, supposing the computer exports from whatever program you were using, and generates random text, its only a problem if you contradict it in the file the index points to. ie. it doesn't matter if it's supercallafrajalisticexpealodosis or 123. They just have to be the same as the pointer in the index and the receiver in the file it points to.

Advert