View Single Post
Old 08-14-2012, 06:56 PM   #3
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 27,549
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
oebps/toc.ncx on line 19

This <content> element's "src" attribute value is "text/[name of book file]#heading_id_2", but an element with an ID the fragment is referring to does not exist in that file.

If I go to the content.opf file and look at line 19, here is what it is:
Why would you look near line 19 of the content.opf file when the error is telling you it's on or near line 19 of the toc.ncx file?

The src for one of your toc navpoints is likely looking for an element/anchor with the id of "heading_id_2" in the "text/[name of book file]" file and it doesn't seem to exist.

Either make sure an element with the id of "heading_id_2" exists in the target file or remove the extraneous url fragment (#heading_id_2) from the src attribute of the <content> tag for the navpoint entr(y|ies) in your NCX file.

Last edited by DiapDealer; 08-14-2012 at 07:12 PM.
DiapDealer is offline   Reply With Quote