[[project @ 2004-10-24 11:35:49 by panne]
panne**20041024113549
Updated the DocBook story
] {
hunk ./docs/building/building.xml 3389
- If you're on a recent RedHat system (7.0+), you probably
- have working DocBook tools already installed. The configure
- script should detect your setup and you're away.
+ If you're on a recent RedHat (7.0+) or SuSE (8.1+) system,
+ you probably have working DocBook tools already installed. The
+ configure script should detect your setup and you're away.
hunk ./docs/building/building.xml 3394
- using a system that can handle RedHat RPM packages, you can
- probably use the Cygnus
- DocBook tools, which is the most shrink-wrapped SGML
- suite that we could find. You need all the RPMs except for
- psgml (i.e. docbook,
- jade, jadetex,
- sgmlcommon and
- stylesheets). Note that most of these
- RPMs are architecture neutral, so are likely to be found in a
- noarch directory. The SuSE RPMs also
- work; the RedHat ones don't in RedHat 6.2
- (7.0 and later should be OK), but they are easy to fix: just
- make a symlink from
- /usr/lib/sgml/stylesheets/nwalsh-modular/lib/dblib.dsl
- to /usr/lib/sgml/lib/dblib.dsl.
+ using a system that can handle RPM packages, you can use Rpmfind.net to find suitable
+ packages for your system. Search for the packages
+ docbook-dtd,
+ docbook-xsl-stylesheets,
+ libxslt,
+ libxml2,
+ fop,
+ xmltex, and
+ dvips.
hunk ./docs/building/building.xml 3425
- It's a good idea to use Norman Walsh's installation
- notes as a guide. You should get version 3.1 of
- DocBook, and note that his file test.sgm
- won't work, as it needs version 3.0. You should unpack Jade
- into \Jade, along with the entities,
- DocBook into \docbook, and the DocBook
- stylesheets into \docbook\stylesheets (so
- they actually end up in
- \docbook\stylesheets\docbook).
-
-
-
-
- Installing the DocBook tools from source
-
-
- Jade
-
- Install OpenJade
- (Windows binaries are available as well as sources). If you
- want DVI, PS, or PDF then install JadeTeX from the
- dsssl subdirectory. (If you get the
- error:
-
-! LaTeX Error: Unknown option implicit=false' for package hyperref'.
-
- your version of hyperref is out of date;
- download it from CTAN
- (macros/latex/contrib/supported/hyperref),
- and make it, ensuring that you have first removed or renamed
- your old copy. If you start getting file not found errors
- when making the test for hyperref, you
- can abort at that point and proceed straight to
- make install, or enter them as
- ../filename.)
-
- Make links from virtex to
- jadetex and
- pdfvirtex to
- pdfjadetex (otherwise DVI, PostScript
- and PDF output will not work). Copy
- dsssl/*.{dtd,dsl} and
- catalog to
- /usr/[local/]lib/sgml.
-
-
-
- DocBook and the DocBook stylesheets
+ Probably the fastest route to a working DocBook environment on
+ Windows is to install Cygwin
+ with the complete Doc category. If you are using
+ MinGW for compilation, you
+ have to help configure a little bit: Set the
+ environment variables XmllintCmd and
+ XsltprocCmd to the paths of the Cygwin executables
+ xmllint and xsltproc,
+ respectively, and set fp_cv_dir_docbook_xsl to the path
+ of the directory where the XSL stylesheets are installed,
+ e.g. c:/cygwin/usr/share/docbook-xsl.
+
hunk ./docs/building/building.xml 3438
- Get a Zip of DocBook
- and install the contents in
- /usr/[local/]/lib/sgml.
-
- Get the DocBook
- stylesheets and install in
- /usr/[local/]lib/sgml/stylesheets
- (thereby creating a subdirectory docbook). For indexing,
- copy or link collateindex.pl from the
- DocBook stylesheets archive in bin into
- a directory on your PATH.
-
- Download the ISO
- entities into
- /usr/[local/]lib/sgml.
-
+ If you want to build HTML Help, you have to install the
+ HTML Help SDK,
+ too, and make sure that hhc is in your PATH.
hunk ./docs/building/building.xml 3442
+
hunk ./docs/building/building.xml 3453
-
-
- Remaining problems
-
- If you install from source, you'll get a pile of warnings
- of the form
-
-DTDDECL catalog entries are not supported
-
- every time you build anything. These can safely be ignored, but
- if you find them tedious you can get rid of them by removing all
- the DTDDECL entries from
- docbook.cat.
-
}