/usr/share/doc/refdb/refdb-manual/ch07.html

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 7. Data input</title><link rel="stylesheet" type="text/css" href="manual.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /><link rel="home" href="index.html" title="RefDB handbook" /><link rel="up" href="pt03.html" title="Part III. User manual" /><link rel="prev" href="ch06s05.html" title="Common command-line options for all clients" /><link rel="next" href="ch07s02.html" title="The Emacs helpers" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 7. Data input</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch06s05.html">Prev</a> </td><th width="60%" align="center">Part III. User manual</th><td width="20%" align="right"> <a accesskey="n" href="ch07s02.html">Next</a></td></tr></table><hr /></div><div class="chapter"><div class="titlepage"><div><div><h2 class="title"><a id="chapter-data-input"></a>Chapter 7. Data input</h2></div></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="sect1"><a href="ch07.html#sect1-ris-format">Writing RIS datasets</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch07.html#idp66711760">Overview</a></span></dt><dt><span class="sect2"><a href="ch07.html#idp66560960">Character encodings</a></span></dt><dt><span class="sect2"><a href="ch07.html#idp66564016">RIS tags</a></span></dt><dt><span class="sect2"><a href="ch07.html#idp67940896">Examples</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch07s02.html">The Emacs helpers</a></span></dt><dt><span class="sect1"><a href="ch07s03.html">Input filters</a></span></dt><dt><span class="sect1"><a href="ch07s04.html">Writing risx datasets</a></span></dt><dt><span class="sect1"><a href="ch07s05.html">Writing extended notes</a></span></dt><dt><span class="sect1"><a href="ch07s06.html">Input data mangling</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch07s06.html#idp68071968">Information that RefDB generates for you</a></span></dt><dt><span class="sect2"><a href="ch07s06.html#idp68078496">Information that RefDB mangles</a></span></dt></dl></dd></dl></div><p>This chapter explains the ways how you can generate reference and extended note data suitable for RefDB databases. We'll cover manual generation of RIS files and automatic conversion of other bibliographic data with the help of input filters. You'll learn about writing risx documents, a new XML data format designed to simplify funneling XML or SGML bibliographic data into RefDB. risx is the preferable format to fully utilize RefDB's capabilities. Finally we'll cover writing extended notes that allow to append additional information to objects in your database or to categorize references in a very flexible way.</p><p>To actually import the resulting RIS datasets into the RefDB database, use the <a class="link" href="ch08.html#sect1-add-references" title="Add references">addref</a> command of the refdbc command line client, as explained in the next chapter.</p><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="sect1-ris-format"></a>Writing RIS datasets</h2></div></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a id="idp66711760"></a>Overview</h3></div></div></div><p>The <a class="ulink" href="http://www.referencemanager.com/support/docs/ReferenceManager11.pdf" target="_top">Reference Manager Manual</a> contains sort of a specification of the RIS data format. This format is a tagged file format with the following general rules:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>A file can hold one or more references</p></li><li class="listitem"><p>Each reference starts with a newline. This also means that every RIS file starts with an empty line.</p></li><li class="listitem"><p>There can be only one tag per line.</p></li><li class="listitem"><p>The tag must be at the very beginning of the line.</p></li><li class="listitem"><p>The tags consist of two capital letters denoting the type, followed by two spaces, a dash, and another space.</p></li><li class="listitem"><p>The first tag of each reference is the Type tag (TY  - )</p></li><li class="listitem"><p>The last tag of each reference is the End tag (ER  - )</p></li><li class="listitem"><p>The sequence of all other elements is arbitrary.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>There is one exception: In the case of multiple authors, editors, or series editors, the sequence of these authors <span class="emphasis"><em>is</em></span> significant. E.g. the first AU tag will be used as the first author, the last one as the last author.</p></div></li></ul></div><p>Therefore a minimal RIS file may look like this:</p><pre class="programlisting"><a id="newline"></a><span><img src="images/callouts/1.png" alt="1" border="0" /></span>
TY  - BOOK                 <a id="type"></a><span><img src="images/callouts/2.png" alt="2" border="0" /></span> 
AU  - Hoenicka,M.          <a id="contents"></a><span><img src="images/callouts/3.png" alt="3" border="0" /></span>
TI  - The RefDB manual
PY  - 2001
ER  -                      <a id="end"></a><span><img src="images/callouts/4.png" alt="4" border="0" /></span></pre><div class="calloutlist"><table border="0" summary="Callout list"><tr><td width="5%" valign="top" align="left"><p><a href="#newline"><span><img src="images/callouts/1.png" alt="1" border="0" /></span></a> </p></td><td valign="top" align="left"><p>This is the empty line generated by a linefeed character (0x0A) that precedes every RIS citation, even at the start of a RIS file.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a href="#type"><span><img src="images/callouts/2.png" alt="2" border="0" /></span></a> </p></td><td valign="top" align="left"><p>This is the mandatory first tag, the type specifier. In this case, we're looking at a BOOK entry.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a href="#contents"><span><img src="images/callouts/3.png" alt="3" border="0" /></span></a> </p></td><td valign="top" align="left"><p>This and the following lines are the contents proper of the citation. All additional tags would go here as well</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a href="#end"><span><img src="images/callouts/4.png" alt="4" border="0" /></span></a> </p></td><td valign="top" align="left"><p>This is the mandatory last tag which closes the citation. Although invisible here, this tag also has a trailing space like all others.</p></td></tr></table></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a id="idp66560960"></a>Character encodings</h3></div></div></div><p>The RIS specification has no built-in means to specify the character encoding of the data. Commercial applications usually expect the data to be supplied in a particular encoding (e.g. Reference Manager uses the Windows ANSI character set). RefDB does not have this limitation, you are free to use any encoding available on your platform (except UTF-16 and UTF-32). However, you should be aware that this may cause an interchange issue if you plan to use these data in a commercial reference management program. In any case, as the datasets do not specify their encoding, you have to use <code class="option">-E</code> option of the <a class="link" href="re11.html#app-c-command-getref" title="getref">getref</a> command if your input data use an encoding different from the default (UTF-8).</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a id="idp66564016"></a>RIS tags</h3></div></div></div><p>The following list shows all available tags and their use.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Please keep in mind that a full tag consists of the letters mentioned below followed by two spaces, a dash, and another space. E.g. the first tag below would be written as <span class="quote">“<span class="quote"><code class="computeroutput">TY  - </code></span>”</span> in a RIS file.</p></div><div class="variablelist"><dl class="variablelist"><dt><span class="term"><a id="ris-typetag"></a>TY</span></dt><dd><p>This tag specifies the type of the reference and must be the first tag of each RIS dataset, preceeded by a newline.</p><p><span class="emphasis"><em>Format:</em></span> This can be any of the following strings:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>ABST (abstract reference)</p></li><li class="listitem"><p>ADVS (audiovisual material)</p></li><li class="listitem"><p>ART (art work)</p></li><li class="listitem"><p>BILL (bill/resolution)</p></li><li class="listitem"><p>BOOK (whole book reference)</p></li><li class="listitem"><p>CASE (case)</p></li><li class="listitem"><p>CHAP (book chapter reference)</p></li><li class="listitem"><p>COMP (computer program)</p></li><li class="listitem"><p>CONF (conference proceeding)</p></li><li class="listitem"><p>CTLG (catalog)</p></li><li class="listitem"><p>DATA (data file)</p></li><li class="listitem"><p>ELEC (electronic citation)</p></li><li class="listitem"><p>GEN (generic)</p></li><li class="listitem"><p>HEAR (hearing)</p></li><li class="listitem"><p>ICOMM (internet communication)</p></li><li class="listitem"><p>INPR (in press reference)</p></li><li class="listitem"><p>JFULL (journal/periodical - full)</p></li><li class="listitem"><p>JOUR (journal/periodical reference)</p></li><li class="listitem"><p>MAP (map)</p></li><li class="listitem"><p>MGZN (magazine article)</p></li><li class="listitem"><p>MPCT (motion picture)</p></li><li class="listitem"><p>MUSIC (music score)</p></li><li class="listitem"><p>NEWS (newspaper)</p></li><li class="listitem"><p>PAMP (pamphlet)</p></li><li class="listitem"><p>PAT (patent)</p></li><li class="listitem"><p>PCOMM (personal communication)</p></li><li class="listitem"><p>RPRT (report)</p></li><li class="listitem"><p>SER (serial - book, monograph)</p></li><li class="listitem"><p>SLIDE (slide)</p></li><li class="listitem"><p>SOUND (sound recording)</p></li><li class="listitem"><p>STAT (statute)</p></li><li class="listitem"><p>THES (thesis/dissertation)</p></li><li class="listitem"><p>UNBILL (unenacted bill/resolution)</p></li><li class="listitem"><p>UNPB (unpublished work reference)</p></li><li class="listitem"><p>VIDEO (video recording)</p></li></ul></div></dd><dt><span class="term">ER</span></dt><dd><p>This empty tag denotes the end of the reference. It must be the last tag of each RIS dataset.</p></dd><dt><span class="term">ID</span></dt><dd><p>This tag is used to uniquely identify the reference in the database. The value is either the unique ID that RefDB generates when a reference is imported into a database, or a unique citation key. The latter can be supplied by the user. If no citation key is specified when adding a reference, RefDB will automatically generate a unique citation key, based on the name of the first author and the publication year. RefDB will create an unique ID value for internal use regardless of whether a citation key is provided or not.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>ID values are always numerical (e.g. "11"), whereas citation keys are alphanumerical (e.g. "Miller1999").</p><p>While you are free to choose any reasonable citation key (as long as it is unique within the database), you should not attempt to create a ID value manually. It is ignored when adding the dataset, but it may overwrite an existing entry if you update a reference. Along the same line, you should leave the ID tag alone if you retrieve a dataset from the database and plan to update it. The citation key in the retrieved data set is essential to match the modified data with the copy in the database.</p></div><p><span class="emphasis"><em> ID Format:</em></span> Integer &gt;0.</p><p><span class="emphasis"><em> Citation key Format:</em></span> A string with up to 255 characters. You should use 7-bit ASCII characters only to avoid character encoding issues. If you want to work with SGML documents, the citation keys should be all uppercase.</p></dd><dt><span class="term">TI</span></dt><dd><p>This is the title of a publication. For BOOK and UNPB references this is the same as the BT tag.</p><p><span class="emphasis"><em>Format:</em></span> A string with unlimited length.</p></dd><dt><span class="term">T2</span></dt><dd><p>This is the secondary title of a publication, e.g. the book title for a CHAP reference.</p><p><span class="emphasis"><em>Format:</em></span> A string with unlimited length.</p></dd><dt><span class="term">T3</span></dt><dd><p>This is the tertiary title of a publication, e.g. the series title for a CHAP reference.</p><p><span class="emphasis"><em>Format:</em></span> A string with unlimited length.</p></dd><dt><span class="term">AU</span></dt><dd><p>Synonym: A1. This is the name of one author of the reference. If a reference has multiple authors, each author is specified with an AU tag on a separate line. The number of authors per RIS dataset is not limited. The sequence of the authors in the authorlist will be determined from the sequence as they appear in the RIS dataset.</p><p><span class="emphasis"><em>Format:</em></span> A string with up to 255 characters in the form: Lastname[,(F.|First)[(M.|Middle)...][,Suffix]]. First and middle names can either be abbreviated or spelled out. Use periods to separate initials, and spaces to separate spelled-out first or middle names. Lastname can be a corporate name. Some examples for valid entries:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>King,B.B.</p></li><li class="listitem"><p>Benberg,Steven C.</p></li><li class="listitem"><p>Mellencamp,John Cougar,Jr.</p></li><li class="listitem"><p>Van Zandt,Steven</p></li></ul></div></dd><dt><span class="term">A2</span></dt><dd><p>Synonym: ED. This is the name of an editor of the reference, e.g. an editor of the book in which a CHAP reference was published. The same formatting requirements as for AU apply.</p></dd><dt><span class="term">A3</span></dt><dd><p>This is the name of a series editor of the reference, e.g. an editor of a series of books in one of which a CHAP reference was published. The same formatting requirements as for AU apply.</p></dd><dt><span class="term">PY</span></dt><dd><p>Synonym: Y1. This is the primary publication date.</p><p><span class="emphasis"><em>Format:</em></span> A string with the format <span class="quote">“<span class="quote">YYYY/MM/DD/otherinfo</span>”</span>, where YYYY denotes the four-digit year, MM and DD denote the two-digit month and day, respectively, and otherinfo denotes any other information with up to 255 characters. If any of these parts is not available, it can be left out, but the slashes must be present. E.g. <span class="quote">“<span class="quote">1999///Christmas edition</span>”</span> is a valid string.</p></dd><dt><span class="term">Y2</span></dt><dd><p>This is the secondary publication date.</p><p><span class="emphasis"><em>Format:</em></span> A string with the format <span class="quote">“<span class="quote">YYYY/MM/DD/otherinfo</span>”</span>, where YYYY denotes the four-digit year, MM and DD denote the two-digit month and day, respectively, and otherinfo denotes any other information with up to 255 characters. If any of these parts is not available, it can be left out, but the slashes must be present. E.g. <span class="quote">“<span class="quote">1999///Christmas edition</span>”</span> is a valid string.</p></dd><dt><span class="term">N1</span></dt><dd><p>Synonym: AB (this is not logical as it sounds like ABstract, but I'm sure there is a reason in RIS' crooked history). The notes. This can be any form of additional information, like pointers to corrections or editorials, or just personal notes about the contents of the reference.</p><p><span class="emphasis"><em>Format:</em></span> A string with unlimited length</p></dd><dt><span class="term">N2</span></dt><dd><p>The abstract of a reference.</p><p><span class="emphasis"><em>Format:</em></span> A string with unlimited length</p></dd><dt><span class="term">KW</span></dt><dd><p>A keyword. If a publication has multiple keywords, each goes on a separate line preceeded with this tag. Keywords are crucial to find references in larger databases.</p><p><span class="emphasis"><em>Format:</em></span> A string with up to 255 characters</p></dd><dt><span class="term">RP</span></dt><dd><p>The reprint status of a reference. This can be any of the following strings:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>IN FILE</p></li><li class="listitem"><p>NOT IN FILE</p></li><li class="listitem"><p>ON REQUEST MM/DD/YY</p></li></ul></div></dd><dt><span class="term">AV</span></dt><dd><p>The availability information. This is a hint where you can find a physical copy or offprint of the reference.</p><p><span class="emphasis"><em>Format:</em></span> A string with up to 255 characters. This can either be a plain-text description like "methods folder, second drawer from top in the green cabinet on the yellow hallway", or a call number.</p></dd><dt><span class="term">SP</span></dt><dd><p>The start page of the reference</p><p><span class="emphasis"><em>Format:</em></span> A string with up to 255 characters</p></dd><dt><span class="term">EP</span></dt><dd><p>The end page of the reference</p><p><span class="emphasis"><em>Format:</em></span> A string with up to 255 characters</p></dd><dt><span class="term">JO</span></dt><dd><p>The abbreviated name of a journal or periodical.</p><p><span class="emphasis"><em>Format:</em></span> A string with up to 255 characters. The components should be separated by a single space without a period after abbreviated words. If you use periods, these should not be followed by spaces.</p></dd><dt><span class="term">JF</span></dt><dd><p>The full name of a journal or periodical.</p><p><span class="emphasis"><em>Format:</em></span> A string with up to 255 characters</p></dd><dt><span class="term">J1</span></dt><dd><p>The abbreviated name of a journal or periodical (user abbreviation 1).</p><p><span class="emphasis"><em>Format:</em></span> A string with up to 255 characters</p></dd><dt><span class="term">J2</span></dt><dd><p>The abbreviated name of a journal or periodical (user abbreviation 2).</p><p><span class="emphasis"><em>Format:</em></span> A string with up to 255 characters</p></dd><dt><span class="term">VL</span></dt><dd><p>The volume of the journal/periodical.</p><p><span class="emphasis"><em>Format:</em></span> A string with up to 255 characters</p></dd><dt><span class="term">IS</span></dt><dd><p>The issue of the journal/periodical</p><p><span class="emphasis"><em>Format:</em></span> A string with up to 255 characters</p></dd><dt><span class="term">CY</span></dt><dd><p>City of publication of a book.</p><p><span class="emphasis"><em>Format:</em></span> A string with up to 255 characters</p></dd><dt><span class="term">PB</span></dt><dd><p>Name of the publisher or the publishing company.</p><p><span class="emphasis"><em>Format:</em></span> A string with up to 255 characters</p></dd><dt><span class="term">SN</span></dt><dd><p>The ISBN or ISSN number.</p><p><span class="emphasis"><em>Format:</em></span> A string with up to 255 characters</p></dd><dt><span class="term">AD</span></dt><dd><p>The contact address, usually the any combination of postal or email address and the phone or fax number of the corresponding author.</p><p><span class="emphasis"><em>Format:</em></span> A string of unlimited length</p></dd><dt><span class="term">UR</span></dt><dd><p>The URL of an online version of the reference.</p><p><span class="emphasis"><em>Format:</em></span> A string with up to 255 characters</p></dd><dt><span class="term">L1 through L4</span></dt><dd><p>These fields hold the URLs of an offprint (e.g. a PDF or Postscript copy), of the fulltext (often available as HTML in addition to PDF), of a related resource, and of an image, respectively. Multiple entries of each type per reference are allowed. In contrast to the UR field above, these fields hold information which is stored for each user separately.</p><p>The L1 field is meant to store the location of local offprints. It is most common to use the "file://" protocol and specify a full path (starting with another slash on Unix systems) or a relative path. In the latter case the path is expanded with the pdfroot setting before it is displayed to the user. Using this feature requires some thought and is therefore explained in a separate <a class="link" href="ch08s10.html" title="Use pdfroot">section</a>.</p><p><span class="emphasis"><em>Format:</em></span> A string with up to 255 characters</p></dd><dt><span class="term">U1 through U5</span></dt><dd><p>The user-defined fields 1 through 5. These fields are not intended to be filled with random bits of information. Each database should have a set of rules what information is to be stored in these fields.</p><p>A possible use for these fields is some relevance indicator (e.g. <span class="quote">“<span class="quote">#</span>”</span> means low, <span class="quote">“<span class="quote">#####</span>”</span> means high relevance).</p><p>You may also use one of these fields to create the equivalents of <span class="quote">“<span class="quote">folders</span>”</span> that some other reference databases praise as the panacea to organize your references. Just assign the same value to one of these fields for all references that belong to the same folder. Retrieve them by specifying this value in addition to your other search criteria.</p><p><span class="emphasis"><em>Format:</em></span> A string with up to 255 characters</p></dd><dt><span class="term">M1 through M3</span></dt><dd><p>The miscellaneous fields 1 through 3. These fields are used by various reference types to deal with additional information that doesn't fit anywhere else, and the usage differs from one type to another. An important information among the data contained here is the <a class="ulink" href="http://www.doi.org" target="_top">digital object identifier</a>. Please refer to the <a class="ulink" href="http://www.referencemanager.com/support/docs/ReferenceManager11.pdf" target="_top">Reference Manager Manual</a> for the nasty details of these fields.</p><p><span class="emphasis"><em>Format:</em></span> A string with up to 255 characters</p></dd></dl></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a id="idp67940896"></a>Examples</h3></div></div></div><p>The following listing shows a few examples of valid RIS datasets. See also the example RIS file in the <code class="filename">/usr/local/share/refdb/examples</code> directory.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Long entries like abstracts were divided into several lines using slashes. This is to make it more human-readable for this manual and should not be used in real data.</p></div><pre class="programlisting"> 
TY  - JOUR
T1  - T-lymphocytes from normal human peritoneum are phenotypically /
different from their counterparts in peripheral blood and CD3- lymphocyte /
subsets contain mRNA for the recombination activating gene RAG-1
A1  - Hartmann,J.
A1  - Maassen,V.
A1  - Rieber,P.
A1  - Fricke,H.
Y1  - 1995///
KW  - Peritoneum
KW  - T cell
KW  - T lymphocyte
KW  - lymphocyte
KW  - immunology
KW  - CD3
KW  - human
KW  - Adult
KW  - blood
RP  - IN FILE
SP  - 2626
EP  - 2631
JF  - European Journal of Immunology
JA  - Eur.J.Immunol.
VL  - 25
N2  - These findings are compatible with the hypothesis that the adult /
human peritoneum provides a microenvirinment capable of supporting a /
thymus-independent differentiation of T lymphocytes.
ER  - 

TY  - BOOK
T1  - Porphyrins and metalloporphyrins
A1  - Smith,K.M.
Y1  - 1975///
KW  - Porphyrins
KW  - Metalloporphyrins
KW  - Spectrophotometry [methods]
KW  - spectroscopy
RP  - NOT IN FILE
CY  - Amsterdam
PB  - Elsevier Scientific Publishing Company
ER  - 

TY  - CHAP
T1  - Physiological studies of the natriuretic peptide family
A1  - Lewicki,J.A.
A1  - Protter,A.A.
Y1  - 1995///
N1  - Atrial Natriuretic Peptide   Cardiac synthesis and secretion of /
ANP   Regulation of ANP Gene Expression   Regulation of ANP Release /
ANP Receptors   Biologic Actions of ANP Brain Natriuretic Peptide (BNP) /
BNP Structure   Biosynthesis of BNP   Biological Actions of BNP C-Type /
Natriuretic Peptide (CNP)   Biologic Actions of CNP Modulators of /
Natriuretic Peptide Clearance   Effects of Clearance Receptor Blockers /
Effects of Neutral Endopeptidase Inhibitors Role of the Natriuretic /
Peitedes in Physiology and Disease   Hypertension   Congestive Heart  /
Failure   Supraventricular Tachyarrhythmias   Acute Renal Dysfunction
KW  - natriuretic
KW  - ANF
KW  - ANP
KW  - receptors
KW  - BNP
KW  - CNP
KW  - hypertension
KW  - congestive heart failure
KW  - review
KW  - cardiac
KW  - regulation
KW  - gene expression
KW  - expression
KW  - brain
KW  - structure
KW  - biosynthesis
KW  - receptor
KW  - inhibitor
KW  - physiology
KW  - renal
KW  - study
KW  - Peptides
KW  - atrial natriuretic peptide
KW  - MODULATOR
KW  - secretion
KW  - Gene Expression Regulation
RP  - IN FILE
SP  - 1029
EP  - 1053
VL  - 2
T2  - Hypertension: Pathophysiology, Diagnosis, and Management
A2  - Laragh,J.H.
A2  - Brenner,B.M.
IS  - 61
CY  - New York
PB  - Raven Press, Ltd.
ER  - </pre></div></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch06s05.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="pt03.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch07s02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Common command-line options for all clients </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> The Emacs helpers</td></tr></table></div></body></html>
refdb-doc 1.0.2-3 / usr / share / doc / refdb / refdb-manual / ch07.html
