View Single Post
Old 12-02-2014, 05:55 PM   #12
Peter Ahlstrom
Connoisseur
Peter Ahlstrom ought to be getting tired of karma fortunes by now.Peter Ahlstrom ought to be getting tired of karma fortunes by now.Peter Ahlstrom ought to be getting tired of karma fortunes by now.Peter Ahlstrom ought to be getting tired of karma fortunes by now.Peter Ahlstrom ought to be getting tired of karma fortunes by now.Peter Ahlstrom ought to be getting tired of karma fortunes by now.Peter Ahlstrom ought to be getting tired of karma fortunes by now.Peter Ahlstrom ought to be getting tired of karma fortunes by now.Peter Ahlstrom ought to be getting tired of karma fortunes by now.Peter Ahlstrom ought to be getting tired of karma fortunes by now.Peter Ahlstrom ought to be getting tired of karma fortunes by now.
 
Posts: 80
Karma: 500000
Join Date: Oct 2011
Location: Utah
Device: iPad
The error that the validator gave me was "different playOrder values for navPoint/navTarget/pageTarget that refer to same target." The error wasn't "multiple navPoints/navTargets/pageTargets refer to same target." I corrected the error that the validator called out, and now it passes.

If it was supposed to be illegal for multiple navPoints/navTargets/pageTargets to refer to the same target, wouldn't the validator call that out as an error, instead of specifically checking for something more esoteric, making sure that multiple navPoints/navTargets/pageTargets referring to the same targets don't have different playOrders? To me, this indicates that the way I edited the toc.ncx is exactly what is intended by the IDPF.
Peter Ahlstrom is offline   Reply With Quote