<HTML
><HEAD
><TITLE
>Install the Packages</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.63
"><LINK
REL="HOME"
TITLE="DocBook Install mini-HOWTO"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Download the Packages"
HREF="download.html"><LINK
REL="NEXT"
TITLE="Using DocBook"
HREF="using.html"></HEAD
><BODY
CLASS="SECT1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>DocBook Install mini-HOWTO</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="download.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="using.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="INSTALL"
>3. Install the Packages</A
></H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN231"
>3.1. Before You Install</A
></H2
><P
> The following sections suggest how you might install the downloaded packages to setup your
DocBook SGML environment. The examples may make reference to old versions of the packages
but you should adapt the examples and use the most recent versions instead.
</P
><P
> For the most up-to-date, authoritative information, always read the documentation
that comes with a package you are installing. Often, you will find a <TT
CLASS="FILENAME"
>README</TT
>
and a <TT
CLASS="FILENAME"
>INSTALL</TT
> file after you unpack an archive.
</P
><P
> The detailed instructions below may not work exactly as shown since packages are changing
all the time. However, the instructions should still give you a general idea of the procedure to
get DocBook SGML working.
</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN238"
>3.2. Install OpenJade</A
></H2
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN240"
>3.2.1. openjade</A
></H3
><P
> Here is what to do, but remember to read the files that come with OpenJade to see if
there are any things you want to do special for your platform:
<TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
> cd /usr/local
tar -xvzf ~/openjade-1.3.tar.gz
cd openjade-1.3
./configure --prefix=/usr/local/openjade-1.3
make
make install
# Once installed, the objects etc. can be deleted.
make clean
</PRE
></FONT
></TD
></TR
></TABLE
>
The installation puts libraries in /usr/local/openjade-1.3/lib, so you might
like to add it to /etc/ld.so.conf and run ldconfig.
Add /usr/local/openjade-1.3/bin to your <TT
CLASS="ENVAR"
>$PATH</TT
>.
</P
><P
> You might be wondering why I dump the openjade source directly into <TT
CLASS="FILENAME"
>/usr/local</TT
>.
The author experienced some issues with openjade's installation. However, with newer releases
of OpenJade, you might try a standard (<TT
CLASS="FILENAME"
>/usr/local/src</TT
>) location for the
openjade source package with some other prefix install location, and see how it goes.
</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN248"
>3.2.2. jadetex & pdfjadetex</A
></H3
><P
> As mentioned, <B
CLASS="COMMAND"
>jadetex</B
> and <B
CLASS="COMMAND"
>pdfjadetex</B
> are TeX macros that are packaged with
OpenJade. They can be found in /usr/local/openjade-3.1/dsssl. A handy
guide to installing these macros was prepared by
Frank Atanassow Christoph and can be found at:
</P
><P
><A
HREF="ftp://ftp.dante.de/tex-archive/macros/jadetex/install.pdf"
TARGET="_top"
>ftp://ftp.dante.de/tex-archive/macros/jadetex/install.pdf</A
></P
><P
><A
HREF="http://reaster.com/installjadetex.pdf"
TARGET="_top"
>http://reaster.com/installjadetex.pdf</A
></P
><P
> The following is based on the instructions in install.pdf:
</P
><DIV
CLASS="SECT4"
><H4
CLASS="SECT4"
><A
NAME="AEN264"
>3.2.2.1. Create hugelatex (if needed)</A
></H4
><P
> The <B
CLASS="COMMAND"
>jadetex</B
> and <B
CLASS="COMMAND"
>pdfjadetex</B
> tex macros require more memory than a regular run of <B
CLASS="COMMAND"
>tex</B
>.
The default <B
CLASS="COMMAND"
>tex</B
> memory limit configuration is often too limited. The tex configuration file,
<TT
CLASS="FILENAME"
>texmf.cnf</TT
>, can be edited and variables which limit tex's memory use can be increased. But
rather than just editing the <TT
CLASS="FILENAME"
>texmf.cnf</TT
> file to allow tex in all instances to have more
memory, a custom <B
CLASS="COMMAND"
>tex</B
> context can be created, called <B
CLASS="COMMAND"
>hugelatex</B
>.
If <B
CLASS="COMMAND"
>hugelatex</B
> is already configured on your system, you can skip this
subsection (<B
CLASS="COMMAND"
>which hugelatex</B
>).
</P
><P
> Verify that a working TeX is installed and find its directory:
<TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
> bash$ which tex
/usr/share/texmf/bin/tex
bash$ kpsewhich -expand-var='$TEXMFMAIN'
/usr/share/texmf
bash$
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><P
> Using <B
CLASS="COMMAND"
>which</B
> should find the location of the <B
CLASS="COMMAND"
>tex</B
> program. If its not
found, then you might need to install teTeX then return here.
<B
CLASS="COMMAND"
>kpsewhich</B
> is a utility that comes with teTeX and finds the main tex
directory if all goes well.
</P
><P
> Now that the <TT
CLASS="FILENAME"
>texmf</TT
> directory is known, installation can begin:
<TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
> cd /usr/share/texmf
cd tex/latex
cp -r config config-temp
cd config-temp
tex -ini -progname=hugelatex latex.ini
mv latex.fmt hugelatex.fmt
mv hugelatex.fmt /usr/share/texmf/web2c
cd ..
rm -r config-temp
cd /usr/share/texmf/bin
ln -s tex hugelatex
cd /usr/share/texmf/web2c
</PRE
></FONT
></TD
></TR
></TABLE
>
The <TT
CLASS="FILENAME"
>web2c</TT
> directory contains the <TT
CLASS="FILENAME"
>texmf.cnf</TT
> configuration file.
Make a backup of this file: <B
CLASS="COMMAND"
>cp texmf.cnf texmf.cnf.orig</B
>. Edit
the file using whatever editor you like, and add the following
lines at the end:
<TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
> % hugelatex settings
extra_mem_top.hugelatex = 8000000
extra_mem_bot.hugelatex = 8000000
hash_extra.hugelatex = 15000
pool_size.hugelatex = 5000000
string_vacancies.hugelatex = 45000
max_strings.hugelatex = 55000
pool_free.hugelatex = 47500
nest_size.hugelatex = 500
param_size.hugelatex = 1500
save_size.hugelatex = 5000
stack_size.hugelatex = 15000
% jadetex
extra_mem_top.jadetex = 8000000
extra_mem_bot.jadetex = 8000000
hash_extra.jadetex = 20000
pool_size.jadetex = 5000000
string_vacancies.jadetex = 45000
max_strings.jadetex = 55000
pool_free.jadetex = 47500
nest_size.jadetex = 500
param_size.jadetex = 1500
save_size.jadetex = 5000
stack_size.jadetex = 15000
% pdfjadetex
extra_mem_top.pdfjadetex = 8000000
extra_mem_bot.pdfjadetex = 8000000
hash_extra.pdfjadetex = 20000
pool_size.pdfjadetex = 5000000
string_vacancies.pdfjadetex = 45000
max_strings.pdfjadetex = 55000
pool_free.pdfjadetex = 47500
nest_size.pdfjadetex = 500
param_size.pdfjadetex = 1500
save_size.pdfjadetex = 5000
stack_size.pdfjadetex = 15000
</PRE
></FONT
></TD
></TR
></TABLE
>
Here, we've gone ahead and added entries for
<B
CLASS="COMMAND"
>jadetex</B
> and <B
CLASS="COMMAND"
>pdfjadetex</B
>, which we'll be setting
up below. You can play with these memory settings
any way you like if you experience trouble with them.
</P
><P
> After setting up <B
CLASS="COMMAND"
>hugelatex</B
>, like above, it may not
work until the <B
CLASS="COMMAND"
>texhash</B
> program is called:
<TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
> root# texhash
texhash: Updating /usr/share/texmf/ls-R...
texhash: Updating /var/cache/fonts/ls-R...
texhash: Done.
root#
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
></DIV
><DIV
CLASS="SECT4"
><H4
CLASS="SECT4"
><A
NAME="AEN296"
>3.2.2.2. jadetex & pdfjadetex</A
></H4
><P
> Setting up <B
CLASS="COMMAND"
>jadetex</B
> and <B
CLASS="COMMAND"
>pdfjadetex</B
>
is similar to <B
CLASS="COMMAND"
>hugelatex</B
>.
<TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
> cd /usr/local/openjade-1.3/dsssl
make -f Makefile.jadetex install
# make creates and installs the .fmt
# files to /usr/share/texmf/web2c
# Now create symlinks ...
cd /usr/share/texmf/bin
ln -s tex jadetex
ln -s pdftex pdfjadetex
# Finally, run texhash.
root# texhash
</PRE
></FONT
></TD
></TR
></TABLE
>
This <TT
CLASS="FILENAME"
>Makefile</TT
> uses <B
CLASS="COMMAND"
>hugelatex</B
>,
so <B
CLASS="COMMAND"
>hugelatex</B
> must have been
setup already. When tex is run as <B
CLASS="COMMAND"
>hugelatex</B
>, <B
CLASS="COMMAND"
>jadetex</B
>, or
<B
CLASS="COMMAND"
>pdfjadetex</B
>, it gets its program name (context) from <TT
CLASS="VARNAME"
>argv[0]</TT
>
in the environment. Then, it scans <TT
CLASS="FILENAME"
>texmf.cnf</TT
>, and uses
any context-specific settings it finds. The format (<TT
CLASS="FILENAME"
>.fmt</TT
>)
files in <TT
CLASS="FILENAME"
>/usr/share/texmf/web2c</TT
> are also loaded based on
the context.
</P
><P
> The <B
CLASS="COMMAND"
>jadetex</B
> command takes a tex file generated from
<B
CLASS="COMMAND"
>openjade</B
>, and outputs a <TT
CLASS="FILENAME"
>dvi</TT
> file.
<B
CLASS="COMMAND"
>pdfjadetex</B
> takes a <TT
CLASS="FILENAME"
>tex</TT
> file
generated from <B
CLASS="COMMAND"
>openjade</B
>, and outputs a <TT
CLASS="FILENAME"
>pdf</TT
>.
The <B
CLASS="COMMAND"
>dvips</B
> program takes the <TT
CLASS="FILENAME"
>dvi</TT
> file and outputs a <SPAN
CLASS="PRODUCTNAME"
>PostScript</SPAN
>
<TT
CLASS="FILENAME"
>ps</TT
> file that you can send to your printer or view with ghostscript <B
CLASS="COMMAND"
>gs</B
>.
</P
></DIV
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN326"
>3.3. DocBook SGML DTD</A
></H2
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN328"
>3.3.1. Unpack the DocBook SGML DTD</A
></H3
><P
> The DocBook DTD is just some <TT
CLASS="FILENAME"
>sgml</TT
> text files, so there is nothing to compile.
Just <B
CLASS="COMMAND"
>unzip</B
> them somewhere:
<TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
> # DocBook DTD V4.1 in
# /usr/local/share/sgml/docbook/4.1
cd /usr/local/share
mkdir sgml; cd sgml
mkdir docbook; cd docbook
mkdir 4.1; cd 4.1
unzip -a ~/docbk41.zip
</PRE
></FONT
></TD
></TR
></TABLE
>
If you install <TT
CLASS="FILENAME"
>doctools-1.2</TT
> from the XFree86 distribution, it will
put some older versions of DocBook DTD, like <TT
CLASS="FILENAME"
>2.4.1/</TT
> and
<TT
CLASS="FILENAME"
>3.0/</TT
> in subdirectories of <TT
CLASS="FILENAME"
>docbook</TT
>.
</P
><P
> There are some differences between
the different versions of the DocBook DTD. The <TT
CLASS="FILENAME"
>xxissues.txt</TT
> files
document those issues. Tags have been added, removed, and renamed
between the versions.
</P
><P
> If you need to use DocBook DTD V3.1, it is available from the same
place where V4.1 is downloaded. V3.1 is used a lot, so its
a good idea to get it and install it in a <TT
CLASS="FILENAME"
>3.1/</TT
> subdirectory.
</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN342"
>3.3.2. Unpack the ISO8879 Entities</A
></H3
><P
> For each DocBook DTD version unpacked, go into its directory and unpack
the <TT
CLASS="FILENAME"
>iso8879-entities.tar.gz</TT
> file:
<TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
> cd /usr/local/share/sgml/docbook/4.1
tar -xvzf ~/iso8879-entities.tar.gz
</PRE
></FONT
></TD
></TR
></TABLE
>
In each DocBook directory, there should be a <TT
CLASS="FILENAME"
>docbook.cat</TT
> file or
a <TT
CLASS="FILENAME"
>catalog</TT
> file, or both. If both are present, they are likely to be
identical. If only <TT
CLASS="FILENAME"
>docbook.cat</TT
> is present, go ahead and make
a symlink:
<TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
> # If needed ...
cd /usr/local/share/sgml/docbook/4.1
ln -s docbook.cat catalog
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN351"
>3.4. DocBook DSSSL</A
></H2
><P
> Installation of the DocBook DSSSL, which works for all versions of DocBook, is
just a matter of <B
CLASS="COMMAND"
>unzip</B
>ping it somwhere.
<TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
> cd /usr/local/share/sgml
mkdir dsssl; cd dsssl
unzip -a ~/db160.zip
# If you downloaded the ldp.dsl stylesheet
# customization, copy it to ...
cd docbook
cp ~/ldp.dsl html
cp ~/ldp.dsl print
# Copy into both directories.
</PRE
></FONT
></TD
></TR
></TABLE
>
That's all there is to installing the DSSSL, except for the setup
of the <TT
CLASS="ENVAR"
>$SGML_CATALOG_PATH</TT
> discussed later. Don't
forget to straighten out the file modes and owner/group of these
unpacked files - often they are scrambled and inappropriate.
</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN357"
>3.5. SGMLtools-Lite</A
></H2
><P
> If you like it, you can install the SGMLtools-Lite, but it is optional.
Its installation is the standard:
<TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
> cd /usr/src
tar -xvzf ~/sgmltools-lite-3.0.2.tar.gz
cd sgmltools-lite-3.0.2
./configure
make install
</PRE
></FONT
></TD
></TR
></TABLE
>
This installs the <B
CLASS="COMMAND"
>sgmltools</B
> <B
CLASS="COMMAND"
>python</B
> script to
<TT
CLASS="FILENAME"
>/usr/local/bin</TT
>. Note that it uses <B
CLASS="COMMAND"
>python</B
>,
so if you don't have it, then this package is useless.
</P
><P
> One tweak that has to be done to make the <B
CLASS="COMMAND"
>sgmltools</B
> script work, is
you have to edit it and set the path to <B
CLASS="COMMAND"
>openjade</B
>:
<B
CLASS="COMMAND"
>vi `which sgmltools`</B
>. Consult its docs to learn more about it.
</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN369"
>3.6. htmldoc</A
></H2
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN371"
>3.6.1. binary</A
></H3
><P
> Preferrably you downloaded a binary distribution of <B
CLASS="COMMAND"
>htmldoc</B
> for
your platform. The installation is straightforward: just unpack it
and run the setup. Read the docs in the package for more info.
</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN375"
>3.6.2. source</A
></H3
><P
> If you downloaded the source, you will also need the <EM
>Fast Light Tool Kit</EM
>
or else it will not link:
</P
><P
> <A
HREF="http://www.fltk.org/"
TARGET="_top"
>http://www.fltk.org/</A
>
</P
><P
> Installation is <B
CLASS="COMMAND"
>autoconf</B
> style.
Just run the <B
CLASS="COMMAND"
>configure</B
> script, <B
CLASS="COMMAND"
>make</B
>,
<B
CLASS="COMMAND"
>make install</B
>. If all goes well, it will install in
<TT
CLASS="FILENAME"
>/usr/bin</TT
>.
</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN387"
>3.6.3. ldp_print</A
></H3
><P
> The <B
CLASS="COMMAND"
>htmldoc</B
> program has (or had) a few glitches when generating output from
<TT
CLASS="FILENAME"
>html</TT
> files from <B
CLASS="COMMAND"
>openjade</B
>. For instance, bullet items are not
rendered properly and shaded areas are not always shaded.
</P
><P
> To fix this problem, a <B
CLASS="COMMAND"
>perl</B
> script
(<A
HREF="http://www.linuxdoc.org/authors/tools/ldp_print.tar.gz"
TARGET="_top"
>ldp_print</A
>)
is available from <A
HREF="http://www.linuxdoc.org/"
TARGET="_top"
>LinuxDoc.org</A
>.
The <B
CLASS="COMMAND"
>lpd_print</B
> script processes a nochunks <TT
CLASS="FILENAME"
>html</TT
>
file from <B
CLASS="COMMAND"
>openjade</B
> and then runs <B
CLASS="COMMAND"
>htmldoc</B
>
on it to produce correctly rendered <TT
CLASS="FILENAME"
>pdf</TT
> and <TT
CLASS="FILENAME"
>ps</TT
>.
<DIV
CLASS="TIP"
><P
></P
><TABLE
CLASS="TIP"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Get it!</P
></TD
></TR
></TABLE
></DIV
>
</P
><P
> <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
> tar -xvzf ldp_print.tar.gz
cd ldp_print
# Copy the lib somewhere where perl looks.
cp fix_print_html.lib /usr/lib/perl5/site_perl
cp ldp_print /usr/local/bin
</PRE
></FONT
></TD
></TR
></TABLE
>
Take a look at the script in case there are lines in it you need
to change for your system. Perhaps someday <B
CLASS="COMMAND"
>htmldoc</B
>'s bugs will
be fixed and this script will not be needed anymore.
</P
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN408"
>3.7. DocBook2X and SGMLS.pm (sgmlspl)</A
></H2
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN410"
>3.7.1. sgmlspl</A
></H3
><P
> Before the spec files from DocBook2X are of any use, the <TT
CLASS="FILENAME"
>SGMLS.pm</TT
> module
for <B
CLASS="COMMAND"
>perl</B
> version 5 has to be installed, assuming that
<B
CLASS="COMMAND"
>perl</B
> version 5 is installed. The
installation of this module is not as automated as most <B
CLASS="COMMAND"
>perl</B
> module
installs. It uses a <TT
CLASS="FILENAME"
>Makefile</TT
> that has to be edited first before
running <B
CLASS="COMMAND"
>make</B
>.
<TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
> cd /usr/src
tar -xvzf ~/SGMLSpm-1.03ii.tar.gz
cd SGMLSpm
# Edit Makfile
vi Makefile
# In the user options of the Makefile
# set everything correct for
# your system.
# Example:
# PERL = /usr/bin/perl
# BINDIR = /usr/local/bin
# PERL5DIR = /usr/lib/perl5/site_perl
# MODULEDIR = ${PERL5DIR}/SGMLS
# SPECDIR = ${PERL5DIR}
# HTMLDIR= /usr/local/apache/htdocs
make install
</PRE
></FONT
></TD
></TR
></TABLE
>
sgmlspl gets copied to /usr/local/bin.
</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN420"
>3.7.2. docbook2X (docbook2man-spec.pl)</A
></H3
><P
> DocBook2X contains no program to compile or <B
CLASS="COMMAND"
>install</B
>,
though it has some scripts you might want to look at,
so all there is to do is unpack it somwhere.
<TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
> cd /usr/local/share/sgml
tar -xvzf ~/docbook2X-0.6.0.tar.gz
cd docbook2X
</PRE
></FONT
></TD
></TR
></TABLE
>
In the unpacked directory is the <TT
CLASS="FILENAME"
>docbook2man-spec.pl</TT
> and
a patch file for it that corrects a few things.
Applying the patch is optional but recommended.
<TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
> patch docbook2man-spec.pl docbook2man-spec.pl.patch
</PRE
></FONT
></TD
></TR
></TABLE
>
Later, in <EM
>Using DocBook</EM
>, you will see how to use
<B
CLASS="COMMAND"
>sgmlspl</B
> and <TT
CLASS="FILENAME"
>docbook2man-spec.pl</TT
>
to generate a <B
CLASS="COMMAND"
>man</B
> page from a <TT
CLASS="SGMLTAG"
><refentry></TT
>
DocBook document.
</P
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN432"
>3.8. $SGML_CATALOG_FILES</A
></H2
><P
> The <TT
CLASS="ENVAR"
>$SGML_CATALOG_FILES</TT
> environment variable is used by
<B
CLASS="COMMAND"
>openjade</B
> (and other SGML software) to locate DTDs and DSL (stylesheets).
SGML software cannot function without finding these files, which have
been unpacked to various directories. Given the setup as done so far,
here is how <TT
CLASS="ENVAR"
>$SGML_CATALOG_FILES</TT
> can be set in <TT
CLASS="FILENAME"
>/etc/profile</TT
>:
<TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>##########################################################################################
# SGML DocBook - openjade sgmltools-lite
JADE_HOME=/usr/local/openjade-1.3
SGML_SHARE=/usr/local/share/sgml
PATH=$PATH:$JADE_HOME/bin
# DSSSL stylesheets
# Norman Walsh's Modular DocBook Stylesheets
SGML_CATALOG_FILES=$SGML_SHARE/dsssl/docbook/catalog
# OpenJade stylesheets
SGML_CATALOG_FILES=$SGML_CATALOG_FILES:$JADE_HOME/dsssl/catalog
# sgmltools-lite's stylesheets
SGML_CATALOG_FILES=$SGML_CATALOG_FILES:$SGML_SHARE/stylesheets/sgmltools/sgmltools.cat
# DocBook DTD
# From OASIS-Open.org
SGML_CATALOG_FILES=$SGML_CATALOG_FILES:$SGML_SHARE/docbook/3.1/catalog
SGML_CATALOG_FILES=$SGML_CATALOG_FILES:$SGML_SHARE/docbook/4.1/catalog
# These old ones were installed with doctools-1.2 from XFree86.org
SGML_CATALOG_FILES=$SGML_CATALOG_FILES:$SGML_SHARE/docbook/2.4.1/catalog
SGML_CATALOG_FILES=$SGML_CATALOG_FILES:$SGML_SHARE/docbook/3.0/catalog
# sgmltools-lite catalogs for LinuxDoc
SGML_CATALOG_FILES=$SGML_CATALOG_FILES:$SGML_SHARE/dtd/sgmltools/catalog
export JADE_HOME SGML_SHARE PATH SGML_CATALOG_FILES
##########################################################################################
</PRE
></FONT
></TD
></TR
></TABLE
>
Save your <TT
CLASS="FILENAME"
>profile</TT
>, <B
CLASS="COMMAND"
>logout</B
> and then log back in to take effect.
</P
><P
> Installation is complete! In the next section, we'll test the installation
and <B
CLASS="COMMAND"
>convert</B
> some test DocBook files.
</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="download.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="using.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Download the Packages</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
> </TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Using DocBook</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
