refdb-cvs Mailing List for RefDB (Page 60)
Status: Beta
Brought to you by:
mhoenicka
Menu
▾
▴
refdb-cvs — All cvs checkins go to this list
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(47) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(88) |
Feb
(50) |
Mar
(36) |
Apr
(9) |
May
(30) |
Jun
(30) |
Jul
(22) |
Aug
(16) |
Sep
(42) |
Oct
(18) |
Nov
(29) |
Dec
(23) |
| 2005 |
Jan
(18) |
Feb
(28) |
Mar
(21) |
Apr
(35) |
May
(62) |
Jun
(22) |
Jul
(5) |
Aug
(40) |
Sep
(98) |
Oct
(81) |
Nov
(51) |
Dec
(62) |
| 2006 |
Jan
(46) |
Feb
(36) |
Mar
(8) |
Apr
(16) |
May
(14) |
Jun
(16) |
Jul
(47) |
Aug
(60) |
Sep
(34) |
Oct
(16) |
Nov
(46) |
Dec
(11) |
| 2007 |
Jan
(16) |
Feb
(13) |
Mar
(58) |
Apr
(32) |
May
(4) |
Jun
(8) |
Jul
(31) |
Aug
(46) |
Sep
(22) |
Oct
(30) |
Nov
(58) |
Dec
(15) |
| 2008 |
Jan
(8) |
Feb
(8) |
Mar
(2) |
Apr
(6) |
May
(3) |
Jun
(2) |
Jul
(1) |
Aug
|
Sep
|
Oct
(6) |
Nov
(3) |
Dec
(5) |
| 2009 |
Jan
(1) |
Feb
(20) |
Mar
(8) |
Apr
(5) |
May
(8) |
Jun
(3) |
Jul
(6) |
Aug
(4) |
Sep
(7) |
Oct
(8) |
Nov
(2) |
Dec
(1) |
| 2010 |
Jan
(1) |
Feb
(4) |
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2011 |
Jan
(5) |
Feb
(5) |
Mar
(13) |
Apr
(3) |
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(5) |
Nov
|
Dec
(3) |
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(13) |
| 2014 |
Jan
(2) |
Feb
(2) |
Mar
(2) |
Apr
(4) |
May
(1) |
Jun
(1) |
Jul
|
Aug
(6) |
Sep
(3) |
Oct
|
Nov
(2) |
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2022 |
Jan
(9) |
Feb
(16) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Markus H. <mho...@us...> - 2004-11-28 02:58:47
|
Update of /cvsroot/refdb/refdb/xsl/refdb/docbk-refdb-xsl/docbk-fo In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv25093/xsl/refdb/docbk-refdb-xsl/docbk-fo Modified Files: Tag: Release_0_9_5_stable docbk-refdb-fo.xsl.in Log Message: force hyperlink in bib output to new line Index: docbk-refdb-fo.xsl.in =================================================================== RCS file: /cvsroot/refdb/refdb/xsl/refdb/docbk-refdb-xsl/docbk-fo/docbk-refdb-fo.xsl.in,v retrieving revision 1.9.2.2 retrieving revision 1.9.2.3 diff -u -U2 -r1.9.2.2 -r1.9.2.3 --- docbk-refdb-fo.xsl.in 17 Oct 2004 00:35:47 -0000 1.9.2.2 +++ docbk-refdb-fo.xsl.in 27 Nov 2004 23:20:08 -0000 1.9.2.3 @@ -107,4 +107,7 @@ <xsl:variable name="reftype" select="ancestor::bibliomixed/@role"/> <xsl:variable name="target" select="@url"/> + <!-- the empty block forces the hyperlink into a new line. This + is less intrusive than half-emtpy lines due to bad hyphenation --> + <fo:block/> <fo:basic-link external-destination='url({$target})'> <xsl:choose> |
|
From: Markus H. <mho...@us...> - 2004-11-28 01:47:27
|
Update of /cvsroot/refdb/refdb/src In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv24684/src Modified Files: Tag: Release_0_9_5_stable refdbdbib.c Log Message: initialize conv_descriptor to NULL to avoid possible segfault Index: refdbdbib.c =================================================================== RCS file: /cvsroot/refdb/refdb/src/refdbdbib.c,v retrieving revision 1.36.2.13 retrieving revision 1.36.2.14 diff -u -U2 -r1.36.2.13 -r1.36.2.14 --- refdbdbib.c 25 Nov 2004 21:38:59 -0000 1.36.2.13 +++ refdbdbib.c 27 Nov 2004 23:18:32 -0000 1.36.2.14 @@ -168,5 +168,5 @@ struct lilimem sentinel; Lilifstring notfound_first; - iconv_t conv_descriptor; + iconv_t conv_descriptor = NULL; sentinel.ptr_mem = NULL; |
|
From: Markus H. <mho...@us...> - 2004-11-28 00:33:48
|
Update of /cvsroot/refdb/refdb/doc In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23138/doc Modified Files: Tag: Release_0_9_5_stable refdb-manual-chapter10.sgml refdb-manual-chapter13.sgml refdb-manual-chapter5.sgml refdb-manual-chapter6.sgml refdb-manual-chapter7.sgml Log Message: updated for 0.9.5 Index: refdb-manual-chapter10.sgml =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdb-manual-chapter10.sgml,v retrieving revision 1.19.2.1 retrieving revision 1.19.2.2 diff -u -U2 -r1.19.2.1 -r1.19.2.2 --- refdb-manual-chapter10.sgml 14 Nov 2004 16:04:49 -0000 1.19.2.1 +++ refdb-manual-chapter10.sgml 27 Nov 2004 23:11:15 -0000 1.19.2.2 @@ -175,5 +175,5 @@ <row> <entry>timeout</entry> - <entry>60</entry> + <entry>180</entry> <entry>The timeout in seconds. After this time has elapsed, a stalled connection is taken down. Increase this value if you encounter frequent timeout errors due to high network traffic or &appname;d overload.</entry> </row> @@ -254,5 +254,5 @@ <row> <entry>timeout</entry> - <entry>60</entry> + <entry>180</entry> <entry>The timeout in seconds. After this time has elapsed, a stalled connection is taken down. Increase this value if you encounter frequent timeout errors due to high network traffic or &appname;d overload.</entry> </row> Index: refdb-manual-chapter13.sgml =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdb-manual-chapter13.sgml,v retrieving revision 1.16.2.1 retrieving revision 1.16.2.2 diff -u -U2 -r1.16.2.1 -r1.16.2.2 --- refdb-manual-chapter13.sgml 14 Nov 2004 16:04:49 -0000 1.16.2.1 +++ refdb-manual-chapter13.sgml 27 Nov 2004 23:11:16 -0000 1.16.2.2 @@ -122,5 +122,5 @@ <row> <entry>timeout</entry> - <entry>60</entry> + <entry>180</entry> <entry>The timeout in seconds. After this time has elapsed, a stalled connection is taken down. Increase this value if you encounter frequent timeout errors due to high network traffic or refdbs overload.</entry> </row> Index: refdb-manual-chapter5.sgml =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdb-manual-chapter5.sgml,v retrieving revision 1.24.2.2 retrieving revision 1.24.2.3 diff -u -U2 -r1.24.2.2 -r1.24.2.3 --- refdb-manual-chapter5.sgml 25 Nov 2004 21:28:41 -0000 1.24.2.2 +++ refdb-manual-chapter5.sgml 27 Nov 2004 23:11:16 -0000 1.24.2.3 @@ -242,5 +242,5 @@ port 9734 pager more -timeout 60 +timeout 180 # end of refdbcrc </programlisting> @@ -254,5 +254,5 @@ # end of .refdbcrc </programlisting> - <para>As you can see our hypothetical system administrator configured the IP address (<varname>serverip</varname>) and the <varname>port</varname> where &appname;d listens to the client requests. This value is most likely the same for all users on the system, so this is nothing to worry about for the users. <filename>more</filename> is defined as the default <varname>pager</varname>, and the <varname>timeout</varname> is set to 1 minute.</para> + <para>As you can see our hypothetical system administrator configured the IP address (<varname>serverip</varname>) and the <varname>port</varname> where &appname;d listens to the client requests. This value is most likely the same for all users on the system, so this is nothing to worry about for the users. <filename>more</filename> is defined as the default <varname>pager</varname>, and the <varname>timeout</varname> is set to 3 minutes.</para> <para>Joe Sixpack, our reckless user, does not like <filename>more</filename> as a pager and prefers to use <filename>less</filename> instead. He also thinks that half a minute as a timeout should be enough. Both of these settings override the corresponding values in the global file. <varname>serverip</varname> and <varname>port</varname> are not redefined in the user's copy, so the values of the global file take effect. Joe also defined <varname>username</varname> and <varname>passwd</varname> so the correct values will be used for the database access (the asterisk in the <varname>passwd</varname> field will cause &appname;c to ask for the password interactively for security reasons).</para> </sect3> @@ -802,5 +802,5 @@ to: PostgreSQL 7.2.1 on i386-portbld-freebsd4.3, compiled by GCC 2.95.3 serverip: localhost -timeout: 60 +timeout: 180 dbs_port: 5432 logfile: /home/markus/prog/refdb/pseudotest/log/refdbd.log Index: refdb-manual-chapter6.sgml =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdb-manual-chapter6.sgml,v retrieving revision 1.17.2.1 retrieving revision 1.17.2.2 diff -u -U2 -r1.17.2.1 -r1.17.2.2 --- refdb-manual-chapter6.sgml 14 Nov 2004 16:04:50 -0000 1.17.2.1 +++ refdb-manual-chapter6.sgml 27 Nov 2004 23:11:17 -0000 1.17.2.2 @@ -313,5 +313,5 @@ <row> <entry>timeout</entry> - <entry>60</entry> + <entry>180</entry> <entry>The timeout in seconds. After this time has elapsed, a stalled connection is taken down. Increase this value if you encounter frequent timeout errors due to high network traffic.</entry> </row> Index: refdb-manual-chapter7.sgml =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdb-manual-chapter7.sgml,v retrieving revision 1.16.2.1 retrieving revision 1.16.2.2 diff -u -U2 -r1.16.2.1 -r1.16.2.2 --- refdb-manual-chapter7.sgml 14 Nov 2004 16:04:50 -0000 1.16.2.1 +++ refdb-manual-chapter7.sgml 27 Nov 2004 23:11:18 -0000 1.16.2.2 @@ -120,5 +120,5 @@ <row> <entry>timeout</entry> - <entry>60</entry> + <entry>180</entry> <entry>The timeout in seconds. After this time has elapsed, a stalled connection is taken down. Increase this value if you encounter frequent timeout errors due to high network traffic or <application>&appname;d</application> overload.</entry> </row> |
|
From: Markus H. <mho...@us...> - 2004-11-28 00:11:19
|
Update of /cvsroot/refdb/refdb In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv22831 Modified Files: Tag: Release_0_9_5_stable configure.in Log Message: fixed qu vs llu; checks for XSL stylesheets now uses XML catalog; bumped up version number Index: configure.in =================================================================== RCS file: /cvsroot/refdb/refdb/configure.in,v retrieving revision 1.49.2.6 retrieving revision 1.49.2.7 diff -u -U2 -r1.49.2.6 -r1.49.2.7 --- configure.in 25 Oct 2004 21:13:16 -0000 1.49.2.6 +++ configure.in 27 Nov 2004 23:09:16 -0000 1.49.2.7 @@ -6,5 +6,5 @@ dnl Use automake -AM_INIT_AUTOMAKE(refdb, 0.9.5-pre6) +AM_INIT_AUTOMAKE(refdb, 0.9.5) dnl Find out host type @@ -253,5 +253,5 @@ psarg="-e" ;; *) - ULLSPEC="%qu" + ULLSPEC="%llu" psarg="ax" ;; esac @@ -312,5 +312,5 @@ AC_CHECK_FILE($docbk_xsl/fo/docbook.xsl, [echo "DocBook XSL stylesheets found"], -[if test -z "$my_xmlcatalog"; then +[if test -n "$myxmlcatalog"; then REFDB_XML_FILE($myxmlcatalog,${docbk_xsl}/fo/docbook.xsl) else @@ -319,9 +319,9 @@ AC_CHECK_FILE($tei_xsl/P4/fo/tei.xsl, -[echo "DocBook XSL stylesheets found"], -[if test -z "$my_xmlcatalog"; then +[echo "TEI XSL stylesheets found"], +[if test -n "$myxmlcatalog"; then REFDB_XML_FILE($myxmlcatalog,${tei_xsl}/P4/fo/tei.xsl) else -echo "cannot locate DocBook XSL stylesheets via XML catalog" +echo "cannot locate TEI XSL stylesheets via XML catalog" fi]) |
|
From: Markus H. <mho...@us...> - 2004-11-27 23:23:57
|
Update of /cvsroot/refdb/refdb/xsl/refdb/tei-refdb-xsl/tei-html In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv25909/xsl/refdb/tei-refdb-xsl/tei-html Modified Files: Tag: Release_0_9_5_stable tei-refdb-html.xsl.in Log Message: initialize variables to non-personal stuff; set STDOUT to true to obtain html output from xsltproc with the desired name Index: tei-refdb-html.xsl.in =================================================================== RCS file: /cvsroot/refdb/refdb/xsl/refdb/tei-refdb-xsl/tei-html/tei-refdb-html.xsl.in,v retrieving revision 1.2.2.2 retrieving revision 1.2.2.3 diff -u -U2 -r1.2.2.2 -r1.2.2.3 --- tei-refdb-html.xsl.in 25 Nov 2004 21:39:58 -0000 1.2.2.2 +++ tei-refdb-html.xsl.in 27 Nov 2004 23:23:06 -0000 1.2.2.3 @@ -24,20 +24,22 @@ <!-- <xsl:variable name="masterFile">index</xsl:variable> --> <xsl:variable name="cssFile"></xsl:variable> + +<!-- the following variable is used to make xsltproc write to stdout --> +<xsl:variable name="STDOUT">true</xsl:variable> <xsl:variable name="alignNavigationPanel">center</xsl:variable> <xsl:variable name="topNavigationPanel"></xsl:variable> <xsl:variable name="bottomNavigationPanel">true</xsl:variable> -<xsl:variable name="institution">Mechelsoft Inc.</xsl:variable> -<xsl:variable name="homeURL">http://ourworld.compuserve.com/homepages/hoenicka_markus/teitest.html</xsl:variable> -<xsl:variable name="homeWords">teitest.html</xsl:variable> -<xsl:variable name="parentURL">http://ourworld.compuserve.com/homepages/hoenicka_markus/</xsl:variable> -<xsl:variable name="parentWords">Markus Hoenicka's web home</xsl:variable> -<xsl:variable name="feedbackURL">http://ourworld.compuserve.com/homepages/hoenicka_markus/</xsl:variable> -<xsl:variable name="feedbackWords">Markus Hoenicka's web home</xsl:variable> +<xsl:variable name="institution">CustomizeMe:institution</xsl:variable> +<xsl:variable name="homeURL">CustomizeMe:homeURL</xsl:variable> +<xsl:variable name="homeWords">CustomizeMe:homeWords</xsl:variable> +<xsl:variable name="parentURL">CustomizeMe:parentURL</xsl:variable> +<xsl:variable name="parentWords">CustomizeMe:parentWords</xsl:variable> +<xsl:variable name="feedbackURL">CustomizeMe:feedbackURL</xsl:variable> +<xsl:variable name="feedbackWords">CustomizeMe:feedbackWords</xsl:variable> <xsl:variable name="searchURL"></xsl:variable> <xsl:variable name="searchWords"></xsl:variable> <xsl:template name="logoPicture"></xsl:template> <xsl:variable name="useIDs"></xsl:variable> -<xsl:template name="copyrightStatement"> Copyright Markus Hoenicka 2001 -</xsl:template> +<xsl:template name="copyrightStatement">CustomizeMe:copyrightStatement</xsl:template> |
|
From: Markus H. <mho...@us...> - 2004-11-27 23:16:10
|
Update of /cvsroot/refdb/refdb/src In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23988/src Modified Files: Tag: Release_0_9_5_stable refdba.c refdbc.c refdbd.c refdbib.c Log Message: increased timeout to 180 Index: refdba.c =================================================================== RCS file: /cvsroot/refdb/refdb/src/refdba.c,v retrieving revision 1.45.2.1 retrieving revision 1.45.2.2 diff -u -U2 -r1.45.2.1 -r1.45.2.2 --- refdba.c 12 Jul 2004 21:51:58 -0000 1.45.2.1 +++ refdba.c 27 Nov 2004 23:15:39 -0000 1.45.2.2 @@ -117,5 +117,5 @@ char username[PREFS_BUF_LEN] = ""; /*+ default username (emtpy) +*/ char passwd[PREFS_BUF_LEN] = "*"; /*+ default password (ask user) +*/ -char refdb_timeout[PREFS_BUF_LEN] = "60"; /*+ 60 seconds default timeout +*/ +char refdb_timeout[PREFS_BUF_LEN] = "180"; /*+ 180 seconds default timeout +*/ char verbose[PREFS_BUF_LEN] = "f"; /*+ 1 = verbose output, 0 = terse output +*/ char log_file[PREFS_BUF_LEN] = "/var/log/refdba.log"; /*+ default log file +*/ Index: refdbc.c =================================================================== RCS file: /cvsroot/refdb/refdb/src/refdbc.c,v retrieving revision 1.72.2.1 retrieving revision 1.72.2.2 diff -u -U2 -r1.72.2.1 -r1.72.2.2 --- refdbc.c 6 Jul 2004 22:08:09 -0000 1.72.2.1 +++ refdbc.c 27 Nov 2004 23:15:39 -0000 1.72.2.2 @@ -134,5 +134,5 @@ char username[PREFS_BUF_LEN] = ""; /*+ default username (emtpy) +*/ char passwd[PREFS_BUF_LEN] = "*"; /*+ default password (ask user) +*/ -char refdb_timeout[PREFS_BUF_LEN] = "60"; /*+ 60 seconds default timeout +*/ +char refdb_timeout[PREFS_BUF_LEN] = "180"; /*+ 180 seconds default timeout +*/ char pdfroot[PREFS_BUF_LEN] = ""; /* root path for pdf or other offprint files */ char verbose[PREFS_BUF_LEN] = "f"; /*+ 1 = verbose output, 0 = terse output +*/ Index: refdbd.c =================================================================== RCS file: /cvsroot/refdb/refdb/src/refdbd.c,v retrieving revision 1.74.2.4 retrieving revision 1.74.2.5 diff -u -U2 -r1.74.2.4 -r1.74.2.5 --- refdbd.c 25 Oct 2004 21:20:25 -0000 1.74.2.4 +++ refdbd.c 27 Nov 2004 23:15:40 -0000 1.74.2.5 @@ -105,5 +105,5 @@ char pid_file[PREFS_BUF_LEN] = "/var/run/refdbd.pid"; /* default pid file */ char port_address[PREFS_BUF_LEN] = "9734"; /* default port */ -char refdb_timeout[PREFS_BUF_LEN] = "60"; /* 1 minute default timeout */ +char refdb_timeout[PREFS_BUF_LEN] = "180"; /* 3 minutes default timeout */ char remote_admin[PREFS_BUF_LEN] = "f"; /* remote administration not allowed */ char remote_connect[PREFS_BUF_LEN] = "f"; /* remote connections not allowed */ Index: refdbib.c =================================================================== RCS file: /cvsroot/refdb/refdb/src/refdbib.c,v retrieving revision 1.41.2.1 retrieving revision 1.41.2.2 diff -u -U2 -r1.41.2.1 -r1.41.2.2 --- refdbib.c 26 Sep 2004 21:10:59 -0000 1.41.2.1 +++ refdbib.c 27 Nov 2004 23:15:40 -0000 1.41.2.2 @@ -92,5 +92,5 @@ char username[PREFS_BUF_LEN] = ""; /*+ default username (emtpy) +*/ char passwd[PREFS_BUF_LEN] = "*"; /*+ default password (ask user) +*/ -char refdb_timeout[PREFS_BUF_LEN] = "60"; /* 60 seconds default timeout */ +char refdb_timeout[PREFS_BUF_LEN] = "180"; /* 180 seconds default timeout */ char output_type[PREFS_BUF_LEN] = "db31"; /* docbook is default output fmt */ char output_format[PREFS_BUF_LEN] = ""; /* format specification */ |
|
From: Markus H. <mho...@us...> - 2004-11-27 23:14:00
|
Update of /cvsroot/refdb/refdb/scripts In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23772/scripts Modified Files: Tag: Release_0_9_5_stable libgen.pl Log Message: generate matchlist for biblScope elements dynamically Index: libgen.pl =================================================================== RCS file: /cvsroot/refdb/refdb/scripts/libgen.pl,v retrieving revision 1.5.2.2 retrieving revision 1.5.2.3 diff -u -U2 -r1.5.2.2 -r1.5.2.3 --- libgen.pl 25 Nov 2004 21:32:41 -0000 1.5.2.2 +++ libgen.pl 27 Nov 2004 23:13:47 -0000 1.5.2.3 @@ -297,6 +297,15 @@ # "elements" which are in fact biblScope elements with an attribute -#todo: generate match list dynamically from tei_biblscope_elements - print "<!-- biblScope elements in the bibliography -->\n<xsl:template match=\"biblScope[\@type=\'pages\']|biblScope[\@type=\'volume\']|biblScope[\@type=\'issue\']|biblScope[\@type=\'issn\']|biblScope[\@type=\'isbn\']\" mode=\"refdb\">\n <xsl:variable name=\"reftype\" select=\"ancestor::bibl/\@rend\"/>\n <xsl:choose>\n"; + # generate match list dynamically from tei_biblscope_elements + print "<!-- biblScope elements in the bibliography -->\n<xsl:template match=\""; + + foreach $element (@tei_biblscope_elements) { + $match = $match . "biblScope[\@type=\'$element\']|"; + } + + # remove trailing pipe char + chop($match); + print($match); + print "\" mode=\"refdb\">\n <xsl:variable name=\"reftype\" select=\"ancestor::bibl/\@rend\"/>\n <xsl:choose>\n"; foreach $element (@tei_biblscope_elements) { |
|
From: Markus H. <mho...@us...> - 2004-11-27 23:13:03
|
Update of /cvsroot/refdb/refdb/etc In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23537/etc Modified Files: Tag: Release_0_9_5_stable refdbarc refdbcgirc refdbcrc refdbdrc refdbibrc Log Message: increased timeout to 180 Index: refdbarc =================================================================== RCS file: /cvsroot/refdb/refdb/etc/refdbarc,v retrieving revision 1.2 retrieving revision 1.2.4.1 diff -u -U2 -r1.2 -r1.2.4.1 --- refdbarc 22 Nov 2001 21:42:04 -0000 1.2 +++ refdbarc 27 Nov 2004 23:12:40 -0000 1.2.4.1 @@ -36,5 +36,5 @@ # The time in seconds which has to elapse before a stalled connection # to the application server is taken down -# timeout 60 +# timeout 180 # The destination of the log information. Uncomment *one* of the Index: refdbcgirc =================================================================== RCS file: /cvsroot/refdb/refdb/etc/refdbcgirc,v retrieving revision 1.3.4.1 retrieving revision 1.3.4.2 diff -u -U2 -r1.3.4.1 -r1.3.4.2 --- refdbcgirc 17 Aug 2004 00:36:22 -0000 1.3.4.1 +++ refdbcgirc 27 Nov 2004 23:12:43 -0000 1.3.4.2 @@ -41,5 +41,5 @@ # The time in seconds which has to elapse before a stalled connection # to the application server is taken down -# timeout 60 +# timeout 180 # The full path of a custom log file. This will be used if logdest is Index: refdbcrc =================================================================== RCS file: /cvsroot/refdb/refdb/etc/refdbcrc,v retrieving revision 1.6 retrieving revision 1.6.2.1 diff -u -U2 -r1.6 -r1.6.2.1 --- refdbcrc 25 Jan 2004 01:08:31 -0000 1.6 +++ refdbcrc 27 Nov 2004 23:12:43 -0000 1.6.2.1 @@ -43,5 +43,5 @@ # The time in seconds which has to elapse before a stalled connection # to the application server is taken down -# timeout 60 +# timeout 180 # The destination of the log information. Uncomment *one* of the Index: refdbdrc =================================================================== RCS file: /cvsroot/refdb/refdb/etc/refdbdrc,v retrieving revision 1.10 retrieving revision 1.10.2.1 diff -u -U2 -r1.10 -r1.10.2.1 --- refdbdrc 25 Jan 2004 01:08:32 -0000 1.10 +++ refdbdrc 27 Nov 2004 23:12:43 -0000 1.10.2.1 @@ -39,5 +39,5 @@ # The time in seconds which has to elapse before a stalled connection # to the client is taken down -#timeout 60 +#timeout 180 # The full path of a custom log file. This will be used if logdest is Index: refdbibrc =================================================================== RCS file: /cvsroot/refdb/refdb/etc/refdbibrc,v retrieving revision 1.6.2.1 retrieving revision 1.6.2.2 diff -u -U2 -r1.6.2.1 -r1.6.2.2 --- refdbibrc 26 Sep 2004 21:05:58 -0000 1.6.2.1 +++ refdbibrc 27 Nov 2004 23:12:43 -0000 1.6.2.2 @@ -42,5 +42,5 @@ # The time in seconds which has to elapse before a stalled connection # to the application server is taken down -#timeout 60 +#timeout 180 # Bibliography output type. Currently "db31", "db31x", "teix", and "bibtex" |
|
From: Markus H. <mho...@us...> - 2004-11-25 21:40:10
|
Update of /cvsroot/refdb/refdb/xsl/refdb/tei-refdb-xsl/tei-html In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv2026/xsl/refdb/tei-refdb-xsl/tei-html Modified Files: Tag: Release_0_9_5_stable tei-refdb-html.xsl.in Log Message: various fixes to work properly with latest stylesheets Index: tei-refdb-html.xsl.in =================================================================== RCS file: /cvsroot/refdb/refdb/xsl/refdb/tei-refdb-xsl/tei-html/tei-refdb-html.xsl.in,v retrieving revision 1.2.2.1 retrieving revision 1.2.2.2 diff -u -U2 -r1.2.2.1 -r1.2.2.2 --- tei-refdb-html.xsl.in 17 Oct 2004 00:37:40 -0000 1.2.2.1 +++ tei-refdb-html.xsl.in 25 Nov 2004 21:39:58 -0000 1.2.2.2 @@ -55,10 +55,198 @@ and suppress the inline parts --> <xsl:template match="bibl" mode="refdb"> - <!-- <xsl:variable name="ident"> - <xsl:apply-templates select="." mode="ident"/> - </xsl:variable> - <a name="{$ident}"/> --> - <a name="{@id}"/> - <xsl:apply-templates select="seg[@type='BIBLIOGRAPHY']" mode="refdb"/> + <xsl:choose> + <xsl:when test="@rend='multixref'"> + <!-- do not render directly --> + </xsl:when> + <xsl:otherwise> + <a name="{@id}"/> + <xsl:apply-templates select="seg[@type='bibliography']" mode="refdb"/> + </xsl:otherwise> + </xsl:choose> +</xsl:template> + +<!-- ulink needs special care as we want to hyperlink --> +<xsl:template match="biblScope[@type='ulink']" mode="refdb"> + <xsl:variable name="reftype" select="ancestor::bibl/@rend"/> + <xsl:variable name="target" select="."/> + <a href='{$target}'> + <xsl:choose> + <xsl:when test="$reftype='ABST'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$ABSTURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='ADVS'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$ADVSURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='ART'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$ARTURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='BILL'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$BILLURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='BOOK'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$BOOKURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='CASE'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$CASEURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='CHAP'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$CHAPURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='COMP'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$COMPURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='CONF'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$CONFURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='CTLG'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$CTLGURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='DATA'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$DATAURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='ELEC'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$ELECURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='GEN'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$GENURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='HEAR'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$HEARURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='ICOMM'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$ICOMMURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='INPR'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$INPRURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='JFULL'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$JFULLURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='JOUR'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$JOURURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='MAP'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$MAPURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='MGZN'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$MGZNURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='MPCT'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$MPCTURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='MUSIC'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$MUSICURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='NEWS'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$NEWSURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='PAMP'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$PAMPURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='PAT'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$PATURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='PCOMM'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$PCOMMURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='RPRT'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$RPRTURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='SER'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$SERURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='SLIDE'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$SLIDEURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='SOUND'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$SOUNDURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='STAT'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$STATURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='THES'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$THESURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='UNBILL'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$UNBILLURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='UNPB'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$UNPBURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='VIDEO'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$VIDEOURLSTYLE"/> + </xsl:call-template> + </xsl:when> + </xsl:choose> + </a> </xsl:template> @@ -99,17 +287,17 @@ <a href='#{$realtarget}'> <xsl:choose> - <xsl:when test="$ptrtype='INTEXT'"> + <xsl:when test="$ptrtype='intext'"> <xsl:apply-templates mode="INTEXT" select="id(@target)"/> </xsl:when> - <xsl:when test="$ptrtype='INTEXTSQ'"> + <xsl:when test="$ptrtype='intextsq'"> <xsl:apply-templates mode="INTEXTSQ" select="id(@target)"/> </xsl:when> - <xsl:when test="$ptrtype='AUTHORONLY'"> + <xsl:when test="$ptrtype='authoronly'"> <xsl:apply-templates mode="AUTHORONLY" select="id(@target)"/> </xsl:when> - <xsl:when test="$ptrtype='AUTHORONLYSQ'"> + <xsl:when test="$ptrtype='authoronlysq'"> <xsl:apply-templates mode="AUTHORONLYSQ" select="id(@target)"/> </xsl:when> - <xsl:when test="$ptrtype='YEARONLY'"> + <xsl:when test="$ptrtype='yearonly'"> <xsl:apply-templates mode="YEARONLY" select="id(@target)"/> </xsl:when> @@ -127,35 +315,36 @@ <xsl:template name="refdb-process-inline"> <xsl:param name="style"></xsl:param> - <xsl:if test="$style='ULINE' or $style='ITULINE' or $style='BOLDULINE' or $style='BOLDITULINE'"> - <xsl:text disable-output-escaping="yes"><U></xsl:text> - </xsl:if> - <xsl:if test="$style='ITALIC' or $style='ITULINE' or $style='BOLDITALIC' or $style='BOLDITULINE'"> - <xsl:text disable-output-escaping="yes"><I></xsl:text> - </xsl:if> - <xsl:if test="$style='BOLD' or $style='BOLDITALIC' or $style='BOLDULINE' or $style='BOLDITULINE'"> - <xsl:text disable-output-escaping="yes"><B></xsl:text> - </xsl:if> - <xsl:if test="$style='SUB'"> - <xsl:text disable-output-escaping="yes"><SUB></xsl:text> - </xsl:if> - <xsl:if test="$style='SUPER'"> - <xsl:text disable-output-escaping="yes"><SUP></xsl:text> - </xsl:if> - <xsl:apply-templates mode="refdb"/> - <xsl:if test="$style='SUPER'"> - <xsl:text disable-output-escaping="yes"></SUP></xsl:text> - </xsl:if> - <xsl:if test="$style='SUB'"> - <xsl:text disable-output-escaping="yes"></SUB></xsl:text> - </xsl:if> - <xsl:if test="$style='BOLD' or $style='BOLDITALIC' or $style='BOLDULINE' or $style='BOLDITULINE'"> - <xsl:text disable-output-escaping="yes"></B></xsl:text> - </xsl:if> - <xsl:if test="$style='ITALIC' or $style='ITULINE' or $style='BOLDITALIC' or $style='BOLDITULINE'"> - <xsl:text disable-output-escaping="yes"></I></xsl:text> - </xsl:if> - <xsl:if test="$style='ULINE' or $style='ITULINE' or $style='BOLDULINE' or $style='BOLDITULINE'"> - <xsl:text disable-output-escaping="yes"></U></xsl:text> - </xsl:if> + <xsl:choose> + <xsl:when test="$style='ULINE'"> + <u><xsl:apply-templates mode="refdb"/></u> + </xsl:when> + <xsl:when test="$style='ITULINE'"> + <i><u><xsl:apply-templates mode="refdb"/></u></i> + </xsl:when> + <xsl:when test="$style='BOLDULINE'"> + <b><u><xsl:apply-templates mode="refdb"/></u></b> + </xsl:when> + <xsl:when test="$style='BOLDITULINE'"> + <b><i><u><xsl:apply-templates mode="refdb"/></u></i></b> + </xsl:when> + <xsl:when test="$style='ITALIC'"> + <i><xsl:apply-templates mode="refdb"/></i> + </xsl:when> + <xsl:when test="$style='BOLDITALIC'"> + <b><i><xsl:apply-templates mode="refdb"/></i></b> + </xsl:when> + <xsl:when test="$style='BOLD'"> + <b><xsl:apply-templates mode="refdb"/></b> + </xsl:when> + <xsl:when test="$style='SUB'"> + <sub><xsl:apply-templates mode="refdb"/></sub> + </xsl:when> + <xsl:when test="$style='SUPER'"> + <sup><xsl:apply-templates mode="refdb"/></sup> + </xsl:when> + <xsl:otherwise> + <xsl:apply-templates mode="refdb"/> + </xsl:otherwise> + </xsl:choose> </xsl:template> @@ -165,33 +354,33 @@ <xsl:param name="string"></xsl:param> <xsl:if test="$style='ULINE' or $style='ITULINE' or $style='BOLDULINE' or $style='BOLDITULINE'"> - <xsl:text disable-output-escaping="yes"><U></xsl:text> + <xsl:text disable-output-escaping="yes"><u></xsl:text> </xsl:if> <xsl:if test="$style='ITALIC' or $style='ITULINE' or $style='BOLDITALIC' or $style='BOLDITULINE'"> - <xsl:text disable-output-escaping="yes"><I></xsl:text> + <xsl:text disable-output-escaping="yes"><i></xsl:text> </xsl:if> <xsl:if test="$style='BOLD' or $style='BOLDITALIC' or $style='BOLDULINE' or $style='BOLDITULINE'"> - <xsl:text disable-output-escaping="yes"><B></xsl:text> + <xsl:text disable-output-escaping="yes"><b></xsl:text> </xsl:if> <xsl:if test="$style='SUB'"> - <xsl:text disable-output-escaping="yes"><SUB></xsl:text> + <xsl:text disable-output-escaping="yes"><sub></xsl:text> </xsl:if> <xsl:if test="$style='SUPER'"> - <xsl:text disable-output-escaping="yes"><SUP></xsl:text> + <xsl:text disable-output-escaping="yes"><sup></xsl:text> </xsl:if> <xsl:value-of select="$string"/> <xsl:if test="$style='SUPER'"> - <xsl:text disable-output-escaping="yes"></SUP></xsl:text> + <xsl:text disable-output-escaping="yes"></sup></xsl:text> </xsl:if> <xsl:if test="$style='SUB'"> - <xsl:text disable-output-escaping="yes"></SUB></xsl:text> + <xsl:text disable-output-escaping="yes"></sub></xsl:text> </xsl:if> <xsl:if test="$style='BOLD' or $style='BOLDITALIC' or $style='BOLDULINE' or $style='BOLDITULINE'"> - <xsl:text disable-output-escaping="yes"></B></xsl:text> + <xsl:text disable-output-escaping="yes"></b></xsl:text> </xsl:if> <xsl:if test="$style='ITALIC' or $style='ITULINE' or $style='BOLDITALIC' or $style='BOLDITULINE'"> - <xsl:text disable-output-escaping="yes"></I></xsl:text> + <xsl:text disable-output-escaping="yes"></i></xsl:text> </xsl:if> <xsl:if test="$style='ULINE' or $style='ITULINE' or $style='BOLDULINE' or $style='BOLDITULINE'"> - <xsl:text disable-output-escaping="yes"></U></xsl:text> + <xsl:text disable-output-escaping="yes"></u></xsl:text> </xsl:if> </xsl:template> |
|
From: Markus H. <mho...@us...> - 2004-11-25 21:40:09
|
Update of /cvsroot/refdb/refdb/xsl/refdb/tei-refdb-xsl/tei-fo In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv2026/xsl/refdb/tei-refdb-xsl/tei-fo Modified Files: Tag: Release_0_9_5_stable tei-refdb-fo.xsl.in Log Message: various fixes to work properly with latest stylesheets Index: tei-refdb-fo.xsl.in =================================================================== RCS file: /cvsroot/refdb/refdb/xsl/refdb/tei-refdb-xsl/tei-fo/tei-refdb-fo.xsl.in,v retrieving revision 1.2.2.3 retrieving revision 1.2.2.4 diff -u -U2 -r1.2.2.3 -r1.2.2.4 --- tei-refdb-fo.xsl.in 17 Oct 2004 00:37:40 -0000 1.2.2.3 +++ tei-refdb-fo.xsl.in 25 Nov 2004 21:39:58 -0000 1.2.2.4 @@ -71,4 +71,190 @@ +<!-- ulink needs special care as we want to hyperlink --> +<xsl:template match="biblScope[@type='ulink']" mode="refdb"> + <xsl:variable name="reftype" select="ancestor::bibl/@rend"/> + <xsl:variable name="target" select="."/> + <fo:basic-link external-destination='url({$target})'> + <xsl:choose> + <xsl:when test="$reftype='ABST'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$ABSTURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='ADVS'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$ADVSURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='ART'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$ARTURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='BILL'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$BILLURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='BOOK'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$BOOKURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='CASE'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$CASEURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='CHAP'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$CHAPURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='COMP'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$COMPURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='CONF'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$CONFURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='CTLG'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$CTLGURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='DATA'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$DATAURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='ELEC'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$ELECURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='GEN'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$GENURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='HEAR'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$HEARURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='ICOMM'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$ICOMMURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='INPR'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$INPRURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='JFULL'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$JFULLURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='JOUR'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$JOURURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='MAP'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$MAPURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='MGZN'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$MGZNURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='MPCT'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$MPCTURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='MUSIC'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$MUSICURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='NEWS'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$NEWSURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='PAMP'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$PAMPURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='PAT'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$PATURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='PCOMM'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$PCOMMURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='RPRT'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$RPRTURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='SER'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$SERURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='SLIDE'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$SLIDEURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='SOUND'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$SOUNDURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='STAT'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$STATURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='THES'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$THESURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='UNBILL'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$UNBILLURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='UNPB'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$UNPBURLSTYLE"/> + </xsl:call-template> + </xsl:when> + <xsl:when test="$reftype='VIDEO'"> + <xsl:call-template name="refdb-process-inline"> + <xsl:with-param name="style" select="$VIDEOURLSTYLE"/> + </xsl:call-template> + </xsl:when> + </xsl:choose> + </fo:basic-link> +</xsl:template> + + <!-- overrides for xref elements --> <!-- *************************** --> |
|
From: Markus H. <mho...@us...> - 2004-11-25 21:39:23
|
Update of /cvsroot/refdb/refdb/src In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv1787/src Modified Files: Tag: Release_0_9_5_stable refdbdbib.c Log Message: added sorted_pos to SELECT DISTINCT query to pacify PostgreSQL Index: refdbdbib.c =================================================================== RCS file: /cvsroot/refdb/refdb/src/refdbdbib.c,v retrieving revision 1.36.2.12 retrieving revision 1.36.2.13 diff -u -U2 -r1.36.2.12 -r1.36.2.13 --- refdbdbib.c 28 Sep 2004 22:14:40 -0000 1.36.2.12 +++ refdbdbib.c 25 Nov 2004 21:38:59 -0000 1.36.2.13 @@ -1501,5 +1501,5 @@ /* select all unique author_abbrevlists */ - sprintf(sql_command, "SELECT DISTINCT author_abbrevlist,pubyear FROM %s WHERE sorted_pos>0 ORDER BY sorted_pos", table_name); + sprintf(sql_command, "SELECT DISTINCT author_abbrevlist,pubyear, sorted_pos FROM %s WHERE sorted_pos>0 ORDER BY sorted_pos", table_name); LOG_PRINT(LOG_DEBUG, sql_command); dbires1 = dbi_conn_query(ptr_bibconns->conn, sql_command); |
|
From: Markus H. <mho...@us...> - 2004-11-25 21:34:37
|
Update of /cvsroot/refdb/refdb/src In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv943/src Modified Files: Tag: Release_0_9_5_stable dbfncs.c Log Message: fixed a couple of INT/BIGINT mismatches in mysql table definitions Index: dbfncs.c =================================================================== RCS file: /cvsroot/refdb/refdb/src/dbfncs.c,v retrieving revision 1.15.2.1 retrieving revision 1.15.2.2 diff -u -U2 -r1.15.2.1 -r1.15.2.2 --- dbfncs.c 14 Nov 2004 15:53:03 -0000 1.15.2.1 +++ dbfncs.c 25 Nov 2004 21:34:16 -0000 1.15.2.2 @@ -174,5 +174,5 @@ refdb_pyother_info VARCHAR(255), \ refdb_secother_info VARCHAR(255), \ - refdb_periodical_id INT, \ + refdb_periodical_id BIGINT, \ refdb_user1 VARCHAR(255), \ refdb_user2 VARCHAR(255), \ @@ -262,5 +262,5 @@ note_content_type VARCHAR(255), \ note_content_xmllang VARCHAR(255), \ - note_user_id INT, \ + note_user_id BIGINT, \ note_date DATE, \ KEY (note_title), \ |
|
From: Markus H. <mho...@us...> - 2004-11-25 21:33:01
|
Update of /cvsroot/refdb/refdb/scripts In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv663 Modified Files: Tag: Release_0_9_5_stable libgen.pl Log Message: moved tei ulink handling to html and fo driver files Index: libgen.pl =================================================================== RCS file: /cvsroot/refdb/refdb/scripts/libgen.pl,v retrieving revision 1.5.2.1 retrieving revision 1.5.2.2 diff -u -U2 -r1.5.2.1 -r1.5.2.2 --- libgen.pl 29 Jul 2004 20:47:23 -0000 1.5.2.1 +++ libgen.pl 25 Nov 2004 21:32:41 -0000 1.5.2.2 @@ -33,5 +33,5 @@ # this list holds all "elements" that are created as a biblScope with # an attribute -my @tei_biblscope_elements = ("pages", "volume", "issue", "issn", "isbn", "ulink"); +my @tei_biblscope_elements = ("pages", "volume", "issue", "issn", "isbn"); # this list holds all real elements @@ -297,5 +297,6 @@ # "elements" which are in fact biblScope elements with an attribute - print "<!-- biblScope elements in the bibliography -->\n<xsl:template match=\"biblScope\" mode=\"refdb\">\n <xsl:variable name=\"reftype\" select=\"ancestor::bibl/\@rend\"/>\n <xsl:choose>\n"; +#todo: generate match list dynamically from tei_biblscope_elements + print "<!-- biblScope elements in the bibliography -->\n<xsl:template match=\"biblScope[\@type=\'pages\']|biblScope[\@type=\'volume\']|biblScope[\@type=\'issue\']|biblScope[\@type=\'issn\']|biblScope[\@type=\'isbn\']\" mode=\"refdb\">\n <xsl:variable name=\"reftype\" select=\"ancestor::bibl/\@rend\"/>\n <xsl:choose>\n"; foreach $element (@tei_biblscope_elements) { |
|
From: Markus H. <mho...@us...> - 2004-11-25 21:31:56
|
Update of /cvsroot/refdb/refdb/scripts In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv497 Added Files: Tag: Release_0_9_5_stable migrate_mysql_0.9.5 Log Message: initial version --- NEW FILE --- # this SQL script migrates RefDB reference databases generated with # version 0.9.4 to the schema used in 0.9.5. Use like this: # # mysql -r admin_name -p dbname < migrate_mysql_0.9.5 # ALTER TABLE t_author MODIFY author_id BIGINT NOT NULL AUTO_INCREMENT; ALTER TABLE t_keyword MODIFY keyword_id BIGINT NOT NULL AUTO_INCREMENT; ALTER TABLE t_note MODIFY note_id BIGINT NOT NULL AUTO_INCREMENT, MODIFY note_user_id BIGINT; ALTER TABLE t_periodical MODIFY periodical_id BIGINT NOT NULL AUTO_INCREMENT; ALTER TABLE t_refdb MODIFY refdb_id BIGINT NOT NULL AUTO_INCREMENT, MODIFY refdb_periodical_id BIGINT; ALTER TABLE t_user MODIFY user_id BIGINT NOT NULL AUTO_INCREMENT; ALTER TABLE t_xauthor MODIFY xauthor_id BIGINT NOT NULL AUTO_INCREMENT, MODIFY author_id BIGINT NOT NULL, MODIFY refdb_id BIGINT NOT NULL; ALTER TABLE t_xkeyword MODIFY xkeyword_id BIGINT NOT NULL AUTO_INCREMENT, MODIFY keyword_id BIGINT NOT NULL, MODIFY xref_id BIGINT NOT NULL; ALTER TABLE t_xnote MODIFY xnote_id BIGINT NOT NULL AUTO_INCREMENT, MODIFY note_id BIGINT NOT NULL, MODIFY xref_id BIGINT NOT NULL; ALTER TABLE t_xuser MODIFY xuser_id BIGINT NOT NULL AUTO_INCREMENT, MODIFY user_id BIGINT NOT NULL, MODIFY refdb_id BIGINT NOT NULL; |
|
From: Markus H. <mho...@us...> - 2004-11-25 21:31:07
|
Update of /cvsroot/refdb/refdb/scripts In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv32767/scripts Modified Files: Tag: Release_0_9_5_stable Makefile.am Log Message: added migrate_mysql_0.9.5 to EXTRA_DIST Index: Makefile.am =================================================================== RCS file: /cvsroot/refdb/refdb/scripts/Makefile.am,v retrieving revision 1.23 retrieving revision 1.23.2.1 diff -u -U2 -r1.23 -r1.23.2.1 --- Makefile.am 5 Mar 2004 00:10:05 -0000 1.23 +++ Makefile.am 25 Nov 2004 21:30:52 -0000 1.23.2.1 @@ -3,5 +3,5 @@ bin_SCRIPTS = @server_scripts@ @client_scripts@ -EXTRA_DIST=refdbjade.in runbib.in tex2mail db2ris.in refdb-bug.in refdbxml.in refdb.dump refdb.dump.pgsql refdb.dump.sqlite refdb refdbctl.in empty.mysql.dump empty.pgsql.dump.in refdb-upgrade.sql marc2ris.pl.in med2ris.pl.in en2ris.pl.in refdbnd.in vargen.pl libgen.pl dos2unix.in +EXTRA_DIST=refdbjade.in runbib.in tex2mail db2ris.in refdb-bug.in refdbxml.in refdb.dump refdb.dump.pgsql refdb.dump.sqlite refdb refdbctl.in empty.mysql.dump empty.pgsql.dump.in refdb-upgrade.sql marc2ris.pl.in med2ris.pl.in en2ris.pl.in refdbnd.in vargen.pl libgen.pl dos2unix.in migrate_mysql_0.9.5 MOSTLYCLEANFILES=refdbjade runbib db2ris refdbxml refdbctl refdb-bug refdbnd marc2ris.pl med2ris.pl en2ris.pl dos2unix |
|
From: Markus H. <mho...@us...> - 2004-11-25 21:28:52
|
Update of /cvsroot/refdb/refdb/doc In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv32032/doc Modified Files: Tag: Release_0_9_5_stable refdb-manual-chapter14.sgml refdb-manual-chapter2.sgml refdb-manual-chapter5.sgml refdb-manual-chapter8.sgml refdb-manual-configopts.sgml Log Message: updated for 0.9.5 Index: refdb-manual-chapter14.sgml =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdb-manual-chapter14.sgml,v retrieving revision 1.9.2.1 retrieving revision 1.9.2.2 diff -u -U2 -r1.9.2.1 -r1.9.2.2 --- refdb-manual-chapter14.sgml 14 Nov 2004 16:04:49 -0000 1.9.2.1 +++ refdb-manual-chapter14.sgml 25 Nov 2004 21:28:41 -0000 1.9.2.2 @@ -38,6 +38,6 @@ <arg choice="req" rep="norepeat">database</arg> <arg choice="req" rep="norepeat">style</arg> - <arg choice="opt" rep="norepeat">encoding</arg> - <arg choice="opt" rep="norepeat">css-file</arg> + <arg choice="req" rep="norepeat">encoding</arg> + <arg choice="req" rep="norepeat">css-file</arg> </cmdsynopsis> <para>The script will create two files in your current working directory:</para> Index: refdb-manual-chapter2.sgml =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdb-manual-chapter2.sgml,v retrieving revision 1.15.2.1 retrieving revision 1.15.2.2 diff -u -U2 -r1.15.2.1 -r1.15.2.2 --- refdb-manual-chapter2.sgml 14 Nov 2004 16:04:49 -0000 1.15.2.1 +++ refdb-manual-chapter2.sgml 25 Nov 2004 21:28:41 -0000 1.15.2.2 @@ -22,5 +22,5 @@ </listitem> <listitem> - <para>Solaris</para> + <para>Solaris/SunOS</para> </listitem> <listitem> @@ -159,7 +159,7 @@ </varlistentry> <varlistentry> - <term>XSL processor (required for DocBook and TEI XML documents)</term> + <term>XSLT and FO processors (required for DocBook and TEI XML documents)</term> <listitem> - <para>If you're working with XML documents and want to transform them using the XSL stylesheets, you'll need some sort of XSL processing machinery. Popular choices are <ulink url="http://xml.apache.org">Xalan</ulink>, <ulink url="http://saxon.sourceforge.net">Saxon</ulink>, and <ulink url="http://xmlsoft.org/XSLT">xsltproc</ulink>. The latter is checked for in the configure script and will be used as the default processor if available. The Java-based tools among these need the <ulink url="http://java.sun.com">Java Virtual Machine</ulink> installed, of course. Generating printable output seems to work best with <ulink url="http://xml.apache.org/fop/index.html">FOP</ulink>.</para> + <para>If you're working with XML documents and want to transform them using the XSL stylesheets, you'll need some sort of XSL processing machinery. Popular choices are <ulink url="http://xml.apache.org">Xalan</ulink>, <ulink url="http://saxon.sourceforge.net">Saxon</ulink>, and <ulink url="http://xmlsoft.org/XSLT">xsltproc</ulink>. The latter is checked for in the configure script and will be used as the default processor if available. The Java-based tools among these need the <ulink url="http://java.sun.com">Java Virtual Machine</ulink> installed, of course. Generating printable output from FO seems to work best with <ulink url="http://xml.apache.org/fop/index.html">FOP</ulink>.</para> </listitem> </varlistentry> Index: refdb-manual-chapter5.sgml =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdb-manual-chapter5.sgml,v retrieving revision 1.24.2.1 retrieving revision 1.24.2.2 diff -u -U2 -r1.24.2.1 -r1.24.2.2 --- refdb-manual-chapter5.sgml 14 Nov 2004 16:04:50 -0000 1.24.2.1 +++ refdb-manual-chapter5.sgml 25 Nov 2004 21:28:41 -0000 1.24.2.2 @@ -43,5 +43,5 @@ <para>Once again, the database schema of the main database has changed. However, starting from this version the name of the main database is a configure option. If you do not have to run this and an older version in parallel, you don't have to change the configuration. However, if you want to keep your existing setup while test-driving the new version, there is a new configure switch <option>--with-main-db</option> to set the name of the main database.</para> <para>In the first case, you'll have to replace your existing main database with the new version. In the second case, you create another main database with a different name. Only the new version of &appname; will be able to access this database if configured properly.</para> - <para>Finally, a bug in the MySQL table definitions was fixed. If you're using MySQL as your database engine, you'll have to dump your data and re-create your reference databases with the new version installed. See the instructions about migrating your data to 0.9.4. With this version it is also safe to use risx as the dump format.</para> + <para>Finally, a bug in the MySQL table definitions was fixed. If you're using MySQL as your database engine, you'll have to migrate your reference databases as well. 0.9.5 provides a SQL script that changes the table definitions appropriately.</para> </listitem> <listitem> @@ -213,5 +213,5 @@ <sect3> <title>Types of configuration files</title> - <para>All &appname; applications and scripts that use configuration files (these are the server <link linkend="chapter-refdbd">&appname;d</link>, the clients <link linkend="chapter-refdbc">&appname;c</link>, <link linkend="chapter-refdbib">&appname;ib</link>, <link linkend="chapter-refdba">&appname;a</link>, as well as the conversion filters <link linkend="sect-bibtoris">bib2ris</link>, <link linkend="sect-dbtoris">db2ris</link>, <link linkend="sect-medtorispl">med2ris.pl</link>, <link linkend="sect-marctoris">marc2ris.pl</link>, and <link linkend="sect-entorispl">en2ris.pl</link>) can use two configuration files each. One global configuration file is supplied by the system administrator and can be used to set values that are common for all users on that box, like the IP address of the application server. Another file can be used by every user to supply the values that were not set in the global file or to override settings in this file. The users' copies can have a leading dot to hide the files (the &appname; programs will first try to read a hidden configuration file, and only if that cannot be found they try to read a non-hidden file).</para> + <para>All &appname; applications and scripts that use configuration files (these are the server <link linkend="chapter-refdbd">&appname;d</link>, the clients <link linkend="chapter-refdbc">&appname;c</link>, <link linkend="chapter-refdbib">&appname;ib</link>, <link linkend="chapter-refdba">&appname;a</link>, the script <link linkend="sect2-refdbxml-init-variables">&appname;xml</link>, as well as the conversion filters <link linkend="sect-bibtoris">bib2ris</link>, <link linkend="sect-dbtoris">db2ris</link>, <link linkend="sect-medtorispl">med2ris.pl</link>, <link linkend="sect-marctoris">marc2ris.pl</link>, and <link linkend="sect-entorispl">en2ris.pl</link>) can use two configuration files each. One global configuration file is supplied by the system administrator and can be used to set values that are common for all users on that box, like the IP address of the application server. Another file can be used by every user to supply the values that were not set in the global file or to override settings in this file. The users' copies can have a leading dot to hide the files (the &appname; programs will first try to read a hidden configuration file, and only if that cannot be found they try to read a non-hidden file).</para> <para>&appname;c, bib2ris, marc2ris.pl, and med2ris.pl use a second global configuration file if they are run as a CGI applications. A local configuration file does not make sense in this case.</para> <para>The default location for the global configuration files is <filename>/usr/local/etc/refdb</filename>. There are two ways to change this. If you compile &appname; from the sources you can specify a different directory with the <option>--prefix</option> or <option>--sysconfdir</option> options of <command moreinfo="none">./configure</command>. E.g. if you specify <option>--sysconfdir=/etc</option>, then the configuration files will be installed in <filename class="directory" moreinfo="none">/etc/&appname;</filename> (the <filename moreinfo="none">&appname;</filename> part is automatically appended by the &appname; install routines). If you use precompiled binaries, use the <option>-y</option> command line option to specify the directory. In this case you have to specify the full path, i.e. <filename class="directory" moreinfo="none">/etc/refdb</filename> to read the configuration files installed by the previous example.</para> @@ -431,13 +431,13 @@ <step performance="required"> <para>Run the following command (adapt this accordingly if you use some graphical CVS frontend instead of the command line tool):</para> - <screen format="linespecific"><prompt moreinfo="none">$~/build </prompt><userinput moreinfo="none">cvs -d :pserver:ano...@cv...:/cvsroot/refdb login</userinput></screen> + <screen format="linespecific"><prompt moreinfo="none">$~/build </prompt><userinput moreinfo="none">cvs -d :pserver:ano...@cv...:/cvsroot/refdb login</userinput></screen> <para>Just press enter if you're asked for a password. This login is required only once as CVS will remember the required information for all later accesses.</para> </step> <step performance="required"> <para>Check out the latest &appname; sources with this command:</para> - <screen format="linespecific"><prompt moreinfo="none">$~/build </prompt><userinput moreinfo="none">cvs -d :pserver:ano...@cv...:/cvsroot/refdb -z3 checkout refdb</userinput></screen> + <screen format="linespecific"><prompt moreinfo="none">$~/build </prompt><userinput moreinfo="none">cvs -d :pserver:ano...@cv...:/cvsroot/refdb -z3 checkout refdb</userinput></screen> <para>Other interesting modules are <filename>perlmod</filename> (the Perl modules and the Perl client library) and <filename>elisp</filename> (the Emacs support files).</para> <para>If you are interested in a particular release or branch, use a command along the lines of this example instead:</para> - <screen format="linespecific"><prompt moreinfo="none">$~/build </prompt><userinput moreinfo="none">cvs -d :pserver:ano...@cv...:/cvsroot/refdb -z3 checkout -r Release_0_9_1 refdb</userinput></screen> + <screen format="linespecific"><prompt moreinfo="none">$~/build </prompt><userinput moreinfo="none">cvs -d :pserver:ano...@cv...:/cvsroot/refdb -z3 checkout -r Release_0_9_1 refdb</userinput></screen> </step> <step performance="required"> @@ -701,5 +701,5 @@ <title>PostgreSQL</title> <note> - <para>If <filename>postmaster</filename> (the PostgreSQL database server) is installed on a remote box or if the security settings require it, you may have to use the <option>-h <replaceable>hostname</replaceable></option> and/or the <option>-U <replaceable>username</replaceable></option> options to run the <filename>psql</filename> client as shown below (most fresh PostgreSQL installations on Unix-style systems use "pgsql" with no password as the default database administrator. The Cygwin port of PostgreSQL uses the name of whoever installed the package, usually "Administrator"). <filename>postmaster</filename> needs to be up and running and you need the appropriate permissions, of course. See the <application>PostgreSQL</application> documentation for further details.</para> + <para>If <filename>postmaster</filename> (the PostgreSQL database server) is installed on a remote box or if the security settings require it, you may have to use the <option>-h <replaceable>hostname</replaceable></option> and/or the <option>-U <replaceable>username</replaceable></option> options to run the <filename>psql</filename> client as shown below (most fresh PostgreSQL installations on Unix-style systems use "pgsql" with no password as the default database administrator. The Cygwin port of PostgreSQL uses the name of whoever installed the package, usually "Administrator". On Debian you need to be logged in as user "postgres": first <command moreinfo="none">su root</command>, then <command moreinfo="none">su postgres</command>). <filename>postmaster</filename> needs to be up and running and you need the appropriate permissions, of course. See the <application>PostgreSQL</application> documentation for further details.</para> </note> <itemizedlist> @@ -816,322 +816,4 @@ <para>This is all it takes to test the basic functionality of your setup. Everything beyond this is either site-specific setup or mere usage of the tools. Please peruse the manual, especially the hints about getting your <link linkend="sect-database-server-access-control">database access rights</link> correct.</para> </sect1> - <sect1> - <title>Setting up the &appname; web services</title> - <para>This section guides you through the necessary steps to run &appname;c, bib2ris, and med2ris.pl as <acronym>CGI</acronym> applications. This will allow the users to enjoy a part of the functionality of &appname; through a web interface.</para> - <para>If you want to work through this section you'll need some basic knowledge about the administration of your web server. Needless to say that you also need the proper privileges to fiddle with your web server settings. The procedure below was written with <ulink url="http://www.apache.org">Apache</ulink> 1.3 on Debian GNU/Linux in mind. Apache is by far the most popular web server and available on various platforms, including all platforms that &appname; currently supports. If you use a different Linux distribution or a different operating system, the location and name of the files may slightly differ. If you use a different web server, the configuration process may be entirely different, but with the user manual at your hands you may be able to adapt the following instructions to your needs.</para> - <note> - <para>If your web server and the &appname;d application server run on different machines, please notice that all but one steps below talk about the computer running the web server. One step talks about the computer running &appname;d.</para> - </note> - <procedure> - <step performance="required"> - <para>To tell Apache about the &appname; web pages, add the following line to <filename>/etc/apache/httpd.conf</filename>:</para> - <programlisting format="linespecific"> -Alias /refdb/ /usr/local/share/refdb/www/ -</programlisting> - <para>This entry will let you access the &appname; web interface through the address [hostname]/refdb. While you're at modifying <filename moreinfo="none">httpd.conf</filename>, the next step may require another change to this file.</para> - </step> - <step performance="required"> - <para>Most web servers expect CGI applications in one specific, configurable directory. If your web server is not already set up for CGI applications, you`ll have to register a cgi-bin directory. To do this in the case of Apache, add the following line to <filename>/etc/apache/httpd.conf</filename>:</para> - <programlisting> -ScriptAlias /cgi-bin/ /usr/local/bin/apache/cgi-bin/ -</programlisting> - <para>You can of course choose a different directory if you wish.</para> - <para>The directory must be readable and accessible for the account that the web server daemon runs in (this is often user "www" and group "www", which I will use in the example below). If this is not already the case, issue something like the following commands:</para> - <screen format="linespecific"><prompt moreinfo="none">#~ </prompt><userinput moreinfo="none">chown www:www /usr/local/bin/apache/cgi-bin</userinput></screen> - <screen><prompt>#~ </prompt><userinput>chmod u+rx /usr/local/bin/apache/cgi-bin</userinput></screen> - <para>Now you have to tell Apache about the updated configuration:</para> - <screen><prompt>#~ </prompt><userinput>apachectl restart</userinput></screen> - </step> - <step performance="required"> - <para>Place copies of <filename>&appname;c</filename>, <filename>bib2ris</filename>, and <filename>med2ris.pl</filename> in your <filename class="directory">/cgi-bin</filename> directory. Unless they are readable and executable for everyone you'll have to make them read/executable for the web server daemon:</para> - <screen format="linespecific"><prompt moreinfo="none">#~ </prompt><userinput moreinfo="none">cd /usr/local/bin/apache/cgi-bin/</userinput></screen> - <screen format="linespecific"><prompt moreinfo="none">#~ </prompt><userinput moreinfo="none">chown www:www &appname;c bib2ris med2ris.pl</userinput></screen> - <screen><prompt>#~ </prompt><userinput>chmod u+rx &appname;c bib2ris med2ris.pl</userinput></screen> - </step> - <step performance="required"> - <para>Create the <link linkend="sect1-mystery-init-files">configuration files</link> <filename>/usr/local/etc/&appname;/&appname;cgirc</filename>, <filename>/usr/local/etc/&appname;/bib2riscgirc</filename>, and <filename>/usr/local/etc/&appname;/med2riscgirc</filename> (unless you chose a different directory during configuration) and fill in appropriate values. Remember that bib2ris and med2ris need access to HTML templates. You should specify the proper value for &appname;lib in the configuration files.</para> - </step> - <step> - <para>You can of course <link linkend="ch-customize-web">modify the HTML files and the stylesheet</link> according to your needs. The static HTML files, a CSS stylesheet file, and a JavaScript file are installed by default in <filename class="directory">/usr/local/share/refdb/www</filename>, whereas the HTML templates are installed in <filename class="directory">/usr/local/share/refdb/templates</filename> <emphasis>on the computer that runs &appname;d</emphasis>. Both the computer that runs Apache and the CGI programs and the computer that runs &appname;d need a copy of <filename class="directory">/usr/local/share/refdb/templates</filename>.</para> - </step> - <step> - <para>The file <filename>refdbquery.html</filename> is the main entry point to the &appname; web interface. Web visitors should be guided to this page as it allows username/password authentication. The &appname; installation procedure creates a symlink with the name <filename moreinfo="none">index.html</filename> pointing to <filename>refdbquery.html</filename>, so you'll be able to access the main query page by pointing your browser to "[hostname]/refdb/".Provide links on your web pages accordingly.</para> - </step> - </procedure> - <para>It may be a good idea to check the access rights of all related files again to make sure the site visitors can access them from their browser. The static HTML pages, the templates, the javascript file, and the CSS style sheet must be readable for the account the web server is started under. The templates must be readable for the account &appname;d is started under.</para> - </sect1> - <sect1> - <title>Logging data</title> - <para>The &appname; programs can spill out quite a lot of log messages to keep track of what is happening in your programs. This section explains the basics of setting up your message logging.</para> - <sect2> - <title>What to log</title> - <para>The application server &appname;d as well as all command-line clients can generate log messages. Message logging is most important for two purposes:</para> - <itemizedlist> - <listitem> - <para>Keep track of non-interactive programs. This includes &appname;d as well as &appname;c, bib2ris, and nmed2ris if they are run as CGI applications. It may include all clients if they are run from scripts.</para> - </listitem> - <listitem> - <para>Track down bugs or user errors.</para> - </listitem> - </itemizedlist> - <para>A useful approach is to log all messages with a log level (explained <link linkend="sect2-log-level">below</link>) of 6. This would give you a good overview over the usage of these programs but would not clutter the log files with debug information. Switch to log level 7 only if you suspect a bug or some user error and need the full debug information to understand the problem.</para> - <para>For the interactive use of the clients logging is usually not necessary, so you'd use a log level of -1 to prevent logging altogether or a log level of maybe 3 or 4. In the latter case you'd get log messages only if something goes badly wrong. Again, if you encounter bugs or user errors you may switch on debug messages by using a log level of 7.</para> - </sect2> - <sect2> - <title>Destinations</title> - <para>There are three possible destinations the log messages can be sent to. Select the proper destination with either the <varname>logdest</varname> variable in the configuration file or the <option>-e</option> switch on the command line. In both cases the values in the following list are accepted. You may use either the numerical value or the case-insensitive string in brackets, e.g. <option>-e 1</option> and <option>-e syslog</option> are equivalent.</para> - <variablelist> - <varlistentry> - <term>0 (stderr)</term> - <listitem> - <para>stderr is mostly useful for debugging purposes when &appname;d is run as a standalone process and when clients are run interactively. stderr does not make much sense if you run &appname;d as a daemon (daemons detach from the console at startup, so all output to stderr is lost).</para> - </listitem> - </varlistentry> - <varlistentry> - <term>1 (syslog)</term> - <listitem> - <para>Sending the data to syslog integrates the log data with the rest of your system's log output. The log messages will be sent to the user facility, which usually is configured to write to <filename>/var/log/user.log</filename>. See the syslog(8) man page for information how to configure the syslog facility.</para> - <note> - <para>If you run &appname;d on Cygwin, the syslog messages are sent to the application message list in the NT message logging system. If you are used to going through your log output with tools like grep and awk, you may find it more useful to write to a custom log file instead.</para> - </note> - </listitem> - </varlistentry> - <varlistentry> - <term>2 (file)</term> - <listitem> - <para>You can define the full path of a custom log file with either the <varname>logfile</varname> configuration file parameter or the <option>-L</option> command line option. By default, &appname; applications write their log output to <filename>/var/log/<appname>.log</filename>. Make sure to set the appropriate access rights for these log files.</para> - </listitem> - </varlistentry> - </variablelist> - <note> - <para>Some libraries used by &appname;, e.g. the PostgreSQL client library, send log messages to stderr. This is not controlled by the log settings of &appname;d. The same PostgreSQL log messages show up in the PostgreSQL log which is usually sent to <filename moreinfo="none">/var/log/pgsql</filename>.</para> - </note> - </sect2> - <sect2 id="sect2-log-level"> - <title>Log levels</title> - <para>You can select how verbose the log output of &appname;d will be. You can do this by either setting the <varname>loglevel</varname> configuration file variable or the <option>-l</option> command line option to an appropriate value. You may either use the numerical value or the case-insensitive string as explained in the table below. E.g. <option>-l 5</option> and <option>-l notice</option> are equivalent. Set the log level to -1 to disable logging completely. Use a value from 0 through 7 to generate increasingly verbose log output. The definitions of the log levels are taken from the include file <filename>syslog.h</filename>:</para> - <table id="table-loglevel-definitions"> - <title>Log level definitions</title> - <tgroup cols="3"> - <thead> - <row> - <entry>level</entry> - <entry>verbose</entry> - <entry>explanation</entry> - </row> - </thead> - <tbody> - <row> - <entry>0</entry> - <entry>emerg</entry> - <entry>system is unusable</entry> - </row> - <row> - <entry>1</entry> - <entry>alert</entry> - <entry>action must be taken immediately</entry> - </row> - <row> - <entry>2</entry> - <entry>crit</entry> - <entry>the system is in a critical condition</entry> - </row> - <row> - <entry>3</entry> - <entry>err</entry> - <entry>there is an error condition</entry> - </row> - <row> - <entry>4</entry> - <entry>warning</entry> - <entry>there is a warning condition</entry> - </row> - <row> - <entry>5</entry> - <entry>notice</entry> - <entry>a normal but significant condition</entry> - </row> - <row> - <entry>6</entry> - <entry>info</entry> - <entry>a purely informational message</entry> - </row> - <row> - <entry>7</entry> - <entry>debug</entry> - <entry>messages generated to debug the application</entry> - </row> - </tbody> - </tgroup> - </table> - <para>Setting the log level to a given value means that all messages with a priority level up to the given value will be logged. E.g. if you set the log level to 6 (which is a reasonable default value), all messages with a priority from 0 through 6 will be logged, whereas messages with a priority level of 7 will be ignored.</para> - <warning> - <para>Use log level 7 with caution. The amount of log messages is considerable and sufficient to slow down the application. You should not use this level in everyday use, only to track down bugs or user errors that you may encounter.</para> - </warning> - </sect2> - <sect2> - <title>Interpreting the log information</title> - <para>If the messages are sent to stderr, only the message proper will be printed. If the messages are sent to the syslog facility, the default format including the process name and process ID is used.</para> - <para>A line in the custom log file looks like this:</para> - <programlisting>6:pid=267:Sun Jul 22 18:39:52 2001:application server started</programlisting> - <para>You will easily recognize the following fields:</para> - <programlisting>message_priority:process_id:time:message</programlisting> - <variablelist> - <varlistentry> - <term>message priority</term> - <listitem> - <para>This is the priority assigned to the message by &appname;d. The values are explained <link linkend="table-loglevel-definitions">above</link>.</para> - </listitem> - </varlistentry> - <varlistentry> - <term>process ID</term> - <listitem> - <para>This is the process ID (as seen in the <command>ps ax</command> listing) of the &appname; process that generated the message. In the case of &appname;d this may either be the parent process (the one that generated the above "application server started" message) or one of the children that are forked off to answer client requests.</para> - </listitem> - </varlistentry> - <varlistentry> - <term>time</term> - <listitem> - <para>This is the full time and date information when the message was generated.</para> - </listitem> - </varlistentry> - <varlistentry> - <term>message</term> - <listitem> - <para>This is the message text proper.</para> - </listitem> - </varlistentry> - </variablelist> - <para>The message entries are sufficiently structured to allow easy access to the information with the standard Unix tools like <application>awk</application> and <application>grep</application>.</para> - </sect2> - </sect1> - <sect1> - <title>Security issues</title> - <para>This section briefly discusses some security-related issues that you might want to think about as an administrator. We'll look at the access control provided by the external database servers MySQL and PostgreSQL.</para> - <note> - <para>The embedded database engine SQLite does not provide built-in access control. All you can do is use <command moreinfo="none">chown</command> and <command moreinfo="none">chmod</command> to restrict access to the database files. There is no way to restrict access through &appname;.</para> - </note> - <sect2> - <title>Passwords</title> - <para>&appname; tries to support the security features of the SQL database servers as far as possible. This includes the username/password-based access rights scheme (not much surprise here). Since version 0.6.0 the passwords are no longer transmitted as plain text between the clients and the server. This means that it now makes sense to keep the passwords secret. There are several ways to specify the password when starting a &appname; client. These ways differ with respect to the security of the passwords and are listed here in the order of <emphasis>increasing</emphasis> security:</para> - <variablelist> - <varlistentry> - <term>Specify the password on the command line</term> - <listitem> - <para>The password is stored nowhere on the filesystem and thus pretty secure from this point of view. But the full command line can be viewed with the <command moreinfo="none">ps</command> command by any user on the system, so the unencrypted password is basically world-readable at least for a very brief period until the applications have a chance to hide the string.</para> - </listitem> - </varlistentry> - <varlistentry> - <term>Store the password in the personal configuration file</term> - <listitem> - <para>This way the password is protected from other users who habitually run the <command moreinfo="none">ps</command> command just for the heck of it. But now it is stored unencrypted on the hard drive, and you must make sure that no one else can read the configuration file (no group or world read access).</para> - </listitem> - </varlistentry> - <varlistentry> - <term>Specify the password interactively</term> - <listitem> - <para>This is the default behaviour if the password is not specified either in the configuration file or on the command line. The &appname; client will ask for the password. This is certainly the most secure way to provide a password, but this won't work if you run the clients unattended via scripts.</para> - </listitem> - </varlistentry> - </variablelist> - </sect2> - <sect2 id="sect-database-server-access-control"> - <title>Database server access control</title> - <para>It is beyond the scope of this manual to reiterate the security models of the database servers, but you need to keep in mind a few aspects relevant to &appname;.</para> - <itemizedlist> - <listitem> - <para>One component of the database server access control is based on the host from which you connect to the database server. This is partially circumvented by the &appname; three-tier design. Keep in mind that only &appname;d communicates with the database server. Therefore only the host where &appname;d runs is relevant for the access control. There is currently no system in place for checking whether a client is allowed to connect to the &appname;d application server from a particular host.</para> - </listitem> - <listitem> - <para>Both MySQL and PostgreSQL distinguish between local and remote connections. Access needs to be granted separately if you want to use both local and remote connections</para> - <note> - <para>On many operating systems the default installations of MySQL and PostreSQL do not allow remote connections for security reasons. You need to manually allow remote connections as described below.</para> - </note> - </listitem> - <listitem> - <para>The &appname;a commands to remotely reconfigure a running application server are currently protected by a simple table access test. In any serious database server installation, only the database administators have read access to certain system tables. The current implementation of this check requires that you have access to this table if you want to run the <link linkend="app-admin-command-confserv"><command moreinfo="none">confserv</command></link> commands. You should be aware that if the access rights are set up improperly, you may also allow everyone and their grandma to stop or reconfigure the &appname;d application server. If you cannot restrict read access to system tables for whatever reason, you should not enable &appname;d remote administration (default is off) and use the <link linkend="chapter-refdbd"><command moreinfo="none">kill</command> command</link> or the <link linkend="sect2-starting-refdbd-script">refdbctl</link> script instead.</para> - </listitem> - <listitem> - <para>Most of the &appname;a commands require database administrator rights. </para> - </listitem> - </itemizedlist> - <sect3> - <title>MySQL</title> - <para>If you run MySQL as your database server, these things apply as well:</para> - <itemizedlist> - <listitem> - <para>When adding users with the <link linkend="app-admin-command-adduser"><command moreinfo="none">adduser</command></link> command the <option>-H</option> option has to specify the box where &appname;d runs as the host, not the box from where the user will run the clients. If you do not specify a host, "localhost" is assumed.</para> - </listitem> - <listitem> - <para>To allow remote connections to the database server, the MySQL configuration file <filename moreinfo="none">my.cnf</filename> must not contain the option "skip-networking", and the start script must not use the command-line option <option>--skip-networking</option>. Many operating systems use one of these methods in default installations to restrict access to local users for security reasons.</para> - </listitem> - <listitem> - <para>If you install and run MySQL yourself, you should not use the default database administrator account. The name (root) is widely known and by default this account is not password-protected. To make your database server secure, please create a new database administrator account with a different name and specify a password.</para> - </listitem> - </itemizedlist> - </sect3> - <sect3> - <title>PostgreSQL</title> - <para>If you run PostgreSQL as your database server, these hints are for you:</para> - <itemizedlist> - <listitem> - <para>The host-based part of the PostgreSQL access control is not accessible through the SQL interface. Therefore, the &appname;a command <link linkend="app-admin-command-adduser"><command>adduser</command></link> cannot provide the host information (in other words, the <option>-H</option> is ignored).</para> - <para>Instead, the host-based part of the access control is specified in the PostgreSQL configuration file, usually <filename moreinfo="none">/home/pgsql/data/pg_hba.conf</filename>. On most operating systems, the default configuration allows unrestricted access for all users on the local system, but no remote access. Use something like the following entries to enforce usage of passwords for both local access and remote access from the network 192.168.1.0 to &appname; and a reference database "refs":</para> - <programlisting format="linespecific"> -# host DBNAME IP_ADDRESS ADDRESS_MASK AUTH_TYPE [AUTH_ARGUMENT] - local &appname; crypt - local refs crypt - - host &appname; 192.168.1.0 255.255.255.0 crypt - host refs 192.168.1.0 255.255.255.0 crypt - </programlisting> - <para>As mentioned previously, only the host where &appname;d runs is relevant for the host or network entries in the configuration file.</para> - <para>Make sure to read the PostgreSQL documentation to get your access control right.</para> - <note> - <para>Please keep in mind that <filename>postmaster</filename> (the PostgreSQL database server parent process) needs to be started with the <option>-i</option> option to accept remote connections at all. Most default installations do not use this switch to increase security.</para> - </note> - </listitem> - <listitem> - <para>If you install and run PostgreSQL yourself, you should not use the default database administrator account. The name (pgsql) is widely known and by default this account is not password-protected. To make your database server secure, please create a new database administrator account with a different name and specify a password.</para> - </listitem> - </itemizedlist> - </sect3> - </sect2> - <sect2> - <title>Web access</title> - <para>Web access adds some security flaws to your system. Usernames and passwords will travel happily as plaintext between the browser and the web server. If you choose to store the access information as a cookie to simplify subsequent accesses, the username and password will be stored on the disk as plain text. It may be prudent to create special database accounts with restricted access rights for use with the web interface.</para> - </sect2> - </sect1> - <sect1> - <title>How to run several &appname; instances</title> - <para>In all but a few cases, having one &appname;d daemon per network is absolutely sufficient. However, there are a few cases where you may end up running more than one instance of &appname;d on the same computer at the same time:</para> - <itemizedlist> - <listitem> - <para>You want to provide access to more than one database engine. The only good reason to do this may be to test-drive a different database engine.</para> - </listitem> - <listitem> - <para>You want to test-drive a new &appname; release without interrupting the access to your installed version</para> - </listitem> - <listitem> - <para>You do not want to run &appname;d as a daemon serving all users. Instead, each user should be able to run his own copy of &appname;d</para> - </listitem> - </itemizedlist> - <para>You'll have to configure each &appname;d process individually. If each user starts his own copy of the application server, private <filename moreinfo="none">.refdbdrc</filename> configuration files in the users' <envar>$HOME</envar> directory allow a simple setup. If you want to run more than one daemon as non-user-processes, you cannot safely use the <command>refdbctl</command> script to control the instances. Instead you should start and stop the daemons manually and use the appropriate command-line options to configure each process individually. The options which need to be set differently whenever more than one &appname;d instance runs on the same box are:</para> - <itemizedlist> - <listitem> - <para><option>-D</option>, <option>-i</option>, and<option>-b</option> to set the database engine, IP address, and the port it listens on, respectively. Only required if you fiddle with two different database engines.</para> - </listitem> - <listitem> - <para><option>-e</option> and <parameter moreinfo="none">-L</parameter> to use separate log files for the two instances. This may be easier to evaluate than using syslog, although the processes can be distinguished by means of their process ID.</para> - </listitem> - <listitem> - <para><option>-P</option> to use separate PID files</para> - </listitem> - <listitem> - <para><option>-p</option> to set the port each &appname;d instance listens on. The ports must be different, otherwise clients can't select which instance to connect to.</para> - </listitem> - </itemizedlist> - <para>On the client side you'll need only set the <varname>port</varname> configuration variable or use the <option>-p</option> command line option to select the application server instance that you want to connect to.</para> - </sect1> </chapter> Index: refdb-manual-chapter8.sgml =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdb-manual-chapter8.sgml,v retrieving revision 1.13.2.1 retrieving revision 1.13.2.2 diff -u -U2 -r1.13.2.1 -r1.13.2.2 --- refdb-manual-chapter8.sgml 14 Nov 2004 16:04:50 -0000 1.13.2.1 +++ refdb-manual-chapter8.sgml 25 Nov 2004 21:28:42 -0000 1.13.2.2 @@ -116,4 +116,322 @@ <para>Use the &appname;a command <link linkend="app-a-command-deletestyle"><command moreinfo="none">deletestyle</command></link> to remove one or more bibliography styles from the database. The argument for this command is a Unix regular expression. All styles whose name match the regular expression will be deleted.</para> </sect1> + <sect1> + <title>Setting up the &appname; web services</title> + <para>This section guides you through the necessary steps to run &appname;c, bib2ris, and med2ris.pl as <acronym>CGI</acronym> applications. This will allow the users to enjoy a part of the functionality of &appname; through a web interface.</para> + <para>If you want to work through this section you'll need some basic knowledge about the administration of your web server. Needless to say that you also need the proper privileges to fiddle with your web server settings. The procedure below was written with <ulink url="http://www.apache.org">Apache</ulink> 1.3 on Debian GNU/Linux in mind. Apache is by far the most popular web server and available on various platforms, including all platforms that &appname; currently supports. If you use a different Linux distribution or a different operating system, the location and name of the files may slightly differ. If you use a different web server, the configuration process may be entirely different, but with the user manual at your hands you may be able to adapt the following instructions to your needs.</para> + <note> + <para>If your web server and the &appname;d application server run on different machines, please notice that all but one steps below talk about the computer running the web server. One step talks about the computer running &appname;d.</para> + </note> + <procedure> + <step performance="required"> + <para>To tell Apache about the &appname; web pages, add the following line to <filename>/etc/apache/httpd.conf</filename>:</para> + <programlisting format="linespecific"> +Alias /refdb/ /usr/local/share/refdb/www/ +</programlisting> + <para>This entry will let you access the &appname; web interface through the address [hostname]/refdb. While you're at modifying <filename moreinfo="none">httpd.conf</filename>, the next step may require another change to this file.</para> + </step> + <step performance="required"> + <para>Most web servers expect CGI applications in one specific, configurable directory. If your web server is not already set up for CGI applications, you`ll have to register a cgi-bin directory. To do this in the case of Apache, add the following line to <filename>/etc/apache/httpd.conf</filename>:</para> + <programlisting> +ScriptAlias /cgi-bin/ /usr/local/bin/apache/cgi-bin/ +</programlisting> + <para>You can of course choose a different directory if you wish.</para> + <para>The directory must be readable and accessible for the account that the web server daemon runs in (this is often user "www" and group "www", which I will use in the example below). If this is not already the case, issue something like the following commands:</para> + <screen format="linespecific"><prompt moreinfo="none">#~ </prompt><userinput moreinfo="none">chown www:www /usr/local/bin/apache/cgi-bin</userinput></screen> + <screen><prompt>#~ </prompt><userinput>chmod u+rx /usr/local/bin/apache/cgi-bin</userinput></screen> + <para>Now you have to tell Apache about the updated configuration:</para> + <screen><prompt>#~ </prompt><userinput>apachectl restart</userinput></screen> + </step> + <step performance="required"> + <para>Place copies of <filename>&appname;c</filename>, <filename>bib2ris</filename>, and <filename>med2ris.pl</filename> in your <filename class="directory">/cgi-bin</filename> directory. Unless they are readable and executable for everyone you'll have to make them read/executable for the web server daemon:</para> + <screen format="linespecific"><prompt moreinfo="none">#~ </prompt><userinput moreinfo="none">cd /usr/local/bin/apache/cgi-bin/</userinput></screen> + <screen format="linespecific"><prompt moreinfo="none">#~ </prompt><userinput moreinfo="none">chown www:www &appname;c bib2ris med2ris.pl</userinput></screen> + <screen><prompt>#~ </prompt><userinput>chmod u+rx &appname;c bib2ris med2ris.pl</userinput></screen> + </step> + <step performance="required"> + <para>Create the <link linkend="sect1-mystery-init-files">configuration files</link> <filename>/usr/local/etc/&appname;/&appname;cgirc</filename>, <filename>/usr/local/etc/&appname;/bib2riscgirc</filename>, and <filename>/usr/local/etc/&appname;/med2riscgirc</filename> (unless you chose a different directory during configuration) and fill in appropriate values. Remember that bib2ris and med2ris need access to HTML templates. You should specify the proper value for &appname;lib in the configuration files.</para> + </step> + <step> + <para>You can of course <link linkend="ch-customize-web">modify the HTML files and the stylesheet</link> according to your needs. The static HTML files, a CSS stylesheet file, and a JavaScript file are installed by default in <filename class="directory">/usr/local/share/refdb/www</filename>, whereas the HTML templates are installed in <filename class="directory">/usr/local/share/refdb/templates</filename> <emphasis>on the computer that runs &appname;d</emphasis>. Both the computer that runs Apache and the CGI programs and the computer that runs &appname;d need a copy of <filename class="directory">/usr/local/share/refdb/templates</filename>.</para> + </step> + <step> + <para>The file <filename>refdbquery.html</filename> is the main entry point to the &appname; web interface. Web visitors should be guided to this page as it allows username/password authentication. The &appname; installation procedure creates a symlink with the name <filename moreinfo="none">index.html</filename> pointing to <filename>refdbquery.html</filename>, so you'll be able to access the main query page by pointing your browser to "[hostname]/refdb/".Provide links on your web pages accordingly.</para> + </step> + </procedure> + <para>It may be a good idea to check the access rights of all related files again to make sure the site visitors can access them from their browser. The static HTML pages, the templates, the javascript file, and the CSS style sheet must be readable for the account the web server is started under. The templates must be readable for the account &appname;d is started under.</para> + </sect1> + <sect1> + <title>Logging data</title> + <para>The &appname; programs can spill out quite a lot of log messages to keep track of what is happening in your programs. This section explains the basics of setting up your message logging.</para> + <sect2> + <title>What to log</title> + <para>The application server &appname;d as well as all command-line clients can generate log messages. Message logging is most important for two purposes:</para> + <itemizedlist> + <listitem> + <para>Keep track of non-interactive programs. This includes &appname;d as well as &appname;c, bib2ris, and nmed2ris if they are run as CGI applications. It may include all clients if they are run from scripts.</para> + </listitem> + <listitem> + <para>Track down bugs or user errors.</para> + </listitem> + </itemizedlist> + <para>A useful approach is to log all messages with a log level (explained <link linkend="sect2-log-level">below</link>) of 6. This would give you a good overview over the usage of these programs but would not clutter the log files with debug information. Switch to log level 7 only if you suspect a bug or some user error and need the full debug information to understand the problem.</para> + <para>For the interactive use of the clients logging is usually not necessary, so you'd use a log level of -1 to prevent logging altogether or a log level of maybe 3 or 4. In the latter case you'd get log messages only if something goes badly wrong. Again, if you encounter bugs or user errors you may switch on debug messages by using a log level of 7.</para> + </sect2> + <sect2> + <title>Destinations</title> + <para>There are three possible destinations the log messages can be sent to. Select the proper destination with either the <varname>logdest</varname> variable in the configuration file or the <option>-e</option> switch on the command line. In both cases the values in the following list are accepted. You may use either the numerical value or the case-insensitive string in brackets, e.g. <option>-e 1</option> and <option>-e syslog</option> are equivalent.</para> + <variablelist> + <varlistentry> + <term>0 (stderr)</term> + <listitem> + <para>stderr is mostly useful for debugging purposes when &appname;d is run as a standalone process and when clients are run interactively. stderr does not make much sense if you run &appname;d as a daemon (daemons detach from the console at startup, so all output to stderr is lost).</para> + </listitem> + </varlistentry> + <varlistentry> + <term>1 (syslog)</term> + <listitem> + <para>Sending the data to syslog integrates the log data with the rest of your system's log output. The log messages will be sent to the user facility, which usually is configured to write to <filename>/var/log/user.log</filename>. See the syslog(8) man page for information how to configure the syslog facility.</para> + <note> + <para>If you run &appname;d on Cygwin, the syslog messages are sent to the application message list in the NT message logging system. If you are used to going through your log output with tools like grep and awk, you may find it more useful to write to a custom log file instead.</para> + </note> + </listitem> + </varlistentry> + <varlistentry> + <term>2 (file)</term> + <listitem> + <para>You can define the full path of a custom log file with either the <varname>logfile</varname> configuration file parameter or the <option>-L</option> command line option. By default, &appname; applications write their log output to <filename>/var/log/<appname>.log</filename>. Make sure to set the appropriate access rights for these log files.</para> + </listitem> + </varlistentry> + </variablelist> + <note> + <para>Some libraries used by &appname;, e.g. the PostgreSQL client library, send log messages to stderr. This is not controlled by the log settings of &appname;d. The same PostgreSQL log messages show up in the PostgreSQL log which is usually sent to <filename moreinfo="none">/var/log/pgsql</filename>.</para> + </note> + </sect2> + <sect2 id="sect2-log-level"> + <title>Log levels</title> + <para>You can select how verbose the log output of &appname;d will be. You can do this by either setting the <varname>loglevel</varname> configuration file variable or the <option>-l</option> command line option to an appropriate value. You may either use the numerical value or the case-insensitive string as explained in the table below. E.g. <option>-l 5</option> and <option>-l notice</option> are equivalent. Set the log level to -1 to disable logging completely. Use a value from 0 through 7 to generate increasingly verbose log output. The definitions of the log levels are taken from the include file <filename>syslog.h</filename>:</para> + <table id="table-loglevel-definitions"> + <title>Log level definitions</title> + <tgroup cols="3"> + <thead> + <row> + <entry>level</entry> + <entry>verbose</entry> + <entry>explanation</entry> + </row> + </thead> + <tbody> + <row> + <entry>0</entry> + <entry>emerg</entry> + <entry>system is unusable</entry> + </row> + <row> + <entry>1</entry> + <entry>alert</entry> + <entry>action must be taken immediately</entry> + </row> + <row> + <entry>2</entry> + <entry>crit</entry> + <entry>the system is in a critical condition</entry> + </row> + <row> + <entry>3</entry> + <entry>err</entry> + <entry>there is an error condition</entry> + </row> + <row> + <entry>4</entry> + <entry>warning</entry> + <entry>there is a warning condition</entry> + </row> + <row> + <entry>5</entry> + <entry>notice</entry> + <entry>a normal but significant condition</entry> + </row> + <row> + <entry>6</entry> + <entry>info</entry> + <entry>a purely informational message</entry> + </row> + <row> + <entry>7</entry> + <entry>debug</entry> + <entry>messages generated to debug the application</entry> + </row> + </tbody> + </tgroup> + </table> + <para>Setting the log level to a given value means that all messages with a priority level up to the given value will be logged. E.g. if you set the log level to 6 (which is a reasonable default value), all messages with a priority from 0 through 6 will be logged, whereas messages with a priority level of 7 will be ignored.</para> + <warning> + <para>Use log level 7 with caution. The amount of log messages is considerable and sufficient to slow down the application. You should not use this level in everyday use, only to track down bugs or user errors that you may encounter.</para> + </warning> + </sect2> + <sect2> + <title>Interpreting the log information</title> + <para>If the messages are sent to stderr, only the message proper will be printed. If the messages are sent to the syslog facility, the default format including the process name and process ID is used.</para> + <para>A line in the custom log file looks like this:</para> + <programlisting>6:pid=267:Sun Jul 22 18:39:52 2001:application server started</programlisting> + <para>You will easily recognize the following fields:</para> + <programlisting>message_priority:process_id:time:message</programlisting> + <variablelist> + <varlistentry> + <term>message priority</term> + <listitem> + <para>This is the priority assigned to the message by &appname;d. The values are explained <link linkend="table-loglevel-definitions">above</link>.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>process ID</term> + <listitem> + <para>This is the process ID (as seen in the <command>ps ax</command> listing) of the &appname; process that generated the message. In the case of &appname;d this may either be the parent process (the one that generated the above "application server started" message) or one of the children that are forked off to answer client requests.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>time</term> + <listitem> + <para>This is the full time and date information when the message was generated.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>message</term> + <listitem> + <para>This is the message text proper.</para> + </listitem> + </varlistentry> + </variablelist> + <para>The message entries are sufficiently structured to allow easy access to the information with the standard Unix tools like <application>awk</application> and <application>grep</application>.</para> + </sect2> + </sect1> + <sect1> + <title>Security issues</title> + <para>This section briefly discusses some security-related issues that you might want to think about as an administrator. We'll look at the access control provided by the external database servers MySQL and PostgreSQL.</para> + <note> + <para>The embedded database engine SQLite does not provide built-in access control. All you can do is use <command moreinfo="none">chown</command> and <command moreinfo="none">chmod</command> to restrict access to the database files. There is no way to restrict access through &appname;.</para> + </note> + <sect2> + <title>Passwords</title> + <para>&appname; tries to support the security features of the SQL database servers as far as possible. This includes the username/password-based access rights scheme (not much surprise here). Since version 0.6.0 the passwords are no longer transmitted as plain text between the clients and the server. This means that it now makes sense to keep the passwords secret. There are several ways to specify the password when starting a &appname; client. These ways differ with respect to the security of the passwords and are listed here in the order of <emphasis>increasing</emphasis> security:</para> + <variablelist> + <varlistentry> + <term>Specify the password on the command line</term> + <listitem> + <para>The password is stored nowhere on the filesystem and thus pretty secure from this point of view. But the full command line can be viewed with the <command moreinfo="none">ps</command> command by any user on the system, so the unencrypted password is basically world-readable at least for a very brief period until the applications have a chance to hide the string.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>Store the password in the personal configuration file</term> + <listitem> + <para>This way the password is protected from other users who habitually run the <command moreinfo="none">ps</command> command just for the heck of it. But now it is stored unencrypted on the hard drive, and you must make sure that no one else can read the configuration file (no group or world read access).</para> + </listitem> + </varlistentry> + <varlistentry> + <term>Specify the password interactively</term> + <listitem> + <para>This is the default behaviour if the password is not specified either in the configuration file or on the command line. The &appname; client will ask for the password. This is certainly the most secure way to provide a password, but this won't work if you run the clients unattended via scripts.</para> + </listitem> + </varlistentry> + </variablelist> + </sect2> + <sect2 id="sect-database-server-access-control"> + <title>Database server access control</title> + <para>It is beyond the scope of this manual to reiterate the security models of the database servers, but you need to keep in mind a few aspects relevant to &appname;.</para> + <itemizedlist> + <listitem> + <para>One component of the database server access control is based on the host from which you connect to the database server. This is partially circumvented by the &appname; three-tier design. Keep in mind that only &appname;d communicates with the database server. Therefore only the host where &appname;d runs is relevant for the access control. There is currently no system in place for checking whether a client is allowed to connect to the &appname;d application server from a particular host.</para> + </listitem> + <listitem> + <para>Both MySQL and PostgreSQL distinguish between local and remote connections. Access needs to be granted separately if you want to use both local and remote connections</para> + <note> + <para>On many operating systems the default installations of MySQL and PostreSQL do not allow remote connections for security reasons. You need to manually allow remote connections as described below.</para> + </note> + </listitem> + <listitem> + <para>The &appname;a commands to remotely reconfigure a running application server are currently protected by a simple table access test. In any serious database server installation, only the database administators have read access to certain system tables. The current implementation of this check requires that you have access to this table if you want to run the <link linkend="app-admin-command-confserv"><command moreinfo="none">confserv</command></link> commands. You should be aware that if the access rights are set up improperly, you may also allow everyone and their grandma to stop or reconfigure the &appname;d application server. If you cannot restrict read access to system tables for whatever reason, you should not enable &appname;d remote administration (d... [truncated message content] |
|
From: Markus H. <mho...@us...> - 2004-11-14 16:25:18
|
Update of /cvsroot/refdb/refdb/src In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv29437 Modified Files: Tag: Release_0_9_5_stable refdbdref.c Log Message: added wishlist for next release Index: refdbdref.c =================================================================== RCS file: /cvsroot/refdb/refdb/src/refdbdref.c,v retrieving revision 1.65.2.3 retrieving revision 1.65.2.4 diff -u -U2 -r1.65.2.3 -r1.65.2.4 --- refdbdref.c 30 Jul 2004 21:34:54 -0000 1.65.2.3 +++ refdbdref.c 14 Nov 2004 16:25:09 -0000 1.65.2.4 @@ -20,4 +20,24 @@ ++++++++++++++++++++++++*/ +/* ToDo: duplicate check. Could work like this: + new command checkref sends datasets like addref/updateref + but adds the refs to a temporary database + refdbd then checks + - fuzzy title search + - JO,PY,VL,IS,SP + - fuzzy author search + - fuzzy journal name search + + Output is a screen or html report of possible duplicate references, + possible duplicate author names, and possible journal name duplicates +*/ + +/* ToDo: implement updatejo command. Could work like this: + use four parameters or arguments, like in + updatejo -a abbrev -f full -1 custabbrev1 -2 custabbrev2 + refdbd tries to match the data to an existing entry from left to right + and updates the other fields +*/ + #include <stdio.h> #include <unistd.h> |
|
From: Markus H. <mho...@us...> - 2004-11-14 16:22:58
|
Update of /cvsroot/refdb/refdb/doc In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv28912 Modified Files: Tag: Release_0_9_5_stable refdbmanualfig1.eps refdbmanualfig1.pdf refdbmanualfig1.png refdbmanualfig4.eps refdbmanualfig4.pdf refdbmanualfig4.png Log Message: updated for 0.9.5 Index: refdbmanualfig1.eps =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdbmanualfig1.eps,v retrieving revision 1.1.1.1 retrieving revision 1.1.1.1.4.1 diff -u -U2 -r1.1.1.1 -r1.1.1.1.4.1 Binary files /tmp/cvscw26J4 and /tmp/cvsRWW5W2 differ Index: refdbmanualfig1.pdf =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdbmanualfig1.pdf,v retrieving revision 1.2 retrieving revision 1.2.4.1 diff -u -U2 -r1.2 -r1.2.4.1 Binary files /tmp/cvsJ4iGsb and /tmp/cvsFhb0J9 differ Index: refdbmanualfig1.png =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdbmanualfig1.png,v retrieving revision 1.1.1.1 retrieving revision 1.1.1.1.4.1 diff -u -U2 -r1.1.1.1 -r1.1.1.1.4.1 Binary files /tmp/cvsxrqoUf and /tmp/cvsQjByee differ Index: refdbmanualfig4.eps =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdbmanualfig4.eps,v retrieving revision 1.1.1.1 retrieving revision 1.1.1.1.4.1 diff -u -U2 -r1.1.1.1 -r1.1.1.1.4.1 Binary files /tmp/cvs7A9FU9 and /tmp/cvsR03mh8 differ Index: refdbmanualfig4.pdf =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdbmanualfig4.pdf,v retrieving revision 1.2 retrieving revision 1.2.4.1 diff -u -U2 -r1.2 -r1.2.4.1 Binary files /tmp/cvsX731Ym and /tmp/cvspzvCvl differ Index: refdbmanualfig4.png =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdbmanualfig4.png,v retrieving revision 1.1.1.1 retrieving revision 1.1.1.1.4.1 diff -u -U2 -r1.1.1.1 -r1.1.1.1.4.1 Binary files /tmp/cvsuSJNMC and /tmp/cvsn5IysB differ |
|
From: Markus H. <mho...@us...> - 2004-11-14 16:20:29
|
Update of /cvsroot/refdb/refdb/doc In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv28537 Added Files: Tag: Release_0_9_5_stable refdbmanualfig4.sxd Log Message: replaces refdbmanualfig4.fig --- NEW FILE --- PK f³z æ 8´ |'Ëz½Jßé0nÌF%̶V óËVY¢cï´ô!öE h ZµG+ fóÞ ½|±e8D>"Ø¡&á(ZqìÐïÌÒ±üËMáïTy}h³Æ¦²fì»´%ÑéýVÙ*\¬²C w¯ÖÛòßí^è3lº¥9Ó§áá(ü5íÛ°*à¡)òÒéO<ŵ¤µÓ/±¼&]"Û\ ÿþó÷{h»4ä»q?È'éç× f"Ls*&-.Ýøsiúõ \0 ¡CgBt£CµÉr÷Y6Á>]m]¶J;Ï_+¯ ó ¥æð Þ 9è\MÝÊ%T¾±Ìäêÿd:iæºN¦jnè´â õSªTª½¡^·VUbRß0¯ §äeYNuÒ¬ 3qoK²I;í~ɦ²K&y)KA<B$ ç8¸%ã@C¤V ÑÚ @)ÿùpVÅŽ Ò?´ ¹21uá4JLyé'Ç" O ò [][! ªôiD!8Ë!GBz$ zºQJ³_.H Ã?âµñ'Q¢¦~reo-qñç&v p î 1¢JI?*#ß $ÞDdJ9Z'RàÓ<á °\·=e%èYî <0WI9L_ÌTØ]ÍÍÿþý§Ûmæ÷9ô¢óxA£;V3g'¯Ä¾ÄîCº Þ~HCù}e-0lâ°hH¢=HM,zZÀÓÊ>zX´gëþx?÷Ý÷¢ÝìëþôE»°ûÞhò¢Ý?ÜÏýñvþõοðÆ7ÝÏýÉ o|³}ÝÙÏuöóÿàyv¾ºØÏu³Û[X-]|Á>_QGGíäVótÄÊóVk?ÿ ¹»Ràò¨« ¿î'Ç*þ½ÜØÞ=F=H vE2"yÈëïp(®8 xÕ¹d>w¦ß .Û Þ7q£×¸ÀVwý%Ï`µq÷1ØÂWÇY«HHx³» ÐÚÓ8pÇ3«Ç¢ìÝT÷9d~ ó Èü@æ2?ùÌd¾Øà^{?õT¼b2ÙWÌî£îyÞ-ïF·½>º½¥lyÝö¦¶NtÔÅ!õî9¤mÇ6ÎAé]#aèû³Ù£Ç±ÉÔmvµ)WwFnÇRQ[¥ña÷*=)só{ ÛÀÜæ60·¹ Ìm`nsÚy¯0 ĵ¾'})Qì'^×VØkÙ {;±=íçã¾{qÔÖ/Ñ껯_Áîîß79{ ÷ÛîäÇß7*1FYÎ 4÷ë×kõ¬® ´k\ ¨Fõ¼õÚjÇÞø©OñQü"FøVè°,±£ Èg#ª?8 tëiÐbE©Û µJ ûÞlôÚqë }]ÙsF³é¬ºj2á T¿ `M3 ¥õwê5'o÷Û½ßð1>èÊÿÃÃ6ÿ[Æ Õz ÜñÈs¦mqî' ÛÕ¤[͵øÑ %ÆwÊù_æÄ*;Ýá¦Ý¡ BA.¥rÂÝø >×ÊËòh×Wxïb£n«dݦ>%£QEѦDÿVö¦ *( ³"Öu9U?3ªºY¹V¸ºkU-N,§]Åx#vû/aOþPKè7P <!DOCTYPE office:document-meta PUBLIC "-//OpenOffice.org//DTD OfficeDocument 1.0//EN" "office.dtd"><office:document-meta xmlns:office="http://openoffice.org/2000/office" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:meta="http://openoffice.org/2000/meta" xmlns:presentation="http://openoffice.org/2000/presentation" office:version="1.0"><office:meta><meta:generator>OpenOffice.org 1.1.1 (Linux)</meta:generator><!--645(Build:8762)--><meta:initial-creator>Markus Hoenicka</meta:initial-creator><meta:creation-date>2004-11-13T17:08:07</meta:creation-date><dc:date>2004-11-14T02:25:10</dc:date><dc:language>en-US</dc:language><meta:editing-cycles>10</meta:editing-cycles><meta:editing-duration>PT2H25M28S</meta:editing-duration><meta:user-defined meta:name="Info 1"/><meta:user-defined meta:name="Info 2"/><meta:user-defined meta:name="Info 3"/><meta:user-defined meta:name="Info 4"/><meta:document-statistic meta:object-count="28"/></office:meta></office:document-meta>PK 6Áâ£Ã[,ÕV£ èØÁ¦@¢!#Tm=uCÚ ]¦W:²r:ì®ØæÒ±E«ýè yø@ ou%_5óÓã³|² à¿"Mù~,ù1ÔÙRyOÇX¶-bñÃ~Ä5ÄU_¨(¼'ç+ÓÉi7"Ê£!)pW¤G¡Ï çUdz£ÔßdÚÄÁþd b-1>%hÌ¡+¶Î¿|9Á!âW,ÎÞäÃÜqqÎâ!GIÖ¥i2¡kÃß0õÄg $ßð]FRWÈà ;R hÀ7 <9p =`rËP¾71AeW «ÿiY÷é²+gYw¿i0ÀÚ-}å{NÅ¿¿#{!ô¶2Ï;8*¼[êBÐIU±[ÛVÞdx ý® c§bOQ8ëSͤ(K3ûl½gÛa ·zÖÑi5дhR èè$è¶)cÁ%ÍH=?T3n¾n9íz¼êbeH~®W¹¼x°ýNÓÒC² Ä@¯Ï$êXªEºÉ1_õv4Ôî0A'ªÐ³ ¥FÈr?þKLJËGGHç®%_ãɪØ6CcÕË [ÁÈI>fwM¸ºæ¡'¯Ætf o«ug94ÿýà¡®çÑ8ÛËÇg%æ°´´)^ÕêPKZÕý |
|
From: Markus H. <mho...@us...> - 2004-11-14 16:19:32
|
Update of /cvsroot/refdb/refdb/doc In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv28309 Removed Files: Tag: Release_0_9_5_stable refdbmanualfig4.fig Log Message: replaced by refdbmanualfig4.sxd --- refdbmanualfig4.fig DELETED --- |
|
From: Markus H. <mho...@us...> - 2004-11-14 16:15:14
|
Update of /cvsroot/refdb/refdb/doc In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv27413 Added Files: Tag: Release_0_9_5_stable refdbmanualfig1.sxd Log Message: replaces refdbmanualfig1.fig --- NEW FILE --- PK n1å3и n1 ØGÝïAâ¢Û´Àé&@R ûHK´Lºí¸?±ûû% RK¾È l'öKlÏçÌphëÏ æ$KodCÕe §a4¾¿=}Q|ùÃè·ëßoï?=ýóðYÊ&â«( g NK%ÌÒ^¥oÞýõIM»Ïqz/`jÆbM»}ºªñmí%Á>öùoY«õÔ¨äÑõ®ÅcZ\U³7ò´,ó+MË`lµ©ëºVåÚ¡(t/ ¼ÄÏå Z0ïY[ xÄÐbÍó?ÉZôb±P@Ahß ï´/KPËåôÇN¼m é,c6̨á²JqD<»À6óx³*úóVo8El8ø± §í §5`ÔtGt|í+L?_ïV±gÉàâ Ðê ÉW¹)¢¢¸Û×æ^ ¶¥PùjíÍÊ ôP)*F×âµ:êRõ>E Ì(7äÚ0A ¡ËvK%G1µÝ®1Ûpʧ$,{/P1P*¯¢Di¯ãà ¬$¸ø΢¾À )ÓPÚ*4°fònνÃ*!QDsC}Hy b?0 qd?2-äÍeA"~îtÕ þ<N£~`ßæõæq{ØH? Ðm Ê$ãb*O ":g¾22O;ÖIÆãM~Â>ÎËlùº¤ÆLÒ,ÿËl$~A«dÑv Õã3Â!Y¢è!rR¸9_qñ¿\ëËeY¯uÈnOÇ@| xBýq=w'hFùC¯ n1 m¼F¥è J9Mb$2ñ0d ^ ã4ry*;±õLO@@"lÌFпP`[3¡!!¬ÈLÁçEBk T¦q nn&m!ª%}>´Zª´"1Oß¡.de^z+& ñT *'Zå5qV7¿Xò®Uj @B{+bè¶Þ ö*Ú·× päu Ú¦Á> ÂBRA:ø~¦IZ Y,·¥ [²9åù*<ÜÈ*yMS.³UEå2$"/Á&¯×oJ¦¶;ØR,ç˶U½iäa¦ü¬û±Æ*ÈùL¯ÜBKçÊN¹Laî0xöfZYém@[LäÂà:¨ZáïýÊɺÌV̶¬7º&&9ÁÀn¨ ÜË«d>;ê$Eg,^á sbæj2)é³¹Ê[²þß¿ÿ4µÈÍ¢¸vu Îið¨j¬'úèèØÌ]HwðÃÙÁi(¿ä9 ]l,zÔ¢Q¡9<h¾ã¬ý°î÷sß 8íþh_÷'íþÑ~î;ÑA»?ÞÏýáA;¼§óÞø&û¹?:ðÆ7Ý×ýÃn|¶µÿG?f竨³ý\;%~ ÓùWìò5áuÞÔÌsrXqHkléï'ÍûhWÞ\u0êãnFâßI¨ÍÝè¸×³Ä1cu+ÉQ ËÀÅÂsø¬+$óy40ufÿ|y¬xØ^ðæÔ»y½Æ Ýö×4ÕÆíggÏ _Ad_ !þýî.@+h¯ãÀ#º^²ïJufGDh\|þ( ? èú£þ( ? èú£þ( Û ^yóõZ¬d4ÚÌöîxs®^gïFÖ.²¾¥lxuÞôr¸JÔqÇ!u8¤M>ÖQá]-¾ïºÓéDZÎÌÔmn¶)W×vËEBQY¥á¸}^÷9?zï[ÏÜzæÖ3·¹õÌgn=sëÚy/1òÄ¥ÀW}¥íGNÛVØiØ ;;±½ÜÏ%|Oâ¨=©ÞÛͯÛB~y»»ÿÔäì%Üoº¶L8 wߨ%){ÖܯRþ]/!Ô³¼dÐ8®vù ÕñþÖiª sã×EÙGñ»qâ¹"Ë!J|Ö¢úåÒj¹â[M Ø+JÝL¨s©Ä¹ïLÇ]Uä k0LËÛý1#ÊHùcµ ¹Ê t/Dâ;´ü\ýå h*K£Y_â}ºç´ºP Y½[Z~¨ dÎX×Öå\ýª©ìdÅZeÒæ «lob9Í2Æ¡4x{ö?PK¨ÀÒ n1fÝ+{à <!DOCTYPE office:document-meta PUBLIC "-//OpenOffice.org//DTD OfficeDocument 1.0//EN" "office.dtd"><office:document-meta xmlns:office="http://openoffice.org/2000/office" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:meta="http://openoffice.org/2000/meta" xmlns:presentation="http://openoffice.org/2000/presentation" office:version="1.0"><office:meta><meta:generator>OpenOffice.org 1.1.1 (Linux)</meta:generator><!--645(Build:8762)--><meta:creation-date>2004-11-13T22:50:39</meta:creation-date><dc:date>2004-11-14T02:23:00</dc:date><dc:language>en-US</dc:language><meta:editing-cycles>7</meta:editing-cycles><meta:editing-duration>PT3H32M23S</meta:editing-duration><meta:user-defined meta:name="Info 1"/><meta:user-defined meta:name="Info 2"/><meta:user-defined meta:name="Info 3"/><meta:user-defined meta:name="Info 4"/><meta:document-statistic meta:object-count="21"/></office:meta></office:document-meta>PK n1 ÑpÈ/ yú;*6pHÓ}ûu!Snâ£úRFáÝ8¹¤LºNN¿± 'ôbð/îñÄÔSsx5ÐbsP*oÑPnb#÷ÁO¢í!%1>!h.YÀkºÍ¿|9F ä#È®i¾ÉG¹ãâF#ã$GdBÕ¿a ,¯ÅÆ#[B4`»DÆ^¸ R±ç(_» Ó+ÂÕËÿ´¬û¦¸¬;Ì_Í4)` fK_ýÓ^^Àß½zGºg¦àßòÖÒ[äl© AÇUE¶¶¼Éðú ]ÆNÄ C 2 (S§Y döé,zÏ ·ÿÂ:nÕ¬£Çj*¦i¸PÑ-ÑmsJý+z~"¨¦Ü|ÝrÊz¼éb¥àP|®W¹¾Y°ýNÓÒ ¼pÈZ@¯Ï$HÈEÚ±L®û µ;á©,ôÔºØCÈõ&¯^9z( ÜÈ óMbrÀ©O0â2 ë Ö¤~Ür»Å¶êKK¤°S¹x7\-À*Åòrï@ ÌéÖïDäì q2y $ÏFP¼cÜSR²nÔ I^ cþ Ô3s ½ ñõí\ ÷Os#´÷îü¢éÇxH©ôE¾Í¹ nxdN£=®ÖB¯;=Jd Óï-`¨¦@¿ÛÂÉ < <ìe:áÛÐp¾ÀÙiÐ÷~'¥gýd¬þPK@¿ä: n1 ¥FÈr?þKLJËGGHç®%_ãɪØ6CcÕË [ÁÈI>fwM¸ºæ¡'¯Ætf o«ug94ÿýà¡®çÑ8ÛËÇg%æ°´´)^ÕêPKZÕý n1å3и n1,®äýÊ n1¨ÀÒ n1fÝ+{à n1@¿ä: n1ZÕý |
|
From: Markus H. <mho...@us...> - 2004-11-14 16:12:22
|
Update of /cvsroot/refdb/refdb/doc In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv26857 Removed Files: Tag: Release_0_9_5_stable refdbmanualfig1.fig Log Message: replaced by refdbmanualfig1.sxd --- refdbmanualfig1.fig DELETED --- |
Update of /cvsroot/refdb/refdb/doc In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv25085 Modified Files: Tag: Release_0_9_5_stable refdb-manual-chapter1.sgml refdb-manual-chapter10.sgml refdb-manual-chapter12.sgml refdb-manual-chapter13.sgml refdb-manual-chapter14.sgml refdb-manual-chapter15.sgml refdb-manual-chapter2.sgml refdb-manual-chapter3.sgml refdb-manual-chapter4.sgml refdb-manual-chapter5.sgml refdb-manual-chapter6.sgml refdb-manual-chapter7.sgml refdb-manual-chapter8.sgml refdb-manual-chapter9.sgml refdb-manual-configopts.sgml refdb-manual.sgml Log Message: updated for 0.9.5 Index: refdb-manual-chapter1.sgml =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdb-manual-chapter1.sgml,v retrieving revision 1.12 retrieving revision 1.12.2.1 diff -u -U2 -r1.12 -r1.12.2.1 --- refdb-manual-chapter1.sgml 8 Feb 2004 00:32:45 -0000 1.12 +++ refdb-manual-chapter1.sgml 14 Nov 2004 16:04:49 -0000 1.12.2.1 @@ -1,7 +1,7 @@ -<!DOCTYPE CHAPTER PUBLIC "-//OASIS//DTD DocBook V3.1//EN" [ +<!DOCTYPE CHAPTER PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [ <!ENTITY appname "refdb"> ]> <!-- $Id$ --> -<chapter> +<chapter id="chapter-introduction"> <title>Introduction</title> <sect1> @@ -32,5 +32,5 @@ <figure float="0" id="figure-threetier"> <title>&appname; three-tier architecture</title> - <graphic fileref="refdbmanualfig1"></graphic> + <graphic fileref="refdbmanualfig1"> </figure> <para>Optionally you may use an internal database engine instead of the external SQL server, resulting in a simpler two-tier setup.</para> @@ -40,5 +40,5 @@ </listitem> <listitem> - <para>The server can run as a daemon in a non-privileged account if security concerns require this. Besides, users can start it as a standalone application on demand.</para> + <para>The server can run as a daemon in a non-privileged account if security concerns require this. Besides, users can start it as a standalone application on demand. As just about everything is configurable, a thoughtful setup will allow to run several copies of the server on the same box in parallel.</para> </listitem> <listitem> @@ -95,5 +95,5 @@ <itemizedlist> <listitem> - <para>Bibliographic output for DocBook works with both the SGML and XML version of the DTD. The DocBook output is sufficiently structured to allow transformation into other SGML or XML document types (this is in fact the way how the TEI bibliographies are created currently). DocBook SGML and XML documents can be transformed with DSSSL stylesheets which act as driver files for the well-known modular stylesheets by Norm Walsh. DocBook XML documents can also be transformed with XSL stylesheets which again are driver files for the corresponding stylesheets by Norm Walsh.</para> + <para>Bibliographic output for DocBook works with both the SGML and XML version of the DTD. The DocBook output is sufficiently structured to allow transformation into other SGML or XML document types (this is in fact the way how the TEI bibliographies are created currently). DocBook SGML and XML documents can be transformed with DSSSL and XSL stylesheets, respectively, which act as driver files for the well-known modular stylesheets by Norm Walsh.</para> <para>The TEI camp has apparently completely switched from SGML to XML, so RefDB supports only XML documents and transformation with XSL stylesheets.</para> </listitem> Index: refdb-manual-chapter10.sgml =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdb-manual-chapter10.sgml,v retrieving revision 1.19 retrieving revision 1.19.2.1 diff -u -U2 -r1.19 -r1.19.2.1 --- refdb-manual-chapter10.sgml 8 Feb 2004 00:32:45 -0000 1.19 +++ refdb-manual-chapter10.sgml 14 Nov 2004 16:04:49 -0000 1.19.2.1 @@ -84,5 +84,5 @@ <para>Use the <option>-d</option> option to specify the database that you want to work with. In an interactive session you can also set and change the default database with the <link linkend="app-c-command-selectdb"><command>selectdb</command> command</link>.</para> <para>The <option>-F</option> option specifies the default fields that are to be displayed in a <link linkend="app-c-command-getref"><command moreinfo="none">getref</command></link> query.</para> - <para>The <option>-g</option> option can be used to add some default fields to all references that are added or updated. The argument <replaceable>deffile</replaceable> is the filename of a <link linkend="sect1-ris-format">RIS file</link> containing these additional fields. &appname;c first tries the filename as is, so it should be a valid relative or absolute path. If the file is not found, &appname; looks for the file in <filename><envar>$HOME</envar>/</filename>. The command aborts if the file cannot be found.</para> + <para>The <option>-g</option> option can be used to add some default fields to all references that are added or updated. The argument <replaceable>deffile</replaceable> is the filename of a <link linkend="sect1-ris-format">RIS file</link> containing these additional fields. &appname;c first tries the filename as is, so it should be a valid relative or absolute path. If the file is not found, &appname; looks for the file in <envar>$HOME</envar>. The command aborts if the file cannot be found.</para> <para>Use the <option>-G</option> option to specify the URL of a Cascading Style Sheets (CSS) file. This file will be used to customize the HTML output of the <link linkend="app-c-command-getref"><command>getref</command></link> command. The URL can be either a local path (e.g. <filename>refdb.css</filename>, <filename>/home/myname/custom.css</filename>) or the web address of a file on a web server (e.g. <filename>http://www.mycomp.com/refdb.css</filename>).</para> <para>The <option>-R</option> option specifies the root path of your collection of electronic offprints. See the information about <link linkend="sect1-pdfroot">pdfroot</link> for further details.</para> @@ -370,5 +370,5 @@ <para>Select an input character encoding with the <option>-E</option> option if it is different from the default UTF-8. RIS datasets can use any encoding that your local libiconv supports (see <command moreinfo="none">man iconv_open</command> for a list of available encodings), except UTF-16 and UTF-32. RISX datasets carry the encoding in the processing instructions, therefore this option is ignored.</para> <para>You can use two different input file formats with this command. The default format is the <link linkend="sect1-ris-format">tagged RIS format</link>. Use <option>-t risx</option> to use XML files according to the RISX DTD as input data.</para> - <para>The <option>-g</option> option can be used in conjunction with RIS data to add some default fields to all references that are added with this command. The argument <replaceable>deffile</replaceable> is the filename of a <link linkend="sect1-ris-format">RIS file</link> containing these additional fields. &appname;c first tries the filename as is, so it should be a valid relative or absolute path. If the file is not found, &appname; looks for the file in <filename><envar>$HOME</envar>/</filename>. The command aborts if the file cannot be found.</para> + <para>The <option>-g</option> option can be used in conjunction with RIS data to add some default fields to all references that are added with this command. The argument <replaceable>deffile</replaceable> is the filename of a <link linkend="sect1-ris-format">RIS file</link> containing these additional fields. &appname;c first tries the filename as is, so it should be a valid relative or absolute path. If the file is not found, &appname; looks for the file in <envar>$HOME</envar>. The command aborts if the file cannot be found.</para> <para>Keep in mind that this default file, just like any other RIS file, has to start with a newline and needs at least the TY and ER fields.</para> <para>The following example RIS file would switch the reprint status of all added references to <quote>ON REQUEST</quote> as of Jan 1, 2001 and let them have the type <quote>journal</quote> (please note the mandatory empty first line created by a LF):</para> @@ -1003,5 +1003,5 @@ <sect2 id="sect-getref-output-html"> <title>html</title> - <para>The html backend works just like the scrn backend, but encodes this information in a <acronym>HTML</acronym> text. This comes in handy if you would like to view the results of your queries in a web browser rather than in a terminal window. You simply use the <option>-o</option> switch to write the results of your queries to a file, reusing the same filename for each query. After each query you just have to hit the reload button of your browser to view the results of the most recent query.</para> + <para>The html backend works just like the scrn backend, but encodes this information in a <acronym>HTML</acronym> text. This comes in handy if you would like to view the results of your queries in a web browser rather than in a terminal window. This is also the easiest way to obtain fairly nice-looking printed output of your reference data. You simply use the <option>-o</option> switch to write the results of your queries to a file, reusing the same filename for each query. After each query you just have to hit the reload button of your browser to view the results of the most recent query.</para> <para>The visual appearance of the generated HTML files can be customized using CSS files. The URL of the CSS file must be specified with the &appname;c <option>-G</option> command-line option or by setting the configuration variable <varname>cssurl</varname>. The global configuration file <filename moreinfo="none">/usr/local/etc/&appname;/&appname;crc</filename> is preconfigured with a <varname>cssurl</varname> entry pointing to the default CSS file installed in <filename class="directory" moreinfo="none">/usr/local/share/&appname;/css</filename>. If you want a different appearance, it might be prudent to create a copy of this CSS file and customize it as you see fit. The following element classes can be customized. In most cases, the class name reflects the database field to be formatted:</para> <itemizedlist> @@ -1094,5 +1094,5 @@ <sect2> <title>html</title> - <para>The information returned by this backend is encoded as a HTML document. Otherwise the same applies as said for the scrn backend. See <link linkend="sect-getref-output-html">above</link> for some hints about formatting the output with a CSS file.</para> + <para>The information returned by this backend is encoded as a HTML document. Use this format to print nicely formatted notes from your web browser. Otherwise the same applies as said for the scrn backend. See <link linkend="sect-getref-output-html">above</link> for some hints about formatting the output with a CSS file.</para> </sect2> <sect2> @@ -1145,7 +1145,7 @@ </varlistentry> <varlistentry> - <term>:TI:, :T2:, :T3:</term> + <term>:TI:, :T2:, :T3:, :TA:</term> <listitem> - <para>The title of the reference, of the secondary title, and of the series title, respectively.</para> + <para>The title of the reference, of the secondary title, and of the series title, respectively. :TA: performs a search in all title levels.</para> </listitem> </varlistentry> Index: refdb-manual-chapter12.sgml =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdb-manual-chapter12.sgml,v retrieving revision 1.11 retrieving revision 1.11.2.1 diff -u -U2 -r1.11 -r1.11.2.1 --- refdb-manual-chapter12.sgml 8 Feb 2004 00:32:45 -0000 1.11 +++ refdb-manual-chapter12.sgml 14 Nov 2004 16:04:49 -0000 1.11.2.1 @@ -115,4 +115,19 @@ </sect1> <sect1> + <title>Print references</title> + <para>There are two ways to print references:</para> + <itemizedlist> + <listitem> + <para>Send the output of the <command moreinfo="none">getref</command> command to a printer:</para> + <screen format="linespecific"><prompt>&appname;c: </prompt><userinput>getref -c lpr :ID:>0</userinput></screen> + <para>You should probably be a bit more selective about the references than shown above unless you want to empty the paper tray of your printer. In any case, this command will print a list of your references in the screen output format. You can use some additional plumbing along these lines to obtain a more beautiful printer output:</para> + <screen format="linespecific"><prompt>&appname;c: </prompt><userinput>getref :ID:>0 -c 'pr -f | fmt -w 70 | lpr'</userinput></screen> + </listitem> + <listitem> + <para>The second option is to write the HTML output to a file and use your browser's print capabilities.</para> + </listitem> + </itemizedlist> + </sect1> + <sect1> <title>Use the personal reference list</title> <para>If you share your reference database with other users, the personal reference list is your tool to still have the personalized database that you want. In a way, you can eat your cake and still have it. First of all, you can limit your database search with the <option>-P</option> switch of the <link linkend="app-c-command-getref">getref</link> command to those references that you added to your personal reference list. But that's not all. With &appname;, all fields of a RIS dataset which must be the same for all users (like the title or the journal information), are common and accessible to all users. The information which is likely to differ between users (the reprint status, the availability information, and the notes), are stored separately for each user. If you later retrieve datasets, you will see your own notes for the reference, while your colleague will see his notes. All the <quote>hard</quote> bibliographic information will be the same for both of you, though.</para> @@ -252,4 +267,7 @@ <title>Viewer</title> <para>While a pager will do in many cases to view the query results, a web browser is a nice alternative. The &appname; command <link linkend="app-c-command-getref"><command moreinfo="none">getref</command></link> can generate HTML output at your request with the <option>-t html</option> option. Save the output to a file and view this file with your favourite web browser. When you run the next query, reuse the filename and hit the <guibutton>reload</guibutton> button of your browser to display the new results.</para> + <tip> + <para>A web browser is also a convenient way to print references.</para> + </tip> </sect2> </sect1> Index: refdb-manual-chapter13.sgml =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdb-manual-chapter13.sgml,v retrieving revision 1.16 retrieving revision 1.16.2.1 diff -u -U2 -r1.16 -r1.16.2.1 --- refdb-manual-chapter13.sgml 17 Feb 2004 22:14:40 -0000 1.16 +++ refdb-manual-chapter13.sgml 14 Nov 2004 16:04:49 -0000 1.16.2.1 @@ -7,9 +7,9 @@ <sect1> <title>Overview</title> - <para>The purpose of this application is to create bibliographies based on an input file which contains a list of citations conforming to the CitationList XML DTD. This input file is thus not the document that you write but rather a list of citations that is extracted from your document. In the case of LaTeX/BibTeX bibliographies, the citations are listed in the <filename>.aux</filename> file which is automatically created by the LaTeX interpreter. In the case of SGML and XML bibliographies, the citation list is extracted from your document with (Open)Jade.</para> + <para>The purpose of this application is to create bibliographies based on an input file which contains a list of citations conforming to the CitationList XML DTD. This input file is thus not the document that you write but rather a list of citations that is extracted from your document. In the case of LaTeX/BibTeX bibliographies, the citations are listed in the <filename>.aux</filename> file which is automatically created by the LaTeX interpreter. In the other cases, the citation list is extracted from your document with (Open)Jade or xsltproc for SGML and XML documents, respectively.</para> <para>Besides the bibliography data, &appname;ib creates additional files in the case of SGML and XML documents. These are style sheet driver files which can be used for subsequent document transformations. They contain a few variable definitions to adapt the formatting to the required citation and bibliography style.</para> <note> <para>While you certainly can run &appname;ib directly, it is not recommended to do so in most cases. Some output, like the style specification driver files, needs post-processing to be fully usable. For your convenience, &appname; ships with the <link linkend="sect-runbib">runbib</link> script which extracts the citation list, creates the bibliography file, and performs all necessary post-processing with a single command.</para> - <para>To make things even simpler, please have a look at the <link linkend="sect-refdbnd">&appname;nd</link> script. This script creates a skeleton SGML or XML file along with a customized <filename>Makefile</filename> which takes care of everything.</para> + <para>To make things even simpler, please have a look at the <link linkend="sect-refdbnd">&appname;nd</link> script. This script creates a skeleton SGML or XML file along with a customized <filename>Makefile</filename> which takes care of everything (except preparing coffee, that is).</para> </note> </sect1> @@ -28,4 +28,5 @@ <arg>-l <replaceable>log level</replaceable></arg> <arg>-L <replaceable>log file</replaceable></arg> + <arg choice="opt" rep="norepeat">-m</arg> <arg>-n</arg> <arg choice="opt" rep="norepeat">-N <replaceable>number</replaceable></arg> @@ -47,4 +48,5 @@ <para>Use the <option>-E</option> option to select a useful output character encoding. If this option is not used, the bibliography data will use the character encoding of the database. See <command moreinfo="none">man iconv_open</command> for a list of available encodings.</para> <para>The <option>-f stdin</option> option is a crutch to make reading data from stdin possible on platforms that do not allow automatic detection of data on stdin, like Windows/Cygwin. On other platforms, &appname;ib automatically reads data from stdin if data are available.</para> + <para>If you pass the <option>-m</option> option to &appname;ib, missing references (i.e. cited references that are not in the database) will not cause an error. Processing scripts like <link linkend="sect-runbib">runbib</link> will thus continue regardless instead of throwing in the towel.</para> <para>The <option>-n</option> option instructs &appname;ib not to create style specification files. Use this option if you are sure that a current style specification file already exists. This saves about as much computing time as you need to key in this option.</para> <para>Use the <option>-N</option> option to specify where the numbering of the references is supposed to start. The default is 1. This option comes in handy if you need to cobble together composite bibliographies or per-chapter bibliographies that still need to be numbered consecutively.</para> @@ -52,5 +54,5 @@ <para>The <option>-t</option> option selects the type of output. Use "db31" to generate DocBook SGML bibliographies, "db31x" for DocBook XML bibliographies, "teix" for TEI XML bibliographies, and "bibtex" for BibTeX bibliographies. The type of output also determines the type of style specification file, if any, that will be generated in addition to the bibliography for formatting purposes. This is only a matter of concern if you want to process a DocBook XML document with the DSSSL stylesheets: In this case you should use "db31" with this option. The SGML bibliography element is also a valid XML element, but you will get a DSSSL driver file instead of a XSL driver file when you use "db31x".</para> <note> - <para>In the current implementation, the <option>-t teix</option> option will also return a DocBook bibliography which needs to be transformed to a TEI bibliography with the <link linkend="sect-bibdb2tei"><filename>bibdb2tei.xsl</filename></link> DSSSL stylesheet.</para> + <para>In the current implementation, the <option>-t teix</option> option will also return a DocBook bibliography which needs to be transformed to a TEI bibliography with the <link linkend="sect-bibdb2tei"><filename>bibdb2tei.xsl</filename></link> stylesheet.</para> </note> <para>The purpose of all other command-line switches is explained in the section <link linkend="sect1-common-command-line-options">common command-line options</link>.</para> @@ -173,4 +175,9 @@ <entry>The character encoding for the bibliography output. If this is not specified, the data will use the same encoding as the database.</entry> </row> + <row> + <entry>ignore_missing</entry> + <entry>f</entry> + <entry>If this is set to "f", missing references (i.e. cited but not in the database) will throw an error. If set to "t", you'll get a warning but missing references will not cause &appname;ib to return an error.</entry> + </row> </tbody> </tgroup> Index: refdb-manual-chapter14.sgml =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdb-manual-chapter14.sgml,v retrieving revision 1.9 retrieving revision 1.9.2.1 diff -u -U2 -r1.9 -r1.9.2.1 --- refdb-manual-chapter14.sgml 8 Feb 2004 00:32:45 -0000 1.9 +++ refdb-manual-chapter14.sgml 14 Nov 2004 16:04:49 -0000 1.9.2.1 @@ -38,4 +38,6 @@ <arg choice="req" rep="norepeat">database</arg> <arg choice="req" rep="norepeat">style</arg> + <arg choice="opt" rep="norepeat">encoding</arg> + <arg choice="opt" rep="norepeat">css-file</arg> </cmdsynopsis> <para>The script will create two files in your current working directory:</para> @@ -52,8 +54,10 @@ <sect1 id="sect-runbib"> <title>The runbib shell script</title> - <para>This shell script is a wrapper for the bibliography client &appname;ib to simplify the creation of bibliographies. For SGML and XML documents, <command>runbib</command> first runs Jade/OpenJade to retrieve a list of citations from your source document. Then it runs <link linkend="chapter-refdbib">&appname;ib</link> to generate the bibliography as an external entity based on the extracted citation information. It will also create stylesheet driver files with the formatting information for subsequent document transformations. For BibTeX documents, <command>runbib</command> uses the information in the <filename>.aux</filename> file to retrieve a bibliography file that you can use as an input file for <command>bibtex</command>.</para> + <para>This shell script is a wrapper for the bibliography client &appname;ib to simplify the creation of bibliographies. For SGML and XML documents, <command>runbib</command> first runs <command moreinfo="none">openjade</command> or <command>xsltproc</command>, respectively, to retrieve a list of citations from your source document. Then it runs <link linkend="chapter-refdbib">&appname;ib</link> to generate the bibliography as an external entity based on the extracted citation information. It will also create stylesheet driver files with the formatting information for subsequent document transformations. For BibTeX documents, <command>runbib</command> uses the information in the <filename>.aux</filename> file to retrieve a bibliography file that you can use as an input file for <command>bibtex</command>.</para> <cmdsynopsis> <command>runbib</command> <arg>-d <replaceable>database</replaceable></arg> + <arg choice="opt" rep="norepeat">-E <replaceable>encoding</replaceable></arg> + <arg choice="opt" rep="norepeat">-G <replaceable>css-file</replaceable></arg> <arg>-h</arg> <arg rep="repeat">-i <replaceable>includevar</replaceable></arg> @@ -62,4 +66,6 @@ <arg>-S <replaceable>style</replaceable></arg> <arg>-t <replaceable>type</replaceable></arg> + <arg choice="opt" rep="norepeat">-u <replaceable>username</replaceable></arg> + <arg choice="opt" rep="norepeat">-w <replaceable>password</replaceable></arg> <arg choice="req" rep="repeat">file</arg> </cmdsynopsis> @@ -73,4 +79,16 @@ </varlistentry> <varlistentry> + <term>-E <replaceable>encoding</replaceable></term> + <listitem> + <para>Specify the character encoding that the retrieved bibliography data should use.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>-G <replaceable>css-file</replaceable></term> + <listitem> + <para>Set the path or the URL of a CSS file to be used by the (x)html output</para> + </listitem> + </varlistentry> + <varlistentry> <term>-h</term> <listitem> @@ -115,5 +133,5 @@ <sect2> <title>DocBook SGML output</title> - <para>&appname;ib generates two output files in addition to the ID listing created by Jade/OpenJade. Assuming you have a source file <filename moreinfo="none">foo.sgml</filename> and use the bibliography style <filename moreinfo="none">J.Biol.Chem.</filename> you will get:</para> + <para>&appname;ib generates two output files in addition to the ID listing created by Jade/OpenJade. runbib creates another output file from these. Assuming you have a source file <filename moreinfo="none">foo.sgml</filename> and use the bibliography style <filename moreinfo="none">J.Biol.Chem.</filename> you will get:</para> <variablelist> <varlistentry> @@ -135,9 +153,15 @@ </listitem> </varlistentry> + <varlistentry> + <term><filename moreinfo="none">J.Biol.Chem.css</filename></term> + <listitem> + <para>This is a CSS file which contains formatting information used by the html output.</para> + </listitem> + </varlistentry> </variablelist> </sect2> <sect2> <title>DocBook and TEI XML output</title> - <para>&appname;ib again generates two output files as for the DocBook SGML output above, and we also count the ID listing created by Jade/OpenJade. However, runbib does a little post-processing, so you'll get one additional file in the end. Assuming you have a source file <filename moreinfo="none">foo.xml</filename> and use the bibliography style <filename moreinfo="none">J.Biol.Chem.</filename> you will get:</para> + <para>&appname;ib again generates two output files as for the DocBook SGML output above, and we also count the ID listing created by xsltproc. However, runbib does a little post-processing, so you'll get two additional files in the end. Assuming you have a source file <filename moreinfo="none">foo.xml</filename> and use the bibliography style <filename moreinfo="none">J.Biol.Chem.</filename> you will get:</para> <variablelist> <varlistentry> @@ -165,4 +189,10 @@ </listitem> </varlistentry> + <varlistentry> + <term><filename moreinfo="none">J.Biol.Chem.css</filename></term> + <listitem> + <para>This is a CSS file which contains formatting information used by the html or xhtml output.</para> + </listitem> + </varlistentry> </variablelist> </sect2> @@ -188,8 +218,8 @@ <cmdsynopsis> <command>&appname;jade</command> - <arg>-d <replaceable>stylesheet</replaceable></arg> <arg>-h</arg> <arg>-i <replaceable>variable</replaceable></arg> <arg>-p <replaceable>prefix</replaceable></arg> + <arg>-s <replaceable>stylesheet</replaceable></arg> <arg>-t <replaceable>format</replaceable></arg> <arg choice="req" rep="repeat">file</arg> @@ -198,10 +228,4 @@ <variablelist> <varlistentry> - <term>-d <replaceable>stylesheet</replaceable></term> - <listitem> - <para>Select the stylesheet with this switch. Use <quote>r</quote> to select the &appname; stylesheets (default) or <quote>d</quote> to select the plain DocBook stylesheets</para> - </listitem> - </varlistentry> - <varlistentry> <term>-h</term> <listitem> @@ -236,4 +260,8 @@ </sect2> <sect2> + <title>Resolution of public identifiers</title> + <para>Public identifiers are resolved according to the SGML catalog files specified in <envar>$SGML_CATALOG_FILES</envar>. While <command>(open)jade</command> can retrieve DTDs from the web, it is advisable to keep local copies and add <command moreinfo="none">OVERRIDE YES</command> to the top of your catalog files. This ensures that the local copies are used.</para> + </sect2> + <sect2> <title>Examples</title> <para>Here we'll use the files generated in the last example above (see <link linkend="sect-runbib">runbib</link>) and generate a nicely formatted PDF file:</para> @@ -250,7 +278,9 @@ <cmdsynopsis> <command>&appname;xml</command> - <arg>-d <replaceable>stylesheet</replaceable></arg> + <arg choice="opt" rep="norepeat">-c <replaceable>fop_config_file</replaceable></arg> + <arg>-f <replaceable>fo_processor</replaceable></arg> <arg>-h</arg> - <arg>-p <replaceable>processor</replaceable></arg> + <arg>-p <replaceable>xslt_processor</replaceable></arg> + <arg>-s <replaceable>stylesheet</replaceable></arg> <arg>-t <replaceable>format</replaceable></arg> <arg choice="req" rep="repeat">file</arg> @@ -259,10 +289,4 @@ <variablelist> <varlistentry> - <term>-d <replaceable>stylesheet</replaceable></term> - <listitem> - <para>Select the appropriate stylesheet driver file with this switch. The driver file that you want to use is one of the driver files which were generated by <link linkend="sect-runbib">runbib</link>. Use the HTML driver file for HTML output and the FO driver file for all other output. You can also use this script for non-RefDB documents. Use the values <quote>"db"</quote> and <quote>tei</quote> to select the plain DocBook and TEI XSL stylesheets, respectively.</para> - </listitem> - </varlistentry> - <varlistentry> <term>-h</term> <listitem> @@ -277,4 +301,10 @@ </varlistentry> <varlistentry> + <term>-s <replaceable>stylesheet</replaceable></term> + <listitem> + <para>Select the appropriate stylesheet driver file with this switch. The driver file that you want to use is one of the driver files which were generated by <link linkend="sect-runbib">runbib</link>. Use the HTML driver file for HTML output and the FO driver file for all other output. You can also use this script for non-RefDB documents. Use the values <quote>"db"</quote> and <quote>tei</quote> to select the plain DocBook and TEI XSL stylesheets, respectively.</para> + </listitem> + </varlistentry> + <varlistentry> <term>-t <replaceable>format</replaceable></term> <listitem> @@ -283,7 +313,56 @@ </varlistentry> </variablelist> - <note> - <para>Unless you manually tweak files, the DTD and stylesheet files reference documents found on the internet. The XSL processors will therefore complain if you do not have an active internet connection.</para> - </note> + </sect2> + <sect2 id="sect2-refdbxml-init-variables"> + <title>Configuring &appname;xml</title> + <para>Instead of using the command-line switches, &appname;xml can also be configured by means of the &appname;xmlrc configuration file. As with all &appname; configuration files, you may maintain a global copy in <filename class="directory" moreinfo="none">/usr/local/etc/refdb/</filename> and one copy per user in <envar>$HOME</envar>.</para> + <table> + <title>&appname;xmlrc</title> + <tgroup cols="3"> + <thead> + <row> + <entry>Variable</entry> + <entry>Default</entry> + <entry>Comment</entry> + </row> + </thead> + <tbody> + <row> + <entry>xslt_processor</entry> + <entry>xsltproc</entry> + <entry>The name of the XSLT processor used to transform XML documents to html or fo files. Supported values are xsltproc (default), xalan, xt, saxon, saxon-xerces (using the xerces parser instead of the built-in parser)</entry> + </row> + <row> + <entry>xslt_classpath</entry> + <entry>/usr/share/java</entry> + <entry>Specify the directory which contains the Java classes for Java-based XSLT processors. This variable is not required if you use a non-Java processor (xsltproc).</entry> + </row> + <row> + <entry>fo_processor</entry> + <entry>fop</entry> + <entry>The name of the FO processor used to transform FO files into printable output. Supported values are fop (default), passivetex, xep, and xfor.</entry> + </row> + <row> + <entry>fo_classpath</entry> + <entry>/usr/share/java</entry> + <entry>Specify the directory which contains the Java classes for Java-based FO processors. This variable is not required if you use a non-Java processor (passivetex).</entry> + </row> + <row> + <entry>fop_config_file</entry> + <entry>(none)</entry> + <entry>The path to a custom configuration file for FOP.</entry> + </row> + <row> + <entry>outformat</entry> + <entry>html</entry> + <entry>Set the default output format. Supported values are html, xhtml, pdf, and rtf. Be aware that pdf and rtf are not supported by all FO processors.</entry> + </row> + </tbody> + </tgroup> + </table> + </sect2> + <sect2> + <title>Resolution of public identifiers</title> + <para>Public identifiers can be resolved to local files if you have a working XML catalog on your system and if your XSLT processor supports XML catalogs. xalan and saxon require additional Java classes to support XML catalogs. For further information, please consult Bob Stayton's <ulink url="http://www.sagehill.net/docbookxsl/UseCatalog.html">book</ulink> about XSLT.</para> </sect2> <sect2> Index: refdb-manual-chapter15.sgml =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdb-manual-chapter15.sgml,v retrieving revision 1.9 retrieving revision 1.9.2.1 diff -u -U2 -r1.9 -r1.9.2.1 --- refdb-manual-chapter15.sgml 17 Aug 2003 16:50:46 -0000 1.9 +++ refdb-manual-chapter15.sgml 14 Nov 2004 16:04:49 -0000 1.9.2.1 @@ -50,4 +50,7 @@ <para>Appearance of name, volume, and issue number of journals (bold, underlined, italics)</para> </listitem> + <listitem> + <para>Formatting of the bibliographic listing: indentation, font sizes.</para> + </listitem> </itemizedlist> <note> @@ -59,12 +62,15 @@ <para>It is recommended to use an XML editor like Emacs/PSGML to write bibliography styles using the CiteStyle XML DTD. This ensures that most XML errors get caught while you write. After you're done, the text should be validated with a validating SGML/XML parser like nsgmls or onsgmls.</para> <para>The <sgmltag>CITESTYLE</sgmltag> element defines a bibliography style for one particular journal or publisher. You can group several styles in one file with the <sgmltag>STYLESET</sgmltag> wrapper element.</para> - <para>Each <sgmltag>CITESTYLE</sgmltag> element contains exactly three top-level elements (<xref linkend="fig-citestyleschema">). The <sgmltag>STYLENAME</sgmltag> defines the name of this style. For the sake of simplicity this could be identical with the name of the journal or publisher whose bibliography style it defines, e.g. <quote>J.Biol.Chem.</quote>. The <sgmltag>REFSTYLE</sgmltag> element contains the style definitions for the various publication types that can appear in a bibliography, like books, journals, or personal communications. A special case is the type <quote>GEN</quote> which defines a default bibliography style that is applied whenever no specific definition is available for the requested type. Although the DTD does not enforce this, it is strongly recommended to define a <quote>GEN</quote> definition for each bibliography style. Finally, the <sgmltag>CITSTYLE</sgmltag> element defines the citation style, i.e. the appearance of the citations in the main text, as well as some general properties of the bibliography.</para> + <para>Each <sgmltag>CITESTYLE</sgmltag> element contains exactly four top-level elements (<xref linkend="fig-citestyleschema">). The <sgmltag>STYLENAME</sgmltag> defines the name of this style. For the sake of simplicity this could be identical with the name of the journal or publisher whose bibliography style it defines, e.g. <quote>J.Biol.Chem.</quote> or <quote>Elsevier</quote>. The <sgmltag>REFSTYLE</sgmltag> element contains the style definitions for the various publication types that can appear in a bibliography, like books, journals, or personal communications. A special case is the type <quote>GEN</quote> which defines a default bibliography style that is applied whenever no specific definition is available for the requested type. Although the DTD does not enforce this, it is strongly recommended to define a <quote>GEN</quote> definition for each bibliography style. The <sgmltag>CITSTYLE</sgmltag> element defines the citation style, i.e. the appearance of the citations in the main text. Finally, the <sgmltag>BIBSTYLE</sgmltag> element defines the properties of the bibliographic listing.</para> <figure float="0" id="fig-citestyleschema"> <title>Schematic representation of a <sgmltag>CITESTYLE</sgmltag> element</title> - <graphic fileref="refdbmanualfig4"></graphic> + <graphic fileref="refdbmanualfig4"> </figure> <para>Each definition for a publication type in turn can contain various elements that define the sequence and rendering of authorlists, publication dates, titles, and so on. This is where the real pain in defining bibliography styles lies. All available elements can hold a <sgmltag>PRECEEDING</sgmltag> and a <sgmltag>FOLLOWING</sgmltag> element which define strings that are inserted before and after the corresponding element, respectively. This can be used to place punctuation characters or brackets wherever such a non-empty element occurs. A special element is <sgmltag>SEPARATOR</sgmltag> which usually also contains punctuation characters. This element is always inserted even if the preceeding or following element is empty.</para> <para>The <sgmltag>CITSTYLE</sgmltag> element can define three different styles for citations: <sgmltag>INTEXTDEF</sgmltag> for regular citations as well as <sgmltag>AUTHORONLY</sgmltag> and <sgmltag>YEARONLY</sgmltag> for citations that keep the authors in the flow of the text. These elements are equivalent to the definition of a publication type in the <sgmltag>REFSTYLE</sgmltag> element.</para> <para>Please peruse the separate documentation for the <ulink url="http://refdb.sourceforge.net/docs.html">CiteStyle XML DTD</ulink> for the details about the individual elements.</para> + <tip> + <para>The &appname; project also provides a tool to create citation styles interactively. The <command moreinfo="none">&appname;-ms</command> Perl script is available separately from the <ulink url="http://sourceforge.net/projects/refdb/">main project page</ulink>.</para> + </tip> </sect2> </sect1> @@ -171,8 +177,8 @@ <programlisting> <citation role="REFDB"> <co id="list1-citation"> -<xref linkend="ID1X"> <co id="list1-xref"> +<xref linkend="ID1-X"> <co id="list1-xref"> </citation> <citation role="REFDB"> -<xref linkend="LITIBP-ID2X"> <co id="list1-xref2"> +<xref linkend="LITIBP-ID2-X"> <co id="list1-xref2"> </citation> </programlisting> @@ -182,5 +188,5 @@ </callout> <callout arearefs="list1-xref"> - <para>Each <sgmltag class="element">xref</sgmltag> element specifies one bibliographic reference. The value of the <sgmltag class="attribute">linkend</sgmltag> attribute encodes which bibliographic item is referenced (in this case, the database entry with the ID 1) and how the reference should be rendered (see below). It consists of the string "ID" followed by the numerical database entry ID, and a trailing one-letter type specifier ("X" in this case). This simple form does not encode the database from which the reference is to be pulled. When generating the bibliography, you will specify a default database from which all references without an explicit database label will be taken from. This form is most convenient if all your bibliographic items are stored in one database.</para> + <para>Each <sgmltag class="element">xref</sgmltag> element specifies one bibliographic reference. The value of the <sgmltag class="attribute">linkend</sgmltag> attribute encodes which bibliographic item is referenced (in this case, the database entry with the ID 1) and how the reference should be rendered (see below). It consists of the string "ID" followed by the numerical database entry ID, and a trailing one-letter type specifier ("X" in this case), separated from the rest by a dash. This simple form does not encode the database from which the reference is to be pulled. When generating the bibliography, you will specify a default database from which all references without an explicit database label will be taken from. This form is most convenient if all your bibliographic items are stored in one database.</para> </callout> <callout arearefs="list1-xref2"> @@ -192,5 +198,5 @@ <itemizedlist> <listitem> - <para>The empty <sgmltag class="element">xref</sgmltag> elements need a closing slash as in <xref linkend="ID2X"/>.</para> + <para>The empty <sgmltag class="element">xref</sgmltag> elements need a closing slash as in <xref linkend="ID2-X"/>.</para> </listitem> <listitem> @@ -202,8 +208,8 @@ <programlisting> <seg type="REFDBCITATION" part="N" TEIform="seg"> <co id="list2-citation"> -<ptr targOrder="U" target="ID1X" TEIform="ptr"/> <co id="list2-xref"> +<ptr targOrder="U" target="ID1-X" TEIform="ptr"/> <co id="list2-xref"> </seg> <seg type="REFDBCITATION" part="N" TEIform="seg"> -<ptr targOrder="U" target="LITIBP-ID2X" TEIform="ptr"/><co id="list2-xref2"> +<ptr targOrder="U" target="LITIBP-ID2-X" TEIform="ptr"/><co id="list2-xref2"> </seg> </programlisting> @@ -267,7 +273,7 @@ <citation role="REFDB"> <xref endterm="IMTHEFIRST" linkend="ID1" role="MULTIXREF"><co id="list3-multixref"> -<xref linkend="ID1X"> <co id="list3-xref"> -<xref linkend="ID14X"> -<xref linkend="ID7X"> +<xref linkend="ID1-X"> <co id="list3-xref"> +<xref linkend="ID14-X"> +<xref linkend="ID7-X"> </citation> </programlisting> @@ -288,7 +294,7 @@ <seg type="REFDBCITATION" part="N" TEIform="seg"> <ptr type="MULTIXREF" targOrder="U" target="IMTHEFIRST" TEIform="ptr"/><co id="list4-multixref"> -<ptr targOrder="U" target="ID1X" TEIform="ptr"/> <co id="list4-xref"> -<ptr targOrder="U" target="LITIBP-ID21X" TEIform="ptr"/> -<ptr targOrder="U" target="ID5X" TEIform="ptr"/> +<ptr targOrder="U" target="ID1-X" TEIform="ptr"/> <co id="list4-xref"> +<ptr targOrder="U" target="LITIBP-ID21-X" TEIform="ptr"/> +<ptr targOrder="U" target="ID5-X" TEIform="ptr"/> </seg> </programlisting> @@ -324,5 +330,5 @@ <title>Extract the list of bibliographic references</title> <para>Use Jade or OpenJade with the <filename>citations.dsl</filename> stylesheet to create a list of the reference IDs (provide full paths as needed):</para> - <screen width="60" format="linespecific"><prompt>#~ </prompt><userinput>jade -t sgml -d citations.dsl /usr/lib/sgml/declaration/docbook-3.1.dcl foo.sgml > foo.id.xml</userinput></screen> + <screen width="60" format="linespecific"><prompt>#~ </prompt><userinput>openjade -t sgml -d citations.dsl /usr/lib/sgml/declaration/docbook-3.1.dcl foo.sgml > foo.id.xml</userinput></screen> <para>Be prepared for a long list of "missing ID" error messages. This is due to the fact that the elements with the IDs that the <sgmltag>xref</sgmltag> elements in the citations point to do not yet exist, they will be generated in the &appname; bibliography output. If you process documents with more than 200 citations, you'll have to increase the maximum error limit of Jade in order to obtain all IDs the first time. After the first complete pass (including the steps outlined below), Jade will only complain about any additional citations that you have inserted since the last run.</para> <para>The output is a simple XML file that contains the information about all <sgmltag>citation</sgmltag> and <sgmltag>xref</sgmltag> elements with their relevant attributes. It is absolutely legal to extend this file with additional citation elements to specify references which are not cited but nonetheless should appear in the bibliography.</para> @@ -330,5 +336,5 @@ <para>If you edit this intermediate XML file (that is, if you do more than just fixing the Doctype line), you should make sure that the result is still valid according to the CitationList XML DTD. &appname; uses a non-validating parser to read this file so deviations from the DTD may slip through undetected and may have undesired consequences. The intermediate XML file carries the SYSTEM identifier of the CitationList XML DTD in the document type declaration. You may have to adapt the stylesheet <filename>citations.dsl</filename> to use the correct path for your local system.</para> <para>The following command line can be used to validate the document with <application>(o)nsgmls</application> (change the path to the XML declaration as necessary):</para> - <screen width="60" format="linespecific"><prompt>~$ </prompt><userinput>nsgmls -wxml -s /usr/lib/sgml/declaration/xml.dcl foo.id.xml</userinput></screen> + <screen width="60" format="linespecific"><prompt>~$ </prompt><userinput>onsgmls -wxml -s /usr/lib/sgml/declaration/xml.dcl foo.id.xml</userinput></screen> </step> <step> @@ -361,5 +367,5 @@ <title>The &appname;nd shortcut</title> <para>Now that you know all necessary steps to process SGML and XML documents, it's about time to reveal that there is a simple shortcut if you can live with some minor restrictions. The <link linkend="sect-refdbnd">&appname;nd</link> script helps you to start new SGML or XML projects and sets up a Makefile to process your document.</para> - <para>Start the script in a clean subdirectory by typing <command moreinfo="none">&appname;nd</command>. The script will start in interactive mode and ask a couple of questions. You'll have to specify the basename of your project, the SGML or XML document type declaration you'd like to use, the top-level element, the &appname; database that holds the references which you intend to cite, and the name of the bibliography style to be used with this document. The script will then create a file <basename>.short.[sgml|xml]. The ".short" reminds you that the Makefile assumes you will be using the <link linkend="sect-short-notation">short notation</link> for citations. It will also create a Makefile which is set up to perform the necessary steps to create all sorts of available formatted output.</para> + <para>Start the script in a clean subdirectory by typing <command moreinfo="none">&appname;nd</command>. The script will start in interactive mode and ask a couple of questions. You'll have to specify the basename of your project, the SGML or XML document type declaration you'd like to use, the top-level element, the &appname; database that holds the references which you intend to cite, the name of the bibliography style to be used with this document, the character encoding, and the name of a CSS file to be used with (x)html output. The script will then create a file <basename>.short.[sgml|xml]. The ".short" reminds you that the Makefile assumes you will be using the <link linkend="sect-short-notation">short notation</link> for citations. It will also create a Makefile which is set up to perform the necessary steps to create all sorts of available formatted output.</para> <para>Once you have written your document, including a few citations and a reference to the external bibliography file as explained in the previous sections, you can use the Makefile to process your document. You may know how to use Makefiles anyway, but if not, here are the main properties:</para> <itemizedlist> @@ -379,5 +385,5 @@ <term>pdf</term> <listitem> - <para>This target generates a PDF file from your source document. PDF is a widely accepted document format with free viewers for essentially all current operating systems.</para> + <para>This target generates a PDF file from your source document. PDF is a widely accepted document format with free viewers for essentially all current operating systems. Be aware that not all FO processors (used in transforming XML documents) offer PDF output.</para> </listitem> </varlistentry> @@ -391,5 +397,5 @@ <term>rtf</term> <listitem> - <para>This target generates a Rich Text Format (RTF) file. This plain text format is sort of a word processor interchange format understood by most current word processors, including MS Word, WordPerfect, and OpenOffice/StarOffice.</para> + <para>This target generates a Rich Text Format (RTF) file. This plain text format is sort of a word processor interchange format understood by most current word processors, including MS Word, WordPerfect, and OpenOffice/StarOffice. Be aware that not all FO processors offer RTF output.</para> </listitem> </varlistentry> @@ -401,5 +407,5 @@ </varlistentry> </variablelist> - <para>The Makefile also offers a few more targets. For each of the above targets there is a corresponding '<target>dist' target which creates a <filename moreinfo="none">.tar.gz</filename> archive of the output document. The target 'all', which is also the default if you don't specify a target to <command moreinfo="none">make</command>, builds all available output formats. Accordingly, the target 'dist' creates all archives. And finally, the target 'clean' removes all intermediate files and returns your directory to the original state.</para> + <para>The Makefile also offers a few more targets. For each of the above targets there is a corresponding '<target>dist' target which creates a <filename moreinfo="none">.tar.gz</filename> archive of the output document, along with its associated CSS stylesheet if applicable. The target 'all', which is also the default if you don't specify a target to <command moreinfo="none">make</command>, builds all available output formats. Accordingly, the target 'dist' creates all archives. And finally, the target 'clean' removes all intermediate files and returns your directory to the original state.</para> <para>For example, to create a formatted PDF document <filename><basename>.pdf</filename> from your <filename moreinfo="none"><basename>.short.sgml</filename> file you'd type <command moreinfo="none">make pdf</command>. <command moreinfo="none">make</command> will first convert the short-style citations to the full style using the <command moreinfo="none">&appname;xp</command> tool. Then it will generate the bibliography and the stylesheet driver files by running <command moreinfo="none">&appname;ib</command>. Finally it will run the <command moreinfo="none">&appname;jade</command> script to create the PDF output.</para> <para>The &appname;nd-generated Makefiles should be sufficient for the average document. However, feel free to modify them in order to adapt them to specific needs. For example you can specify a different style in order to switch your output to a different citation and bibliography style. <command moreinfo="none">make</command> also allows you to override variable settings on the command line. E.g. if you want to output your document using a different bibliography style without making it the permanent default, invoke <command moreinfo="none">make</command> like this:</para> Index: refdb-manual-chapter2.sgml =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdb-manual-chapter2.sgml,v retrieving revision 1.15 retrieving revision 1.15.2.1 diff -u -U2 -r1.15 -r1.15.2.1 --- refdb-manual-chapter2.sgml 8 Feb 2004 00:32:45 -0000 1.15 +++ refdb-manual-chapter2.sgml 14 Nov 2004 16:04:49 -0000 1.15.2.1 @@ -1,3 +1,3 @@ -<!DOCTYPE CHAPTER PUBLIC "-//OASIS//DTD DocBook V3.1//EN" [ +<!DOCTYPE CHAPTER PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [ <!ENTITY appname "refdb"> ]> @@ -28,5 +28,5 @@ </listitem> </itemizedlist> - <para>While this portability excludes fancy GUI bells and whistles, it makes it (most likely) possible to run &appname; on the hardware and operating system that you happen to have. Both the clients and the application server should compile on all systems with a decent C compiler like <application>gcc</application>. There should be no problems to run &appname; on heterogenous networks. For Windows users the free Cygwin tools are recommended. <ulink url="http://www.cygwin.com">Cygwin</ulink> is a POSIX layer on top of Win32 including a useful selection of the popular <ulink url="http://www.gnu.org">GNU tools</ulink>.</para> + <para>Other Unix-like operating systems may work out of the box or with a minimum amount of tweaking. While this portability excludes fancy GUI bells and whistles, it makes it (most likely) possible to run &appname; on the hardware and operating system that you happen to have. Both the clients and the application server should compile on all systems with a decent C compiler like <application>gcc</application>. There should be no problems to run &appname; on heterogenous networks. For Windows users the free Cygwin tools are recommended. <ulink url="http://www.cygwin.com">Cygwin</ulink> is a POSIX layer on top of Win32 including a useful selection of the popular <ulink url="http://www.gnu.org">GNU tools</ulink>.</para> <para>To simplify the task of porting &appname; to other operating systems the package uses <application moreinfo="none">autoconf</application> and <application moreinfo="none">automake</application>.</para> </sect1> @@ -152,5 +152,5 @@ <term>Jade/OpenJade and SP/OSP-based tools (required for DocBook SGML bibliographies, import of DocBook bibliography data)</term> <listitem> - <para>Jade is a freely available and well-proven DSSSL engine which is based on the SP parser. The Jade package contains a few more SP-based tools, e.g. the nsgmls validator and the sgmlnorm normalizer. &appname; uses Jade both to extract the IDs of the references which are cited in SGML documents and to transform SGML documents using DSSSL stylesheets. sgmlnorm is required to preprocess multipart documents using the short notation for &appname; citations. The Jade/SP package is available on <ulink url="http://www.jclark.com">James Clarks homepage</ulink>. Prebuilt binaries are available for some platforms, and it builds out of the box on quite a number of platforms. Jade has seen some further development by an independent group of programmers. These newer versions were released as OpenJade/OpenSP and are available at the <ulink url="http://www.sourceforge.net/projects/openjade/">OpenJade homepage</ulink>. Instructions to build OpenJade on Windows NT/Cygwin and precompiled binaries are available <ulink url="http://members.tripod.com/~mhoenicka/openjadesp.html">here</ulink> (official Cygwin packages of OpenJade and related tools are in preparation).</para> + <para>Jade is a freely available and well-proven DSSSL engine which is based on the SP parser. The Jade package contains a few more SP-based tools, e.g. the nsgmls validator and the sgmlnorm normalizer. &appname; uses Jade both to extract the IDs of the references which are cited in SGML documents and to transform SGML documents using DSSSL stylesheets. sgmlnorm is required to preprocess multipart documents using the short notation for &appname; citations. The Jade/SP package is available on <ulink url="http://www.jclark.com">James Clarks homepage</ulink>. Prebuilt binaries are available for some platforms, and it builds out of the box on quite a number of platforms. Jade has seen some further development by an independent group of programmers. These newer versions were released as OpenJade/OpenSP and are available at the <ulink url="http://www.sourceforge.net/projects/openjade/">OpenJade homepage</ulink>.</para> <note> <para>OpenJade has some advantages over Jade for our purposes. If it is possible to obtain or compile OpenJade on your platform, you should go for it. Both Jade and OpenJade can be installed on the same machine without conflicts. The configure script will look for both OpenJade and Jade and will use the former as the default DSSSL engine in the shell script customizations if it is available.</para> @@ -161,5 +161,5 @@ <term>XSL processor (required for DocBook and TEI XML documents)</term> <listitem> - <para>If you're working with XML documents and want to transform them using the XSL stylesheets, you'll need some sort of XSL processing machinery. Popular choices are <ulink url="http://xml.apache.org">Xalan</ulink>, <ulink url="http://saxon.sourceforge.net">Saxon</ulink>, and <ulink url="http://xmlsoft.org/XSLT">xsltproc</ulink>. The latter is checked for in the configure script and will be used as the default processor if available. The Java-based tools among these need the <ulink url="http://java.sun.com">Java Virtual Machine</ulink> installed, of course. Generating printable output seems to work best through the TeX path (see below) using the <ulink url="http://users.ox.ac.uk/~rahtz/passivetex/">PassiveTeX</ulink> macros.</para> + <para>If you're working with XML documents and want to transform them using the XSL stylesheets, you'll need some sort of XSL processing machinery. Popular choices are <ulink url="http://xml.apache.org">Xalan</ulink>, <ulink url="http://saxon.sourceforge.net">Saxon</ulink>, and <ulink url="http://xmlsoft.org/XSLT">xsltproc</ulink>. The latter is checked for in the configure script and will be used as the default processor if available. The Java-based tools among these need the <ulink url="http://java.sun.com">Java Virtual Machine</ulink> installed, of course. Generating printable output seems to work best with <ulink url="http://xml.apache.org/fop/index.html">FOP</ulink>.</para> </listitem> </varlistentry> Index: refdb-manual-chapter3.sgml =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdb-manual-chapter3.sgml,v retrieving revision 1.12 retrieving revision 1.12.2.1 diff -u -U2 -r1.12 -r1.12.2.1 --- refdb-manual-chapter3.sgml 17 Aug 2003 16:50:46 -0000 1.12 +++ refdb-manual-chapter3.sgml 14 Nov 2004 16:04:49 -0000 1.12.2.1 @@ -1,3 +1,3 @@ -<!DOCTYPE CHAPTER PUBLIC "-//OASIS//DTD DocBook V3.1//EN" [ +<!DOCTYPE CHAPTER PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [ <!ENTITY appname "refdb"> ]> @@ -43,4 +43,7 @@ <listitem> <para>Cygwin currently does not support named pipes/FIFOs. &appname;d uses these to implement a child->parent messaging after the application server has forked. On Cygwin, this messaging is emulated with a temporary file. This is a bit slower (and a lot kludgier and error-prone) than a named pipe and almost certainly is a security hole.</para> + <note> + <para>As of this writing, support for named pipes appears to be implemented as an experimental feature in Cygwin. </para> + </note> </listitem> <listitem> Index: refdb-manual-chapter4.sgml =================================================================== RCS file: /cvsroot/refdb/refdb/doc/refdb-manual-chapter4.sgml,v retrieving revision 1.14 retrieving revision 1.14.2.1 diff -u -U2 -r1.14 -r1.14.2.1 --- refdb-manual-chapter4.sgml 8 Feb 2004 00:32:45 -0000 1.14 +++ refdb-manual-chapter4.sgml 14 Nov 2004 16:04:49 -0000 1.14.2.1 @@ -1,3 +1,3 @@ -<!DOCTYPE CHAPTER PUBLIC "-//OASIS//DTD DocBook V3.1//EN" [ +<!DOCTYPE CHAPTER PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [ <!ENTITY appname "refdb"> ]> @@ -184,5 +184,5 @@ <title>nmed2ris</title... [truncated message content] |
|
From: Markus H. <mho...@us...> - 2004-11-14 15:54:55
|
Update of /cvsroot/refdb/refdb/src In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23448/src Modified Files: Tag: Release_0_9_5_stable xmlhandler.c Log Message: added some comments Index: xmlhandler.c =================================================================== RCS file: /cvsroot/refdb/refdb/src/xmlhandler.c,v retrieving revision 1.22.2.9 retrieving revision 1.22.2.10 diff -u -U2 -r1.22.2.9 -r1.22.2.10 --- xmlhandler.c 28 Sep 2004 22:12:34 -0000 1.22.2.9 +++ xmlhandler.c 14 Nov 2004 15:54:46 -0000 1.22.2.10 @@ -1462,5 +1462,5 @@ dbi_conn_close(conn_source); } - } + } /* end if numerical */ @@ -1681,5 +1681,5 @@ } } - else { + else { /* ID not found */ /* don't count the first dummy citation in a multiple citation */ if (!nis_multi) { @@ -1702,5 +1702,5 @@ /* reset multi-id */ (ptr_gbdata->ptr_curr_multi_id)[0] = '\0'; - } + } /* end if XREF or CITATION */ /* remove current element from element stack */ |
|
From: Markus H. <mho...@us...> - 2004-11-14 15:53:12
|
Update of /cvsroot/refdb/refdb/src In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23157/src Modified Files: Tag: Release_0_9_5_stable dbfncs.c Log Message: moved ID columns to BIGINT for MySQL Index: dbfncs.c =================================================================== RCS file: /cvsroot/refdb/refdb/src/dbfncs.c,v retrieving revision 1.15 retrieving revision 1.15.2.1 diff -u -U2 -r1.15 -r1.15.2.1 --- dbfncs.c 29 Jan 2004 01:42:11 -0000 1.15 +++ dbfncs.c 14 Nov 2004 15:53:03 -0000 1.15.2.1 @@ -154,5 +154,5 @@ dbires = dbi_conn_query(conn, "CREATE TABLE t_refdb \ - (refdb_id INT NOT NULL AUTO_INCREMENT, \ + (refdb_id BIGINT NOT NULL AUTO_INCREMENT, \ refdb_citekey VARCHAR(255), \ refdb_type VARCHAR(6), \ @@ -201,5 +201,5 @@ /* create the author table */ dbires = dbi_conn_query(conn, "CREATE TABLE t_author \ - (author_id INT NOT NULL AUTO_INCREMENT, \ + (author_id BIGINT NOT NULL AUTO_INCREMENT, \ author_name VARCHAR(255) NOT NULL, \ author_lastname VARCHAR(255), \ @@ -220,5 +220,5 @@ /* create the keyword table */ dbires = dbi_conn_query(conn, "CREATE TABLE t_keyword \ - (keyword_id INT NOT NULL AUTO_INCREMENT, \ + (keyword_id BIGINT NOT NULL AUTO_INCREMENT, \ keyword_name VARCHAR(255) NOT NULL, \ PRIMARY KEY (keyword_id), \ @@ -235,5 +235,5 @@ /* create the periodical table */ dbires = dbi_conn_query(conn, "CREATE TABLE t_periodical \ - (periodical_id INT NOT NULL AUTO_INCREMENT, \ + (periodical_id BIGINT NOT NULL AUTO_INCREMENT, \ periodical_name VARCHAR(255) NOT NULL, \ periodical_abbrev VARCHAR(255) NOT NULL, \ @@ -256,5 +256,5 @@ /* create the notes table */ dbires = dbi_conn_query(conn, "CREATE TABLE t_note \ - (note_id INT NOT NULL AUTO_INCREMENT, \ + (note_id BIGINT NOT NULL AUTO_INCREMENT, \ note_key VARCHAR(255), \ note_title VARCHAR(255), \ @@ -281,5 +281,5 @@ /* the user_name length limit is imposed by MySQL, don't know about PostgreSQL */ dbires = dbi_conn_query(conn, "CREATE TABLE t_user \ - (user_id INT NOT NULL AUTO_INCREMENT, \ + (user_id BIGINT NOT NULL AUTO_INCREMENT, \ user_name VARCHAR(16) NOT NULL, \ PRIMARY KEY (user_id), \ @@ -296,7 +296,7 @@ /* create the author xtable */ dbires = dbi_conn_query(conn, "CREATE TABLE t_xauthor \ - (xauthor_id INT NOT NULL AUTO_INCREMENT, \ - author_id INT NOT NULL, \ - refdb_id INT NOT NULL, \ + (xauthor_id BIGINT NOT NULL AUTO_INCREMENT, \ + author_id BIGINT NOT NULL, \ + refdb_id BIGINT NOT NULL, \ xauthor_type ENUM('primary', 'secondary', 'tertiary'), \ xauthor_role VARCHAR(64), \ @@ -316,7 +316,7 @@ /* create the keyword xtable */ dbires = dbi_conn_query(conn, "CREATE TABLE t_xkeyword \ - (xkeyword_id INT NOT NULL AUTO_INCREMENT, \ - keyword_id INT NOT NULL, \ - xref_id INT NOT NULL, \ + (xkeyword_id BIGINT NOT NULL AUTO_INCREMENT, \ + keyword_id BIGINT NOT NULL, \ + xref_id BIGINT NOT NULL, \ xkeyword_type ENUM(\"REFERENCE\",\"NOTE\"), \ PRIMARY KEY (xkeyword_id), \ @@ -334,7 +334,7 @@ /* create the user xtable */ dbires = dbi_conn_query(conn, "CREATE TABLE t_xuser \ - (xuser_id INT NOT NULL AUTO_INCREMENT, \ - user_id INT NOT NULL, \ - refdb_id INT NOT NULL, \ + (xuser_id BIGINT NOT NULL AUTO_INCREMENT, \ + user_id BIGINT NOT NULL, \ + refdb_id BIGINT NOT NULL, \ xuser_reprint ENUM(\"IN FILE\",\"NOT IN FILE\",\"ON REQUEST\"), \ xuser_date DATE, \ @@ -355,7 +355,7 @@ /* create the notes xtable */ dbires = dbi_conn_query(conn, "CREATE TABLE t_xnote \ - (xnote_id INT NOT NULL AUTO_INCREMENT, \ - note_id INT NOT NULL, \ - xref_id INT NOT NULL, \ + (xnote_id BIGINT NOT NULL AUTO_INCREMENT, \ + note_id BIGINT NOT NULL, \ + xref_id BIGINT NOT NULL, \ xnote_type ENUM(\"REFERENCE\",\"KEYWORD\",\"AUTHOR\",\"PERIODICAL\"), \ PRIMARY KEY (xnote_id), \ @@ -1665,4 +1665,7 @@ unsigned long long my_dbi_result_get_idval(dbi_result dbires, const char* fieldname) { dbi_conn conn; + char buffer[512]; + unsigned long the_ulong; + unsigned long long the_ulonglong; conn = dbi_result_get_conn(dbires); @@ -1671,8 +1674,14 @@ /* database server does not support long long ints, retrieve as long int instead and cast */ - return (unsigned long long)dbi_result_get_ulong(dbires, fieldname); + the_ulong = dbi_result_get_ulong(dbires, fieldname); +/* sprintf(buffer, "ulong: u %u<< lu %lu<< llu %llu", the_ulong, the_ulong, the_ulong); */ +/* LOG_PRINT(LOG_DEBUG, buffer); */ + return (unsigned long long)the_ulong; } else { - return dbi_result_get_ulonglong(dbires, fieldname); + the_ulonglong = dbi_result_get_ulonglong(dbires, fieldname); +/* sprintf(buffer, "ulonglong: u %u<< lu %lu<< llu %llu", the_ulonglong, the_ulonglong, the_ulonglong); */ +/* LOG_PRINT(LOG_DEBUG, buffer); */ + return the_ulonglong; } } |
1 message has been excluded from this view by a project administrator.
