View Single Post
Old 09-27-2014, 02:25 AM   #8
roger64
Wizard
roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.
 
Posts: 2,625
Karma: 3120635
Join Date: Jan 2009
Device: Kindle PW3 (wifi)
Quote:
Originally Posted by DiapDealer View Post
I still believe cumbersome is not an accurate word in this regard.
"Lengthy-string-you-don't-like-looking-at-very-much" ... sure.
OK. When I find thirty of them in a row, my head spins... (it's fragile)

Regarding the play-order attribute, I read in the specs:
Code:
NCX documents that do not contain a DOCTYPE may omit the playOrder attribute.
which seems to apply to the EPUB done with Calibre, but it's probably safer to keep them.

Let me remark also that the navpoint id must be a unique identifier. If I select only the play-order number to replace them (i.e. a plain number with single or double digits), it seems very probable that this number will NOT be an unique identifier suitable for this purpose. If I name them, 'text1', ou 'navpoint-1' (the Sigil way), this risk disappear.

Last edited by roger64; 09-27-2014 at 03:00 AM.
roger64 is offline   Reply With Quote