Replace ASCII-quotes with proper markup.

Author: petere

doc/src/sgml/arch-pg.sgml

@@ -73,9 +73,9 @@ From that  point  on,  the  frontend process and the backend
      "superuser."  
 Note that the <ProductName>Postgres</ProductName> superuser does not
 have  to  be  a special user (e.g., a user named 
-"postgres"), although many systems are installed that way.
+<literal>postgres</literal>), although many systems are installed that way.
 Furthermore,  the  <ProductName>Postgres</ProductName>  superuser should
-     definitely  not  be the Unix superuser, "root"!  In any
+     definitely  not  be the Unix superuser, <literal>root</literal>!  In any
      case, all files relating to a database should belong to
      this <ProductName>Postgres</ProductName> superuser.
 </Para>

doc/src/sgml/catalogs.sgml

@@ -1,6 +1,6 @@
 <!--
  Documentation of the system catalogs, directed toward PostgreSQL developers
- $Header: /cvsroot/pgsql/doc/src/sgml/catalogs.sgml,v 2.24 2001/09/10 05:46:41 ishii Exp $
+ $Header: /cvsroot/pgsql/doc/src/sgml/catalogs.sgml,v 2.25 2001/09/13 15:55:22 petere Exp $
  -->
 
 <chapter id="catalogs">
@@ -1737,7 +1737,7 @@
    to assume very much about what sort of statistics it stores.  Only
    extremely general statistics (such as NULL-ness) are given dedicated
    columns in <structname>pg_statistic</structname>.  Everything else
-   is stored in "slots", which are groups of associated columns whose
+   is stored in <quote>slots</quote>, which are groups of associated columns whose
    content is identified by a code number in one of the slot's columns.
    For more information see
    <filename>src/include/catalog/pg_statistic.h</filename>.
@@ -1803,7 +1803,7 @@
       <entry><type>int2</type></entry>
       <entry></entry>
       <entry>A code number indicating the kind of statistics stored in the Nth
-      "slot" of the <structname>pg_statistic</structname> row.
+      <quote>slot</quote> of the <structname>pg_statistic</structname> row.
       </entry>
      </row>
 
@@ -1812,7 +1812,7 @@
       <entry><type>oid</type></entry>
       <entry>pg_operator.oid</entry>
       <entry>An operator used to derive the statistics stored in the
-      Nth "slot".  For example, a histogram slot would show the "&lt;"
+      Nth <quote>slot</quote>.  For example, a histogram slot would show the <literal>&lt;</literal>
       operator that defines the sort order of the data.
       </entry>
      </row>
@@ -1822,7 +1822,7 @@
       <entry><type>float4[]</type></entry>
       <entry></entry>
       <entry>Numerical statistics of the appropriate kind for the Nth
-      "slot", or NULL if the slot kind does not involve numerical values.
+      <quote>slot</quote>, or NULL if the slot kind does not involve numerical values.
       </entry>
      </row>
 
@@ -1831,7 +1831,7 @@
       <entry><type>text[]</type></entry>
       <entry></entry>
       <entry>Column data values of the appropriate kind for the Nth
-      "slot", or NULL if the slot kind does not store any data values.
+      <quote>slot</quote>, or NULL if the slot kind does not store any data values.
       For datatype independence, all column data values are converted
       to external textual form and stored as TEXT datums.
       </entry>

doc/src/sgml/charset.sgml

@@ -1,4 +1,4 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/charset.sgml,v 2.9 2001/09/09 23:52:12 petere Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/charset.sgml,v 2.10 2001/09/13 15:55:22 petere Exp $ -->
 
 <chapter id="charset">
  <title>Localization</>
@@ -396,7 +396,7 @@ perl: warning: Falling back to the standard locale ("C").
      </programlisting>
 
      sets the default encoding to <literal>EUC_JP</literal> (Extended Unix Code for Japanese).
-     Note that you can use "--encoding" instead of "-E" if you prefer
+     Note that you can use <option>--encoding</option> instead of <option>-E</option> if you prefer
      to type longer option strings. 
      If no -E or --encoding option is given, the encoding
      specified at configure time is used.
@@ -529,7 +529,7 @@ int PQsetClientEncoding(PGconn *<replaceable>conn</replaceable>, const char *<re
 int PQclientEncoding(const PGconn *<replaceable>conn</replaceable>)
 	</programlisting>
 
-	Note that it returns the "encoding id," not the encoding symbol string
+	Note that it returns the encoding id, not the encoding symbol string
 	such as <literal>EUC_JP</literal>. To convert an encoding id to an encoding symbol, you
 	can use:
 
@@ -549,7 +549,7 @@ char *pg_encoding_to_char(int <replaceable>encoding_id</replaceable>)
 SET CLIENT_ENCODING TO 'encoding';
 	</programlisting>
 
-	Also you can use SQL92 syntax "SET NAMES" for this purpose:
+	Also you can use SQL92 syntax <literal>SET NAMES</literal> for this purpose:
 
 	<programlisting>
 SET NAMES 'encoding';
@@ -801,7 +801,7 @@ Sorry for my Eglish and C code, I'm not native :-)
 
       <listitem>
        <para>
-	A locale such as "<literal>ch</literal>" is correctly sorted
+	A locale such as <literal>ch</literal> is correctly sorted
 	only if your system
 	supports that locale; older systems may not do so but new ones
 	(e.g. RH6.0) do.

doc/src/sgml/cvs.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/cvs.sgml,v 1.15 2001/09/07 21:36:46 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/cvs.sgml,v 1.16 2001/09/13 15:55:22 petere Exp $
 CVS code repository
 Thomas Lockhart
 -->
@@ -206,8 +206,8 @@ $ cvs checkout -r REL6_4 tc
 
   <para>
    When you tag more than one file with the same tag you can think
-   about the tag as "a curve drawn through a matrix of filename vs.
-   revision number".  Say we have 5 files with the following revisions:
+   about the tag as <quote>a curve drawn through a matrix of filename vs.
+   revision number</quote>.  Say we have 5 files with the following revisions:
 
    <programlisting>
              file1   file2   file3   file4   file5
@@ -220,7 +220,7 @@ $ cvs checkout -r REL6_4 tc
                              1.6
    </programlisting>
 
-   then the tag "<literal>TAG</literal>" will reference
+   then the tag <literal>TAG</literal> will reference
    file1-1.2, file2-1.3, etc.
 
    <note>
@@ -487,7 +487,7 @@ pgsql
       <para>
        <productname>CVSup</productname> was originally developed as a
        tool for distributing the <productname>FreeBSD</productname>
-       source tree. It is available as a "port", and for those running 
+       source tree. It is available as a <quote>port</quote>, and for those running 
        FreeBSD, if this is not sufficient to tell how to obtain and
        install it then please contribute a procedure here.
       </para>

doc/src/sgml/datatype.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.62 2001/09/09 17:21:51 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.63 2001/09/13 15:55:22 petere Exp $
 -->
 
  <chapter id="datatype">
@@ -1060,9 +1060,9 @@ SELECT b, char_length(b) FROM test2;
      The ordering of month and day in date input can be ambiguous, therefore a setting
      exists to specify how it should be interpreted in ambiguous cases. The command
      <literal>SET DateStyle TO 'US'</literal> or <literal>SET DateStyle TO 'NonEuropean'</literal>
-     specifies the variant "month before day", the command
+     specifies the variant <quote>month before day</quote>, the command
      <literal>SET DateStyle TO 'European'</literal> sets the variant
-     "day before month". The <literal>ISO</literal> style
+     <quote>day before month</quote>. The <literal>ISO</literal> style
      is the default but this default can be changed at compile time or at run time.
     </para>
 
@@ -2129,8 +2129,9 @@ SELECT * FROM test1 WHERE a;
     </indexterm>
 
     <para>
-     Paths are represented by connected sets of points. Paths can be "open", where
-     the first and last points in the set are not connected, and "closed",
+     Paths are represented by connected sets of points. Paths can be
+     <firstterm>open</firstterm>, where
+     the first and last points in the set are not connected, and <firstterm>closed</firstterm>,
      where the first and last point are connected. Functions
      <function>popen(p)</function>
      and

doc/src/sgml/datetime.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v 2.20 2001/09/09 17:21:58 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v 2.21 2001/09/13 15:55:22 petere Exp $
 Date/time details
 -->
 
@@ -426,7 +426,7 @@ Date/time details
     interpreted as Australian timezone names.  Without this option,
     <literal>CST</literal> and <literal>EST</literal> are taken as
     American timezone names, while <literal>SAT</literal> is interpreted as a
-    noise word indicating "<literal>Saturday</literal>".
+    noise word indicating <literal>Saturday</literal>.
 
     <table tocentry="1">
      <title><productname>Postgres</productname> Australian Time Zones</title>
@@ -494,7 +494,7 @@ Date/time details
       <step>
        <para>
 	If the token is numeric only, then it is either a single field
-	or an ISO-8601 concatenated date (e.g. "19990113" for January 13, 1999)
+	or an ISO-8601 concatenated date (e.g. <literal>19990113</literal> for January 13, 1999)
 	or time (e.g. 141516 for 14:15:16).
        </para>
       </step>
@@ -553,7 +553,7 @@ Date/time details
        <para>
 	If there are more than 4 digits, 
 	and if no other date fields have been previously read, then interpret 
-	as a "concatenated date" (e.g. <literal>19990118</literal>). 8
+	as a <quote>concatenated date</quote> (e.g. <literal>19990118</literal>). 8
 	and 6 digits are interpreted as year, month, and day, while 7
 	and 5 digits are interpreted as year, day of year, respectively.
        </para>
@@ -658,7 +658,7 @@ Date/time details
   </para>
 
   <para>
-   "Julian Day" is different from "Julian Date".
+   <quote>Julian Day</quote> is different from <quote>Julian Date</quote>.
 
    The Julian calendar was introduced by Julius Caesar in 45 BC. It was
    in common use until the 1582, when countries started changing to the

doc/src/sgml/docguide.sgml

@@ -1,4 +1,4 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/docguide.sgml,v 1.32 2001/04/20 15:52:33 thomas Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/docguide.sgml,v 1.33 2001/09/13 15:55:22 petere Exp $ -->
 
 <appendix label="DG2" id="docguide">
  <title>Documentation</title>
@@ -626,7 +626,7 @@ gmake man
    <acronym>SGML</acronym> source code to <acronym>RTF</acronym>, then
    importing into <productname>ApplixWare-4.4.1</productname>. 
    After a little cleanup (see the following
-   section) the output is "printed" to a postscript file.
+   section) the output is <quote>printed</quote> to a postscript file.
   </para>
 
 <!--
@@ -828,7 +828,7 @@ exit
 	  <para>
 	   Not all documents have figures.
 	   You can grep the <acronym>SGML</acronym> source files for
-	   the string "<literal>graphic</literal>" to identify those parts of the
+	   the string <literal>graphic</literal> to identify those parts of the
 	   documentation that may have figures. A few figures are replicated in
 	   various parts of the documentation.
 	  </para>
@@ -866,7 +866,7 @@ exit
 
     <step performance="required">
      <para>
-      "Print" the document
+      <quote>Print</quote> the document
       to a file in Postscript format.
      </para>
     </step>
@@ -987,14 +987,14 @@ exit
 
     <step performance="required">
      <para>
-      Export the result as "ASCII Layout".
+      Export the result as <literal>ASCII Layout</literal>.
      </para>
     </step>
 
     <step performance="required">
      <para>
       Using emacs or vi, clean up the tabular information in
-      <filename>INSTALL</filename>. Remove the "mailto"
+      <filename>INSTALL</filename>. Remove the <literal>mailto</literal>
       <acronym>URLs</acronym> for the porting contributors to shrink
       the column heights.
      </para>

doc/src/sgml/ecpg.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v 1.22 2001/09/10 21:58:46 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v 1.23 2001/09/13 15:55:22 petere Exp $
 -->
 
  <chapter id="ecpg">
@@ -114,7 +114,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v 1.22 2001/09/10 21:58:46 petere
     </para>
 
     <para>
-     The library has some methods that are "hidden" but may prove
+     The library has some methods that are <quote>hidden</quote> but may prove
      useful.
 
      <itemizedlist>
@@ -316,7 +316,7 @@ struct sqlca
 	<para>
 	 This means the host variable is of type <type>bool</type> and
 	 the field in the <productname>Postgres</productname> database
-	 is neither 't' nor 'f'.
+	 is neither <literal>'t'</> nor <literal>'f'</>.
 	</para>
        </listitem>
       </varlistentry>
@@ -393,7 +393,7 @@ struct sqlca
        <term><computeroutput>100, Data not found line %d.</computeroutput></term>
        <listitem>
 	<para>
-	 This is a "normal" error that tells you that what you are querying cannot
+	 This is a <quote>normal</quote> error that tells you that what you are querying cannot
 	 be found or you are at the end of the cursor.
 	</para>
        </listitem>
@@ -421,7 +421,7 @@ struct sqlca
        <para>
 	Oracle version 7.0 on <systemitem class="osname">AIX</> 3 uses OS-supported locks in shared
 	memory that allow an application designer to link an application
-	in a "single tasking" way. Instead of starting one client
+	in a <quote>single tasking</quote> way. Instead of starting one client
 	process per application process, both the database part and the
 	application part run in the same process. In later versions of
 	Oracle this is no longer supported.
@@ -555,7 +555,7 @@ struct sqlca
        <term>message 'no data found'</term>
        <listitem>
 	<para>
-	 The error message for "no data" in:
+	 The error message for <quote>no data</quote> in:
 	 <programlisting>
 exec sql insert select from statement
 	</programlisting>

doc/src/sgml/extend.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.11 2001/09/10 21:58:46 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.12 2001/09/13 15:55:22 petere Exp $
 -->
 
  <chapter id="extend">
@@ -67,7 +67,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.11 2001/09/10 21:58:46 pete
     or shared library) that implements a new type or  function 
     and <productname>Postgres</productname> will load it as required.  Code written 
     in <acronym>SQL</acronym> are even more trivial to add to the  server.
-    This ability to modify its operation "on the fly" makes
+    This ability to modify its operation <quote>on the fly</quote> makes
     <productname>Postgres</productname> uniquely suited for rapid prototyping  of  new
     applications and storage structures.
    </para>
@@ -82,7 +82,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.11 2001/09/10 21:58:46 pete
     Types are divided into base types and composite  types.
     Base  types  are those, like <firstterm>int4</firstterm>, that are implemented
     in a language such as <productname>C</productname>.  They generally correspond  to
-    what are often known as "abstract data types"; <productname>Postgres</productname>
+    what are often known as <firstterm>abstract data types</firstterm>; <productname>Postgres</productname>
     can only operate on such types through methods provided
     by  the  user and only understands the behavior of such
     types to the extent that the user describes them.  
@@ -94,7 +94,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.11 2001/09/10 21:58:46 pete
     <productname>Postgres</productname>  stores  these  types
     in only one way (within the
     file that stores all rows of a table)  but  the
-    user can "look inside" at the attributes of these types
+    user can <quote>look inside</quote> at the attributes of these types
     from the query language and optimize their retrieval by
     (for example) defining indexes on the attributes.
     <productname>Postgres</productname>  base  types are further

doc/src/sgml/geqo.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/geqo.sgml,v 1.17 2001/05/17 21:50:15 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/geqo.sgml,v 1.18 2001/09/13 15:55:22 petere Exp $
 Genetic Optimizer
 -->
 
@@ -114,7 +114,7 @@ Genetic Optimizer
    </para>
 
    <para>
-    According to the "comp.ai.genetic" <acronym>FAQ</acronym> it cannot be stressed too
+    According to the <systemitem class="resource">comp.ai.genetic</> <acronym>FAQ</acronym> it cannot be stressed too
     strongly that a <acronym>GA</acronym> is not a pure random search for a solution to a
     problem. A <acronym>GA</acronym> uses stochastic processes, but the result is distinctly
     non-random (better than random). 

doc/src/sgml/history.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.14 2001/09/09 17:21:59 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.15 2001/09/13 15:55:22 petere Exp $
 -->
 
 <sect1 id="history">
@@ -40,7 +40,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.14 2001/09/09 17:21:59 pet
 
   <para>
    <productname>Postgres</productname> has undergone  several  major  releases  since
-   then.   The  first "demoware" system became operational
+   then.   The  first <quote>demoware</quote> system became operational
    in 1987 and was shown at the  1988  <acronym>ACM-SIGMOD</acronym>  
    Conference.   We  released Version 1, described in 
    <xref endterm="STON90a-full" linkend="STON90a">,
@@ -186,7 +186,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.14 2001/09/09 17:21:59 pet
   <title><productname>PostgreSQL</productname></title>
 
   <para>
-   By 1996, it became clear that the name "Postgres95" would
+   By 1996, it became clear that the name <quote>Postgres95</quote> would
    not stand the test of time. We chose a new name,
    <productname>PostgreSQL</productname>, to reflect the relationship
    between the original <productname>Postgres</productname> and the more