View Single Post
Old 11-30-2014, 10:54 PM   #10
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: 28,708
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by Peter Ahlstrom View Post
This is a GUI frontend for the NCX, so it should produce a valid NCX if you give it valid data. Currently, in this case, I'm giving it valid data but it's producing an invalid NCX.
Whatever.
I remain unconvinced that you're giving it valid data.
I remain unconvinced that two navPoints (with or without duplicate PlayOrders) pointing to the exact same url is valid.
I remain unconvinced that duplicate PlayOrders are valid (regardless of what various validation engines might not bark about).

I believe all you're doing is fooling the IDPF validator into giving your ncx a clean bill of health by duplicating the playorders.

I don't think Sigil needs to take responsibility for helping to slip an unorthodox ncx past Apple's and Kobo's validator.
DiapDealer is offline   Reply With Quote