Mats B. wrote:
For the toolchain, I'm using OxygenXML as the editor, then Saxon > FOP > PDF.
A few comments/issues:
·Yes, pls pipe the code samples to <programlisting>.
Very easy. Documented.
·In the docx, the words *Namespace:* and *Assembly:* which are almost in
every class of our SDK, are generated on two lines, but in the DocBook,
they appear as inline in the same para. Can you handle this?
Probably easy. Needs analysis.
·Can you somehow retain the proportional width in table columns?
This is basically a FOP problem which, unlike all the other XSL-FO
processor, does not support the automatic layout of tables.
If you simply replace Apache FOP by say, RenderX XEP, your tables will
look good.
More precisely, your Help Builder does not generate any column width
information in the DOCX (which is unusual), that's why the programs
rendering/processing the XHTML/XML files generated by our product are
forced to use the automatic layout of tables.
·Can you make the tableheads in the docx create proper tableheads in the
resulting DB?
Your Help Builder does not generate proper header rows in the DOCX,
that's why you don't get table headers in the XHTML/XML files generated
by our product.
Such table headers need to be recreated using a XED script. Probably
feasible. Needs analysis.
I think that's all. Pls keep me updated on the costs.
The costs would be a few hundred euros.
We expect our customers to read the documentation and write a few
XED/XSLT scripts when needed too. That's why we are currently not
organized to deal with small customizations like the above ones. Sorry
for that.
--
XMLmind Word To XML Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/w2x-support
