refdb-cvs Mailing List for RefDB (Page 44)
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
|
Update of /cvsroot/refdb/refdb/doc/risx/ele-desc In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv14404 Added Files: Tag: Release_0_9_5_stable abstract.html address.html author.html availability.html city.html contents.html date.html day.html endpage.html entry.html firstname.html issue.html keyword.html lastname.html libinfo.html middlename.html misc.html month.html name.html notes.html otherinfo.html part.html pubdate.html pubinfo.html publication.html publisher.html reprint.html ris.html serial.html set.html startpage.html suffix.html title.html url.html userdef.html volume.html year.html Log Message: initial version --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>abstract description</title> </head> <body> <h2>Description</h2> <p>The abstract element contains an abstract of the reference. Articles published in scientific journals usually contain abstracts. For books, the liner or backcover texts might just be fine.</p> <h2>Example</h2> <pre> <contents> <abstract>Dinosaurs were big animals that ate a lot</abstract> <keyword>dinosaurs</keyword> <keyword>evolution</keyword> <keyword>animals</keyword> </contents> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>address description</title> </head> <body> <h2>Description</h2> <p>The address element contains a string with whatever information is available to contact the author of a publication.</p> <h2>Example</h2> <pre> <pubinfo> <pubdate type="primary"> <date> <year>1999</year> </date> </pubdate> <city>Sebastopol</city> <publisher>O'Reilly</publisher> <serial>1-56592-580-7</serial> <address>mi...@di...</address> <url>http://www.dinosaurs.upenn.edu/</url> </pubinfo> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>author description</title> </head> <body> <h2>Description</h2> <p>The author element contains the name of an author or editor. Whenever possible, the parts of a personal name should be qualified by using the <a href="lastname.html">lastname</a>, <a href="firstname.html">firstname</a>, <a href="middlename.html">middlename</a>, and <a href="suffix.html">suffix</a> elements. If that does not work out, or if you're looking at a corporate or institutional name, use the <a href="name.html">name</a> element instead.</p> <h2>Example</h2> <pre> <author> <lastname>Myers</lastname> <firstname>B</firstname> <middlename>B</middlename> <suffix>Jr.</suffix> </author> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>availability description</title> </head> <body> <h2>Description</h2> <p>The availability element holds the information necessary to keep track of a paper copy or of an electronic offprint of the reference.</p> <p>If the type attribute is set to "full", the element may contain a verbose description of the physical location of a copy of the reference, or a fully qualified URL of an electronic version. The latter should start with a protocol specifier, i.e. "http://", "ftp://", or "file://" if the copy is on the local filesystem.</p> <p>If the type attribute is set to "useroot" instead, the element should contain the partial path of an electronic version. This path will be completed by RefDB using the pdfroot feature.</p> <h2>Example</h2> <pre> <libinfo user="jdoe"> <notes>Not bad, after all</notes> <reprint status="INFILE"/> <availability type="useroot">palaeontology/dinosaurs/millera2002.pdf</availability> </libinfo> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>city description</title> </head> <body> <h2>Description</h2> <p>The city element holds the city of publication, usually the location of the headquarter of the publishing company.</p> <h2>Example</h2> <pre> <pubinfo> <pubdate type="primary"> <date> <year>1999</year> </date> </pubdate> <city>Sebastopol</city> <publisher>O'Reilly</publisher> <serial>1-56592-580-7</serial> <address>mi...@di...</address> <url>http://www.dinosaurs.upenn.edu/</url> </pubinfo> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>contents description</title> </head> <body> <h2>Description</h2> <p>The contents element is a wrapper for the information that describes the contents of a reference. The contents are further specified by the <a href="abstract.html">abstract</a> and <a href="keyword.html">keyword</a> elements.</p> <h2>Example</h2> <pre> <contents> <abstract>Dinosaurs were big animals that ate a lot</abstract> <keyword>dinosaurs</keyword> <keyword>evolution</keyword> <keyword>animals</keyword> </contents> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>date description</title> </head> <body> <h2>Description</h2> <p>The date element is a wrapper for the <a href="year.html">year</a>, <a href="month.html">month</a>, and <a href="day.html">day</a> elements describing a date.</p> <h2>Example</h2> <pre> <pubdate type="primary"> <date> <year>1999</year> </date> </pubdate> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>day description</title> </head> <body> <h2>Description</h2> <p>The day element holds the day information of a <a href="date.html">date</a> element. The day should be specified as a numeric value in the range of 1 through 31.</p> <h2>Example</h2> <pre> <pubdate type="primary"> <date> <year>1999</year> <month>11</month> <day>12</day> </date> </pubdate> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>endpage description</title> </head> <body> <h2>Description</h2> <p>Journal and magazine articles are usually published on a range of pages. The endpage element specifies the last page of an article.</p> <h2>Example</h2> <pre> <pubinfo> <pubdate type="primary"> <date> <year>2002</year> </date> </pubdate> <volume>63</volume> <issue>4</issue> <startpage>577</startpage> <endpage>85</endpage> </pubinfo> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>entry description</title> </head> <body> <h2>Description</h2> <p>The entry element is the wrapper for a single reference.</p> <p>The id attribute specifies a unique identifier provided by a database application.</p> <p>The type attribute specifies the type of the reference. The following types are supported:</p> <ul> <li>ABST: abstract reference</li> <li>ADVS: audiovisual material</li> <li>ART: art work</li> <li>BILL: bill/resolution</li> <li>BOOK: whole book reference</li> <li>CASE: case</li> <li>CHAP: book chapter reference</li> <li>COMP: computer program</li> <li>CONF: conference proceeding</li> <li>CTLG: catalog</li> <li>DATA: data file</li> <li>ELEC: electronic citation</li> <li>GEN: generic</li> <li>ICOMM: internet communication</li> <li>INPR: in press reference</li> <li>JFULL: journal - full</li> <li>JOUR: journal reference</li> <li>MAP: map</li> <li>MGZN: magazine article</li> <li>MPCT: motion picture</li> <li>MUSIC: music score</li> <li>NEWS: newspaper</li> <li>PAMP: pamphlet</li> <li>PAT: patent</li> <li>PCOMM: personal communication</li> <li>RPRT: report</li> <li>SER: serial - book, monograph</li> <li>SLIDE: slide</li> <li>SOUND: sound recording</li> <li>STAT: statute</li> <li>THES: thesis/dissertation</li> <li>UNBILL: unenacted bill/resolution</li> <li>UNPB: unpublished work reference</li> <li>VIDEO: video recording</li> </ul> <h2>Example</h2> <pre> <ris> <entry type="ABST" citekey="MILLER1999"> ... </entry> <entry type="BOOK" citekey="JONES2000"> ... </entry> </ris> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>firstname description</title> </head> <body> <h2>Description</h2> <p>The firstname element contains the first name of an author or editor.</p> <h2>Example</h2> <pre> <author> <lastname>Myers</lastname> <firstname>B</firstname> <middlename>B</middlename> <suffix>Jr.</suffix> </author> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>issue description</title> </head> <body> <h2>Description</h2> <p>The issue element specifies the issue of a periodical that an article appeared in.</p> <h2>Example</h2> <pre> <pubinfo> <pubdate type="primary"> <date> <year>2002</year> </date> </pubdate> <volume>63</volume> <issue>4</issue> <startpage>577</startpage> <endpage>85</endpage> </pubinfo> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>keyword description</title> </head> <body> <h2>Description</h2> <p>The keyword element holds a keyword or subject heading used as a search term in a database application.</p> <h2>Example</h2> <pre> <contents> <abstract>Dinosaurs were big animals that ate a lot</abstract> <keyword>dinosaurs</keyword> <keyword>evolution</keyword> <keyword>animals</keyword> </contents> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>lastname description</title> </head> <body> <h2>Description</h2> <p>The lastname element contains the last name (surname) of an author or editor.</p> <h2>Example</h2> <pre> <author> <lastname>Myers</lastname> <firstname>B</firstname> <middlename>B</middlename> <suffix>Jr.</suffix> </author> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>libinfo description</title> </head> <body> <h2>Description</h2> <p>The libinfo element is a wrapper for information specific to a particular user of a reference database system.</p> <p>The user attribute specifies the name of the user that provides this information. The name usually corresponds to the username of a particular database application.</p> <h2>Example</h2> <pre> <libinfo user="jdoe"> <notes>Not bad, after all</notes> <reprint status="INFILE"/> <availability type="useroot">palaeontology/dinosaurs/millera2002.pdf</availability> </libinfo> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>middlename description</title> </head> <body> <h2>Description</h2> <p>The middlename element contains the middle name or middle initial of an author or editor.</p> <h2>Example</h2> <pre> <author> <lastname>Myers</lastname> <firstname>B</firstname> <middlename>B</middlename> <suffix>Jr.</suffix> </author> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>misc description</title> </head> <body> <h2>Description</h2> <p>The misc element is an all-purpose element to store information not covered by the other elements. For reasons of consistency, a reference database administrator should figure out rules which kind of information should be stored in the misc element.</p> <p>The type element can be set to one of "1", "2", or "3", thus allowing to use 3 different misc elements per dataset.</p> <h2>Example</h2> <pre> <pubinfo> <pubdate type="primary"> <date> <year>1999</year> </date> </pubdate> <city>Sebastopol</city> <publisher>O'Reilly</publisher> <serial>1-56592-580-7</serial> <address>mi...@di...</address> <url>http://www.dinosaurs.upenn.edu/</url> <misc type="1">high</misc> </pubinfo> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>month description</title> </head> <body> <h2>Description</h2> <p>The month element holds the month information of a <a href="date.html">date</a> element. The month should be specified as a numeric value in the range of 1 through 12.</p> <h2>Example</h2> <pre> <pubdate type="primary"> <date> <year>1999</year> <month>11</month> <day>12</day> </date> </pubdate> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>name description</title> </head> <body> <h2>Description</h2> <p>The name element contains the name of an author or editor if it is not possible to further qualify name parts using the <a href="lastname.html">lastname</a>, <a href="firstname.html">firstname</a>, <a href="middlename.html">middlename</a>, and <a href="suffix.html">suffix</a> elements. Use the name element for corporate and institutional names as well.</p> <h2>Example</h2> <pre> <author> <name>Library of Congress</name> </author> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>notes description</title> </head> <body> <h2>Description</h2> <p>The notes element contains personal notes of a user.</p> <h2>Example</h2> <pre> <libinfo user="jdoe"> <notes>Not bad, after all</notes> <reprint status="INFILE"/> <availability type="useroot">palaeontology/dinosaurs/millera2002.pdf</availability> </libinfo> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>otherinfo description</title> </head> <body> <h2>Description</h2> <p>The otherinfo element holds additional information about the publication date.</p> <h2>Example</h2> <pre> <pubdate type="primary"> <date> <year>1999</year> </date> <otherinfo>Spring meeting</otherinfo> </pubdate> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>part description</title> </head> <body> <h2>Description</h2> <p>The part element contains the information related to a reference that is part of a published work. This corresponds to the analytical level of bibliographic information.</p> <h2>Example</h2> <pre> <entry type="CHAP" id="32" citekey="WALSH1999"> <part> <title>XML: Principles, Tools, and Techniques</title> <author> <lastname>Walsh</lastname> <firstname>N</firstname> </author> </part> <publication> <title>Guide to XML</title> <author> <lastname>Connolly</lastname> <firstname>D</firstname> </author> <pubinfo> <pubdate type="primary"> <date> <year>1999</year> </date> </pubdate> <city>Sebastopol</city> <publisher>O'Reilly</publisher> </pubinfo> </publication> <libinfo user="markus"><notes>Not bad</notes> <reprint status="NOTINFILE"/></libinfo> <contents><abstract>An introduction how to deal with XML</abstract> <keyword>XML</keyword> <keyword>computer</keyword> <keyword>markup languages</keyword> </contents> </entry> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>pubdate description</title> </head> <body> <h2>Description</h2> <p>The pubdate holds the information about the publication date.</p> <p>The type attribute can be set to either "primary" or "secondary".</p> <h2>Example</h2> <pre> <pubdate type="primary"> <date> <year>1999</year> </date> <otherinfo>Spring meeting</otherinfo> </pubdate> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>pubinfo description</title> </head> <body> <h2>Description</h2> <p>The pubinfo element is a wrapper for all bibliographic information of a <a href="publication.html">publication</a> element.</p> <h2>Example</h2> <pre> <pubinfo> <pubdate type="primary"> <date> <year>1999</year> </date> </pubdate> <city>Sebastopol</city> <publisher>O'Reilly</publisher> <serial>1-56592-580-7</serial> <address>mi...@di...</address> <url>http://www.dinosaurs.upenn.edu/</url> </pubinfo> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>publication description</title> </head> <body> <h2>Description</h2> <p>The publication element contains the information related to a published work. Roughly speaking, this is what you find on the shelf of a library. This corresponds to the monographic level of bibliographic information.</p> <h2>Example</h2> <pre> <entry type="CHAP" id="32" citekey="WALSH1999"> <part> <title>XML: Principles, Tools, and Techniques</title> <author> <lastname>Walsh</lastname> <firstname>N</firstname> </author> </part> <publication> <title>Guide to XML</title> <author> <lastname>Connolly</lastname> <firstname>D</firstname> </author> <pubinfo> <pubdate type="primary"> <date> <year>1999</year> </date> </pubdate> <city>Sebastopol</city> <publisher>O'Reilly</publisher> </pubinfo> </publication> <libinfo user="markus"><notes>Not bad</notes> <reprint status="NOTINFILE"/></libinfo> <contents><abstract>An introduction how to deal with XML</abstract> <keyword>XML</keyword> <keyword>computer</keyword> <keyword>markup languages</keyword> </contents> </entry> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>publisher description</title> </head> <body> <h2>Description</h2> <p>The publisher element contains the name of the publisher of a publication.</p> <h2>Example</h2> <pre> <pubinfo> <pubdate type="primary"> <date> <year>1999</year> </date> </pubdate> <city>Sebastopol</city> <publisher>O'Reilly</publisher> <serial>1-56592-580-7</serial> <address>mi...@di...</address> <url>http://www.dinosaurs.upenn.edu/</url> </pubinfo> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>reprint description</title> </head> <body> <h2>Description</h2> <p>The reprint element specifies the status of a reprint request.</p> <p>The status attribute can be set to one of "NOTINFILE", "ONREQUEST", or "INFILE" to specify that no local copy is available, that a reprint was requested, and that a local copy is available, respectively. In the case of "ONREQUEST", an optional <a href="date.html">date</a> element can be used to provide the date when the reprint was requested.</p> <h2>Example</h2> <pre> <libinfo user="jdoe"> <notes>Not bad, after all</notes> <reprint status="INFILE"/> <availability type="useroot">palaeontology/dinosaurs/millera2002.pdf</availability> </libinfo> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>ris description</title> </head> <body> <h2>Description</h2> <p>ris is a container for one or more <a href="entry.html">entry</a> elements. Each entry contains one complete bibliographic dataset.</p> <h2>Example</h2> <pre> <ris> <entry type="ABST" citekey="MILLER1999"> ... </entry> <entry type="BOOK" citekey="JONES2000"> ... </entry> </ris> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>serial description</title> </head> <body> <h2>Description</h2> <p>The serial element contains an ISSN or ISBN. These numbers are provided by the publisher in order to unambiguously identify a published work.</p> <h2>Example</h2> <pre> <pubinfo> <pubdate type="primary"> <date> <year>1999</year> </date> </pubdate> <city>Sebastopol</city> <publisher>O'Reilly</publisher> <serial>1-56592-580-7</serial> <address>mi...@di...</address> <url>http://www.dinosaurs.upenn.edu/</url> </pubinfo> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>set description</title> </head> <body> <h2>Description</h2> <p>The set element contains the information related to a series of published works. This corresponds to the series level of bibliographic information.</p> <h2>Example</h2> <pre> <entry type="BOOK" id="31" citekey="MILLER1999"> <publication> <title>My first book about dinosaurs</title> <author> <lastname>Miller</lastname> <firstname>A</firstname> </author> <author> <lastname>Myers</lastname> <firstname>B</firstname> <middlename>B</middlename> <suffix>Jr.</suffix> </author> <pubinfo> <pubdate type="primary"> <date> <year>1999</year> </date> </pubdate> <city>Sebastopol</city> <publisher>O'Reilly</publisher> <serial>1-56592-580-7</serial> <address>mi...@di...</address> <url>http://www.dinosaurs.upenn.edu/</url> </pubinfo> </publication> <set> <title>My first book series</title> <author> <lastname>Smith</lastname> <firstname>K</firstname> </author> </set> <libinfo user="markus"> <notes>Not bad, after all</notes> <reprint status="ONREQUEST"> <date> <year>2002</year> <month>2</month> <day>24</day> </date> </reprint> <availability type="useroot">palaeontology/dinosaurs/millera2002.pdf</availability> </libinfo> <contents> <abstract>Dinosaurs were big animals that ate a lot</abstract> <keyword>dinosaurs</keyword> <keyword>evolution</keyword> <keyword>animals</keyword> </contents> </entry> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>startpage description</title> </head> <body> <h2>Description</h2> <p>Journal and magazine articles are usually published on a range of pages. The startpage element specifies the first page of an article.</p> <h2>Example</h2> <pre> <pubinfo> <pubdate type="primary"> <date> <year>2002</year> </date> </pubdate> <volume>63</volume> <issue>4</issue> <startpage>577</startpage> <endpage>85</endpage> </pubinfo> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>suffix description</title> </head> <body> <h2>Description</h2> <p>The suffix element contains an optional suffix of an author or editor, such as "3rd", "Jr.".</p> <h2>Example</h2> <pre> <author> <lastname>Myers</lastname> <firstname>B</firstname> <middlename>B</middlename> <suffix>Jr.</suffix> </author> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>title description</title> </head> <body> <h2>Description</h2> <p>The title element contains the title of a <a href="part.html">part</a>, <a href="publication.html">publication</a>, or <a href="set.html">set</a> element.</p> <p>The type attribute should be set to "gen" for all titles except the names of periodicals. In that case, multiple titles can be specified and distinguished by the attribute values "abbrev", "full", "user1", "user2" to denote the official abbreviation of the periodical name (usually as specified by the Index Medicus), the full name, and up to two user-specified abbreviations, respectively.</p> <h2>Example</h2> <pre> <publication> <title type="abbrev">Biochem.Pharmacol.</title> <title type="full">Biochemical Pharmacology</title> <title type="user1">BP</title> <pubinfo> <pubdate type="primary"> <date> <year>2002</year> </date> </pubdate> <volume>63</volume> <issue>4</issue> <startpage>577</startpage> <endpage>85</endpage> </pubinfo> </publication> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>url description</title> </head> <body> <h2>Description</h2> <p>The url element holds the unique resource locator (URL) of an electronic version of the publication or of electronic information relevant to that publication.</p> <h2>Example</h2> <pre> <pubinfo> <pubdate type="primary"> <date> <year>1999</year> </date> </pubdate> <city>Sebastopol</city> <publisher>O'Reilly</publisher> <serial>1-56592-580-7</serial> <address>mi...@di...</address> <url>http://www.dinosaurs.upenn.edu/</url> </pubinfo> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>userdef description</title> </head> <body> <h2>Description</h2> <p>The userdef element is an all-purpose element to store information not covered by the other elements. For reasons of consistency, a reference database administrator should figure out rules which kind of information should be stored in the userdef element.</p> <p>The type element can be set to one of "1", "2", "3", "4", or "5", thus allowing to use 5 different userdef elements per dataset.</p> <h2>Example</h2> <pre> <pubinfo> <pubdate type="primary"> <date> <year>1999</year> </date> </pubdate> <city>Sebastopol</city> <publisher>O'Reilly</publisher> <serial>1-56592-580-7</serial> <address>mi...@di...</address> <url>http://www.dinosaurs.upenn.edu/</url> <userdef type="1">high</userdef> </pubinfo> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>volume description</title> </head> <body> <h2>Description</h2> <p>The volume element specifies the volume of a periodical that an article appeared in.</p> <h2>Example</h2> <pre> <pubinfo> <pubdate type="primary"> <date> <year>2002</year> </date> </pubdate> <volume>63</volume> <issue>4</issue> <startpage>577</startpage> <endpage>85</endpage> </pubinfo> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>year description</title> </head> <body> <h2>Description</h2> <p>The year element holds the year information of a <a href="date.html">date</a> element. The year should be specified as a numeric 4-digit value.</p> <h2>Example</h2> <pre> <pubdate type="primary"> <date> <year>1999</year> <month>11</month> <day>12</day> </date> </pubdate> </pre> </body> </html> |
|
From: Markus H. <mho...@us...> - 2005-10-18 20:02:52
|
Update of /cvsroot/refdb/refdb/doc/risx/ele-desc In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv14337/ele-desc Log Message: Directory /cvsroot/refdb/refdb/doc/risx/ele-desc added to the repository --> Using per-directory sticky tag `Release_0_9_5_stable' |
Update of /cvsroot/refdb/refdb/doc/citestylex/ele-desc In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv14210 Added Files: Tag: Release_0_9_5_stable abbreviatefirst.html abbreviatesubseq.html abstract.html address.html aempty.html apr.html asame.html aug.html authorlist.html authornames.html authoronly.html authorseps.html bibliotitle.html bibstyle.html citestyle.html citseparator.html citstyle.html dec.html feb.html firstsep.html following.html intextdef.html issue.html jan.html journalname.html jul.html jun.html link.html mar.html may.html misc.html months.html namefirst.html nameother.html notes.html nov.html oct.html pagerange.html pages.html preceeding.html pubdate.html publisher.html pubplace.html pubtype.html rangeseparator.html refnumber.html refstyle.html secondsep.html sep.html separator.html serial.html singlepage.html stylename.html styleset.html text.html textmultiple.html textsingle.html threeseps.html threesepseach.html threesepslast.html title.html twoseps.html userdef.html volume.html yearonly.html Log Message: initial version --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>ABBREVIATEFIRST description</title> </head> <body> <h2>Description</h2> <p>In certain cases it is not desired to render the whole list of authors, esp. in in-text citations. The ABBREVIATEFIRST element contains the string that is to be printed instead of the suppressed authors in the first citation of this reference in the text. <a href="abbreviatesubseq.html">ABBREVIATESUBSEQ</a> defines the string for all subsequent citations</p> <p>The MAXAUTHOR attribute denotes the maximum number of authors that should be displayed in the authorlist. Up to this limit, all authors will be rendered. Above this limit, the content of the element will be printed instead of the suppressed authors.</p> <p>The DISPLAYAUTHOR attribute denotes the number of authors that will actually be rendered if the total number of authors exceed the limit in MAXAUTHOR.</p> <h2>Example</h2> <pre> <AUTHORLIST role="PRIMARY"> <ABBREVIATEFIRST MAXAUTHOR="4" DISPLAYAUTHOR="3">, et al</ABBREVIATEFIRST> <ABBREVIATESUBSEQ MAXAUTHOR="4" DISPLAYAUTHOR="1">, et al</ABBREVIATESUBSEQ> ... </AUTHORLIST> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>ABBREVIATESUBSEQ description</title> </head> <body> <h2>Description</h2> <p>In certain cases it is not desired to render the whole list of authors, esp. in in-text citations. The <a href="abbreviatefirst.html">ABBREVIATEFIRST</a> element contains the string that is to be printed instead of the suppressed authors in the first citation of this reference in the text. ABBREVIATESUBSEQ defines the string for all subsequent citations</p> <p>The MAXAUTHOR attribute denotes the maximum number of authors that should be displayed in the authorlist. Up to this limit, all authors will be rendered. Above this limit, the content of the element will be printed instead of the suppressed authors.</p> <p>The DISPLAYAUTHOR attribute denotes the number of authors that will actually be rendered if the total number of authors exceed the limit in MAXAUTHOR.</p> <h2>Example</h2> <pre> <AUTHORLIST role="PRIMARY"> <ABBREVIATEFIRST MAXAUTHOR="4" DISPLAYAUTHOR="3">, et al</ABBREVIATEFIRST> <ABBREVIATESUBSEQ MAXAUTHOR="4" DISPLAYAUTHOR="1">, et al</ABBREVIATESUBSEQ> ... </AUTHORLIST> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>ABSTRACT description</title> </head> <body> <h2>Description</h2> <p>ABSTRACT describes how the abstract of a publication is to be rendered.</p> <p>The STYLE attribute gives the processing system a hint on how this element should be rendered. The styles BOLD, ITALIC, and ULINE are available, as well as all of their combinations. In addition to this, SUB and SUPER can be used to indicate subscripts and superscripts. NONE can be used to explicitly state that no special formatting is desired</p> <h2>Example</h2> <pre> <ABSTRACT> <PRECEEDING>, </PRECEEDING> </ABSTRACT> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>ADDRESS description</title> </head> <body> <h2>Description</h2> <p>ADDRESS describes how the contact address of a publication is to be rendered.</p> <p>The STYLE attribute gives the processing system a hint on how this element should be rendered. The styles BOLD, ITALIC, and ULINE are available, as well as all of their combinations. In addition to this, SUB and SUPER can be used to indicate subscripts and superscripts. NONE can be used to explicitly state that no special formatting is desired</p> <h2>Example</h2> <pre> <ADDRESS> <PRECEEDING>, </PRECEEDING> </ADDRESS> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>AEMPTY description</title> </head> <body> <h2>Description</h2> <p>AEMPTY defines a string that is to be printed if the author of a reference is unknown. If this element is missing, nothing will be printed instead of the author list. If this element is present but empty, the title will be printed.</p> <h2>Example</h2> <pre> <AUTHORLIST role="PRIMARY"> ... <AEMPTY>Anonymous</AEMPTY> ... </AUTHORLIST> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>APR description</title> </head> <body> <h2>Description</h2> <p>APR defines the full name, abbreviation, and three-letter abbreviation, if applicable, for the month April in the language of the publication.</p> <h2>Example</h2> <pre> <MONTHS> ... <APR FULL="April" ABBREV="Apr." THREELET="Apr"/> ... </MONTHS> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>ASAME description</title> </head> <body> <h2>Description</h2> <p>ASAME defines a string that is to be printed instead of the authorlist for subsequent references of the same author(s). This is obviously only useful for bibliographies sorted by author names. If the element is defined and empty, the processing system is expected to suppress the authorlist.</p> <h2>Example</h2> <pre> <AUTHORLIST role="PRIMARY"> ... <ASAME>----</ASAME> ... </AUTHORLIST> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>AUG description</title> </head> <body> <h2>Description</h2> <p>AUG defines the full name, abbreviation, and three-letter abbreviation, if applicable, for the month August in the language of the publication.</p> <h2>Example</h2> <pre> <MONTHS> ... <AUG FULL="August" ABBREV="Aug." THREELET="Aug"/> ... </MONTHS> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>AUTHORLIST description</title> </head> <body> <h2>Description</h2> <p>AUTHORLIST is a wrapper for the authors of a publication.</p> <p>The ROLE attribute defines the purpose of the authorlist. The value of the attribute can be:</p><ul> <li>PRIMARY: The authors that actually did the writing, e.g. the authors of an article, of a book chapter, or of a whole book.</li> <li>SECONDARY: The editors of a book or other publication that contains articles or chapters written by other authors.</li> <li>TERTIARY: The editors of a series of books.</li> <li>ALL: Use this value if it is uncertain which of the above informationi will be available. The processing application should test the availability of author data in the sequence primary, secondary, tertiary, and display the first information it encounters.</li> </ul> <p>The STYLE attribute gives the processing system a hint on how this element should be rendered. The styles BOLD, ITALIC, and ULINE are available, as well as all of their combinations. In addition to this, SUB and SUPER can be used to indicate subscripts and superscripts. NONE can be used to explicitly state that no special formatting is desired</p> <p>The ALTERNATESTYLE attribute serves a similar purpose, but is used if a reference has no author and the title is used in the position of the authorlist. The formatting may then differ from a regular authorlist.</p> <h2>Example</h2> <pre> <AUTHORLIST role="PRIMARY"> <FOLLOWING> </FOLLOWING> <ABBREVIATEFIRST MAXAUTHOR="256" DISPLAYAUTHOR="255">, et al</ABBREVIATEFIRST> <ABBREVIATESUBSEQ MAXAUTHOR="256" DISPLAYAUTHOR="255">, et al</ABBREVIATESUBSEQ> <AEMPTY>Anonymous</AEMPTY> <AUTHORSEPS> <TWOSEPS> and </TWOSEPS> <THREESEPS> <THREESEPSEACH>, </THREESEPSEACH> <THREESEPSLAST>, and </THREESEPSLAST> </THREESEPS> </AUTHORSEPS> <AUTHORNAMES> <NAMEFIRST NAMEORDER="LASTFIRSTMIDDLE" INITIALSTYLE="F.M." UPPERCASE="NONE"> <NAMEOTHER NAMEORDER="FIRSTMIDDLELAST" INITIALSTYLE="F.M." UPPERCASE="NONE"> </AUTHORNAMES> <TEXT> <TEXTSINGLE> <FOLLOWING>, </FOLLOWING> </TEXTSINGLE> <TEXTMULTIPLE> <FOLLOWING>, </FOLLOWING> </TEXTMULTIPLE> </TEXT> </AUTHORLIST> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>AUTHORNAMES description</title> </head> <body> <h2>Description</h2> <p>AUTHORNAMES is a wrapper for the name specification of authors. It holds the <a href="namefirst.html">NAMEFIRST</a> and <a href="nameother.html">NAMEOTHER</a> elements.</p> <h2>Example</h2> <pre> <AUTHORNAMES> <NAMEFIRST NAMEORDER="LASTFIRSTMIDDLE" INITIALSTYLE="F.M." UPPERCASE="NONE"> <NAMEOTHER NAMEORDER="FIRSTMIDDLELAST" INITIALSTYLE="F.M." UPPERCASE="NONE"> </AUTHORNAMES> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>AUTHORONLY description</title> </head> <body> <h2>Description</h2> <p>AUTHORONLY is the wrapper for the information that defines the appearance of an in-text citation that shows only the authors. It can have the same children as a <a href="pubtype.html">PUBTYPE</a> element. This element should be used in conjunction with the <a href="yearonly.html">YEARONLY</a> element to obtain a citation format that keeps the authors in the flow of the normal text, as shown in the following example sentence:</p> <p>... as was shown by Smith and Miller in a recent publication (2001).</p> <h2>Example</h2> <pre> <AUTHORONLY> <AUTHORLIST> <FOLLOWING>. </FOLLOWING> <ABBREVIATE MAXAUTHOR="4" DISPLAYAUTHOR="1" ROLE="ALL"> et al. </ABBREVIATE> <AUTHORSEPS> <TWOSEPS> and </TWOSEPS> <THREESEPS> <THREESEPSEACH>, </THREESEPSEACH> <THREESEPSLAST>, and </THREESEPSLAST> </THREESEPS> </AUTHORSEPS> <AUTHORNAMES> <NAMEFIRST NAMEORDER="LASTFIRSTMIDDLE" INITIALSTYLE="FIRSTSPCMIDDLE" UPPERCASE="NONE"> <NAMEOTHER NAMEORDER="LASTFIRSTMIDDLE" INITIALSTYLE="FIRSTSPCMIDDLE" UPPERCASE="NONE"> </AUTHORNAMES> <TEXT> <TEXTSINGLE> <FOLLOWING>, </FOLLOWING> </TEXTSINGLE> <TEXTMULTIPLE> <FOLLOWING>, </FOLLOWING> </TEXTMULTIPLE> </TEXT> </AUTHORLIST> </AUTHORONLY> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>AUTHORSEPS description</title> </head> <body> <h2>Description</h2> <p>AUTHORSEPS is a wrapper for the separators between authors. It holds the <a href="twoseps.html">TWOSEPS</a> and <a href="threeseps.html">THREESEPS</a> elements.</p> <h2>Example</h2> <pre> <AUTHORSEPS> <TWOSEPS> and </TWOSEPS> <THREESEPS> <THREESEPSEACH>, </THREESEPSEACH> <THREESEPSLAST>, and </THREESEPSLAST> </THREESEPS> </AUTHORSEPS> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>BIBLIOTITLE description</title> </head> <body> <h2>Description</h2> <p>BIBLIOTITLE specifies the string which is to be used as the header of the bibliography. It is not uncommon to use "Bibliography" here.</p> <h2>Example</h2> <pre> <CITSTYLE INTEXTSEQUENCE="AUTHORDATE"> <CITSEPARATOR>;</CITSEPARATOR> <RANGESEPARATOR>-</RANGESEPARATOR> <BIBLIOTITLE>Bibliography</BIBLIOTITLE> <INTEXTDEF> <REFNUMBER> </REFNUMBER> </INTEXTDEF> </CITSTYLE> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>BIBSTYLE description</title> </head> <body> <h2>Description</h2> <p>BIBSTYLE defines the general appearance of the bibliography.</p> <p>The BIBLIOSEQUENCE attribute specifies the sorting order of the references in the bibliography. Possible values are:</p><ul> <li>BASIS: The references appear in the sequence as they are first cited in the text</li> <li>BAUTHORDATE: The references are sorted by authornames and publication dates.</li> <li>BDATEASC: The references are sorted by date, older entries first.</li> <li>BDATEDESC: The references are sorted by date, older entries last.</li> </ul> <p>The BIBLIOFIRSTINDENT attribute can be used to specify the indentation of the first line of each reference in the bibliography listing, e.g. to create hanging indents.</p> <p>The BIBLIOBLOCKINDENT attribute does the same for the remaining lines of each reference.</p> <p>The FONTSIZE attribute sets the font size of the bibliography.</p> <h2>Example</h2> <pre> <BIBSTYLE BIBLIOSEQUENCE="BASIS"> <BIBLIOTITLE>Literatur</BIBLIOTITLE> <MONTHS> ... </MONTHS> </BIBSTYLE> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>CITESTYLE description</title> </head> <body> <h2>Description</h2> <p>CITESTYLE specifies the citation style and the bibliography style of a particular journal or other publication. The style consists of a <a href="citstyle.html">CITSTYLE</a> element to define the citation style, of a <a href="refstyle.html">REFSTYLE</a> element to define the bibliography style, and of a <a href="stylename.html">STYLENAME</a> element to provide a unique name for the style.</p> <h2>Example</h2> <pre> <CITESTYLE> <STYLENAME>Br.J.Chem.</STYLENAME> <REFSTYLE> <PUBTYPE TYPE="GEN"> ... </PUBTYPE> <PUBTYPE TYPE="JOUR"> ... </PUBTYPE> </REFSTYLE> <CITSTYLE INTEXTSEQUENCE="AUTHORDATE"> ... </CITSTYLE> </CITESTYLE> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>CITSEPARATOR description</title> </head> <body> <h2>Description</h2> <p>CITSEPARATOR specifies a string which separates multiple citations like in (Jones, 2000; James, 2001).</p> <h2>Example</h2> <pre> <CITSTYLE INTEXTSEQUENCE="AUTHORDATE"> <CITSEPARATOR>;</CITSEPARATOR> <RANGESEPARATOR>-</RANGESEPARATOR> <BIBLIOTITLE>Bibliography</BIBLIOTITLE> <INTEXTDEF> <REFNUMBER> <PRECEEDING>[</PRECEEDING> <FOLLOWING>]<FOLLOWING> </REFNUMBER> </INTEXTDEF> </CITSTYLE> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>CITSTYLE description</title> </head> <body> <h2>Description</h2> <p>CITSTYLE defines the in-text citation style of the bibliography.</p> <p>The STYLE attribute gives the processing system a hint on how this element should be rendered. The styles BOLD, ITALIC, and ULINE are available, as well as all of their combinations. In addition to this, SUB and SUPER can be used to indicate subscripts and superscripts. NONE can be used to explicitly state that no special formatting is desired</p> <p>The INTEXTSEQUENCE attribute specifies the sorting order of citations within a multiple in-text citation. The value can be one of the following:</p><ul> <li>ASIS: The citations appear in the sequence as they are cited in the text</li> <li>AUTHORDATE: The citations are sorted by authornames and publication dates.</li> <li>DATEASC: The citations are sorted by date, older entries first.</li> <li>DATEDESC: The citations are sorted by date, older entries last.</li> </ul> <h2>Example</h2> <pre> <CITSTYLE INTEXTSEQUENCE="AUTHORDATE" BIBLIOSEQUENCE="BASIS"> <CITSEPARATOR>;</CITSEPARATOR> <RANGESEPARATOR>-</RANGESEPARATOR> <INTEXTDEF> <REFNUMBER> <PRECEEDING>[</PRECEEDING> <FOLLOWING>]</FOLLOWING> </REFNUMBER> </INTEXTDEF> </CITSTYLE> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>DEC description</title> </head> <body> <h2>Description</h2> <p>DEC defines the full name, abbreviation, and three-letter abbreviation, if applicable, for the month December in the language of the publication.</p> <h2>Example</h2> <pre> <MONTHS> ... <DEC FULL="December" ABBREV="Dec." THREELET="Dec"/> </MONTHS> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>FEB description</title> </head> <body> <h2>Description</h2> <p>FEB defines the full name, abbreviation, and three-letter abbreviation, if applicable, for the month February in the language of the publication.</p> <h2>Example</h2> <pre> <MONTHS> ... <FEB FULL="February" ABBREV="Feb." THREELET="Feb"/> ... </MONTHS> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>FIRSTSEP description</title> </head> <body> <h2>Description</h2> <p>FIRSTSEP defines the first separator in a date entry. This is usually a slash or a dash or a period. The second separator, if applicable, is defined by <a href="secondsep.html">SECONDSEP</a></p> <h2>Example</h2> <pre> <PUBDATE FORMAT="YES" SEQUENCE="MDY" MONTHFORMAT="ARABICMONTH" DAYFORMAT="ARABICDAY" YEARFORMAT="FOURDIGIT" PADLEADINGZERO="NN" ROLE="PRIMARY"> <FIRSTSEP>/</FIRSTSEP> <SECONDSEP>/</SECONDSEP> <PRECEEDING></PRECEEDING> <FOLLOWING>. </FOLLOWING> </PUBDATE> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>FOLLOWING description</title> </head> <body> <h2>Description</h2> <p>All elements in <a href="pubtype.html">PUBTYPE</a> and equivalent wrappers can define strings that always precede (<a href="preceeding.html">PRECEEDING</a>) or follow the element. These may e.g. be punctuation characters or whitespace to separate the entries. In some cases the <a href="separator.html">SEPARATOR</a> element may be more appropriate.</p> <h2>Example</h2> <pre> <PUBDATE FORMAT="YES" SEQUENCE="MDY" MONTHFORMAT="ARABICMONTH" DAYFORMAT="ARABICDAY" YEARFORMAT="FOURDIGIT" PADLEADINGZERO="NN" ROLE="PRIMARY"> <FIRSTSEP>/</FIRSTSEP> <SECONDSEP>/</SECONDSEP> <FOLLOWING>. </FOLLOWING> </PUBDATE> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>INTEXTDEF description</title> </head> <body> <h2>Description</h2> <p>INTEXTDEF is the wrapper for the information that defines the appearance of the in-text citation. It can have the same children as a <a href="pubtype.html">PUBTYPE</a> element.</p> <h2>Example</h2> <pre> <INTEXTDEF> <AUTHORLIST> <FOLLOWING>. </FOLLOWING> <ABBREVIATE MAXAUTHOR="4" DISPLAYAUTHOR="1" ROLE="ALL"> et al. </ABBREVIATE> <AUTHORSEPS> <TWOSEPS> and </TWOSEPS> <THREESEPS> <THREESEPSEACH>, </THREESEPSEACH> <THREESEPSLAST>, and </THREESEPSLAST> </THREESEPS> </AUTHORSEPS> <AUTHORNAMES> <NAMEFIRST NAMEORDER="LASTFIRSTMIDDLE" INITIALSTYLE="FIRSTSPCMIDDLE" UPPERCASE="NONE"> <NAMEOTHER NAMEORDER="LASTFIRSTMIDDLE" INITIALSTYLE="FIRSTSPCMIDDLE" UPPERCASE="NONE"> </AUTHORNAMES> <TEXT> <TEXTSINGLE> <PRECEEDING></PRECEEDING> <FOLLOWING>, </FOLLOWING> </TEXTSINGLE> <TEXTMULTIPLE> <PRECEEDING></PRECEEDING> <FOLLOWING>, </FOLLOWING> </TEXTMULTIPLE> </TEXT> </AUTHORLIST> <PUBDATE FORMAT="YES" SEQUENCE="Y" MONTHFORMAT="ARABICMONTH" DAYFORMAT="ARABICDAY" YEARFORMAT="FOURDIGIT" PADLEADINGZERO="YY"> </PUBDATE> </INTEXTDEF> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>ISSUE description</title> </head> <body> <h2>Description</h2> <p>ISSUE describes how the issue information of a periodical is rendered. Most periodicals use the combination of journal name, volume, issue, and page(s) to identify a publication.</p> <p>The STYLE attribute gives the processing system a hint on how this element should be rendered. The styles BOLD, ITALIC, and ULINE are available, as well as all of their combinations. In addition to this, SUB and SUPER can be used to indicate subscripts and superscripts. NONE can be used to explicitly state that no special formatting is desired</p> <h2>Example</h2> <pre> <JOURNALNAME CASE="ASIS" DEFAULTTEXT="FULL" ALTERNATETEXT="AABBREV" PUNCTUATION="PERIOD"> <FOLLOWING> </FOLLOWING> </JOURNALNAME> <VOLUME STYLE="BOLD"> </VOLUME> <ISSUE> <PRECEEDING>(</PRECEEDING> <FOLLOWING>)</FOLLOWING> </ISSUE> <PAGES> <PRECEEDING>:</PRECEEDING> <FOLLOWING>,</FOLLOWING> <PAGERANGE TYPE="FULL"> </PAGERANGE> </PAGES> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>JAN description</title> </head> <body> <h2>Description</h2> <p>JAN defines the full name, abbreviation, and three-letter abbreviation, if applicable, for the month January in the language of the publication.</p> <h2>Example</h2> <pre> <MONTHS> <JAN FULL="January" ABBREV="Jan." THREELET="Jan"/> ... </MONTHS> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>JOURNALNAME description</title> </head> <body> <h2>Description</h2> <p>JOURNALNAME describes how the name of a periodical is rendered. Most periodicals use the combination of journal name, volume, issue, and page(s) to identify a publication.</p> <p>You can select with the CASE attribute whether the case of the letters should be standardized. By default ("ASIS"), no changes are made to the journal name string in the database. If necessary, all letters can be converted to uppercase ("UPPER") or lowercase ("LOWER").</p> <p>The DEFAULTTEXT attribute determines which form of the journal name should be printed, if available. If this form is not in the database, the formatting application should try the form given with the ALTERNATETEXT attribute.</p> <p>The PUNCTUATION attribute selects the punctuation after abbreviated words in the journal name, if applicable.</p> <p>The STYLE attribute gives the processing system a hint on how this element should be rendered. The styles BOLD, ITALIC, and ULINE are available, as well as all of their combinations. In addition to this, SUB and SUPER can be used to indicate subscripts and superscripts. NONE can be used to explicitly state that no special formatting is desired</p> <h2>Example</h2> <pre> <JOURNALNAME CASE="ASIS" DEFAULTTEXT="FULL" ALTERNATETEXT="AABBREV" PUNCTUATION="PERIOD"> <FOLLOWING> </FOLLOWING> </JOURNALNAME> <VOLUME STYLE="BOLD"> </VOLUME> <ISSUE> <PRECEEDING>(</PRECEEDING> <FOLLOWING>)</FOLLOWING> </ISSUE> <PAGES> <PRECEEDING>:</PRECEEDING> <FOLLOWING>,</FOLLOWING> <PAGERANGE TYPE="FULL"> </PAGERANGE> </PAGES> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>JUL description</title> </head> <body> <h2>Description</h2> <p>JUL defines the full name, abbreviation, and three-letter abbreviation, if applicable, for the month July in the language of the publication.</p> <h2>Example</h2> <pre> <MONTHS> ... <JUL FULL="July" ABBREV="Jul." THREELET="Jul"/> ... </MONTHS> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>JUN description</title> </head> <body> <h2>Description</h2> <p>JUN defines the full name, abbreviation, and three-letter abbreviation, if applicable, for the month June in the language of the publication.</p> <h2>Example</h2> <pre> <MONTHS> ... <JUN FULL="June" ABBREV="Jun." THREELET="Jun"/> ... </MONTHS> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>LINK description</title> </head> <body> <h2>Description</h2> <p>LINK describes how links and URLs of a publication are to be rendered.</p> <p>The ROLE attribute picks the contents to be printed. The allowed values and the corresponding RIS fields are:</p> <ul> <li>0: UR</li> <li>1: L1</li> <li>2: L2</li> <li>3: L3</li> <li>4: L4</li> </ul> <p>The STYLE attribute gives the processing system a hint on how this element should be rendered. The styles BOLD, ITALIC, and ULINE are available, as well as all of their combinations. In addition to this, SUB and SUPER can be used to indicate subscripts and superscripts. NONE can be used to explicitly state that no special formatting is desired</p> <h2>Example</h2> <pre> <LINK ROLE="0"> <PRECEEDING>, </PRECEEDING> </LINK> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>MAR description</title> </head> <body> <h2>Description</h2> <p>MAR defines the full name, abbreviation, and three-letter abbreviation, if applicable, for the month March in the language of the publication.</p> <h2>Example</h2> <pre> <MONTHS> ... <MAR FULL="March" ABBREV="Mar." THREELET="Mar"/> ... </MONTHS> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>MAY description</title> </head> <body> <h2>Description</h2> <p>MAY defines the full name, abbreviation, and three-letter abbreviation, if applicable, for the month May in the language of the publication.</p> <h2>Example</h2> <pre> <MONTHS> ... <MAY FULL="May" ABBREV="May" THREELET="May"/> ... </MONTHS> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>MISC description</title> </head> <body> <h2>Description</h2> <p>MISC describes how the MISC fields of a publication are to be rendered.</p> <p>The ROLE attribute picks the contents to be printed. The allowed values and the corresponding RIS fields are:</p> <ul> <li>1: M1</li> <li>2: M2</li> <li>3: M3</li> </ul> <p>The STYLE attribute gives the processing system a hint on how this element should be rendered. The styles BOLD, ITALIC, and ULINE are available, as well as all of their combinations. In addition to this, SUB and SUPER can be used to indicate subscripts and superscripts. NONE can be used to explicitly state that no special formatting is desired</p> <h2>Example</h2> <pre> <MISC ROLE="1"> <PRECEEDING>, </PRECEEDING> </MISC> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>MONTHS description</title> </head> <body> <h2>Description</h2> <p>MONTHS is a wrapper for the individual elements describing the name and abbreviations of month names in the language of the publication.</p> <h2>Example</h2> <pre> <MONTHS> ... <MAY FULL="May" ABBREV="May" THREELET="May"/> ... </MONTHS> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>NAMEFIRST description</title> </head> <body> <h2>Description</h2> <p>NAMEFIRST is an empty element whose attributes describe the formatting of the first author in an authorlist. The formatting of all subsequent authors is described by the <a href="nameother.html">NAMEOTHER</a> element.</p> <p>Use the NAMEORDER attribute to select the general sequence and appearance of lastname and other name parts.</p> <p>Use the INITIALSTYLE attribute to select if the first name and middle initial should be abbreviated and whether a period and a space should follow the abbreviated items.</p> <p>If the whole name or the last name should be rendered in uppercase, set the UPPERCASE attribute to "ALL" or "LASTNAME", respectively.</p> <h2>Example</h2> <pre> <AUTHORNAMES> <NAMEFIRST NAMEORDER="LASTFIRSTMIDDLE" INITIALSTYLE="F.M." UPPERCASE="NONE"> <NAMEOTHER NAMEORDER="FIRSTMIDDLELAST" INITIALSTYLE="F.M." UPPERCASE="NONE"> </AUTHORNAMES> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>NAMEOTHER description</title> </head> <body> <h2>Description</h2> <p>NAMEOTHER is an empty element whose attributes describe the formatting of all authors but the first in an authorlist. The formatting of the first author is described by the <a href="namefirst.html">NAMEFIRST</a> element.</p> <p>Use the NAMEORDER attribute to select the general sequence and appearance of lastname and other name parts.</p> <p>Use the INITIALSTYLE attribute to select if the first name and middle initial should be abbreviated and whether a period and a space should follow the abbreviated items.</p> <p>If the whole name or the last name should be rendered in uppercase, set the UPPERCASE attribute to "ALL" or "LASTNAME", respectively.</p> <h2>Example</h2> <pre> <AUTHORNAMES> <NAMEFIRST NAMEORDER="LASTFIRSTMIDDLE" INITIALSTYLE="F.M." UPPERCASE="NONE"> <NAMEOTHER NAMEORDER="FIRSTMIDDLELAST" INITIALSTYLE="F.M." UPPERCASE="NONE"> </AUTHORNAMES> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>NOTES description</title> </head> <body> <h2>Description</h2> <p>NOTES describes how the notes of a publication are to be rendered.</p> <p>The STYLE attribute gives the processing system a hint on how this element should be rendered. The styles BOLD, ITALIC, and ULINE are available, as well as all of their combinations. In addition to this, SUB and SUPER can be used to indicate subscripts and superscripts. NONE can be used to explicitly state that no special formatting is desired</p> <h2>Example</h2> <pre> <NOTES> <PRECEEDING>, </PRECEEDING> </NOTES> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>NOV description</title> </head> <body> <h2>Description</h2> <p>NOV defines the full name, abbreviation, and three-letter abbreviation, if applicable, for the month November in the language of the publication.</p> <h2>Example</h2> <pre> <MONTHS> ... <NOV FULL="November" ABBREV="Nov." THREELET="Nov"/> ... </MONTHS> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>OCT description</title> </head> <body> <h2>Description</h2> <p>OCT defines the full name, abbreviation, and three-letter abbreviation, if applicable, for the month October in the language of the publication.</p> <h2>Example</h2> <pre> <MONTHS> ... <OCT FULL="October" ABBREV="Oct." THREELET="Oct"/> ... </MONTHS> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>PAGERANGE description</title> </head> <body> <h2>Description</h2> <p>PAGERANGE describes how a range of page numbers is rendered. Journals differ in the way how the end page of a page range is formatted. Some omit it, others print the full end page, some strip the end page to the minimum number of digits necessary.</p> <p>Use the TYPE attribute to select the formatting of the end page.</p> <h2>Example</h2> <pre> <PAGES> <PRECEEDING>:</PRECEEDING> <FOLLOWING>,</FOLLOWING> <PAGERANGE TYPE="FULL"> </PAGERANGE> </PAGES> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>PAGES description</title> </head> <body> <h2>Description</h2> <p>PAGES describes how the page information of a periodical is rendered. Most periodicals use the combination of journal name, volume, issue, and page(s) to identify a publication.</p> <p>The STYLE attribute gives the processing system a hint on how this element should be rendered. The styles BOLD, ITALIC, and ULINE are available, as well as all of their combinations. In addition to this, SUB and SUPER can be used to indicate subscripts and superscripts. NONE can be used to explicitly state that no special formatting is desired</p> <h2>Example</h2> <pre> <JOURNALNAME CASE="ASIS" DEFAULTTEXT="FULL" ALTERNATETEXT="AABBREV" PUNCTUATION="PERIOD"> <FOLLOWING> </FOLLOWING> </JOURNALNAME> <VOLUME STYLE="BOLD"> </VOLUME> <ISSUE> <PRECEEDING>(</PRECEEDING> <FOLLOWING>)</FOLLOWING> </ISSUE> <PAGES> <PRECEEDING>:</PRECEEDING> <FOLLOWING>,</FOLLOWING> <PAGERANGE TYPE="FULL"> </PAGERANGE> </PAGES> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>PRECEEDING description</title> </head> <body> <h2>Description</h2> <p>All elements in <a href="pubtype.html">PUBTYPE</a> and <a href="intextdef.html">INTEXTDEF</a> can define strings that always precede or follow (<a href="following.html">FOLLOWING</a>) the element. These may e.g. be punctuation characters or whitespace to separate the entries. In some cases the <a href="separator.html">SEPARATOR</a> element may be more appropriate.</p> <h2>Example</h2> <pre> <JOURNALNAME CASE="ASIS" DEFAULTTEXT="FULL" ALTERNATETEXT="AABBREV" PUNCTUATION="PERIOD"> <FOLLOWING> </FOLLOWING> </JOURNALNAME> <VOLUME STYLE="BOLD"> </VOLUME> <ISSUE> <PRECEEDING>(</PRECEEDING> <FOLLOWING>)</FOLLOWING> </ISSUE> <PAGES> <PRECEEDING>:</PRECEEDING> <FOLLOWING>,</FOLLOWING> <PAGERANGE TYPE="FULL"> </PAGERANGE> </PAGES> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>PUBDATE description</title> </head> <body> <h2>Description</h2> <p>PUBDATE describes how the publication date is rendered. You can use the <a href="firstsep.html">FIRSTSEP</a> and <a href="secondsep.html">SECONDSEP</a> elements to specify the first and second separator, respectively, between day, month, and year, if applicable.</p> <p>Set the FORMAT attribute to "NO" to switch off all formatting. The publication date string will be printed as it was entered into the database.</p> <p>The SEQUENCE attribute selects where and whether at all day, month, and year should appear.</p> <p>The DAYFORMAT, MONTHFORMAT, and YEARFORMAT attributes specify the formatting of the day, month, and year parts, respectively.</p> <p>Set PADLEADINGZERO to "YY" if single-digit day and month numbers should be padded with a leading zero.</p> <p>Use the ROLE attribute to specify whether this element describes the primary or secondary date. The value of "ALL" indicates that the processing application should first try the primary date. If this information is not available, it should try the secondary date.</p> <p>The STYLE attribute selects the font formatting.</p> <h2>Example</h2> <pre> <PUBDATE FORMAT="YES" SEQUENCE="MDY" MONTHFORMAT="ARABICMONTH" DAYFORMAT="ARABICDAY" YEARFORMAT="FOURDIGIT" PADLEADINGZERO="YY" ROLE="PRIMARY"> <FOLLOWING>, </FOLLOWING> <FIRSTSEP>-</FIRSTSEP> <SECONDSEP>-</SECONDSEP> </PUBDATE> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>PUBLISHER description</title> </head> <body> <h2>Description</h2> <p>PUBLISHER describes how the publisher of a publication is to be rendered.</p> <p>The STYLE attribute gives the processing system a hint on how this element should be rendered. The styles BOLD, ITALIC, and ULINE are available, as well as all of their combinations. In addition to this, SUB and SUPER can be used to indicate subscripts and superscripts. NONE can be used to explicitly state that no special formatting is desired</p> <h2>Example</h2> <pre> <PUBLISHER> <PRECEEDING>, </PRECEEDING> </PUBLISHER> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>PUBPLACE description</title> </head> <body> <h2>Description</h2> <p>PUBPLACE describes how the city where a publication was published should be displayed.</p> <p>The STYLE attribute gives the processing system a hint on how this element should be rendered. The styles BOLD, ITALIC, and ULINE are available, as well as all of their combinations. In addition to this, SUB and SUPER can be used to indicate subscripts and superscripts. NONE can be used to explicitly state that no special formatting is desired</p> <h2>Example</h2> <pre> <PUBPLACE> <PRECEEDING>, </PRECEEDING> </PUBPLACE> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>PUBTYPE description</title> </head> <body> <h2>Description</h2> <p>PUBTYPE is a wrapper for all formatting information that pertains to a specific type of publication.</p> <p>Use the TYPE attribute to select the type of publication that this element describes. Each <a href="citestyle.html">CITESTYLE</a> element should contain at least a description of the type "GEN". This generic type is intended to be used by the formatting application if no specific information for the given publication type is defined.</p> <h2>Example</h2> <pre> <PUBTYPE> <AUTHORLIST> ... </AUTHORLIST> <PUBDATE> ... </PUBDATE> <JOURNALNAME> ... </JOURNALNAME> <VOLUME> ... </VOLUME> <PAGES> ... </PAGES> </PUBTYPE> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>RANGESEPARATOR description</title> </head> <body> <h2>Description</h2> <p>RANGESEPARATOR defines the separator that is used when a sequence of consecutively numbered citations is displayed as a range.</p> <h2>Example</h2> <pre> <CITSTYLE INTEXTSEQUENCE="AUTHORDATE" BIBLIOSEQUENCE="BASIS"> <CITSEPARATOR>;</CITSEPARATOR> <RANGESEPARATOR>-</RANGESEPARATOR> <BIBLIOTITLE>Bibliography</BIBLIOTITLE> <INTEXTDEF> <REFNUMBER; <PRECEEDING>[</PRECEEDING> <FOLLOWING>]</FOLLOWING> </REFNUMBER> </INTEXTDEF> </CITSTYLE> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>REFNUMBER description</title> </head> <body> <h2>Description</h2> <p>REFNUMBER describes the appearance of a reference number in the bibliography or the in-text citation. The presence of this element implies that the bibliography is numbered.</p> <p>The STYLE attribute gives the processing system a hint on how this element should be rendered. The styles BOLD, ITALIC, and ULINE are available, as well as all of their combinations. In addition to this, SUB and SUPER can be used to indicate subscripts and superscripts. NONE can be used to explicitly state that no special formatting is desired</p> <h2>Example</h2> <pre> <CITSTYLE INTEXTSEQUENCE="AUTHORDATE" BIBLIOSEQUENCE="BASIS"> <CITSEPARATOR>;</CITSEPARATOR> <RANGESEPARATOR>-</RANGESEPARATOR> <BIBLIOTITLE>Bibliography</BIBLIOTITLE> <INTEXTDEF> <REFNUMBER STYLE="BOLD"> <PRECEEDING>[</PRECEEDING> <FOLLOWING>]</FOLLOWING> </REFNUMBER> </INTEXTDEF> </CITSTYLE> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>REFSTYLE description</title> </head> <body> <h2>Description</h2> <p>REFSTYLE is a wrapper for all publication types that have a <a href="pubtype.html">PUBTYPE</a> element.</p> <h2>Example</h2> <pre> <CITESTYLE> <STYLENAME>J.Biol.Chem.</STYLENAME> <REFSTYLE> <PUBTYPE TYPE="GEN"> ... </PUBTYPE> <PUBTYPE TYPE="BOOK"> ... </PUBTYPE> <PUBTYPE TYPE="JOURNAL"> ... </PUBTYPE> </REFSTYLE> </CITESTYLE> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>SECONDSEP description</title> </head> <body> <h2>Description</h2> <p>SECONDSEP defines the second separator in a date entry, if applicable. This is usually a slash or a dash or a period. The first separator is defined by <a href="firstsep.html">FIRSTSEP</a></p> <h2>Example</h2> <pre> <PUBDATE FORMAT="YES" SEQUENCE="MDY" MONTHFORMAT="ARABICMONTH" DAYFORMAT="ARABICDAY" YEARFORMAT="FOURDIGIT" PADLEADINGZERO="NN" ROLE="PRIMARY"> <FIRSTSEP>/</FIRSTSEP> <SECONDSEP>/</SECONDSEP> <FOLLOWING>. </FOLLOWING> </PUBDATE> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>SEP description</title> </head> <body> <h2>Description</h2> <p>SEP defines the full name, abbreviation, and three-letter abbreviation, if applicable, for the month September in the language of the publication.</p> <h2>Example</h2> <pre> <MONTHS> ... <SEP FULL="September" ABBREV="Sep." THREELET="Sep"/> ... </MONTHS> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>SEPARATOR description</title> </head> <body> <h2>Description</h2> <p>The SEPARATOR is an alternative to <a href="preceeding.html">PRECEEDING</a> and <a href="following.html">FOLLOWING</a> for introducing punctuation characters, whitespace, or short strings. While PRECEEDING and FOLLOWING are children of the elements to be formatted and appear only if the element itself is present, SEPARATOR is a separate element. Use separator in cases where a string has to appear at a certain position even if it is possible that the adjacent elements are missing.</p> <h2>Example</h2> <pre> <PAGES> <PRECEEDING>, </PRECEEDING> <PAGERANGE TYPE="FULL"> </PAGERANGE> </PAGES> <SEPARATOR>. </SEPARATOR> <PUBDATE FORMAT="NO" SEQUENCE="Y" MONTHFORMAT="ARABICMONTH" DAYFORMAT="ARABICDAY" YEARFORMAT="FOURDIGIT" PADLEADINGZERO="NN" ROLE="PRIMARY"> <FOLLOWING>. </FOLLOWING> </PUBDATE> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>SERIAL description</title> </head> <body> <h2>Description</h2> <p>SERIAL describes how the serial number (like an ISSN or ISBN) of a publication are to be rendered.</p> <p>The STYLE attribute gives the processing system a hint on how this element should be rendered. The styles BOLD, ITALIC, and ULINE are available, as well as all of their combinations. In addition to this, SUB and SUPER can be used to indicate subscripts and superscripts. NONE can be used to explicitly state that no special formatting is desired</p> <h2>Example</h2> <pre> <SERIAL> <PRECEEDING>, </PRECEEDING> </SERIAL> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>SINGLEPAGE description</title> </head> <body> <h2>Description</h2> <p>SINGLEPAGE describes how the start page number is rendered if no end page is available. The appearance of the end page (if there is one) is described by the <a href="pagerange.html">PAGERANGE</a> element.</p> <h2>Example</h2> <pre> <PAGES> <PRECEEDING>:</PRECEEDING> <SINGLEPAGE> <FOLLOWING>,</FOLLOWING> <PAGERANGE TYPE="STARTONLY"> </PAGERANGE> </PAGES> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>STYLENAME description</title> </head> <body> <h2>Description</h2> <p>STYLENAME defines an unique name for the bibliography file defined in the parent <a href="citestyle.html">CITESTYLE</a> element.</p> <h2>Example</h2> <pre> <CITESTYLE> <STYLENAME>J.Biol.Chem.</STYLENAME> ... </CITESTYLE> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>STYLESET description</title> </head> <body> <h2>Description</h2> <p>The STYLESET element is a wrapper to keep several <a href="citestyle.html">CITESTYLE</a> elements in a single document.</p> <h2>Example</h2> <pre> <STYLESET> <CITESTYLE> ... </CITESTYLE> <CITESTYLE> ... </CITESTYLE> </STYLESET> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>TEXT description</title> </head> <body> <h2>Description</h2> <p>TEXT is a wrapper for the <a href="textsingle.html">TEXTSINGLE</a> and the <a href="textmultiple.html">TEXTMULTIPLE</a> elements which govern the preceeding and following strings of single and multiple authors.</p> <h2>Example</h2> <pre> <AUTHORLIST ROLE="PRIMARY"> <FOLLOWING> </FOLLOWING> <ABBREVIATEFIRST MAXAUTHOR="256" DISPLAYAUTHOR="255">, et al</ABBREVIATEFIRST> <ABBREVIATESUBSEQ MAXAUTHOR="256" DISPLAYAUTHOR="255">, et al</ABBREVIATESUBSEQ> <AEMPTY>Anonymous</AEMPTY> <AUTHORSEPS> <TWOSEPS> and </TWOSEPS> <THREESEPS> <THREESEPSEACH>, </THREESEPSEACH> <THREESEPSLAST>, and </THREESEPSLAST> </THREESEPS> </AUTHORSEPS> <AUTHORNAMES> <NAMEFIRST NAMEORDER="LASTFIRSTMIDDLE" INITIALSTYLE="F.M." UPPERCASE="NONE"> <NAMEOTHER NAMEORDER="FIRSTMIDDLELAST" INITIALSTYLE="F.M." UPPERCASE="NONE"> </AUTHORNAMES> <TEXT> <TEXTSINGLE> <FOLLOWING>, </FOLLOWING> </TEXTSINGLE> <TEXTMULTIPLE> <FOLLOWING>, </FOLLOWING> </TEXTMULTIPLE> </TEXT> </AUTHORLIST> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>TEXTMULTIPLE description</title> </head> <body> <h2>Description</h2> <p>TEXTMULTIPLE is a wrapper for the <a href="preceeding.html">preceeding</a> and the <a href="following.html">following</a> elements which govern the preceeding and following strings of multiple authors.</p> <h2>Example</h2> <pre> <AUTHORLIST ROLE="PRIMARY"> <FOLLOWING> </FOLLOWING> <ABBREVIATEFIRST MAXAUTHOR="256" DISPLAYAUTHOR="255">, et al</ABBREVIATEFIRST> <ABBREVIATESUBSEQ MAXAUTHOR="256" DISPLAYAUTHOR="255">, et al</ABBREVIATESUBSEQ> <AEMPTY>Anonymous</AEMPTY> <AUTHORSEPS> <TWOSEPS> and </TWOSEPS> <THREESEPS> <THREESEPSEACH>, </THREESEPSEACH> <THREESEPSLAST>, and </THREESEPSLAST> </THREESEPS> </AUTHORSEPS> <AUTHORNAMES> <NAMEFIRST NAMEORDER="LASTFIRSTMIDDLE" INITIALSTYLE="F.M." UPPERCASE="NONE"> <NAMEOTHER NAMEORDER="FIRSTMIDDLELAST" INITIALSTYLE="F.M." UPPERCASE="NONE"> </AUTHORNAMES> <TEXT> <TEXTSINGLE> <FOLLOWING>, </FOLLOWING> </TEXTSINGLE> <TEXTMULTIPLE> <FOLLOWING>, </FOLLOWING> </TEXTMULTIPLE> </TEXT> </AUTHORLIST> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>TEXTSINGLE description</title> </head> <body> <h2>Description</h2> <p>TEXTSINGLE is a wrapper for the <a href="preceeding.html">preceeding</a> and the <a href="following.html">following</a> elements which govern the preceeding and following strings of a single author.</p> <h2>Example</h2> <pre> <AUTHORLIST ROLE="PRIMARY"> <FOLLOWING> </FOLLOWING> <ABBREVIATEFIRST MAXAUTHOR="256" DISPLAYAUTHOR="255">, et al</ABBREVIATEFIRST> <ABBREVIATESUBSEQ MAXAUTHOR="256" DISPLAYAUTHOR="255">, et al</ABBREVIATESUBSEQ> <AEMPTY>Anonymous</AEMPTY> <AUTHORSEPS> <TWOSEPS> and </TWOSEPS> <THREESEPS> <THREESEPSEACH>, </THREESEPSEACH> <THREESEPSLAST>, and </THREESEPSLAST> </THREESEPS> </AUTHORSEPS> <AUTHORNAMES> <NAMEFIRST NAMEORDER="LASTFIRSTMIDDLE" INITIALSTYLE="F.M." UPPERCASE="NONE"> <NAMEOTHER NAMEORDER="FIRSTMIDDLELAST" INITIALSTYLE="F.M." UPPERCASE="NONE"> </AUTHORNAMES> <TEXT> <TEXTSINGLE> <FOLLOWING>, </FOLLOWING> </TEXTSINGLE> <TEXTMULTIPLE> <FOLLOWING>, </FOLLOWING> </TEXTMULTIPLE> </TEXT> </AUTHORLIST> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>THREESEPS description</title> </head> <body> <h2>Description</h2> <p>THREESEPS is a wrapper for the strings to be printed between authors if three or more authors are in the <a href="authorlist.html">authorlist</a>.</p> <h2>Example</h2> <pre> <AUTHORLIST ROLE="PRIMARY"> <FOLLOWING> </FOLLOWING> <ABBREVIATEFIRST MAXAUTHOR="256" DISPLAYAUTHOR="255">, et al</ABBREVIATEFIRST> <ABBREVIATESUBSEQ MAXAUTHOR="256" DISPLAYAUTHOR="255">, et al</ABBREVIATESUBSEQ> <AEMPTY>Anonymous</AEMPTY> <AUTHORSEPS> <TWOSEPS> and </TWOSEPS> <THREESEPS> <THREESEPSEACH>, </THREESEPSEACH> <THREESEPSLAST>, and </THREESEPSLAST> </THREESEPS> </AUTHORSEPS> <AUTHORNAMES> <NAMEFIRST NAMEORDER="LASTFIRSTMIDDLE" INITIALSTYLE="F.M." UPPERCASE="NONE"> <NAMEOTHER NAMEORDER="FIRSTMIDDLELAST" INITIALSTYLE="F.M." UPPERCASE="NONE"> </AUTHORNAMES> <TEXT> <TEXTSINGLE> <FOLLOWING>, </FOLLOWING> </TEXTSINGLE> <TEXTMULTIPLE> <FOLLOWING>, </FOLLOWING> </TEXTMULTIPLE> </TEXT> </AUTHORLIST> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>THREESEPSEACH description</title> </head> <body> <h2>Description</h2> <p>THREESEPSEACH defines the strings to be printed between all but the last pair of authors in the <a href="authorlist.html">authorlist</a> if three or more authors are in this list.</p> <h2>Example</h2> <pre> <AUTHORLIST ROLE="PRIMARY"> <FOLLOWING> </FOLLOWING> <ABBREVIATEFIRST MAXAUTHOR="256" DISPLAYAUTHOR="255">, et al</ABBREVIATEFIRST> <ABBREVIATESUBSEQ MAXAUTHOR="256" DISPLAYAUTHOR="255">, et al</ABBREVIATESUBSEQ> <AEMPTY>Anonymous</AEMPTY> <AUTHORSEPS> <TWOSEPS> and </TWOSEPS> <THREESEPS> <THREESEPSEACH>, </THREESEPSEACH> <THREESEPSLAST>, and </THREESEPSLAST> </THREESEPS> </AUTHORSEPS> <AUTHORNAMES> <NAMEFIRST NAMEORDER="LASTFIRSTMIDDLE" INITIALSTYLE="F.M." UPPERCASE="NONE"> <NAMEOTHER NAMEORDER="FIRSTMIDDLELAST" INITIALSTYLE="F.M." UPPERCASE="NONE"> </AUTHORNAMES> <TEXT> <TEXTSINGLE> <FOLLOWING>, </FOLLOWING> </TEXTSINGLE> <TEXTMULTIPLE> <FOLLOWING>, </FOLLOWING> </TEXTMULTIPLE> </TEXT> </AUTHORLIST> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>THREESEPSLAST description</title> </head> <body> <h2>Description</h2> <p>THREESEPSLAST defines the string to be printed between the last pair of authors in the <a href="authorlist.html">authorlist</a> if three or more authors are in this list.</p> <h2>Example</h2> <pre> <AUTHORLIST ROLE="PRIMARY"> <FOLLOWING> </FOLLOWING> <ABBREVIATEFIRST MAXAUTHOR="256" DISPLAYAUTHOR="255">, et al</ABBREVIATEFIRST> <ABBREVIATESUBSEQ MAXAUTHOR="256" DISPLAYAUTHOR="255">, et al</ABBREVIATESUBSEQ> <AEMPTY>Anonymous</AEMPTY> <AUTHORSEPS> <TWOSEPS> and </TWOSEPS> <THREESEPS> <THREESEPSEACH>, </THREESEPSEACH> <THREESEPSLAST>, and </THREESEPSLAST> </THREESEPS> </AUTHORSEPS> <AUTHORNAMES> <NAMEFIRST NAMEORDER="LASTFIRSTMIDDLE" INITIALSTYLE="F.M." UPPERCASE="NONE"> <NAMEOTHER NAMEORDER="FIRSTMIDDLELAST" INITIALSTYLE="F.M." UPPERCASE="NONE"> </AUTHORNAMES> <TEXT> <TEXTSINGLE> <FOLLOWING>, </FOLLOWING> </TEXTSINGLE> <TEXTMULTIPLE> <FOLLOWING>, </FOLLOWING> </TEXTMULTIPLE> </TEXT> </AUTHORLIST> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>TITLE description</title> </head> <body> <h2>Description</h2> <p>TITLE describes how the title of a publication is rendered.</p> <p>The CASE attribute determines whether the case of the title string remains unchanged ("ASIS") or is converted to all uppercase ("UPPER") or all lowercase ("LOWER").</p> <p>The STYLE attribute gives the processing system a hint on how this element should be rendered. The styles BOLD, ITALIC, and ULINE are available, as well as all of their combinations. In addition to this, SUB and SUPER can be used to indicate subscripts and superscripts. NONE can be used to explicitly state that no special formatting is desired.</p> <p>The ROLE attribute decides whether this element pertains to an article/book chapter/book title ("PRIMARY"), to a book title in a chapter reference ("SECONDARY"), or to a series title ("TERTIARY"). Use the value "ALL" if it is not certain which of the data are available. The processing application should try in the mentioned order.</p> <h2>Example</h2> <pre> <TITLE CASE="ASIS" ROLE="PRIMARY"> <FOLLOWING>. </FOLLOWING> </TITLE> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>TWOSEPS description</title> </head> <body> <h2>Description</h2> <p>TWOSEPS defines the string to be printed between authors if exactly two authors are in the <a href="authorlist.html">authorlist</a>.</p> <h2>Example</h2> <pre> <AUTHORLIST ROLE="PRIMARY"> <FOLLOWING> </FOLLOWING> <ABBREVIATEFIRST MAXAUTHOR="256" DISPLAYAUTHOR="255">, et al</ABBREVIATEFIRST> <ABBREVIATESUBSEQ MAXAUTHOR="256" DISPLAYAUTHOR="255">, et al</ABBREVIATESUBSEQ> <AEMPTY>Anonymous</AEMPTY> <AUTHORSEPS> <TWOSEPS> and </TWOSEPS> <THREESEPS> <THREESEPSEACH>, </THREESEPSEACH> <THREESEPSLAST>, and </THREESEPSLAST> </THREESEPS> </AUTHORSEPS> <AUTHORNAMES> <NAMEFIRST NAMEORDER="LASTFIRSTMIDDLE" INITIALSTYLE="F.M." UPPERCASE="NONE"> <NAMEOTHER NAMEORDER="FIRSTMIDDLELAST" INITIALSTYLE="F.M." UPPERCASE="NONE"> </AUTHORNAMES> <TEXT> <TEXTSINGLE> <FOLLOWING>, </FOLLOWING> </TEXTSINGLE> <TEXTMULTIPLE> <FOLLOWING>, </FOLLOWING> </TEXTMULTIPLE> </TEXT> </AUTHORLIST> </pre> </body> </html> --- NEW FILE --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>USERDEF description</title> </head> <body> <h2>Description</h2> <p>USERDEF describes how the USERDEF fields of a publication are to be rendered.</p> <p>The ROLE attribute picks the contents to be printed. The allowed values and the corresponding RIS fields are:</p> <ul> <li>1: U1</li> <li>2: U2</li> <li>3: U3</li> <li>4: U4</li> <li>5: U5</li> </ul> <p>The STYLE attribute gives the processing system a hint on how this element should be rendered. The styles BOLD, ITALIC, and ULINE are available, as well as all of their combinations. In addition to this, SUB and SUPER can be used to indicate subscripts and superscripts. NONE can be u... [truncated message content] |
|
From: Markus H. <mho...@us...> - 2005-10-18 20:01:41
|
Update of /cvsroot/refdb/refdb/doc/citestylex/ele-desc In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv14057/ele-desc Log Message: Directory /cvsroot/refdb/refdb/doc/citestylex/ele-desc added to the repository --> Using per-directory sticky tag `Release_0_9_5_stable' |
|
From: Markus H. <mho...@us...> - 2005-10-18 20:01:16
|
Update of /cvsroot/refdb/refdb/doc/risx In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv13932/risx Log Message: Directory /cvsroot/refdb/refdb/doc/risx added to the repository --> Using per-directory sticky tag `Release_0_9_5_stable' |
|
From: Markus H. <mho...@us...> - 2005-10-18 20:01:16
|
Update of /cvsroot/refdb/refdb/doc/citestylex In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv13932/citestylex Log Message: Directory /cvsroot/refdb/refdb/doc/citestylex added to the repository --> Using per-directory sticky tag `Release_0_9_5_stable' |
|
From: Markus H. <mho...@us...> - 2005-10-18 20:00:53
|
Update of /cvsroot/refdb/refdb/doc In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv13823 Modified Files: Tag: Release_0_9_5_stable Makefile.am Log Message: build dtd documentation Index: Makefile.am =================================================================== RCS file: /cvsroot/refdb/refdb/doc/Attic/Makefile.am,v retrieving revision 1.1.2.4 retrieving revision 1.1.2.5 diff -u -U2 -r1.1.2.4 -r1.1.2.5 --- Makefile.am 2 Oct 2005 23:34:20 -0000 1.1.2.4 +++ Makefile.am 18 Oct 2005 20:00:45 -0000 1.1.2.5 @@ -15,10 +15,10 @@ html_extra_files = manual.css $(png_images) -EXTRA_DIST = $(doc_DATA) $(manual_sources) $(html_extra_files) $(svg_images) +EXTRA_DIST = $(doc_DATA) $(manual_sources) $(html_extra_files) $(svg_images) citestylex risx -all: refdb-manual.pdf refdb-manual/* +all: refdb-manual.pdf refdb-manual/* citestylex/elements.html risx/elements.html -refdb-manual-statustable.sgml: ../scripts/statgen.pl - ../scripts/statgen.pl docbook > refdb-manual-statustable.sgml +refdb-manual-statustable.sgml: $(top_srcdir)/scripts/statgen.pl + $(top_srcdir)/scripts/statgen.pl docbook > refdb-manual-statustable.sgml $(pdf_images): %.pdf: %.svg @@ -39,7 +39,23 @@ @echo "Creating HTML manual..."; rm -rf refdb-manual/* - mkdir -p refdb-manual && cd refdb-manual && openjade -t sgml -d ../include/doc-html.dsl $(sgml_decl) ../refdb-manual.sgml + mkdir -p refdb-manual && cd refdb-manual && openjade -t sgml -d $(top_srcdir)/doc/include/doc-html.dsl $(sgml_decl) $(top_srcdir)/doc/refdb-manual.sgml cp $(html_extra_files) refdb-manual/ +citestylex.xml: $(top_srcdir)/dtd/citestylex.dtd +# dtdparse does not grok CATALOG directives, therefore we have to temporarily +# disable all entries in SGML_CATALOG_FILES + SGML_CATALOG_FILES="" dtdparse --title "citestyle XML DTD" --output citestylex.xml --declaration $(top_srcdir)/declarations/xml.dcl --system-id "http://refdb.sourceforge.net/dtd/citestylex.dtd" $(top_srcdir)/dtd/citestylex.dtd + +citestylex/elements.html: citestylex.xml + dtdformat --html citestylex.xml + $(top_srcdir)/scripts/dtdparseweave citestylex + +risx.xml: $(top_srcdir)/dtd/risx.dtd + SGML_CATALOG_FILES="" dtdparse --title "risx XML DTD" --output risx.xml --declaration $(top_srcdir)/declarations/xml.dcl --system-id "http://refdb.sourceforge.net/dtd/risx.dtd" $(top_srcdir)/dtd/risx.dtd + +risx/elements.html: risx.xml + dtdformat --html risx.xml + $(top_srcdir)/scripts/dtdparseweave risx + distclean: clean rm -f refdb-manual.pdf refdb-manual.tex refdb-manual.aux refdb-manual.log refdb-manual.out @@ -47,4 +63,9 @@ rm -f $(png_images) rm -f $(pdf_images) + rm -f citestylex.xml risx.xml + rm -f citestylex/*.html + rm -rf citestylex/dtdelem citestylex/dtdent citestylex/elements citestylex/entities citestylex/notations + rm -f risx/*.html + rm -rf risx/dtdelem risx/dtdent risx/elements risx/entities risx/notations # this can't be kosher... |
|
From: Markus H. <mho...@us...> - 2005-10-18 20:00:30
|
Update of /cvsroot/refdb/refdb/scripts In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv13716 Modified Files: Tag: Release_0_9_5_stable Makefile.am Log Message: added dtdparseweave Index: Makefile.am =================================================================== RCS file: /cvsroot/refdb/refdb/scripts/Makefile.am,v retrieving revision 1.23.2.8 retrieving revision 1.23.2.9 diff -u -U2 -r1.23.2.8 -r1.23.2.9 --- Makefile.am 13 Oct 2005 20:06:47 -0000 1.23.2.8 +++ Makefile.am 18 Oct 2005 20:00:19 -0000 1.23.2.9 @@ -3,5 +3,5 @@ bin_SCRIPTS = @server_scripts@ @client_scripts@ -EXTRA_DIST=refdb.in refdbjade.in runbib.in refdb_tex2mail db2ris.in refdb-bug.in refdbxml.in refdb refdbctl.in empty.mysql.dump empty.pgsql.dump.in refdb-upgrade.sql marc2ris.in med2ris.in en2ris.in refdbnd.in vargen.pl libgen.pl statgen.pl refdb_dos2unix.in migrate_mysql_0.9.5 refdb.dump.mysql.in refdb.dump.mysql41.in refdb.dump.pgsql.in refdb.dump.sqlite.in refdb-ms +EXTRA_DIST=refdb.in refdbjade.in runbib.in refdb_tex2mail db2ris.in refdb-bug.in refdbxml.in refdb refdbctl.in empty.mysql.dump empty.pgsql.dump.in refdb-upgrade.sql marc2ris.in med2ris.in en2ris.in refdbnd.in vargen.pl libgen.pl statgen.pl refdb_dos2unix.in migrate_mysql_0.9.5 refdb.dump.mysql.in refdb.dump.mysql41.in refdb.dump.pgsql.in refdb.dump.sqlite.in refdb-ms dtdparseweave MOSTLYCLEANFILES=refdb refdbjade runbib db2ris refdbxml refdbctl refdb-bug refdbnd marc2ris med2ris en2ris refdb_dos2unix refdb.dump.mysql refdb.dump.mysql41 refdb.dump.pgsql refdb.dump.sqlite |
|
From: Markus H. <mho...@us...> - 2005-10-18 20:00:03
|
Update of /cvsroot/refdb/refdb/scripts In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv13454 Added Files: Tag: Release_0_9_5_stable dtdparseweave Log Message: initial version --- NEW FILE --- #!/bin/sh # dtdparseweave - weaves manually edited descriptions into the machine-generated dtdparse output files. # Markus Hoenicka 1999-08-16 # $Id: dtdparseweave,v 1.1.2.1 2005/10/18 19:59:53 mhoenicka Exp $ # initialize variables VERBOSE=f # scan options while getopts ":hv" opt; do case $opt in h ) echo 1>&2 "USAGE: dtdparseweave [-h] [-v] dirname" echo 1>&2 "Weaves hand-coded fragments into dtdparse-generated output." echo 1>&2 "Command-line options:" echo 1>&2 "-h: invokes this help text" echo 1>&2 "-v: verbose" exit 0 ;; v ) VERBOSE=t;; \? ) echo 'usage: dtdparseweave [-h] [-v] dirname' exit 1 ;; esac done # correct the index so the filename argument is always $1 shift $(($OPTIND - 1)) # test for correct number of arguments; should be exactly one directory name if [ $# -ne 1 ]; then echo 1>&2 "Usage: dtdparseweave [-h] [-v] dirname" echo 1>&2 "type dtdparseweave -h to show help" exit 127 fi # test for the existence and accessibility of the specified directory if [ ! -d $1 ]; then echo 1>&2 "$1 does not exist or cannot be accessed." exit 1 fi # copy the dtdparse-generated files to a different folder cp -r $1/elements $1/olements cd $1/ele-desc for filename in *.html; do if [ $VERBOSE = t ]; then echo "weaving $filename ..." fi # extract first part of dtdparse-generated file sgrep '"<HTML>".."<H2>Description</H2>"' ../olements/$filename > $$.tmp # extract description sgrep '"<h2>Description</h2>"__"<h2>Example</h2>"' $filename >> $$.tmp # extract second part of dtdparse-generated file sgrep '"<H2>Description</H2>"__"<P></P>"' ../olements/$filename >> $$.tmp # extract example sgrep '"<h2>Example</h2>"._"</body>"' $filename >> $$.tmp # extract third part of dtdparse-generated file sgrep '"<P></P>".."</HTML>"' ../olements/$filename >> $$.tmp # make it look nice tidy -q < $$.tmp > ../elements/$filename done # clean up rm $$.tmp rm -r ../olements # jump back to origin cd - exit 0 |
|
From: Markus H. <mho...@us...> - 2005-10-18 19:59:28
|
Update of /cvsroot/refdb/refdb In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv13303 Modified Files: Tag: Release_0_9_5_stable configure.in Log Message: added tests for dtd doc build tools Index: configure.in =================================================================== RCS file: /cvsroot/refdb/refdb/configure.in,v retrieving revision 1.49.2.20 retrieving revision 1.49.2.21 diff -u -U2 -r1.49.2.20 -r1.49.2.21 --- configure.in 17 Oct 2005 18:09:31 -0000 1.49.2.20 +++ configure.in 18 Oct 2005 19:59:19 -0000 1.49.2.21 @@ -180,4 +180,11 @@ fi +if test "$ac_docs" = "YES"; then +AC_PATH_PROGS(mydtdparse, dtdparse) +AC_PATH_PROGS(mydtdformat, dtdformat) +AC_PATH_PROGS(mysgrep, sgrep) +AC_PATH_PROGS(mytidy, tidy) +fi + dnl dnl Checks for libraries. |
Update of /cvsroot/refdb/refdb/man In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv14657 Added Files: Tag: Release_0_9_5_stable Makefile.am RefDB.7.in bib2ris.1.in db2ris.1.in eenc.1.in en2ris.1.in marc2ris.1.in med2ris.1.in refdb-backup.1.in refdb-ms.1.in refdb-restore.1.in refdb.8.in refdb.sh.8.in refdba.1.in refdbc.1.in refdbctl.1.in refdbd.1.in refdbib.1.in refdbjade.1.in refdbnd.1.in refdbxml.1.in refdbxp.1.in runbib.1.in Log Message: initial version --- NEW FILE --- # process this file with automake to generate Makefile.in docdir = $(datadir)/doc/$(PACKAGE)-$(VERSION) man_MANS = RefDB.7 refdb.8 refdb.sh.8 refdbd.1 refdba.1 refdbc.1 refdbib.1 bib2ris.1 db2ris.1 en2ris.1 marc2ris.1 med2ris.1 eenc.1 refdb-backup.1 refdb-ms.1 refdb-restore.1 refdbjade.1 refdbnd.1 refdbxml.1 runbib.1 refdbctl.1 refdbxp.1 man_MANS_in = RefDB.7.in refdb.8.in refdb.sh.8.in refdbd.1.in refdba.1.in refdbc.1.in refdbib.1.in bib2ris.1.in db2ris.1.in en2ris.1.in marc2ris.1.in med2ris.1.in eenc.1.in refdb-backup.1.in refdb-ms.1.in refdb-restore.1.in refdbjade.1.in refdbnd.1.in refdbxml.1.in runbib.1.in refdbctl.1.in refdbxp.1.in EXTRA_DIST = $(man_MANS_in) $(man_MANS): %: %.in sed 's%<manualpath>%$(DESTDIR)$(docdir)/refdb-manual%' < $< | \ sed 's%<sharepath>%$(DESTDIR)$(pkgdatadir)/db%' | \ sed 's%<runpath>%$(DESTDIR)$(var_dir)%' | \ sed 's%<etcpath>%$(DESTDIR)$(sysconfdir)/@PACKAGE@%' > $@ clean: rm -f $(man_MANS) --- NEW FILE --- .\" Hey, EMACS: -*- nroff -*- .\" .\" Filename: <FILENAME> .\" Author: David Nebauer .\" History: <DATE> - created .\" .\" For header (.TH), first parameter, NAME, should be all caps .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection .\" Other parameters are allowed: see man(7), man(1) .\" Please adjust the date whenever revising the manpage. .\" .\" Some roff macros, for reference: .\" .nh disable hyphenation .\" .hy enable hyphenation .\" .ad l left justify .\" .ad b justify to both left and right margins .\" .nf disable filling .\" .fi enable filling .\" .br insert line break .\" .sp <n> insert n+1 empty lines .\" for manpage-specific macros, see man(7) .\" .\" Formatting [see groff_char (7) for details]: .\" \(aq : escape sequence for (') .\" `` : left/open double quote .\" '' : right/close double quote .\" ` : left/open single quote .\" ' : right/close single quote .\" \(em : escape sequence for em dash .\" \(en : escape sequence for en dash .\" \. : escape sequence for period/dot .\" \fX : escape sequence that changes font, where 'X' can be 'R|I|B|BI' .\" (R = roman/normal | I = italic | B = bold | BI = bold-italic) .\" \fP : switch to previous font .\" in this case '\fR' could also have been used .\" .\" Bulleted list: .\" A bulleted list: .\" .IP \[bu] 2 .\" lawyers .\" .IP \[bu] .\" guns .\" .IP \[bu] .\" money .\" Numbered list: .\" .nr step 1 1 .\" A numbered list: .\" .IP \n[step] 3 .\" lawyers .\" .IP \n+[step] .\" guns .\" .IP \n+[step] .\" money .TH "REFDB" "7" "2005/10/16" "" "RefDB Manual" .SH "NAME" RefDB \- a set of tools to manage bibliographic references, notes, and bibliographies for markup languages .SH "DESCRIPTION" .SS "GENERAL FEATURES" .IP \[bu] 2 RefDB is a reference/notes database and bibliography tool for SGML, XML, and LaTeX documents. .IP \[bu] RefDB is mainly implemented in C, with a few Perl scripts inbetween, as well as shell scripts as "glue". It can be compiled on all platforms with a decent C compiler (a small amount of porting may be required). It builds and runs out of the box on Linux, FreeBSD, NetBSD, Solaris, OSX, Darwin, and Windows/Cygwin. .IP \[bu] RefDB is modular and accessible. You can plug in a variety of database engines to store your data, and you can choose between a variety of interfaces for interactive work. You can use RefDB in your projects through shell scripts or from Perl programs. .IP \[bu] The RefDB handbook (more than 300 printed pages) helps you to get RefDB up and running quickly and explains how to use the software for both administrators and users in great detail. In addition there is a tutorial targeted at plain users. .SS "APPLICATION DESIGN" .IP \[bu] RefDB uses a SQL database engine to store the references, notes, and the bibliography styles. Choose either an external database server for optimum performance and flexibility, or an embedded database engine for convenience (see below for supported database engines). .IP \[bu] Both reference and bibliography style databases use the relational features of SQL databases extensively to consolidate information and to save storage space. .IP \[bu] RefDB employs a three-tier architecture with lots of flexibility: clients, an application server that can run as a daemon, and the database server. If you prefer the embedded SQL engine, there'll be a two-tier setup. In both cases, all tiers may run on a single workstation for individual use. .IP \[bu] The application server can generate log messages to monitor its operation. .IP \[bu] RefDB contains two standard interfaces: a command line interface for terminal addicts and for use in scripts, and a PHP-based web interface for a more visual approach. In addition, both Emacs and Vim users can access RefDB from the editing environment they're used to. Finally, there is also a Perl client module to integrate RefDB functionality into your own Perl programs. .SS "REFERENCE AND NOTES MANAGEMENT" .IP \[bu] The main input format for bibliographic data is RIS which can be generated and imported by all major reference databases on Windows (Reference Manager, EndNote and the like). An XML representation of RIS using the risx DTD is also supported as a native format. The latter is well suited as a means to import SGML or XML bibliographic data. .IP \[bu] Import filters are provided for Medline (tagged and XML), BibTeX, MARC, and DocBook. .IP \[bu] The data can be retrieved as simple text, formatted as HTML, formatted as a DocBook bibliography element (SGML or XML), formatted as a TEI listBibl element (XML), formatted as BibTeX reference list, or formatted as RIS or risx files. .IP \[bu] All character encodings supported by your platform can be used both for data input and for data export. This includes European character sets like Latin-1 and of course Unicode. .IP \[bu] Extended notes can be linked to one or more references, authors, periodicals, or keywords to create topics or material collections. These are more powerful and flexible than folder systems and the like. .IP \[bu] The query language is fairly simple yet powerful. You can use booleans to combine queries on any combination of fields. You can use brackets to group queries. You can use Unix-style regular expressions to formulate advanced queries. .SS "BIBLIOGRAPHIES" .IP \[bu] Formatted bibliographies can be created automatically from DocBook SGML/XML and TEI XML documents. This does not require any changes or extensions to the DTDs. RefDB can also be integrated as a data source into the LaTeX/BibTeX workflow. .IP \[bu] RefDB is extensible in terms of the supported document types: support for new document types can be added without hacking the tool itself (you only need to hack stylesheets) .IP \[bu] Citation and reference styles can be defined in XML to match the weirdest requirements of journals and publishers. .IP \[bu] Sophisticated shell scripts and makefiles take care of the document transformations. The whole process is transparent to the user as all he needs to do is e.g. type make pdf to turn his document into a PDF file with formatted citations and bibliographies. .SS "NETWORKING CAPABILITIES" .IP \[bu] Due to the client/server design, RefDB is very well suited as a shared reference database for a workgroup or a department. However, it runs just fine on a single standalone workstation. .IP \[bu] Users can share databases and still have their personal reference lists. They can share their notes or keep them private on a per-note base. .IP \[bu] Concurrent read and write access of several users is supported. There is no need to restrict access of other users to read-only. However, if your database engine supports access control (MySQL and PostgreSQL), you can restrict access of some users to read-only. .IP \[bu] A simple method to access electronic offprints (e.g. in PDF or PostScript format) is provided in the HTML output and in the web interface. This also works across networks using mounted shares. .SS "SUPPORTED DATABASE SERVERS" RefDB versions 0.9 and later employ the libdbi database abstraction library to provide support for different SQL database engines. Currently the following external SQL database servers are supported: .IP \[bu] MySQL .IP \[bu] PostgreSQL .PP The following embedded database engines are supported: .IP \[bu] SQLite (versions 2.x and 3.x) .SH "SEE ALSO" \fBrefdbd\fR (1), \fBrefdba\fR (1), \fBrefdbc\fR (1), \fBrefdbbib\fR (1), \fBbib2ris\fR (1), \fBdb2ris\fR (1), \fBen2ris\fR (1), \fBmarc2ris\fR (1), \fBmed2ris\fR (1), \fBeenc\fR (1), \fBrefdb-backup\fR (1), \fBrefdb-ms\fR (1), \fBrefdb-restore\fR (1), \fBrefdbjade\fR (1), \fBrefdbnd\fR (1), \fBrefdbxml\fR (1), \fBrefdbctl\fR (1), \fBrefdb\fR (8). .PP \fIRefDB manual (local copy) \fR <manualpath>/index.html .PP \fIRefDB manual (web) \fR <http://refdb.sourceforge.net/manual/index.html> .PP \fIRefDB on the web \fR <http://refdb.sourceforge.net/> .SH "AUTHOR" RefDB was originally written by Markus Hoenicka <ma...@mh...>. For a list of current authors, see the file \fIAUTHORS\fR. .PP --- NEW FILE --- .\" Hey, EMACS: -*- nroff -*- .\" .\" Filename: <FILENAME> .\" Author: David Nebauer .\" History: <DATE> - created .\" .\" For header (.TH), first parameter, NAME, should be all caps .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection .\" Other parameters are allowed: see man(7), man(1) .\" Please adjust the date whenever revising the manpage. .\" .\" Some roff macros, for reference: .\" .nh disable hyphenation .\" .hy enable hyphenation .\" .ad l left justify .\" .ad b justify to both left and right margins .\" .nf disable filling .\" .fi enable filling .\" .br insert line break .\" .sp <n> insert n+1 empty lines .\" for manpage-specific macros, see man(7) .\" .\" Formatting [see groff_char (7) for details]: .\" \(aq : escape sequence for (') .\" `` : left/open double quote .\" '' : right/close double quote .\" ` : left/open single quote .\" ' : right/close single quote .\" \(em : escape sequence for em dash .\" \(en : escape sequence for en dash .\" \. : escape sequence for period/dot .\" \fX : escape sequence that changes font, where 'X' can be 'R|I|B|BI' .\" (R = roman/normal | I = italic | B = bold | BI = bold-italic) .\" \fP : switch to previous font .\" in this case '\fR' could also have been used .\" .\" Bulleted list: .\" A bulleted list: .\" .IP \[bu] 2 .\" lawyers .\" .IP \[bu] .\" guns .\" .IP \[bu] .\" money .\" Numbered list: .\" .nr step 1 1 .\" A numbered list: .\" .IP \n[step] 3 .\" lawyers .\" .IP \n+[step] .\" guns .\" .IP \n+[step] .\" money .TH "BIB2RIS" "1" "2005-10-16" "" "bib2ris Manual" .SH "NAME" bib2ris \- converts bibtex bibliographic data to the RIS format .SH "SYNOPSIS" .PP \fBbib2ris\fR [\fB\-e\fR \fIlog-destination\fR] [\fB\-h\fR] [\fB\-j\fR] [\fB\-l\fR \fIlog-level\fR] [\fB\-L\fR \fIlog-file\fR] [\fB\-q\fR] [\fB\-s\fR \fIseparator\fR] [\fB\-v\fR] [\fB\-y\fR \fIconfdir\fR] \fIfile\fR .SH "DESCRIPTION" bib2ris converts BibTeX bibliography files into RIS files. .PP This man page describes only the startup options of bib2ris. Please consult the RefDB manual (see below) to see how you can change the mapping of bibtex to RIS reference types and data fields. .SH "OPTIONS" .TP \fB\-e\fR \fIlog-destination\fR log-destination can have the values 0, 1, or 2, or the equivalent strings \fIstderr\fR, \fIsyslog\fR, or \fIfile\fR, respectively. This value specifies where the log information goes to. \fI0\fR (zero) means the messages are sent to stderr. They are immediately available on the screen but they may interfere with command output. \fI1\fR will send the output to the syslog facility. Keep in mind that syslog must be configured to accept log messages from user programs, see the syslog(8) man page for further information. Unix-like systems usually save these messages in \fI/var/log/user.log\fR. \fI2\fR will send the messages to a custom log file which can be specified with the \fI-L\fR option. .TP \fB\-h\fR Displays help and usage screen, then exits. .TP \fB\-j\fR Force bib2ris to use \fBJO\fR RIS fields in all cases. If this option is not used, bib2ris tries to infer whether a journal name is an abbreviation or not. If the string contains at least one period, \fBJO\fR will be used, otherwise \fBJF\fR will be used. .TP \fB\-l\fR \fIlog-level\fR Specify the priority up to which events are logged. This is either a number between \fI0\fR and \fI7\fR or one of the strings \fIemerg\fR, \fIalert\fR, \fIcrit\fR, \fIerr\fR, \fIwarning\fR, \fInotice\fR, \fIinfo\fR, \fIdebug\fR, respectively (see also Log level definitions). \fI-1\fR disables logging completely. A low log level like \fI0\fR means that only the most critical messages are logged. A higher log level means that less critical events are logged as well. \fI7\fR will include debug messages. The latter can be verbose and abundant, so you want to avoid this log level unless you need to track down problems. .TP \fB\-L\fR \fIlog-file\fR Specify the full path to a log file that will receive the log messages. Typically this would be \fI/var/log/refdba\fR. .TP \fB\-q\fR Start without reading the configuration files. The client will use the compile-time defaults for all values that you do not set with command-line switches. .TP \fB\-s\fR \fIseparator\fR Specify the delimiter which separates individual keywords in a non-standard keyword field. Use the string \fBspc\fR for whitespace-separated lists (spaces and tabs). .TP \fB\-v\fR Prints version and copyright information, then exits. .TP \fB\-y\fR \fIconfdir\fR Specify the directory where the global configuration files are Note: By default, all RefDB applications look for their configuration files in a directory that is specified during the configure step when building the package. That is, you don't need the \fB-y\fR option unless you use precompiled binaries in unusual locations, e.g. by relocating a rpm package. .TP \fIfile\fR If used, this parameter denotes the names of one or more bibtex files. If no file is specified, bib2ris tries to read the data from stdin. Output is always sent to stdout. .SH "FILES" .TP \fI<etcpath>/bib2risrc\fR The global configuration file of bib2ris. .TP \fI$HOME/.bib2risrc\fR The user configuration file of bib2ris. .SH "SEE ALSO" \fBRefDB\fR (7), \fBdb2ris\fR (1). \fBen2ris\fR (1). \fBmarc2ris\fR (1). \fBmed2ris\fR (1). .PP \fIRefDB manual (local copy) \fR <manualpath>/index.html .PP \fIRefDB manual (web) \fR <http://refdb.sourceforge.net/manual/index.html> .PP \fIRefDB on the web \fR <http://refdb.sourceforge.net/> .SH "AUTHOR" bib2ris was written by Markus Hoenicka <ma...@mh...>. .PP --- NEW FILE --- .\" Hey, EMACS: -*- nroff -*- .\" .\" Filename: <FILENAME> .\" Author: David Nebauer .\" History: <DATE> - created .\" .\" For header (.TH), first parameter, NAME, should be all caps .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection .\" Other parameters are allowed: see man(7), man(1) .\" Please adjust the date whenever revising the manpage. .\" .\" Some roff macros, for reference: .\" .nh disable hyphenation .\" .hy enable hyphenation .\" .ad l left justify .\" .ad b justify to both left and right margins .\" .nf disable filling .\" .fi enable filling .\" .br insert line break .\" .sp <n> insert n+1 empty lines .\" for manpage-specific macros, see man(7) .\" .\" Formatting [see groff_char (7) for details]: .\" \(aq : escape sequence for (') .\" `` : left/open double quote .\" '' : right/close double quote .\" ` : left/open single quote .\" ' : right/close single quote .\" \(em : escape sequence for em dash .\" \(en : escape sequence for en dash .\" \. : escape sequence for period/dot .\" \fX : escape sequence that changes font, where 'X' can be 'R|I|B|BI' .\" (R = roman/normal | I = italic | B = bold | BI = bold-italic) .\" \fP : switch to previous font .\" in this case '\fR' could also have been used .\" .\" Bulleted list: .\" A bulleted list: .\" .IP \[bu] 2 .\" lawyers .\" .IP \[bu] .\" guns .\" .IP \[bu] .\" money .\" Numbered list: .\" .nr step 1 1 .\" A numbered list: .\" .IP \n[step] 3 .\" lawyers .\" .IP \n+[step] .\" guns .\" .IP \n+[step] .\" money .TH "DB2RIS" "1" "2005-10-16" "" "db2ris Manual" .SH "NAME" db2ris \- converts DocBook bibliographic data to the RIS format .SH "SYNOPSIS" .PP \fBdb2ris\fR [\fB\-a\fR] [\fB\-e\fR \fIlog-destination\fR] [\fB\-h\fR] [\fB\-L\fR \fIlog-file\fR] [\fB\-o\fR \fIfile\fR] [\fB\-O\fR \fIfile\fR] [\fB\-r\fR \fIreftype\fR] \fIfile\fR .SH "DESCRIPTION" db2ris converts DocBook bibliographic data into RIS files. db2ris is a wrapper script which invokes OpenJade to do the actual transformation. .PP This man page describes only the startup options of db2ris. Please consult the RefDB manual (see below) to see how you can customize the transformation. .SH "OPTIONS" .TP \fB\-a\fR Use full first- and othernames if they are present in the DocBook source. By default, all first- and othernames will be abbreviated. .TP \fB\-e\fR \fIlog-destination\fR log-destination can have the values 0, 1, or 2, or the equivalent strings \fIstderr\fR, \fIsyslog\fR, or \fIfile\fR, respectively. This value specifies where the log information goes to. \fI0\fR (zero) means the messages are sent to stderr. They are immediately available on the screen but they may interfere with command output. \fI1\fR will send the output to the syslog facility. Keep in mind that syslog must be configured to accept log messages from user programs, see the syslog(8) man page for further information. Unix-like systems usually save these messages in \fI/var/log/user.log\fR. \fI2\fR will send the messages to a custom log file which can be specified with the \fI-L\fR option. .TP \fB\-h\fR Displays help and usage screen, then exits. .TP \fB\-L\fR \fIlog-file\fR Specify the full path to a log file that will receive the log messages. Typically this would be \fI/var/log/refdba\fR. .TP \fB\-o\fR \fIfile\fR Send output to \fIfile\fR. If \fIfile\fR exists, its contents will be overwritten. .TP \fB\-O\fR \fIfile\fR Send output to \fIfile\fR. If \fIfile\fR exists, the output will be appended. .TP \fB\-r\fR \fIreftype\fR Set the default RIS reference type. This type will be used if db2ris cannot infer the reference type from the \fIBiblioEntry\fR element. .TP \fIfile\fR The names of one or more DocBook files. .SH "FILES" .TP \fI<etcpath>/db2risrc\fR The global configuration file of db2ris. .TP \fI$HOME/.db2risrc\fR The user configuration file of db2ris. .SH "SEE ALSO" \fBRefDB\fR (7), \fBbib2ris\fR (1). \fBen2ris\fR (1). \fBmarc2ris\fR (1). \fBmed2ris\fR (1). .PP \fIRefDB manual (local copy) \fR <manualpath>/index.html .PP \fIRefDB manual (web) \fR <http://refdb.sourceforge.net/manual/index.html> .PP \fIRefDB on the web \fR <http://refdb.sourceforge.net/> .SH "AUTHOR" db2ris was written by Markus Hoenicka <ma...@mh...>. .PP --- NEW FILE --- .\" Hey, EMACS: -*- nroff -*- .\" .\" Filename: <FILENAME> .\" Author: David Nebauer .\" History: <DATE> - created .\" .\" For header (.TH), first parameter, NAME, should be all caps .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection .\" Other parameters are allowed: see man(7), man(1) .\" Please adjust the date whenever revising the manpage. .\" .\" Some roff macros, for reference: .\" .nh disable hyphenation .\" .hy enable hyphenation .\" .ad l left justify .\" .ad b justify to both left and right margins .\" .nf disable filling .\" .fi enable filling .\" .br insert line break .\" .sp <n> insert n+1 empty lines .\" for manpage-specific macros, see man(7) .\" .\" Formatting [see groff_char (7) for details]: .\" \(aq : escape sequence for (') .\" `` : left/open double quote .\" '' : right/close double quote .\" ` : left/open single quote .\" ' : right/close single quote .\" \(em : escape sequence for em dash .\" \(en : escape sequence for en dash .\" \. : escape sequence for period/dot .\" \fX : escape sequence that changes font, where 'X' can be 'R|I|B|BI' .\" (R = roman/normal | I = italic | B = bold | BI = bold-italic) .\" \fP : switch to previous font .\" in this case '\fR' could also have been used .\" .\" Bulleted list: .\" A bulleted list: .\" .IP \[bu] 2 .\" lawyers .\" .IP \[bu] .\" guns .\" .IP \[bu] .\" money .\" Numbered list: .\" .nr step 1 1 .\" A numbered list: .\" .IP \n[step] 3 .\" lawyers .\" .IP \n+[step] .\" guns .\" .IP \n+[step] .\" money .TH "EENC" "1" "2005-10-16" "" "eenc Manual" .SH "NAME" eenc \- perform password encryption for RefDB clients .SH "SYNOPSIS" \fBeenc\fR [\fB\-p\fR \fIABC-DE-FG-HI\fR] \fIpassword\fR .SH "DESCRIPTION" RefDB(7) clients send passwords to refdbd(1) in an encrypted form. Programmers that implement custom clients in languages other than C or Perl may use this program to perform the password encryption if implementing the algorithm in the target language is too cumbersome. The program writes the encoded password to stdout. As the encoding algorithm is symmetrical, you can use this utility to encode plain text passwords as well as to decode encrypted passwords. .PP The algorithm used by eenc is derived from the ENIGMA algorithm. Security is limited but should be sufficient for the purposes of a reference management software. Please see the RefDB manual (see below) for further information about the client-server protocol. .SH "OPTIONS" .TP \fB\-p\fR \fIABC-DE-FG-HI\fR The slot and rotor position string sent back by refdbd(1) during the first stage of the client-server protocol. ABC denotes which wheel goes into which slot, and the remaining digits encode the positions of the wheels in slots 0 through 2. .TP \fIpassword\fR The plain-text password when encrypting, or the encoded password when decrypting. .SH "SEE ALSO" \fBRefDB\fR (7), \fBrefdbd\fR (1). .PP \fIRefDB manual (local copy) \fR <manualpath>/index.html .PP \fIRefDB manual (web) \fR <http://refdb.sourceforge.net/manual/index.html> .PP \fIRefDB on the web \fR <http://refdb.sourceforge.net/> .SH "AUTHOR" eenc was written by Markus Hoenicka <ma...@mh...>. .PP --- NEW FILE --- .\" Hey, EMACS: -*- nroff -*- .\" .\" Filename: <FILENAME> .\" Author: David Nebauer .\" History: <DATE> - created .\" .\" For header (.TH), first parameter, NAME, should be all caps .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection .\" Other parameters are allowed: see man(7), man(1) .\" Please adjust the date whenever revising the manpage. .\" .\" Some roff macros, for reference: .\" .nh disable hyphenation .\" .hy enable hyphenation .\" .ad l left justify .\" .ad b justify to both left and right margins .\" .nf disable filling .\" .fi enable filling .\" .br insert line break .\" .sp <n> insert n+1 empty lines .\" for manpage-specific macros, see man(7) .\" .\" Formatting [see groff_char (7) for details]: .\" \(aq : escape sequence for (') .\" `` : left/open double quote .\" '' : right/close double quote .\" ` : left/open single quote .\" ' : right/close single quote .\" \(em : escape sequence for em dash .\" \(en : escape sequence for en dash .\" \. : escape sequence for period/dot .\" \fX : escape sequence that changes font, where 'X' can be 'R|I|B|BI' .\" (R = roman/normal | I = italic | B = bold | BI = bold-italic) .\" \fP : switch to previous font .\" in this case '\fR' could also have been used .\" .\" Bulleted list: .\" A bulleted list: .\" .IP \[bu] 2 .\" lawyers .\" .IP \[bu] .\" guns .\" .IP \[bu] .\" money .\" Numbered list: .\" .nr step 1 1 .\" A numbered list: .\" .IP \n[step] 3 .\" lawyers .\" .IP \n+[step] .\" guns .\" .IP \n+[step] .\" money .TH "EN2RIS" "1" "2005-10-16" "" "en2ris Manual" .SH "NAME" en2ris \- converts EndNote bibliographic data to the RIS format .SH "SYNOPSIS" .PP \fBen2ris\fR [\fB\-e\fR \fIlogdest\fR] [\fB\-f\fR \fIencoding\fR] [\fB\-h\fR] [\fB\-l\fR \fIloglevel\fR] [\fB\-L\fR \fIlogfile\fR] [\fB\-o\fR \fIfile\fR] [\fB\-O\fR \fIfile\fR] [\fB\-q\fR] [\fB\-t\fR \fIencoding\fR] [\fB\-y\fR \fIpath\fR] .SH "DESCRIPTION" en2ris fixes the markup errors encountered in EndNote "RIS" output and writes RIS output to stdout. .PP This man page describes only the startup options of en2ris. Please consult the RefDB manual (see below) for further information. .SH "OPTIONS" .TP \fB\-e\fR \fIlog-destination\fR log-destination can have the values 0, 1, or 2, or the equivalent strings \fIstderr\fR, \fIsyslog\fR, or \fIfile\fR, respectively. This value specifies where the log information goes to. \fI0\fR (zero) means the messages are sent to stderr. They are immediately available on the screen but they may interfere with command output. \fI1\fR will send the output to the syslog facility. Keep in mind that syslog must be configured to accept log messages from user programs, see the syslog(8) man page for further information. Unix-like systems usually save these messages in \fI/var/log/user.log\fR. \fI2\fR will send the messages to a custom log file which can be specified with the \fI-L\fR option. .TP \fB\-f\fR \fIencoding\fR Select the input character encoding. Supported encodings are platform-dependent and can usually be found in iconv_open(3). If no encodings are specified, \fBISO-8859-1\fR aka Latin-1 is assumed. .TP \fB\-h\fR Displays help and usage screen, then exits. .TP \fB\-l\fR \fIlog-level\fR Specify the priority up to which events are logged. This is either a number between \fI0\fR and \fI7\fR or one of the strings \fIemerg\fR, \fIalert\fR, \fIcrit\fR, \fIerr\fR, \fIwarning\fR, \fInotice\fR, \fIinfo\fR, \fIdebug\fR, respectively (see also Log level definitions). \fI-1\fR disables logging completely. A low log level like \fI0\fR means that only the most critical messages are logged. A higher log level means that less critical events are logged as well. \fI7\fR will include debug messages. The latter can be verbose and abundant, so you want to avoid this log level unless you need to track down problems. .TP \fB\-L\fR \fIlog-file\fR Specify the full path to a log file that will receive the log messages. Typically this would be \fI/var/log/refdba\fR. .TP \fB\-o\fR \fIfile\fR Send output to \fIfile\fR. If \fIfile\fR exists, its contents will be overwritten. .TP \fB\-O\fR \fIfile\fR Send output to \fIfile\fR. If \fIfile\fR exists, the output will be appended. .TP \fB\-q\fR Start without reading the configuration files. The client will use the compile-time defaults for all values that you do not set with command-line switches. .TP \fB\-t\fR \fIencoding\fR Select the output character encoding. Supported encodings are platform-dependent and can usually be found in iconv_open(3). If no encodings are specified, \fBISO-8859-1\fR aka Latin-1 is assumed. .TP \fB\-y\fR \fIconfdir\fR Specify the directory where the global configuration files are Note: By default, all RefDB applications look for their configuration files in a directory that is specified during the configure step when building the package. That is, you don't need the \fB-y\fR option unless you use precompiled binaries in unusual locations, e.g. by relocating a rpm package. .SH "FILES" .TP \fI<etcpath>/en2risrc\fR The global configuration file of en2ris. .TP \fI$HOME/.en2risrc\fR The user configuration file of en2ris. .SH "SEE ALSO" \fBRefDB\fR (7), \fBbib2ris\fR (1). \fBdb2ris\fR (1). \fBmarc2ris\fR (1). \fBmed2ris\fR (1). .PP \fIRefDB manual (local copy) \fR <manualpath>/index.html .PP \fIRefDB manual (web) \fR <http://refdb.sourceforge.net/manual/index.html> .PP \fIRefDB on the web \fR <http://refdb.sourceforge.net/> .SH "AUTHOR" en2ris was written by Markus Hoenicka <ma...@mh...>. .PP --- NEW FILE --- .\" Hey, EMACS: -*- nroff -*- .\" .\" Filename: <FILENAME> .\" Author: David Nebauer .\" History: <DATE> - created .\" .\" For header (.TH), first parameter, NAME, should be all caps .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection .\" Other parameters are allowed: see man(7), man(1) .\" Please adjust the date whenever revising the manpage. .\" .\" Some roff macros, for reference: .\" .nh disable hyphenation .\" .hy enable hyphenation .\" .ad l left justify .\" .ad b justify to both left and right margins .\" .nf disable filling .\" .fi enable filling .\" .br insert line break .\" .sp <n> insert n+1 empty lines .\" for manpage-specific macros, see man(7) .\" .\" Formatting [see groff_char (7) for details]: .\" \(aq : escape sequence for (') .\" `` : left/open double quote .\" '' : right/close double quote .\" ` : left/open single quote .\" ' : right/close single quote .\" \(em : escape sequence for em dash .\" \(en : escape sequence for en dash .\" \. : escape sequence for period/dot .\" \fX : escape sequence that changes font, where 'X' can be 'R|I|B|BI' .\" (R = roman/normal | I = italic | B = bold | BI = bold-italic) .\" \fP : switch to previous font .\" in this case '\fR' could also have been used .\" .\" Bulleted list: .\" A bulleted list: .\" .IP \[bu] 2 .\" lawyers .\" .IP \[bu] .\" guns .\" .IP \[bu] .\" money .\" Numbered list: .\" .nr step 1 1 .\" A numbered list: .\" .IP \n[step] 3 .\" lawyers .\" .IP \n+[step] .\" guns .\" .IP \n+[step] .\" money .TH "MARC2RIS" "1" "2005-10-16" "" "marc2ris Manual" .SH "NAME" marc2ris \- converts MARC bibliographic data to the RIS format .SH "SYNOPSIS" .PP \fBmarc2ris\fR [\fB\-e\fR \fIlog-destination\fR] [\fB\-h\fR] [\fB\-l\fR \fIlog-level\fR] [\fB\-L\fR \fIlog-file\fR] [\fB\-m\fR] [\fB\-o\fR \fI outfile\fR] [\fB\-O\fR \fI outfile\fR] [\fB\-t\fR \fI input_type\fR] [\fB\-u\fR] \fIfile\fR .SH "DESCRIPTION" marc2ris attempts to extract the information useful to RefDB from MARC datasets. MARC (Machine Readable Catalogue Format) is a standard originating from the 1960s and is widely used by libraries and bibliographic agencies. Most libraries that offer Z39.50 access can provide the records in at least one MARC format (like with most other "standards" there's a couple to choose from). Currently the following MARC dialects are supported: .TP \fBMARC21\fR This is an attempt to consolidate existing MARC variants (mainly USMARC and CANMARC) and will most likely be the format supported by all libraries in the near future. .TP \fBUNIMARC\fR This is the European equivalent of a standardization attempt. .TP \fBUKMARC\fR This format is fairly close to the USMARC variant and is mainly used by libraries in the United Kingdom and in Ireland. Libraries supporting this format may switch to MARC21 in the future. .PP This man page describes only the startup options of en2ris. Please consult the RefDB manual (see below) for further information. .SH "OPTIONS" .TP \fB\-e\fR \fIlog-destination\fR log-destination can have the values 0, 1, or 2, or the equivalent strings \fIstderr\fR, \fIsyslog\fR, or \fIfile\fR, respectively. This value specifies where the log information goes to. \fI0\fR (zero) means the messages are sent to stderr. They are immediately available on the screen but they may interfere with command output. \fI1\fR will send the output to the syslog facility. Keep in mind that syslog must be configured to accept log messages from user programs, see the syslog(8) man page for further information. Unix-like systems usually save these messages in \fI/var/log/user.log\fR. \fI2\fR will send the messages to a custom log file which can be specified with the \fI-L\fR option. .TP \fB\-h\fR Displays help and usage screen, then exits. .TP \fB\-l\fR \fIlog-level\fR Specify the priority up to which events are logged. This is either a number between \fI0\fR and \fI7\fR or one of the strings \fIemerg\fR, \fIalert\fR, \fIcrit\fR, \fIerr\fR, \fIwarning\fR, \fInotice\fR, \fIinfo\fR, \fIdebug\fR, respectively (see also Log level definitions). \fI-1\fR disables logging completely. A low log level like \fI0\fR means that only the most critical messages are logged. A higher log level means that less critical events are logged as well. \fI7\fR will include debug messages. The latter can be verbose and abundant, so you want to avoid this log level unless you need to track down problems. .TP \fB\-L\fR \fIlog-file\fR Specify the full path to a log file that will receive the log messages. Typically this would be \fI/var/log/refdba\fR. .TP \fB\-m\fR Switch on additional MARC output. The output data will be the RIS output interspersed with the source MARC data used to generate the output. This is useful to fix conversion errors manually. .TP \fB\-o\fR \fIfile\fR Send output to \fIfile\fR. If \fIfile\fR exists, its contents will be overwritten. .TP \fB\-O\fR \fIfile\fR Send output to \fIfile\fR. If \fIfile\fR exists, the output will be appended. .TP \fB\-t\fR \fIinput_type\fR Specify the MARC input type. The default is \fIMARC21\fR. Other available types are \fIUNIMARC\fR and \fIUKMARC\fR. .TP \fB\-u\fR Request Unicode output. marc2ris attempts to convert the input data into Unicode (unless the dataset explicitly states that it already uses Unicode). Use this option with care as some MARC variants do not state the character encoding explicitly. .SH "FILES" .TP \fI<etcpath>/marc2risrc\fR The global configuration file of marc2ris. .TP \fI$HOME/.marc2risrc\fR The user configuration file of marc2ris. .SH "SEE ALSO" \fBRefDB\fR (7), \fBbib2ris\fR (1). \fBdb2ris\fR (1). \fBen2ris\fR (1). \fBmed2ris\fR (1). .PP \fIRefDB manual (local copy) \fR <manualpath>/index.html .PP \fIRefDB manual (web) \fR <http://refdb.sourceforge.net/manual/index.html> .PP \fIRefDB on the web \fR <http://refdb.sourceforge.net/> .SH "AUTHOR" marc2ris was written by Markus Hoenicka <ma...@mh...>. .PP --- NEW FILE --- .\" Hey, EMACS: -*- nroff -*- .\" .\" Filename: <FILENAME> .\" Author: David Nebauer .\" History: <DATE> - created .\" .\" For header (.TH), first parameter, NAME, should be all caps .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection .\" Other parameters are allowed: see man(7), man(1) .\" Please adjust the date whenever revising the manpage. .\" .\" Some roff macros, for reference: .\" .nh disable hyphenation .\" .hy enable hyphenation .\" .ad l left justify .\" .ad b justify to both left and right margins .\" .nf disable filling .\" .fi enable filling .\" .br insert line break .\" .sp <n> insert n+1 empty lines .\" for manpage-specific macros, see man(7) .\" .\" Formatting [see groff_char (7) for details]: .\" \(aq : escape sequence for (') .\" `` : left/open double quote .\" '' : right/close double quote .\" ` : left/open single quote .\" ' : right/close single quote .\" \(em : escape sequence for em dash .\" \(en : escape sequence for en dash .\" \. : escape sequence for period/dot .\" \fX : escape sequence that changes font, where 'X' can be 'R|I|B|BI' .\" (R = roman/normal | I = italic | B = bold | BI = bold-italic) .\" \fP : switch to previous font .\" in this case '\fR' could also have been used .\" .\" Bulleted list: .\" A bulleted list: .\" .IP \[bu] 2 .\" lawyers .\" .IP \[bu] .\" guns .\" .IP \[bu] .\" money .\" Numbered list: .\" .nr step 1 1 .\" A numbered list: .\" .IP \n[step] 3 .\" lawyers .\" .IP \n+[step] .\" guns .\" .IP \n+[step] .\" money .TH "MED2RIS" "1" "2005-10-16" "" "med2ris Manual" .SH "NAME" med2ris \- converts Medline/Pubmed bibliographic data to the RIS format .SH "SYNOPSIS" .PP \fBmed2ris\fR [\fB\-e\fR \fIlogdest\fR] [\fB\-f\fR \fIencoding\fR] [\fB\-h\fR] [\fB\-i\fR] [\fB\-l\fR \fIloglevel\fR] [\fB\-L\fR \fIlogfile\fR] [\fB\-o\fR \fIfile\fR] [\fB\-O\fR \fIfile\fR] [\fB\-q\fR] [\fB\-t\fR \fIencoding\fR] [\fB\-y\fR \fIpath\fR] .SH "DESCRIPTION" med2ris converts Pubmed reference data into RIS data. The converter understands both the tagged Pubmed format (which superficially resembles RIS) and the XML format according to the PubMedArticle DTD. In most cases med2ris is able to automatically detect the input data type. .PP This man page describes only the startup options of med2ris. Please consult the RefDB manual (see below) for further information. .SH "OPTIONS" .TP \fB\-e\fR \fIlog-destination\fR log-destination can have the values 0, 1, or 2, or the equivalent strings \fIstderr\fR, \fIsyslog\fR, or \fIfile\fR, respectively. This value specifies where the log information goes to. \fI0\fR (zero) means the messages are sent to stderr. They are immediately available on the screen but they may interfere with command output. \fI1\fR will send the output to the syslog facility. Keep in mind that syslog must be configured to accept log messages from user programs, see the syslog(8) man page for further information. Unix-like systems usually save these messages in \fI/var/log/user.log\fR. \fI2\fR will send the messages to a custom log file which can be specified with the \fI-L\fR option. .TP \fB\-f\fR \fIencoding\fR Select the input character encoding. Supported encodings are platform-dependent and can usually be found in iconv_open(3). If no encodings are specified, \fBISO-8859-1\fR aka Latin-1 is assumed. .TP \fB\-h\fR Displays help and usage screen, then exits. .TP \fB\-i\fR Output additional information about unknown or unused tags. Mainly useful to debug the conversion if the input format has changed. .TP \fB\-l\fR \fIlog-level\fR Specify the priority up to which events are logged. This is either a number between \fI0\fR and \fI7\fR or one of the strings \fIemerg\fR, \fIalert\fR, \fIcrit\fR, \fIerr\fR, \fIwarning\fR, \fInotice\fR, \fIinfo\fR, \fIdebug\fR, respectively (see also Log level definitions). \fI-1\fR disables logging completely. A low log level like \fI0\fR means that only the most critical messages are logged. A higher log level means that less critical events are logged as well. \fI7\fR will include debug messages. The latter can be verbose and abundant, so you want to avoid this log level unless you need to track down problems. .TP \fB\-L\fR \fIlog-file\fR Specify the full path to a log file that will receive the log messages. Typically this would be \fI/var/log/refdba\fR. .TP \fB\-o\fR \fIfile\fR Send output to \fIfile\fR. If \fIfile\fR exists, its contents will be overwritten. .TP \fB\-O\fR \fIfile\fR Send output to \fIfile\fR. If \fIfile\fR exists, the output will be appended. .TP \fB\-q\fR Start without reading the configuration files. The client will use the compile-time defaults for all values that you do not set with command-line switches. .TP \fB\-t\fR \fIencoding\fR Select the output character encoding. Supported encodings are platform-dependent and can usually be found in iconv_open(3). If no encodings are specified, \fBISO-8859-1\fR aka Latin-1 is assumed. .TP \fB\-y\fR \fIconfdir\fR Specify the directory where the global configuration files are Note: By default, all RefDB applications look for their configuration files in a directory that is specified during the configure step when building the package. That is, you don't need the \fB-y\fR option unless you use precompiled binaries in unusual locations, e.g. by relocating a rpm package. .SH "FILES" .TP \fI<etcpath>/med2risrc\fR The global configuration file of med2ris. .TP \fI$HOME/.med2risrc\fR The user configuration file of med2ris. .SH "SEE ALSO" \fBRefDB\fR (7), \fBbib2ris\fR (1). \fBdb2ris\fR (1). \fBen2ris\fR (1). \fBmarc2ris\fR (1). .PP \fIRefDB manual (local copy) \fR <manualpath>/index.html .PP \fIRefDB manual (web) \fR <http://refdb.sourceforge.net/manual/index.html> .PP \fIRefDB on the web \fR <http://refdb.sourceforge.net/> .SH "AUTHOR" med2ris was written by Markus Hoenicka <ma...@mh...>. .PP --- NEW FILE --- .\" Hey, EMACS: -*- nroff -*- .\" .\" Filename: <FILENAME> .\" Author: David Nebauer .\" History: <DATE> - created .\" .\" For header (.TH), first parameter, NAME, should be all caps .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection .\" Other parameters are allowed: see man(7), man(1) .\" Please adjust the date whenever revising the manpage. .\" .\" Some roff macros, for reference: .\" .nh disable hyphenation .\" .hy enable hyphenation .\" .ad l left justify .\" .ad b justify to both left and right margins .\" .nf disable filling .\" .fi enable filling .\" .br insert line break .\" .sp <n> insert n+1 empty lines .\" for manpage-specific macros, see man(7) .\" .\" Formatting [see groff_char (7) for details]: .\" \(aq : escape sequence for (') .\" `` : left/open double quote .\" '' : right/close double quote .\" ` : left/open single quote .\" ' : right/close single quote .\" \(em : escape sequence for em dash .\" \(en : escape sequence for en dash .\" \. : escape sequence for period/dot .\" \fX : escape sequence that changes font, where 'X' can be 'R|I|B|BI' .\" (R = roman/normal | I = italic | B = bold | BI = bold-italic) .\" \fP : switch to previous font .\" in this case '\fR' could also have been used .\" .\" Bulleted list: .\" A bulleted list: .\" .IP \[bu] 2 .\" lawyers .\" .IP \[bu] .\" guns .\" .IP \[bu] .\" money .\" Numbered list: .\" .nr step 1 1 .\" A numbered list: .\" .IP \n[step] 3 .\" lawyers .\" .IP \n+[step] .\" guns .\" .IP \n+[step] .\" money .TH "<HEADER_NAME>" "1" "<DATE>" "" "<TITLE_NAME> Manual" .SH "NAME" <NAME> \- .SH "SYNOPSIS" \fB<NAME>\fR [\fB\-x\fR \fIopt\fR] .SH "DESCRIPTION" <NAME> ... .PP para 2 ... .SH "OPTIONS" .TP \fB\-x\fR \fIopt\fR description .TP \fB\-y\fR \fIopt\fR description .SH "FILES" .I /path/to/file .IP description. .PP .I /path/to/file .IP description. .SH "SEE ALSO" \fBmanpage\fR (1), \fBmanpage\fR (1). .PP \fIDocument\fR </path/to/document> .br \fIDocument\fR </path/to/document> .SH "AUTHOR" <NAME> was written by David Nebauer <da...@ne...>. .PP --- NEW FILE --- .\" Hey, EMACS: -*- nroff -*- .\" .\" Filename: refdb-ms.1 .\" Author: David Nebauer .\" History: 2005-07-17 - created .\" .\" For header (.TH), first parameter, NAME, should be all caps .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection .\" Other parameters are allowed: see man(7), man(1) .\" Please adjust the date whenever revising the manpage. .\" .\" Some roff macros, for reference: .\" .nh disable hyphenation .\" .hy enable hyphenation .\" .ad l left justify .\" .ad b justify to both left and right margins .\" .nf disable filling .\" .fi enable filling .\" .br insert line break .\" .sp <n> insert n+1 empty lines .\" for manpage-specific macros, see man(7) .\" .\" Formatting [see groff_char (7) for details]: .\" \(aq : escape sequence for (') .\" `` : left/open double quote .\" '' : right/close double quote .\" ` : left/open single quote .\" ' : right/close single quote .\" \(em : escape sequence for em dash .\" \(en : escape sequence for en dash .\" \. : escape sequence for period/dot .\" \fX : escape sequence that changes font, where 'X' can be 'R|I|B|BI' .\" (R = roman/normal | I = italic | B = bold | BI = bold-italic) .\" \fP : switch to previous font .\" in this case '\fR' could also have been used .\" .\" Bulleted list: .\" A bulleted list: .\" .IP \[bu] 2 .\" lawyers .\" .IP \[bu] .\" guns .\" .IP \[bu] .\" money .\" Numbered list: .\" .nr step 1 1 .\" A numbered list: .\" .IP \n[step] 3 .\" lawyers .\" .IP \n+[step] .\" guns .\" .IP \n+[step] .\" money .TH "REFDB-MS" "1" "2005-07-17" "" "Refdb-ms Manual" .SH "NAME" refdb-ms \- a console-based style generator for RefDB .SH "SYNOPSIS" \fBrefdb-ms\fR .SH "DESCRIPTION" refdb-ms is a console-based style generator for RefDB. .PP In short, this utility consists of a loop in which you are asked to: .IP \[bu] 2 select an element from a list of elements allowed in that part of the style, .IP \[bu] enter or select appropriate values for mandatory attributes, .IP \[bu] select optional attributes for that element and enter their values, .IP \[bu] select an element from a list of elements ... .PP This process ends when you have exhausted the DTD. .PP Every time you are presented with a list of elements you have the option of selecting help. Doing so will present a screen with a summary of each element on the list. The same thing happens when you are presented with a list of attributes. .PP When an attribute or element is required by the DTD this utility will select it automatically. For some objects you will not need to provide input and so this utility will create the object(s) automatically. This can be disconcerting at first. Please read the console feedback carefully. .PP Whenever you are asked to enter or select a value for an attribute or element, you are given a brief prompt explaining the purpose of the element or attribute. After each element is added to the style you are presented with a "progress report" showing the (major) elements. It may take a little while to understand this feedback. As you add elements they will be appended to the report. When you complete a major element, such as a PUBTYPE or AUTHORLIST, however, its subsidiary elements are no longer displayed -- they are "folded". This saves space and makes it easier to quickly understand where in the style you are at that point in time. As you become more familiar with the structure of the style DTD this display will become increasingly useful. .PP At certain times within PUBTYPE, AUTHORONLY, YEARONLY and INTEXTDEF elements you are able to delete the previous "major" element. "Major" elements are those corresponding to ris fields. These elements may contain other elements. For example, deleting an AUTHORLIST element will delete all the children elements of that author list style. You can view the complete element before deletion occurs. .PP When you select some elements (in general, those corresponding to ris fields) you will be given an opportunity to copy the most recently entered element of that type. If you choose to copy, all attributes and sub-elements will be copied. This can save you a lot of time if, for example, your author lists will always have the same formatting. .PP After you have created your style this utility will save it to a disk file. It will also generate a brief summary of it in html format. This summary can be of great help when entering references in your reference database. .PP This utility will then offer to upload the style to RefDB. There is no foreseeable way in which this operation could damage your reference data, but you use it at your own risk. .SH "FILES" .I RefDB::Makestyle .IP This module is required by refdb-ms. It is available as a tar.gz archive or a Debian package from the RefDB website <refdb.sourceforge.net>. .SH "SEE ALSO" \fBRefDB::Makestyle\fR (3). .PP \fIRefDB manual (local copy) \fR <manualpath>/index.html .PP \fIRefDB manual (web) \fR <http://refdb.sourceforge.net/manual/index.html> .PP \fIRefDB on the web \fR <http://refdb.sourceforge.net/> .SH "AUTHOR" refdb-ms was written by David Nebauer <da...@ne...>. .PP This manual page was written by David Nebauer <da...@ne...> for the Debian project (but may be used by others). --- NEW FILE --- .\" Hey, EMACS: -*- nroff -*- .\" .\" Filename: <FILENAME> .\" Author: David Nebauer .\" History: <DATE> - created .\" .\" For header (.TH), first parameter, NAME, should be all caps .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection .\" Other parameters are allowed: see man(7), man(1) .\" Please adjust the date whenever revising the manpage. .\" .\" Some roff macros, for reference: .\" .nh disable hyphenation .\" .hy enable hyphenation .\" .ad l left justify .\" .ad b justify to both left and right margins .\" .nf disable filling .\" .fi enable filling .\" .br insert line break .\" .sp <n> insert n+1 empty lines .\" for manpage-specific macros, see man(7) .\" .\" Formatting [see groff_char (7) for details]: .\" \(aq : escape sequence for (') .\" `` : left/open double quote .\" '' : right/close double quote .\" ` : left/open single quote .\" ' : right/close single quote .\" \(em : escape sequence for em dash .\" \(en : escape sequence for en dash .\" \. : escape sequence for period/dot .\" \fX : escape sequence that changes font, where 'X' can be 'R|I|B|BI' .\" (R = roman/normal | I = italic | B = bold | BI = bold-italic) .\" \fP : switch to previous font .\" in this case '\fR' could also have been used .\" .\" Bulleted list: .\" A bulleted list: .\" .IP \[bu] 2 .\" lawyers .\" .IP \[bu] .\" guns .\" .IP \[bu] .\" money .\" Numbered list: .\" .nr step 1 1 .\" A numbered list: .\" .IP \n[step] 3 .\" lawyers .\" .IP \n+[step] .\" guns .\" .IP \n+[step] .\" money .TH "<HEADER_NAME>" "1" "<DATE>" "" "<TITLE_NAME> Manual" .SH "NAME" <NAME> \- .SH "SYNOPSIS" \fB<NAME>\fR [\fB\-x\fR \fIopt\fR] .SH "DESCRIPTION" <NAME> ... .PP para 2 ... .SH "OPTIONS" .TP \fB\-x\fR \fIopt\fR description .TP \fB\-y\fR \fIopt\fR description .SH "FILES" .I /path/to/file .IP description. .PP .I /path/to/file .IP description. .SH "SEE ALSO" \fBmanpage\fR (1), \fBmanpage\fR (1). .PP \fIDocument\fR </path/to/document> .br \fIDocument\fR </path/to/document> .SH "AUTHOR" <NAME> was written by David Nebauer <da...@ne...>. .PP --- NEW FILE --- .\" Hey, EMACS: -*- nroff -*- .\" .\" Filename: <FILENAME> .\" Author: David Nebauer .\" History: <DATE> - created .\" .\" For header (.TH), first parameter, NAME, should be all caps .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection .\" Other parameters are allowed: see man(7), man(1) .\" Please adjust the date whenever revising the manpage. .\" .\" Some roff macros, for reference: .\" .nh disable hyphenation .\" .hy enable hyphenation .\" .ad l left justify .\" .ad b justify to both left and right margins .\" .nf disable filling .\" .fi enable filling .\" .br insert line break .\" .sp <n> insert n+1 empty lines .\" for manpage-specific macros, see man(7) .\" .\" Formatting [see groff_char (7) for details]: .\" \(aq : escape sequence for (') .\" `` : left/open double quote .\" '' : right/close double quote .\" ` : left/open single quote .\" ' : right/close single quote .\" \(em : escape sequence for em dash .\" \(en : escape sequence for en dash .\" \. : escape sequence for period/dot .\" \fX : escape sequence that changes font, where 'X' can be 'R|I|B|BI' .\" (R = roman/normal | I = italic | B = bold | BI = bold-italic) .\" \fP : switch to previous font .\" in this case '\fR' could also have been used .\" .\" Bulleted list: .\" A bulleted list: .\" .IP \[bu] 2 .\" lawyers .\" .IP \[bu] .\" guns .\" .IP \[bu] .\" money .\" Numbered list: .\" .nr step 1 1 .\" A numbered list: .\" .IP \n[step] 3 .\" lawyers .\" .IP \n+[step] .\" guns .\" .IP \n+[step] .\" money .TH "REFDB" "8" "2005-10-15" "" "refdb Manual" .SH "NAME" refdb \- refdbd startup script .SH "SYNOPSIS" \fBrefdb\fR \fIstart|stop\fR .SH "DESCRIPTION" refdb is a wrapper script for refdbd(1) to be used as a rc(8) or init(8) control script. The script is called refdb.sh on BSD-style systems. See the documentation of your system how to integrate refdb into the start process to run refdbd(1) automatically as a daemon. .SH "OPTIONS" .TP The script accepts only one of the arguments \fIstart\fR and \fIstop\fR to start and stop refdbd, respectively. .SH "SEE ALSO" \fBRefDB\fR (7), \fBrefdbd\fR (1) \fBrefdbctl\fR (1). .PP \fIRefDB manual (local copy) \fR <manualpath>/index.html .PP \fIRefDB manual (web) \fR <http://refdb.sourceforge.net/manual/index.html> .PP \fIRefDB on the web \fR <http://refdb.sourceforge.net/> .SH "AUTHOR" refdb was written by Markus Hoenicka <ma...@mh...>. .PP --- NEW FILE --- .so man8/refdb.8 --- NEW FILE --- .\" Hey, EMACS: -*- nroff -*- .\" .\" Filename: <FILENAME> .\" Author: David Nebauer .\" History: <DATE> - created .\" .\" For header (.TH), first parameter, NAME, should be all caps .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection .\" Other parameters are allowed: see man(7), man(1) .\" Please adjust the date whenever revising the manpage. .\" .\" Some roff macros, for reference: .\" .nh disable hyphenation .\" .hy enable hyphenation .\" .ad l left justify .\" .ad b justify to both left and right margins .\" .nf disable filling .\" .fi enable filling .\" .br insert line break .\" .sp <n> insert n+1 empty lines .\" for manpage-specific macros, see man(7) .\" .\" Formatting [see groff_char (7) for details]: .\" \(aq : escape sequence for (') .\" `` : left/open double quote .\" '' : right/close double quote .\" ` : left/open single quote .\" ' : right/close single quote .\" \(em : escape sequence for em dash .\" \(en : escape sequence for en dash .\" \. : escape sequence for period/dot .\" \fX : escape sequence that changes font, where 'X' can be 'R|I|B|BI' .\" (R = roman/normal | I = italic | B = bold | BI = bold-italic) .\" \fP : switch to previous font .\" in this case '\fR' could also have been used .\" .\" Bulleted list: .\" A bulleted list: .\" .IP \[bu] 2 .\" lawyers .\" .IP \[bu] .\" guns .\" .IP \[bu] .\" money .\" Numbered list: .\" .nr step 1 1 .\" A numbered list: .\" .IP \n[step] 3 .\" lawyers .\" .IP \n+[step] .\" guns .\" .IP \n+[step] .\" money .TH "REFDBA" "1" "2005-10-15" "" "refdba Manual" .SH "NAME" refdba \- the administration client of RefDB .SH "SYNOPSIS" .PP Interactive mode: .PP \fBrefdba\fR [\fB\-c\fR \fIpager-command\fR] [\fB\-e\fR \fIlog-destination\fR] [\fB\-f\fR \fIstdin\fR] [\fB\-h\fR] [\fB\-i\fR \fIIP-address\fR] [\fB\-l\fR \fIlog-level\fR] [\fB\-L\fR \fIlog-file\fR] [\fB\-p\fR \fIport\fR] [\fB\-q\fR] [\fB\-T\fR \fItime\fR] [\fB\-u\fR \fIname\fR] [\fB\-v\fR] [\fB\-V\fR] [\fB\-w\fR \fIpassword\fR] [\fB\-y\fR \fIconfdir\fR] .PP Non-Interactive mode: .PP \fBrefdba\fR \fB\-C\fR \fIcommand\fR [\fB\-c\fR \fIpager-command\fR] [\fB\-e\fR \fIlog-destination\fR] [\fB\-f\fR \fIstdin\fR] [\fB\-i\fR \fIIP-address\fR] [\fB\-l\fR \fIlog-level\fR] [\fB\-L\fR \fIlog-file\fR] [\fB\-p\fR \fIport\fR] [\fB\-q\fR] [\fB\-T\fR \fItime\fR] [\fB\-u\fR \fIname\fR] [\fB\-w\fR \fIpassword\fR] [\fB\-y\fR \fIconfdir\fR] .SH "DESCRIPTION" refdba is a command-line client providing the commands to administer RefDB(7) databases, users, and styles. refdba can be started in an interactive mode, providing a command prompt. Type \fB?\fR or \fBhelp\fR to see a list of available commands. Alternatively you can start refdba in non-interactive mode. refdba will execute the requested command and return. In this mode refdba will accept input on stdin for a variety of commands, allowing Unix piping. .PP This man page describes only the startup options of refdba. Please consult the RefDB manual (see below) for a description of the available commands. .SH "OPTIONS" .TP \fB\-c\fR \fIpager-command\fR The command line of the pager that is to be used. Instead of a pager you can of course specify any valid command that accepts data on stdin. Use "stdout" to request data output to stdout. This is the default, but you may want to specify it on the command line if you need to temporarily override a default pager setting in your configuration file. .TP \fB\-C\fR \fIcommand\fR The command to be run in non-interactive mode. You can supply all options and parameters that the command accepts on the refdba command line. .TP \fB\-e\fR \fIlog-destination\fR log-destination can have the values 0, 1, or 2, or the equivalent strings \fIstderr\fR, \fIsyslog\fR, or \fIfile\fR, respectively. This value specifies where the log information goes to. \fI0\fR (zero) means the messages are sent to stderr. They are immediately available on the screen but they may interfere with command output. \fI1\fR will send the output to the syslog facility. Keep in mind that syslog must be configured to accept log messages from user programs, see the syslog(8) man page for further information. Unix-like systems usually save these messages in \fI/var/log/user.log\fR. \fI2\fR will send the messages to a custom log file which can be specified with the \fI-L\fR option. .TP \fB\-f\fR \fIstdin\fR This 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, refdbib automatically reads data from stdin if data are available. .TP \fB\-h\fR Displays help and usage screen, then exits. .TP \fB\-i\fR \fIIP-address\fR Set the IP address of the box which is running the application server refdbd(1). Instead of the IP address you can also specify the hostname as long as it can be properly resolved by your system. .TP \fB\-l\fR \fIlog-level\fR Specify the priority up to which events are logged. This is either a number between \fI0\fR and \fI7\fR or one of the strings \fIemerg\fR, \fIalert\fR, \fIcrit\fR, \fIerr\fR, \fIwarning\fR, \fInotice\fR, \fIinfo\fR, \fIdebug\fR, respectively (see also Log level definitions). \fI-1\fR disables logging completely. A low log level like \fI0\fR means that only the most critical messages are logged. A higher log level means that less critical events are logged as well. \fI7\fR will include debug messages. The latter can be verbose and abundant, so you want to avoid this log level unless you need to track down problems. .TP \fB\-L\fR \fIlog-file\fR Specify the full path to a log file that will receive the log messages. Typically this would be \fI/var/log/refdba\fR. .TP \fB\-p\fR \fIport\fR Set the port of the box which is running the application server. .TP \fB\-q\fR Start without reading the configuration files. The client will use the compile-time defaults for all values that you do not set with command-line switches. .TP \fB\-T\fR \fItime\fR Set the timeout for client/application server dialogue in seconds. A connection with unsuccessful read or write attempts will be considered as dead and taken down after this amount of time has elapsed. .TP \fB\-u\fR \fIname\fR Set the username for the database access. Note: This username need not be identical to the login name of the user. This is the username required to access the database server. .TP \fB\-v\fR Prints version and copyright information, then exits. .TP \fB\-V\fR Switches to verbose mode. .TP \fB\-w\fR \fIpassword\fR Set the password for the database access. Note: This password need not be identical to the login password of the user. This is the password required to access the database server. .TP \fB\-y\fR \fIconfdir\fR Specify the directory where the global configuration files are Note: By default, all RefDB applications look for their configuration files in a directory that is specified during the configure step when building the package. That is, you don't need the \fB-y\fR option unless you use precompiled binaries in unusual locations, e.g. by relocating a rpm package. .SH "FILES" .TP \fI<etcpath>/refdbarc\fR The global configuration file of refdba. .TP \fI$HOME/.refdbarc\fR The user configuration file of refdba. .SH "SEE ALSO" \fBRefDB\fR (7), \fBrefdbd\fR (1), \fBrefdbc\fR (1). .PP \fIRefDB manual (local copy) \fR <manualpath>/... [truncated message content] |
|
From: Markus H. <mho...@us...> - 2005-10-17 18:12:59
|
Update of /cvsroot/refdb/refdb/man In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv12254/man Log Message: Directory /cvsroot/refdb/refdb/man added to the repository --> Using per-directory sticky tag `Release_0_9_5_stable' |
|
From: Markus H. <mho...@us...> - 2005-10-17 18:09:54
|
Update of /cvsroot/refdb/refdb In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv11858 Modified Files: Tag: Release_0_9_5_stable configure.in Makefile.am Log Message: added man subdirectory Index: configure.in =================================================================== RCS file: /cvsroot/refdb/refdb/configure.in,v retrieving revision 1.49.2.19 retrieving revision 1.49.2.20 diff -u -U2 -r1.49.2.19 -r1.49.2.20 --- configure.in 12 Oct 2005 19:24:48 -0000 1.49.2.19 +++ configure.in 17 Oct 2005 18:09:31 -0000 1.49.2.20 @@ -153,5 +153,5 @@ client_subdirs="declarations dsssl dtd styles xsl" client_bins="refdbib\$(EXEEXT) refdbc\$(EXEEXT) refdba\$(EXEEXT) refdbxp\$(EXEEXT) nmed2ris\$(EXEEXT) eenc\$(EXEEXT)" -client_scripts="refdbjade runbib refdb_tex2mail db2ris refdbxml marc2ris med2ris en2ris refdbnd refdb_dos2unix refdb-ms document-dtd-entities" +client_scripts="refdbjade runbib refdb_tex2mail db2ris refdbxml marc2ris med2ris en2ris refdbnd refdb_dos2unix refdb-ms" client_etc_objects="bib2risrc.example bib2riscgirc.example db2risrc.example nmed2risrc.example nmed2riscgirc.example refdbarc.example refdbcrc.example refdbcgirc.example refdbibrc.example med2risrc.example med2riscgirc.example marc2risrc.example refdbxmlrc.example" client_etc_distobjects="bib2risrc bib2riscgirc db2risrc nmed2risrc nmed2riscgirc refdbarc refdbcrc refdbcgirc refdbibrc med2risrc med2riscgirc marc2risrc refdbxmlrc" @@ -159,5 +159,5 @@ client_subdirs="declarations dsssl dtd etc examples scripts src styles xsl" client_bins="refdbib refdbc refdba refdbxp nmed2ris eenc" -client_scripts="refdbjade runbib refdb_tex2mail db2ris refdb-bug refdbxml marc2ris med2ris en2ris refdbnd refdb_dos2unix refdb-ms document-dtd-entities" +client_scripts="refdbjade runbib refdb_tex2mail db2ris refdb-bug refdbxml marc2ris med2ris en2ris refdbnd refdb_dos2unix refdb-ms" client_etc_objects="bib2risrc.example bib2riscgirc.example db2risrc.example nmed2risrc.example nmed2riscgirc.example refdbarc.example refdbcrc.example refdbcgirc.example refdbibrc.example med2risrc.example med2riscgirc.example marc2risrc.example refdbxmlrc.example" client_etc_distobjects="bib2risrc bib2riscgirc db2risrc nmed2risrc nmed2riscgirc refdbarc refdbcrc refdbcgirc refdbibrc med2risrc med2riscgirc marc2risrc refdbxmlrc" @@ -294,5 +294,4 @@ AC_SUBST(tei_xsl) AC_SUBST(classpath_root) -dnl AC_SUBST(refdb_url) AC_SUBST(log_dir) AC_SUBST(var_dir) @@ -367,5 +366,5 @@ fi dnl end if build clients -AC_OUTPUT(src/Makefile scripts/Makefile etc/Makefile doc/Makefile dtd/Makefile declarations/Makefile examples/Makefile styles/Makefile phpweb/Makefile dsssl/Makefile dsssl/refdb/Makefile dsssl/refdb/html/Makefile dsssl/refdb/print/Makefile dsssl/refdb/lib/Makefile xsl/Makefile xsl/refdb/Makefile xsl/refdb/common-refdb/Makefile xsl/refdb/docbk-refdb-xsl/Makefile xsl/refdb/docbk-refdb-xsl/docbk-fo/Makefile xsl/refdb/docbk-refdb-xsl/docbk-html/Makefile xsl/refdb/docbk-refdb-xsl/docbk-xhtml/Makefile xsl/refdb/docbk-refdb-xsl/docbk-lib/Makefile xsl/refdb/tei-refdb-xsl/Makefile xsl/refdb/tei-refdb-xsl/tei-fo/Makefile xsl/refdb/tei-refdb-xsl/tei-html/Makefile xsl/refdb/tei-refdb-xsl/tei-lib/Makefile Makefile) +AC_OUTPUT(src/Makefile scripts/Makefile etc/Makefile doc/Makefile dtd/Makefile declarations/Makefile examples/Makefile styles/Makefile phpweb/Makefile dsssl/Makefile dsssl/refdb/Makefile dsssl/refdb/html/Makefile dsssl/refdb/print/Makefile dsssl/refdb/lib/Makefile xsl/Makefile xsl/refdb/Makefile xsl/refdb/common-refdb/Makefile xsl/refdb/docbk-refdb-xsl/Makefile xsl/refdb/docbk-refdb-xsl/docbk-fo/Makefile xsl/refdb/docbk-refdb-xsl/docbk-html/Makefile xsl/refdb/docbk-refdb-xsl/docbk-xhtml/Makefile xsl/refdb/docbk-refdb-xsl/docbk-lib/Makefile xsl/refdb/tei-refdb-xsl/Makefile xsl/refdb/tei-refdb-xsl/tei-fo/Makefile xsl/refdb/tei-refdb-xsl/tei-html/Makefile xsl/refdb/tei-refdb-xsl/tei-lib/Makefile man/Makefile Makefile) echo Index: Makefile.am =================================================================== RCS file: /cvsroot/refdb/refdb/Makefile.am,v retrieving revision 1.15.2.3 retrieving revision 1.15.2.4 diff -u -U2 -r1.15.2.3 -r1.15.2.4 --- Makefile.am 17 Sep 2005 21:28:11 -0000 1.15.2.3 +++ Makefile.am 17 Oct 2005 18:09:31 -0000 1.15.2.4 @@ -1,5 +1,5 @@ ## Process this file with automake to produce Makefile.in -SUBDIRS = @client_subdirs@ @server_subdirs@ @docs_subdirs@ +SUBDIRS = @client_subdirs@ @server_subdirs@ @docs_subdirs@ man EXTRA_DIST = autogen.sh UPGRADING |
|
From: Markus H. <mho...@us...> - 2005-10-14 20:50:19
|
Update of /cvsroot/refdb/refdb/src In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv14803 Modified Files: Tag: Release_0_9_5_stable refdbdnote.c Log Message: commented out debug printf() call Index: refdbdnote.c =================================================================== RCS file: /cvsroot/refdb/refdb/src/refdbdnote.c,v retrieving revision 1.25.2.12 retrieving revision 1.25.2.13 diff -u -U2 -r1.25.2.12 -r1.25.2.13 --- refdbdnote.c 13 Oct 2005 21:18:23 -0000 1.25.2.12 +++ refdbdnote.c 14 Oct 2005 20:50:12 -0000 1.25.2.13 @@ -2648,4 +2648,5 @@ /* function will quote ptr_curr->value */ result = insert_link(my_type, ptr_curr->value, conn, n_id); +/* printf("my_type: %s<< ptr_curr->value: %s<<\n", my_type, ptr_curr->value); */ if (!result) { /* ok */ |
|
From: Markus H. <mho...@us...> - 2005-10-14 20:48:53
|
Update of /cvsroot/refdb/refdb/src In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv14405 Modified Files: Tag: Release_0_9_5_stable refdbc.c Log Message: addlink(), com_updatejo(): further quoting fixes Index: refdbc.c =================================================================== RCS file: /cvsroot/refdb/refdb/src/refdbc.c,v retrieving revision 1.72.2.11 retrieving revision 1.72.2.12 diff -u -U2 -r1.72.2.11 -r1.72.2.12 --- refdbc.c 11 Oct 2005 20:29:35 -0000 1.72.2.11 +++ refdbc.c 14 Oct 2005 20:48:37 -0000 1.72.2.12 @@ -5248,5 +5248,6 @@ /* printf("%d\n", optind); */ for (i = optind; i < inargc; i++) { - strcat(slvals.outbuffer, inargv[i]); + printf("inargv[%d]: %s<<\n", i, inargv[i]); +/* strcat(slvals.outbuffer, inargv[i]); */ /* the tokenizer returns a quoted item as a separate token even if there is no space between e.g. a '=' and the @@ -5254,5 +5255,18 @@ item ended with a '=' */ if (slvals.outbuffer[strlen(slvals.outbuffer)-1] != '=') { - strcat(slvals.outbuffer, " "); + strcat(slvals.outbuffer, inargv[i]); + if (slvals.outbuffer[strlen(slvals.outbuffer)-1] != '=') { + strcat(slvals.outbuffer, " "); + } + } + else { + /* quote item */ + strcat(slvals.outbuffer, "\'"); + + /* in order to allow e.g. single quotes in journal names we + must escape the string properly. It will be unescaped on + the server side */ + escape_chars(slvals.outbuffer + strlen(slvals.outbuffer), inargv[i], strlen(inargv[i]), "'\""); + strcat(slvals.outbuffer, "\' "); } } @@ -5559,5 +5573,7 @@ if (slvals.outbuffer[strlen(slvals.outbuffer)-1] != '=') { strcat(slvals.outbuffer, inargv[i]); -/* strcat(slvals.outbuffer, " "); */ + if (slvals.outbuffer[strlen(slvals.outbuffer)-1] != '=') { + strcat(slvals.outbuffer, " "); + } } else { |
|
From: Markus H. <mho...@us...> - 2005-10-13 21:18:34
|
Update of /cvsroot/refdb/refdb/src In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv30915 Modified Files: Tag: Release_0_9_5_stable refdbdnote.c Log Message: quoting fixes Index: refdbdnote.c =================================================================== RCS file: /cvsroot/refdb/refdb/src/refdbdnote.c,v retrieving revision 1.25.2.11 retrieving revision 1.25.2.12 diff -u -U2 -r1.25.2.11 -r1.25.2.12 --- refdbdnote.c 23 Sep 2005 23:48:34 -0000 1.25.2.11 +++ refdbdnote.c 13 Oct 2005 21:18:23 -0000 1.25.2.12 @@ -2387,4 +2387,5 @@ char *newtoken; char *quoted_token; + char *stripped_token; char *eostring; char note_val[256] = ""; /* note id or citation key value*/ @@ -2523,6 +2524,16 @@ token = nstrtok(buffer, &len, " "); if (token != NULL) { -/* printf("key:%s<<value:%s<<\n", field_buffer, quoted_token); */ - if (insert_liliform(&link_sentinel, field_buffer, token)) { +/* printf("key:%s<<value:%s<<\n", field_buffer, token); */ + quoted_token = malloc(strlen(token)+1); + if (!quoted_token) { + error = 1; + break; + } + + stripped_token = strip_quote(token); + + unescape_chars(quoted_token, stripped_token, strlen(stripped_token)); +/* printf("key:%s<<value:%s<<\n", field_buffer, quoted_token); */ + if (insert_liliform(&link_sentinel, field_buffer, quoted_token)) { error = 1; break; @@ -2534,4 +2545,5 @@ strncmp(token, ":NCK:", 5) == 0) { + /* there is no need to unescape/quote these */ strcpy(field_buffer, buffer); field_buffer[5] = '\0'; /* terminate string */ @@ -2634,8 +2646,7 @@ /* add links */ if (!n_remove) { + /* function will quote ptr_curr->value */ result = insert_link(my_type, ptr_curr->value, conn, n_id); - /* todo: fix output */ - if (!result) { /* ok */ sprintf(assemble_buffer, "421:%s -> %s:%s\n", note_val, my_type, ptr_curr->value); @@ -2651,4 +2662,6 @@ } +/* free(ptr_curr->value); */ + if ((new_buffer = mstrcat(return_msg, assemble_buffer, &return_msg_len, 0)) == NULL) { send_status(ptr_clrequest->fd, 801, TERM_NO); @@ -2775,5 +2788,5 @@ return_msg = new_buffer; } - } + } /* end if add */ } /* end while */ |
|
From: Markus H. <mho...@us...> - 2005-10-13 21:17:12
|
Update of /cvsroot/refdb/refdb/src In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv30612 Modified Files: Tag: Release_0_9_5_stable refdbdref.c Log Message: removed superfluous free calls Index: refdbdref.c =================================================================== RCS file: /cvsroot/refdb/refdb/src/refdbdref.c,v retrieving revision 1.65.2.18 retrieving revision 1.65.2.19 diff -u -U2 -r1.65.2.18 -r1.65.2.19 --- refdbdref.c 11 Oct 2005 20:32:55 -0000 1.65.2.18 +++ refdbdref.c 13 Oct 2005 21:17:00 -0000 1.65.2.19 @@ -2126,5 +2126,5 @@ newtoken = token; - printf("%s\n", token); +/* printf("%s\n", token); */ /* general strategy: scan the command string for items and add all of @@ -2173,5 +2173,4 @@ len = 0; - /* terminate token at the next unprotected space */ token = nstrtok(buffer, &len, " "); if (token != NULL) { @@ -2274,17 +2273,13 @@ if (!strcmp(ptr_curr->name, ":JO:")) { strcpy(jo, quoted_token); - free(ptr_curr->value); } else if (!strcmp(ptr_curr->name, ":JF:")) { strcpy(jf, quoted_token); - free(ptr_curr->value); } else if (!strcmp(ptr_curr->name, ":J1:")) { strcpy(j1, quoted_token); - free(ptr_curr->value); } else if (!strcmp(ptr_curr->name, ":J2:")) { strcpy(j2, quoted_token); - free(ptr_curr->value); } free(quoted_token); |
|
From: Markus H. <mho...@us...> - 2005-10-13 20:06:56
|
Update of /cvsroot/refdb/refdb/scripts In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv15594 Modified Files: Tag: Release_0_9_5_stable Makefile.am Log Message: removed document-dtd-entities Index: Makefile.am =================================================================== RCS file: /cvsroot/refdb/refdb/scripts/Makefile.am,v retrieving revision 1.23.2.7 retrieving revision 1.23.2.8 diff -u -U2 -r1.23.2.7 -r1.23.2.8 --- Makefile.am 12 Oct 2005 19:24:49 -0000 1.23.2.7 +++ Makefile.am 13 Oct 2005 20:06:47 -0000 1.23.2.8 @@ -1,7 +1,7 @@ ## Process this file with automake to produce Makefile.in -EXTRA_SCRIPTS = refdbjade runbib refdb_tex2mail db2ris refdb-bug refdbxml marc2ris med2ris en2ris refdbnd refdb_dos2unix refdbctl refdb-ms document-dtd-entities +EXTRA_SCRIPTS = refdbjade runbib refdb_tex2mail db2ris refdb-bug refdbxml marc2ris med2ris en2ris refdbnd refdb_dos2unix refdbctl refdb-ms bin_SCRIPTS = @server_scripts@ @client_scripts@ -EXTRA_DIST=refdb.in refdbjade.in runbib.in refdb_tex2mail db2ris.in refdb-bug.in refdbxml.in refdb refdbctl.in empty.mysql.dump empty.pgsql.dump.in refdb-upgrade.sql marc2ris.in med2ris.in en2ris.in refdbnd.in vargen.pl libgen.pl statgen.pl refdb_dos2unix.in migrate_mysql_0.9.5 refdb.dump.mysql.in refdb.dump.mysql41.in refdb.dump.pgsql.in refdb.dump.sqlite.in refdb-ms document-dtd-entities +EXTRA_DIST=refdb.in refdbjade.in runbib.in refdb_tex2mail db2ris.in refdb-bug.in refdbxml.in refdb refdbctl.in empty.mysql.dump empty.pgsql.dump.in refdb-upgrade.sql marc2ris.in med2ris.in en2ris.in refdbnd.in vargen.pl libgen.pl statgen.pl refdb_dos2unix.in migrate_mysql_0.9.5 refdb.dump.mysql.in refdb.dump.mysql41.in refdb.dump.pgsql.in refdb.dump.sqlite.in refdb-ms MOSTLYCLEANFILES=refdb refdbjade runbib db2ris refdbxml refdbctl refdb-bug refdbnd marc2ris med2ris en2ris refdb_dos2unix refdb.dump.mysql refdb.dump.mysql41 refdb.dump.pgsql refdb.dump.sqlite |
|
From: Markus H. <mho...@us...> - 2005-10-13 20:06:17
|
Update of /cvsroot/refdb/refdb/scripts In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv15443 Removed Files: Tag: Release_0_9_5_stable document-dtd-entities Log Message: gone for good --- document-dtd-entities DELETED --- |
|
From: Markus H. <mho...@us...> - 2005-10-12 19:27:39
|
Update of /cvsroot/refdb/perlmod/RefDB In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv18813 Modified Files: version Log Message: bumped up version number Index: version =================================================================== RCS file: /cvsroot/refdb/perlmod/RefDB/version,v retrieving revision 1.3 retrieving revision 1.4 diff -u -U2 -r1.3 -r1.4 --- version 8 Jul 2003 21:37:22 -0000 1.3 +++ version 12 Oct 2005 19:27:31 -0000 1.4 @@ -1 +1 @@ -$VERSION = '0.3'; +$VERSION = '0.4'; |
|
From: Markus H. <mho...@us...> - 2005-10-12 19:27:24
|
Update of /cvsroot/refdb/perlmod/RefDB In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv18744 Modified Files: MANIFEST Log Message: added Makestyle.pm Index: MANIFEST =================================================================== RCS file: /cvsroot/refdb/perlmod/RefDB/MANIFEST,v retrieving revision 1.2 retrieving revision 1.3 diff -u -U2 -r1.2 -r1.3 --- MANIFEST 23 Feb 2003 20:59:06 -0000 1.2 +++ MANIFEST 12 Oct 2005 19:27:13 -0000 1.3 @@ -8,6 +8,8 @@ Log.pm Prefs.pm +Makestyle.pm testdata/testdata.good.sorted testdata/testdata.in testdata/testdata_pm.good.sorted testdata/testrc +META.yml Module meta-data (added by MakeMaker) |
|
From: Markus H. <mho...@us...> - 2005-10-12 19:27:05
|
Update of /cvsroot/refdb/perlmod/RefDB In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv18621 Modified Files: Makefile.PL Log Message: added David as author Index: Makefile.PL =================================================================== RCS file: /cvsroot/refdb/perlmod/RefDB/Makefile.PL,v retrieving revision 1.2 retrieving revision 1.3 diff -u -U2 -r1.2 -r1.3 --- Makefile.PL 16 Sep 2003 21:05:09 -0000 1.2 +++ Makefile.PL 12 Oct 2005 19:26:51 -0000 1.3 @@ -5,5 +5,5 @@ 'NAME' => 'RefDB::perlmod', 'VERSION_FROM' => 'version', # finds $VERSION - 'AUTHOR' => 'Markus Hoenicka <ma...@mh...>', + 'AUTHOR' => 'Markus Hoenicka <ma...@mh...>, David Nebauer <da...@ne...>', 'PREREQ_PM' => { 'Text::Iconv' => '1.2', |
|
From: Markus H. <mho...@us...> - 2005-10-12 19:26:34
|
Update of /cvsroot/refdb/perlmod/RefDB In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv18287 Added Files: Makestyle.pm Log Message: moved over from makestyle module --- NEW FILE --- package RefDB::Makestyle; use 5.008006; use strict; use warnings; use base qw(Exporter); our $VERSION = '1.1'; =head1 NAME RefDB::Makestyle - methods used by refdb-ms (RefDB style generator) =head1 SUMMARY Makestyle.pm - a module used by I<refdb-ms> (RefDB MakeStyle) -- a utility that generates RefDB bibliography I<style>s. Provides C<< Element >> and C<< Attribute >> classes for use in generating RefDB I<style>s. [...6297 lines suppressed...] =back =cut 1; __END__ =head1 AUTHOR David Nebauer, david E<lt>atE<gt> nebauer E<lt>dotE<gt> org =head1 COPYRIGHT AND LICENSE Copyright (C) 2004 by David Nebauer This library is distributed under the same license and conditions as the C<RefDB> project E<lt>L<http://refdb.sourceforge.net/>E<gt>. =cut |
|
From: Markus H. <mho...@us...> - 2005-10-12 19:24:57
|
Update of /cvsroot/refdb/refdb/scripts In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv18054/scripts Modified Files: Tag: Release_0_9_5_stable Makefile.am Log Message: added refdb-ms and document-dtd-entities Index: Makefile.am =================================================================== RCS file: /cvsroot/refdb/refdb/scripts/Makefile.am,v retrieving revision 1.23.2.6 retrieving revision 1.23.2.7 diff -u -U2 -r1.23.2.6 -r1.23.2.7 --- Makefile.am 19 Apr 2005 19:33:53 -0000 1.23.2.6 +++ Makefile.am 12 Oct 2005 19:24:49 -0000 1.23.2.7 @@ -1,7 +1,7 @@ ## Process this file with automake to produce Makefile.in -EXTRA_SCRIPTS = refdbjade runbib refdb_tex2mail db2ris refdb-bug refdbxml marc2ris med2ris en2ris refdbnd refdb_dos2unix refdbctl +EXTRA_SCRIPTS = refdbjade runbib refdb_tex2mail db2ris refdb-bug refdbxml marc2ris med2ris en2ris refdbnd refdb_dos2unix refdbctl refdb-ms document-dtd-entities bin_SCRIPTS = @server_scripts@ @client_scripts@ -EXTRA_DIST=refdb.in refdbjade.in runbib.in refdb_tex2mail db2ris.in refdb-bug.in refdbxml.in refdb refdbctl.in empty.mysql.dump empty.pgsql.dump.in refdb-upgrade.sql marc2ris.in med2ris.in en2ris.in refdbnd.in vargen.pl libgen.pl statgen.pl refdb_dos2unix.in migrate_mysql_0.9.5 refdb.dump.mysql.in refdb.dump.mysql41.in refdb.dump.pgsql.in refdb.dump.sqlite.in +EXTRA_DIST=refdb.in refdbjade.in runbib.in refdb_tex2mail db2ris.in refdb-bug.in refdbxml.in refdb refdbctl.in empty.mysql.dump empty.pgsql.dump.in refdb-upgrade.sql marc2ris.in med2ris.in en2ris.in refdbnd.in vargen.pl libgen.pl statgen.pl refdb_dos2unix.in migrate_mysql_0.9.5 refdb.dump.mysql.in refdb.dump.mysql41.in refdb.dump.pgsql.in refdb.dump.sqlite.in refdb-ms document-dtd-entities MOSTLYCLEANFILES=refdb refdbjade runbib db2ris refdbxml refdbctl refdb-bug refdbnd marc2ris med2ris en2ris refdb_dos2unix refdb.dump.mysql refdb.dump.mysql41 refdb.dump.pgsql refdb.dump.sqlite |
|
From: Markus H. <mho...@us...> - 2005-10-12 19:24:57
|
Update of /cvsroot/refdb/refdb In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv18054 Modified Files: Tag: Release_0_9_5_stable configure.in Log Message: added refdb-ms and document-dtd-entities Index: configure.in =================================================================== RCS file: /cvsroot/refdb/refdb/configure.in,v retrieving revision 1.49.2.18 retrieving revision 1.49.2.19 diff -u -U2 -r1.49.2.18 -r1.49.2.19 --- configure.in 17 Sep 2005 21:29:25 -0000 1.49.2.18 +++ configure.in 12 Oct 2005 19:24:48 -0000 1.49.2.19 @@ -153,5 +153,5 @@ client_subdirs="declarations dsssl dtd styles xsl" client_bins="refdbib\$(EXEEXT) refdbc\$(EXEEXT) refdba\$(EXEEXT) refdbxp\$(EXEEXT) nmed2ris\$(EXEEXT) eenc\$(EXEEXT)" -client_scripts="refdbjade runbib refdb_tex2mail db2ris refdbxml marc2ris med2ris en2ris refdbnd refdb_dos2unix" +client_scripts="refdbjade runbib refdb_tex2mail db2ris refdbxml marc2ris med2ris en2ris refdbnd refdb_dos2unix refdb-ms document-dtd-entities" client_etc_objects="bib2risrc.example bib2riscgirc.example db2risrc.example nmed2risrc.example nmed2riscgirc.example refdbarc.example refdbcrc.example refdbcgirc.example refdbibrc.example med2risrc.example med2riscgirc.example marc2risrc.example refdbxmlrc.example" client_etc_distobjects="bib2risrc bib2riscgirc db2risrc nmed2risrc nmed2riscgirc refdbarc refdbcrc refdbcgirc refdbibrc med2risrc med2riscgirc marc2risrc refdbxmlrc" @@ -159,5 +159,5 @@ client_subdirs="declarations dsssl dtd etc examples scripts src styles xsl" client_bins="refdbib refdbc refdba refdbxp nmed2ris eenc" -client_scripts="refdbjade runbib refdb_tex2mail db2ris refdb-bug refdbxml marc2ris med2ris en2ris refdbnd refdb_dos2unix" +client_scripts="refdbjade runbib refdb_tex2mail db2ris refdb-bug refdbxml marc2ris med2ris en2ris refdbnd refdb_dos2unix refdb-ms document-dtd-entities" client_etc_objects="bib2risrc.example bib2riscgirc.example db2risrc.example nmed2risrc.example nmed2riscgirc.example refdbarc.example refdbcrc.example refdbcgirc.example refdbibrc.example med2risrc.example med2riscgirc.example marc2risrc.example refdbxmlrc.example" client_etc_distobjects="bib2risrc bib2riscgirc db2risrc nmed2risrc nmed2riscgirc refdbarc refdbcrc refdbcgirc refdbibrc med2risrc med2riscgirc marc2risrc refdbxmlrc" |
1 message has been excluded from this view by a project administrator.
