Pradeep Padala wrote:
I also wrote a patch to tidy which does the conversion of html to
docbook. Details here.
http://www.cise.ufl.edu/~ppadala/tidy
Let me know, if you need help on this. I have successfully used it on
HTML
documents submitted to TLDP.
Were you ever successful
Dave Pawson wrote:
At 08:00 13/08/2002, you wrote:
member is missing in Lists
Mmmm. No its not (one view).
The 'Lists' is a list of 'types' of lists,
not a list of what children are available?
Its to answer the question, I want to insert a list,
what type of lists are there
Pradeep Padala wrote:
This is the config file you can use to indent the docbook documents
properly. It's actually written by Ismael who tested my work.
It's a dirty hack but works. You don't need the -latin1 option he
mentioned, if your documents contain plain english.
It looks pretty the
Dave Pawson wrote:
At 01:59 14/08/2002, you wrote:
c) after detecting that member is missing, I controlled its
half-brothers: varlistentry, term and seglistitem are missing
too in the refcards
Question.
When using docbook, is it the 'main' elements that require most
thought, or
Hi,
which markup should be used to describe the changelog of software
releases? revhistory and releaseinfo are intended for document
revisions. Should I misuse revhistory and put the changelog in there?
Or is there any better approach?
Thanks for suggestions,
Georges
Hi,
it seems there is a bug in the fo stylesheets. I maintain a FAQ where
I use revhistory in qandaentry (for reasons of a possible later
rendering automatism to mark the entries with new or changed ...).
As far as I could analyze the problem, the FAQ entries are rendered as
fo:list-block and
Hi Norm,
I like your advance on Literate Programming and see some personal
application cases. But there are some points (conceptual uncertainties
from my side included), that prevent me from making full use of it. I'll
make a loose enumeration:
* I'm writing documentation for a DB-model that
xpointer specification came never to a clear final status. XXE itself
uses an enhanced xp parser to handle xpointer and the only other tool I
know of that is able to handle xpointer to this extend is xmllint/xsltproc.
So I let xsltproc/xmllint do the job of preprocessing the main file for
We work with a modular structure and are reusing content many times.
/doc
|_ /app
| | chapter1.xml ...
| | tb-audit-icon-overview-tree.xml
| |_ /images
| |_ /icons
|
|_ /oas
| | book.xml
| | intro.xml
| | chapter1.xml ...
| | ax-icon-overview.xml
| |_
