pazpar2.pdf using jade + pdfjadetex, but there was some constructs in
the documentation that jade considered invalid. So it did not succeed.
And indeed jade is right in a number of cases, where xsltproc does not
validate. However, jade does NOT currently allow references to refsect1,
refsect2.. sections which makes it impossible to refer to stuff from the
Guide to the Reference material. This is major drawback so dblatex is used
instead. dblatex, like jadetex, makes PDF/tex from Docbook. dblatex allows
these references and dblatex is more actively developed and is available
as a Debian package for sarge. Run 'make pazpar2.pdf' to make the
documentation. There is also a 'jade-check' rule.
-## $Id: Makefile.am,v 1.2 2007-01-12 14:54:58 adam Exp $
+## $Id: Makefile.am,v 1.3 2007-01-19 21:50:01 adam Exp $
docdir=$(datadir)/doc/@PACKAGE@
SUBDIRS = common
docdir=$(datadir)/doc/@PACKAGE@
SUBDIRS = common
$(TKL_COMPILE) $(MAINXML)
pazpar2.pdf: $(XMLFILES)
$(TKL_COMPILE) $(MAINXML)
pazpar2.pdf: $(XMLFILES)
+ rm -f pazpar2.pdf
+ dblatex $(MAINXML) && mv book.pdf pazpar2.pdf
+
+jade-check: $(XMLFILES)
jade -E14 -D $(srcdir) -d common/print.dsl -t tex $(srcdir)/common/xml.dcl $(MAINXML)
jade -E14 -D $(srcdir) -d common/print.dsl -t tex $(srcdir)/common/xml.dcl $(MAINXML)
- rm -f pazpar2.tex
- mv book.tex pazpar2.tex
- pdfjadetex pazpar2.tex >/dev/null
- pdfjadetex pazpar2.tex >/dev/null
- pdfjadetex pazpar2.tex >/dev/null
manref.xml: $(XMLMAN) $(srcdir)/common/stripref.xsl
rm -f manref.xml
manref.xml: $(XMLMAN) $(srcdir)/common/stripref.xsl
rm -f manref.xml
<!ENTITY % common SYSTEM "common/common.ent">
%common;
]>
<!ENTITY % common SYSTEM "common/common.ent">
%common;
]>
-<!-- $Id: book.xml,v 1.5 2007-01-19 18:28:08 quinn Exp $ -->
+<!-- $Id: book.xml,v 1.6 2007-01-19 21:50:02 adam Exp $ -->
- <bookinfo>
- <title>Pazpar2 - User's Guide and Reference</title>
- <author>
- <firstname>Sebastian</firstname><surname>Hammer</surname>
- </author>
- <copyright>
- <year>©right-year;</year>
- <holder>Index Data</holder>
- </copyright>
- <abstract>
- <simpara>
- Pazpar2 is a high-performance, user interface-independent, data
- model-independent metasearching
- middleware featuring merging, relevance ranking, record sorting,
- and faceted results.
- </simpara>
- <simpara>
- This document is a guide and reference to Pazpar version &version;.
- </simpara>
- <simpara>
- <inlinemediaobject>
- <imageobject>
- <imagedata fileref="common/id.png" format="PNG"/>
- </imageobject>
- <imageobject>
- <imagedata fileref="common/id.eps" format="EPS"/>
- </imageobject>
- </inlinemediaobject>
- </simpara>
- </abstract>
+ <bookinfo>
+ <title>Pazpar2 - User's Guide and Reference</title>
+ <author>
+ <firstname>Sebastian</firstname><surname>Hammer</surname>
+ </author>
+ <releaseinfo>&version;</releaseinfo>
+ <copyright>
+ <year>©right-year;</year>
+ <holder>Index Data</holder>
+ </copyright>
+ <abstract>
+ <simpara>
+ Pazpar2 is a high-performance, user interface-independent, data
+ model-independent metasearching
+ middleware featuring merging, relevance ranking, record sorting,
+ and faceted results.
+ </simpara>
+ <simpara>
+ This document is a guide and reference to Pazpar version &version;.
+ </simpara>
+ <simpara>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="common/id.png" format="PNG"/>
+ </imageobject>
+ <imageobject>
+ <imagedata fileref="common/id.eps" format="EPS"/>
+ </imageobject>
+ </inlinemediaobject>
+ </simpara>
+ </abstract>
<chapter id="introduction">
<title>Introduction</title>
<para>
<chapter id="introduction">
<title>Introduction</title>
<para>
</section>
</chapter> <!-- Using pazpar2 -->
</section>
</chapter> <!-- Using pazpar2 -->
- <reference id="reference">
- <title>Reference</title>
- <partintro>
- <para>
- The material in this chapter is drawn directly from the individual
- manual entries.
- </para>
- </partintro>
- &manref;
- </reference>
+ <reference id="reference">
+ <title>Reference</title>
+ <partintro>
+ <para>
+ The material in this chapter is drawn directly from the individual
+ manual entries.
+ </para>
+ </partintro>
+ &manref;
+ </reference>
</book>
<!-- Keep this comment at the end of the file
</book>
<!-- Keep this comment at the end of the file
<!ENTITY % common SYSTEM "common/common.ent">
%common;
]>
<!ENTITY % common SYSTEM "common/common.ent">
%common;
]>
-<!-- $Id: pazpar2_conf.xml,v 1.5 2007-01-19 19:12:16 quinn Exp $ -->
+<!-- $Id: pazpar2_conf.xml,v 1.6 2007-01-19 21:50:02 adam Exp $ -->
<refentry id="pazpar2_conf">
<refentryinfo>
<productname>Pazpar2</productname>
<refentry id="pazpar2_conf">
<refentryinfo>
<productname>Pazpar2</productname>
respect to your data model. In pazpar2, incoming records are
normalized, using XSLT, into an internal representation (see
the <link
respect to your data model. In pazpar2, incoming records are
normalized, using XSLT, into an internal representation (see
the <link
- id="config-retrievalprofile">retrievalprofile</link> secion.
+ linkend="config-retrievalprofile">retrievalprofile</link> secion.
The 'service' section controls the further processing and
extraction of data from the internal representation, primarily
through the 'metdata' sub-element.
The 'service' section controls the further processing and
extraction of data from the internal representation, primarily
through the 'metdata' sub-element.
</variablelist> <!-- Data elements in server directive -->
</refsect2>
</variablelist> <!-- Data elements in server directive -->
</refsect2>
- <refsect2 id="config-queryprofile">
+ <refsect2 id="config-queryprofile"><title>queryprofile</title>
<para>
At the moment, this directive is ignored; there is one global
CCL-mapping file which governs the mapping of queries to Z39.50
<para>
At the moment, this directive is ignored; there is one global
CCL-mapping file which governs the mapping of queries to Z39.50
- <refsect2 id="config_retrievalprofile">
+ <refsect2 id="config_retrievalprofile"><title>retrievalprofile</title>
<para>
Note: In the present version, there is a single retrieval
profile. However, in a future release, it will be possible to
<para>
Note: In the present version, there is a single retrieval
profile. However, in a future release, it will be possible to
<refsect1><title>EXAMPLES</title>
<para></para>
</refsect1>
<refsect1><title>EXAMPLES</title>
<para></para>
</refsect1>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml