svn commit - mysqldoc@docsrva: r4167 - in trunk: . refman-4.1 refman-5.0 refman-5.1

[paul]

Author: paul
Date: 2006-12-08 17:09:13 +0100 (Fri, 08 Dec 2006)
New Revision: 4167

Log:
 r13308@frost:  paul | 2006-12-08 10:07:02 -0600
 Fix some markup.


Modified:
   trunk/refman-4.1/client-utility-programs.xml
   trunk/refman-4.1/connector-odbc.xml
   trunk/refman-4.1/mysql-cluster.xml
   trunk/refman-4.1/news-4.1.xml
   trunk/refman-4.1/problems.xml
   trunk/refman-4.1/replication.xml
   trunk/refman-5.0/client-utility-programs.xml
   trunk/refman-5.0/database-administration.xml
   trunk/refman-5.0/installing-cs.xml
   trunk/refman-5.0/mysql-cluster.xml
   trunk/refman-5.0/news-5.0.xml
   trunk/refman-5.0/problems.xml
   trunk/refman-5.0/se-merge.xml
   trunk/refman-5.0/se-myisam.xml
   trunk/refman-5.1/client-utility-programs.xml
   trunk/refman-5.1/mysql-cluster.xml
   trunk/refman-5.1/news-5.1.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:16870
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:13305
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:12611
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:16870
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:13308
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:12611


Modified: trunk/refman-4.1/client-utility-programs.xml
===================================================================
--- trunk/refman-4.1/client-utility-programs.xml	2006-12-08 16:08:49 UTC (rev 4166)
+++ trunk/refman-4.1/client-utility-programs.xml	2006-12-08 16:09:13 UTC (rev 4167)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 686 bytes

@@ -5950,10 +5950,10 @@
 
         <refsection id="safe-updates">
 
-          <title>Using the <literal>--safe-updates</literal>
Option</title>
+          <title>Using the <option>--safe-updates</option>
Option</title>
 
           <indexterm>
-            <primary><literal>safe-updates</literal>
option</primary>
+            <primary>safe-updates option</primary>
           </indexterm>
 
           <para>


Modified: trunk/refman-4.1/connector-odbc.xml
===================================================================
--- trunk/refman-4.1/connector-odbc.xml	2006-12-08 16:08:49 UTC (rev 4166)
+++ trunk/refman-4.1/connector-odbc.xml	2006-12-08 16:09:13 UTC (rev 4167)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 680 bytes

@@ -1509,7 +1509,7 @@
             <para>
               If you have built your own MySQL server and/or client
               libraries from source then you must have used the
-              <literal>--enable-thread-safe-client</literal> option to
+              <option>--enable-thread-safe-client</option> option to
               <literal>configure</literal> when the libraries were
               built.
             </para>


Modified: trunk/refman-4.1/mysql-cluster.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster.xml	2006-12-08 16:08:49 UTC (rev 4166)
+++ trunk/refman-4.1/mysql-cluster.xml	2006-12-08 16:09:13 UTC (rev 4167)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 568 bytes

@@ -9843,7 +9843,7 @@
           <para>
             Clear the cluster filesystem. This stage occurs
             <emphasis>only</emphasis> if the cluster was started with
-            the <literal>--initial</literal> option.
+            the <option>--initial</option> option.
           </para>
         </listitem>
 


Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml	2006-12-08 16:08:49 UTC (rev 4166)
+++ trunk/refman-4.1/news-4.1.xml	2006-12-08 16:09:13 UTC (rev 4167)
Changed blocks: 2, Lines Added: 3, Lines Deleted: 3; 1034 bytes

@@ -3110,8 +3110,8 @@
 
       <listitem>
         <para>
-          The <literal>--replicate-do</literal> and
-          <literal>--replicate-ignore</literal> options were not being
+          The <option>--replicate-do</option> and
+          <option>--replicate-ignore</option> options were not being
           enforced on multiple-table statements. (Bug #15699, Bug
           #16487)
         </para>

@@ -3237,7 +3237,7 @@
         <para>
           Performing a <literal>RENAME TABLE</literal> on an InnoDB
           table when the server is started with the
-          <literal>--innodb-file-per-table</literal> and the data
+          <option>--innodb-file-per-table</option> option and the data
           directory is a symlink caused a server crash. (Bug #15991)
         </para>
       </listitem>


Modified: trunk/refman-4.1/problems.xml
===================================================================
--- trunk/refman-4.1/problems.xml	2006-12-08 16:08:49 UTC (rev 4166)
+++ trunk/refman-4.1/problems.xml	2006-12-08 16:09:13 UTC (rev 4167)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 769 bytes

@@ -1574,7 +1574,7 @@
             in-memory temporary table becomes larger than
             <literal>tmp_table_size</literal> bytes. To avoid this
             problem, you can use the
-           
<literal>--tmp_table_size=<replaceable>val</replaceable></literal>
+           
<option>--tmp_table_size=<replaceable>val</replaceable></option>
             option to make <command>mysqld</command> increase the
             temporary table size or use the SQL option
             <literal>SQL_BIG_TABLES</literal> before you issue the


Modified: trunk/refman-4.1/replication.xml
===================================================================
--- trunk/refman-4.1/replication.xml	2006-12-08 16:08:49 UTC (rev 4166)
+++ trunk/refman-4.1/replication.xml	2006-12-08 16:09:13 UTC (rev 4167)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 565 bytes

@@ -1965,7 +1965,7 @@
       <listitem>
         <para>
           <literal>LOAD DATA INFILE</literal> does not replicate
-          correctly when <literal>--binlog-do-db</literal> is used. (Bug
+          correctly when <option>--binlog-do-db</option> is used. (Bug
           #19662)
         </para>
       </listitem>


Modified: trunk/refman-5.0/client-utility-programs.xml
===================================================================
--- trunk/refman-5.0/client-utility-programs.xml	2006-12-08 16:08:49 UTC (rev 4166)
+++ trunk/refman-5.0/client-utility-programs.xml	2006-12-08 16:09:13 UTC (rev 4167)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 567 bytes

@@ -5853,7 +5853,7 @@
           <title>Using the <option>--safe-updates</option>
Option</title>
 
           <indexterm>
-            <primary><literal>safe-updates</literal>
option</primary>
+            <primary>safe-updates option</primary>
           </indexterm>
 
           <para>


Modified: trunk/refman-5.0/database-administration.xml
===================================================================
--- trunk/refman-5.0/database-administration.xml	2006-12-08 16:08:49 UTC (rev 4166)
+++ trunk/refman-5.0/database-administration.xml	2006-12-08 16:09:13 UTC (rev 4167)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 700 bytes

@@ -944,7 +944,7 @@
             </para>
 
             <para>
-              As of MySQL 5.0.25, using <literal>--with-debug</literal>
+              As of MySQL 5.0.25, using <option>--with-debug</option>
               to configure MySQL with debugging support enables you to
               use the <option>--debug="d,parser_debug"</option> option
               when you start the server. This causes the Bison parser


Modified: trunk/refman-5.0/installing-cs.xml
===================================================================
--- trunk/refman-5.0/installing-cs.xml	2006-12-08 16:08:49 UTC (rev 4166)
+++ trunk/refman-5.0/installing-cs.xml	2006-12-08 16:09:13 UTC (rev 4167)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 669 bytes

@@ -7362,7 +7362,7 @@
           </para>
 
           <para>
-            As of MySQL 5.0.25, using <literal>--with-debug</literal> to
+            As of MySQL 5.0.25, using <option>--with-debug</option> to
             configure MySQL with debugging support enables you to use
             the <option>--debug="d,parser_debug"</option> option when
             you start the server. This causes the Bison parser that is


Modified: trunk/refman-5.0/mysql-cluster.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster.xml	2006-12-08 16:08:49 UTC (rev 4166)
+++ trunk/refman-5.0/mysql-cluster.xml	2006-12-08 16:09:13 UTC (rev 4167)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 568 bytes

@@ -9886,7 +9886,7 @@
           <para>
             Clear the cluster filesystem. This stage occurs
             <emphasis>only</emphasis> if the cluster was started with
-            the <literal>--initial</literal> option.
+            the <option>--initial</option> option.
           </para>
         </listitem>
 


Modified: trunk/refman-5.0/news-5.0.xml
===================================================================
--- trunk/refman-5.0/news-5.0.xml	2006-12-08 16:08:49 UTC (rev 4166)
+++ trunk/refman-5.0/news-5.0.xml	2006-12-08 16:09:13 UTC (rev 4167)
Changed blocks: 4, Lines Added: 5, Lines Deleted: 5; 1855 bytes

@@ -985,7 +985,7 @@
 
       <listitem>
         <para>
-          Using <literal>--with-debug</literal> to configure MySQL with
+          Using <option>--with-debug</option> to configure MySQL with
           debugging support enables you to use the
           <option>--debug="d,parser_debug"</option> option when you
           start the server. This causes the Bison parser that is used to

@@ -6355,7 +6355,7 @@
           InnoDB now caches a list of unflushed files instead of
           scanning for unflushed files during a table flush operation.
           This improves performance when
-          <literal>--innodb-file-per-table</literal> is set on a system
+          <option>--innodb-file-per-table</option> is set on a system
           with a large number of InnoDB tables. (Bug #15653)
         </para>
       </listitem>

@@ -7082,7 +7082,7 @@
         <para>
           Performing a <literal>RENAME TABLE</literal> on an InnoDB
           table when the server is started with the
-          <literal>--innodb-file-per-table</literal> and the data
+          <option>--innodb-file-per-table</option> option and the data
           directory is a symlink caused a server crash. (Bug #15991)
         </para>
       </listitem>

@@ -7175,8 +7175,8 @@
 
       <listitem>
         <para>
-          The <literal>--replicate-do</literal> and
-          <literal>--replicate-ignore</literal> options were not being
+          The <option>--replicate-do</option> and
+          <option>--replicate-ignore</option> options were not being
           enforced on multiple-table statements. (Bug #15699, Bug
           #16487)
         </para>


Modified: trunk/refman-5.0/problems.xml
===================================================================
--- trunk/refman-5.0/problems.xml	2006-12-08 16:08:49 UTC (rev 4166)
+++ trunk/refman-5.0/problems.xml	2006-12-08 16:09:13 UTC (rev 4167)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 769 bytes

@@ -1542,7 +1542,7 @@
             in-memory temporary table becomes larger than
             <literal>tmp_table_size</literal> bytes. To avoid this
             problem, you can use the
-           
<literal>--tmp_table_size=<replaceable>val</replaceable></literal>
+           
<option>--tmp_table_size=<replaceable>val</replaceable></option>
             option to make <command>mysqld</command> increase the
             temporary table size or use the SQL option
             <literal>SQL_BIG_TABLES</literal> before you issue the


Modified: trunk/refman-5.0/se-merge.xml
===================================================================
--- trunk/refman-5.0/se-merge.xml	2006-12-08 16:08:49 UTC (rev 4166)
+++ trunk/refman-5.0/se-merge.xml	2006-12-08 16:09:13 UTC (rev 4167)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 794 bytes

@@ -508,7 +508,7 @@
           as there is with a <literal>MyISAM</literal>, it is therefore
           not possible to merge multiple <literal>MyISAM</literal>
           tables that exceed this limitation. However, you build MySQL
-          with the <literal>--with-big-tables</literal> option then the
+          with the <option>--with-big-tables</option> option then the
           row limitation is increased to
          
(2<superscript>32</superscript>)<superscript>2</superscript>
           (1.844E+19) rows. See <xref linkend="configure-options"/>.


Modified: trunk/refman-5.0/se-myisam.xml
===================================================================
--- trunk/refman-5.0/se-myisam.xml	2006-12-08 16:08:49 UTC (rev 4166)
+++ trunk/refman-5.0/se-myisam.xml	2006-12-08 16:09:13 UTC (rev 4167)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 755 bytes

@@ -118,7 +118,7 @@
         There is a limit of 2<superscript>32</superscript> (~4.295E+09)
         rows in a <literal>MyISAM</literal> table. You can increase this
         limitation if you build MySQL with the
-        <literal>--with-big-tables</literal> option then the row
+        <option>--with-big-tables</option> option then the row
         limitation is increased to
        
(2<superscript>32</superscript>)<superscript>2</superscript>
         (1.844E+19) rows. See <xref linkend="configure-options"/>.


Modified: trunk/refman-5.1/client-utility-programs.xml
===================================================================
--- trunk/refman-5.1/client-utility-programs.xml	2006-12-08 16:08:49 UTC (rev 4166)
+++ trunk/refman-5.1/client-utility-programs.xml	2006-12-08 16:09:13 UTC (rev 4167)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 567 bytes

@@ -5848,7 +5848,7 @@
           <title>Using the <option>--safe-updates</option>
Option</title>
 
           <indexterm>
-            <primary><literal>safe-updates</literal>
option</primary>
+            <primary>safe-updates option</primary>
           </indexterm>
 
           <para>


Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml	2006-12-08 16:08:49 UTC (rev 4166)
+++ trunk/refman-5.1/mysql-cluster.xml	2006-12-08 16:09:13 UTC (rev 4167)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 857 bytes

@@ -9815,7 +9815,7 @@
 
           <para>
             <emphasis>Note</emphasis>: Disk Data files are not removed
-            when restarting a node using <literal>--initial</literal>.
+            when restarting a node using <option>--initial</option>.
           </para>
         </listitem>
 

@@ -9939,7 +9939,7 @@
           <para>
             Clear the cluster filesystem. This stage occurs
             <emphasis>only</emphasis> if the cluster was started with
-            the <literal>--initial</literal> option.
+            the <option>--initial</option> option.
           </para>
         </listitem>
 


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2006-12-08 16:08:49 UTC (rev 4166)
+++ trunk/refman-5.1/news-5.1.xml	2006-12-08 16:09:13 UTC (rev 4167)
Changed blocks: 3, Lines Added: 4, Lines Deleted: 4; 1495 bytes

@@ -2178,7 +2178,7 @@
 
       <listitem>
         <para>
-          Using <literal>--with-debug</literal> to configure MySQL with
+          Using <option>--with-debug</option> to configure MySQL with
           debugging support enables you to use the
           <option>--debug="d,parser_debug"</option> option when you
           start the server. This causes the Bison parser that is used to

@@ -6470,8 +6470,8 @@
       <listitem>
         <para>
           In MySQL 5.1.11, the <option>--with-openssl</option> and
-          <literal>--with-yassl</literal> options were replaced by
-          <literal>--with-ssl</literal>. But no message was issued if
+          <option>--with-yassl</option> options were replaced by
+          <option>--with-ssl</option>. But no message was issued if
           the old options were given. Now <command>configure</command>
           produces a message indicating that the new option should be
           used and exits. (Bug #20002)

@@ -11533,7 +11533,7 @@
 
       <listitem>
         <para>
-          Specifying a value for <literal>--tmpdir</literal> without a
+          Specifying a value for <option>--tmpdir</option> without a
           trailing slash had unpredictable results. (Bug #15904)
         </para>
       </listitem>