View Single Post
Old 12-05-2014, 01:56 PM   #24
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,939
Karma: 6361444
Join Date: Nov 2009
Device: many
Hi Peter,

When you call it "Section 1" and Section 1 clearly and logically starts *after* the preamble, and the preamble has its own link and entry in the ncx, how can linking it backwards to show the preamble (possibly twice or even 3 times if people are electronically navigating by ncx), ever be a "linear reading order". As a reader I would be shown the preamble multiple times instead of the selected "Section 1" which might not even be on the first screen depending on the length of the preamble!! I personally would consider that a bug in how the ebook was created.

I am happy you found a solution that works for you but I am astonished by your unwillingness to even consider perfectly normal id attributes on tags.

If you ever find a clear spec handling this case in epub 2 (or even epub 3 as Sigil is moving toward epub 3), I would be happy to look at this again. Otherwise there are multiple equally valid solutions for you to choose from.

Good luck!

KevinH


Quote:
Originally Posted by Peter Ahlstrom View Post
But I'm never presenting anything out of order. Having two or three references in a row to the exact same location is not violating linear document order. I'm not listing A B C and then saying "for D and E, skip back over C and look at B again"—that would be a violation of linear document reading order.

Regardless, I'm giving up this fight. Since the playOrder is explicitly optional, and since I'm not happy with the other suggestions here, I'll just delete all the playOrder attributes next time. That's easier to do with a regex search than renumbering things manually.

I officially withdraw my bug report. If this issue ever comes up for me again in the future, I'll just deal with it myself.
KevinH is offline   Reply With Quote