View Single Post
Old 03-13-2008, 02:46 PM   #81
llasram
Reticulator of Tharn
llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.
 
llasram's Avatar
 
Posts: 618
Karma: 400000
Join Date: Jan 2007
Location: EST
Device: Sony PRS-505
Quote:
Originally Posted by aapezzuto View Post
I'm not happy with having all elements needing to be reachable in a linear way, This makes footnotes still a problem.
You appear to have missed the //spine/itemref[@linear] attribute. It allows one to specify sections which are not part of the linear document flow and which the reader may choose to make accessible only via links to those sections.

Quote:
Originally Posted by aapezzuto View Post
But the real problem is that epub supports so many things that I don't want to support (Im looking for a structural markup + css) and by the time that I normalize epub its another format, it just happens to be epub compliant.
What don't you want to support exactly? The XML islands and fall-back support for non-standard media types? An epub reader must implement the entire standard to be compliant, but there's no reason an authoring tool can't deal with only a well-defined subset.

Last edited by llasram; 03-13-2008 at 02:49 PM. Reason: fixed typo
llasram is offline   Reply With Quote