Hi Don, I very sorry , but are completely wrong. XML is perfectly well of handling the structures of book. The problem is how you handle and define the structure which is not predefined by the XML standard. As far as the output is concerned that that is a matter of parsing the tree and reacting to the semantics for the entities defined therein. Please do not forget that a paragraph is an entity of a text, where as a page is an entity of a book! On another side. HTML actually has no concept of a page, except maybe the rendering of the file itself. Meaning that i would have to have a file per page. Then you have the same problem. Naturally, that is not how it is done. You can simulate the same semantics for page breaks in XML as in HTML, because the page break is just simulated. regards Keith. Am 03.02.2012 um 21:44 schrieb don kretz:
If you have floats, you can use inset page numbers with spans and an appropriate stylesheet.
But fundamentally what you're running into, and I don't know how you avoid it if you insist on XML/XHTML, is that books simply aren't well-formed in the way that XML defines and requires. You can't embed everything 100% in all its containers.
Page numbers are a reflection of this problem, because conceptually they are boundaries between page elements. But page elements simply aren't well-formed because their tops and bottoms can cut right through paragraphs (and everything within which paragraphs are embredded.)
I think what happened to some devices is that they had to decide between supporting HTML and XHTML, and since writers can't be constrained to create well-formed XML documents (nor should they be), the devices had to choose HTML. _______________________________________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/mailman/listinfo/gutvol-d