Gihan,
You are referring to the instructions in the source tree that enumerate the
steps required for building a "release" package. This is for the developers who
preprocess/build each release that shows up on SourceForge. This is not a normal
process for users of DocBook.
The normal usage for user would be to download the ZIP file of the release
and set up your XSLTPROC (or other tools) to run against that release.
http://sourceforge.net/projects/docbook/files/docbook-xsl/
The XSLT processors transform the DocBook XML into HTML, PDF, EPUB, etc,
via the XSL stylesheets in the release package.
I would also suggest that you read the Bob Stayton's book on DocBook
http://www.sagehill.net/docbookxsl/index.html
also available in paper copy.
Regards,
Dean Nelson
In a message dated 2/29/2012 11:01:46 P.M. Pacific Standard Time,
writes:
Hi devs,
I'm Gihan Chanuka. An undergraduate of
Bsc Engineering, University of Moratuwa, Sri Lanka. I'm new to open
source and also to DocBook. But as I see, DocBook is one of the
interesting and innovative idea. So, I liked to get familiar with the
DocBook project.
I went through some of the tutorials and documentation
about it. And then, transformed a small DocBook document to html using
xsltproc to understand how it works.
I got the DocBook source code by using SVN and went though
"trunk>xsl>ReadMe.BUILD" and follow the steps in that file.
Can
you tell me what is meant by "building" DocBook? It use XSL language to
interpret and virtual processor called "XSLT" to transform the xml files.
Since, we don't need to XSLs, what exactly we do when building?
Thanks in advance!
--
--
~ Gihan Chanuka
~ Undergraduate of Bsc
Engineering,
~ Department of Computer Science and Engineering,
~
University of Moratuwa,
~ Sri
Lanka.
