Quote:
Originally Posted by DiapDealer
I guess I just don't follow why--given that the ncx (or nav) was already declared "good"--there would be any reason for regenerating the ncx from the text the proposed plugin took from that good ncx and plugged into the epub's html (utilizing attributes of h tags or contents of html comments that were later regexed into same).
Why insert non-rendering attributes into the html that can really only be used to regenerate the ncx if the ncx has already been declared sufficient?
Is the whole point to make an already functional, textually satisfactory NCX/NAV regeneratable from the html?
|
Given the OP mentioned splitting omnibuses back into the individual books as a use case, I suspect he is wanting to be able to recreate the navigation documents for the individual books without having to resort to manual editing.
So, yes, being able to regenerate the NCX/NAV from the html is the whole point.