Hello,
while I'm at it I might as well as some more questions. One thing which
I have been strugggling with is understanding what effect specific XML
elements or attributes have in the different contexts (rendering into
HTML, into PDF).
The .dtdx specifies which XML documents are valid and from the element
names one can guess what they might be used for, but not always is the
usage obvious. The example documents are more helpful, but are not
complete.
In particular the "class" attribute seems to have many different
purposes and magic strings to enter there, like the "pageBreakBefore"
mentioned in the FAQ. Is there a complete list of what strings are
recognized there and which output plugins make use of them? More
information how the various output plugins handle specific XML elements
would also be useful.
I understand that maintaining such a single user documentation does not
fit well with the decentralized design of Forrest, but IMHO it would be
useful for users. Of course I am happy to work with whatever you have at
the moment, so any pointer to documentation that I might have missed is
welcome.
--
Bye, Patrick Ohly
--
Patrick.Ohly@gmx.de
http://www.estamos.de/
while I'm at it I might as well as some more questions. One thing which
I have been strugggling with is understanding what effect specific XML
elements or attributes have in the different contexts (rendering into
HTML, into PDF).
The .dtdx specifies which XML documents are valid and from the element
names one can guess what they might be used for, but not always is the
usage obvious. The example documents are more helpful, but are not
complete.
In particular the "class" attribute seems to have many different
purposes and magic strings to enter there, like the "pageBreakBefore"
mentioned in the FAQ. Is there a complete list of what strings are
recognized there and which output plugins make use of them? More
information how the various output plugins handle specific XML elements
would also be useful.
I understand that maintaining such a single user documentation does not
fit well with the decentralized design of Forrest, but IMHO it would be
useful for users. Of course I am happy to work with whatever you have at
the moment, so any pointer to documentation that I might have missed is
welcome.
--
Bye, Patrick Ohly
--
Patrick.Ohly@gmx.de
http://www.estamos.de/