Has anyone automated this process? I'm looking for a tool to help me turn a
few thousand pages of extant HTML into DocBook XML.
Thanks.
Dennis Grace
Information Developer
IBM Linux Technology Center
(512) 838-3937 T/L 678-3937 cell: (512)-296-7830
[EMAIL PROTECTED]
There are only 10 kinds of
Using website 2.2,
the image in the very top left hand corner of the page (I think it should
be the duckbook image)
is neither mentioned in the param.xsl nor omitted.
Any suggestions for the requisite param please?
Or is it a std docbook param?
TIA DaveP
I did some initial work with this. My approach was to use HTML Tidy to
convert the HTML to XHTML, and I then wrote an XSL stylesheet that converts
the HTML into DocBook. I'm not sure how well this will scale to a
several-thousand page documentation set. (I've used it on few-hundered page
books
At 16:12 20/12/2002 +, Dave Pawson wrote:
Using website 2.2,
the image in the very top left hand corner of the page (I think it should
be the duckbook image)
is neither mentioned in the param.xsl nor omitted.
Any suggestions for the requisite param please?
Or is it a std docbook param?
Hello,
I have never been able to use the width attribute of imagedata.
How comes the following piece of code do not have any effect on PDF
output? The image remains the same size as if the width attribute were
not used.
---
imageobject
imagedata
There's a patch to tidy that will produce DocBook SGML or XML
http://www.cise.ufl.edu/~ppadala/tidy/
The last time I tried it, it was actually rather nice, but needed a bit more
patching.
kind regards
Peter Ring
-Original Message-
From: Dennis Grace [mailto:[EMAIL PROTECTED]]
Sent:
Bob Stayton [EMAIL PROTECTED]:
When I used author in some allowed (according to 4.2 DTD) parents I got
errors during rendering to FO with either xsltproc and instant saxon.
This was an omission from the FO stylesheets.
I checked in changes so that it works in a manner
similar to the HTML
On Fri, Dec 20, 2002 at 07:39:52PM +0100, ABX wrote:
Bob Stayton [EMAIL PROTECTED]:
When I used author in some allowed (according to 4.2 DTD) parents I got
errors during rendering to FO with either xsltproc and instant saxon.
This was an omission from the FO stylesheets.
I checked in