List:Commits« Previous MessageNext Message »
From:paul Date:January 3 2006 8:39pm
Subject:svn commit - mysqldoc@docsrva: r655 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-common
View as plain text  
Author: paul
Date: 2006-01-03 21:39:20 +0100 (Tue, 03 Jan 2006)
New Revision: 655

Log:
 r5787@frost:  paul | 2006-01-03 14:13:13 -0600
 Restructure "Information Sources" section.
 Fix xrefs that point to it.


Modified:
   trunk/
   trunk/refman-4.1/apis.xml
   trunk/refman-4.1/connector-odbc.xml
   trunk/refman-4.1/database-administration.xml
   trunk/refman-4.1/extending-mysql.xml
   trunk/refman-4.1/installing.xml
   trunk/refman-4.1/porting.xml
   trunk/refman-4.1/problems.xml
   trunk/refman-4.1/renamed-nodes.txt
   trunk/refman-5.0/apis.xml
   trunk/refman-5.0/connector-odbc.xml
   trunk/refman-5.0/database-administration.xml
   trunk/refman-5.0/extending-mysql.xml
   trunk/refman-5.0/installing.xml
   trunk/refman-5.0/porting.xml
   trunk/refman-5.0/problems.xml
   trunk/refman-5.0/renamed-nodes.txt
   trunk/refman-5.1/apis.xml
   trunk/refman-5.1/connector-odbc.xml
   trunk/refman-5.1/database-administration.xml
   trunk/refman-5.1/extending-mysql.xml
   trunk/refman-5.1/installing.xml
   trunk/refman-5.1/porting.xml
   trunk/refman-5.1/problems.xml
   trunk/refman-5.1/renamed-nodes.txt
   trunk/refman-common/information-sources.xml
   trunk/refman-common/titles.en.ent


Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:5781
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1848
   + b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:5787
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1848

Modified: trunk/refman-4.1/apis.xml
===================================================================
--- trunk/refman-4.1/apis.xml	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-4.1/apis.xml	2006-01-03 20:39:20 UTC (rev 655)
@@ -13140,7 +13140,7 @@
           <ulink url="http://dbi.perl.org/"/>. That site hosts a general
           DBI mailing list. MySQL AB hosts a list specifically about
           <literal>DBD::mysql</literal>; see
-          <xref linkend="mailing-list"/>.
+          <xref linkend="mailing-lists"/>.
         </para>
       </listitem>
 

Modified: trunk/refman-4.1/connector-odbc.xml
===================================================================
--- trunk/refman-4.1/connector-odbc.xml	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-4.1/connector-odbc.xml	2006-01-03 20:39:20 UTC (rev 655)
@@ -318,6 +318,7 @@
         For information about subscribing to MySQL mailing lists or to
         browse list archives, visit
         <ulink url="http://lists.mysql.com/"/>.
+See <xref linkend="mailing-lists"/>.
       </para>
 
       <para>
@@ -335,6 +336,7 @@
         Community support from experienced users is available through
         the MySQL Forums, located at
         <ulink url="http://forums.mysql.com"/>.
+See <xref linkend="forums"/>.
       </para>
 
     </section>
@@ -393,7 +395,7 @@
       <para>
         If you find out something is wrong, please only send the
         relevant rows (maximum 40 rows) to the <literal>myodbc</literal>
-        mailing list. See <xref linkend="mailing-list"/>. Please never
+        mailing list. See <xref linkend="mailing-lists"/>. Please never
         send the whole MyODBC or ODBC log file!
       </para>
 

Modified: trunk/refman-4.1/database-administration.xml
===================================================================
--- trunk/refman-4.1/database-administration.xml	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-4.1/database-administration.xml	2006-01-03 20:39:20 UTC (rev 655)
@@ -20388,7 +20388,7 @@
         If you want to have the character set included in the MySQL
         distribution, mail a patch to the MySQL
         <literal>internals</literal> mailing list. See
-        <xref linkend="mailing-list"/>.
+        <xref linkend="mailing-lists"/>.
       </para>
 
     </section>

Modified: trunk/refman-4.1/extending-mysql.xml
===================================================================
--- trunk/refman-4.1/extending-mysql.xml	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-4.1/extending-mysql.xml	2006-01-03 20:39:20 UTC (rev 655)
@@ -34,7 +34,7 @@
       you are interested in MySQL internals, you should also subscribe
       to our <literal>internals</literal> mailing list. This list is
       relatively low traffic. For details on how to subscribe, please
-      see <xref linkend="mailing-list"/>. All developers at MySQL AB are
+      see <xref linkend="mailing-lists"/>. All developers at MySQL AB are
       on the <literal>internals</literal> list and we help other people
       who are working on the MySQL code. Feel free to use this list both
       to ask questions about the code and to send patches that you would
@@ -347,8 +347,8 @@
               If you have a question about the test suite, or have a
               test case to contribute, send an email message to the
               MySQL <literal>internals</literal> mailing list. See
-              <xref linkend="mailing-list"/>. As this list does not
-              accept attachments, you should ftp all the relevant files
+              <xref linkend="mailing-lists"/>. This list does not
+              accept attachments, so you should FTP all the relevant files
               to: <ulink url="ftp://ftp.mysql.com/pub/mysql/upload/"/>
             </para>
           </listitem>

Modified: trunk/refman-4.1/installing.xml
===================================================================
--- trunk/refman-4.1/installing.xml	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-4.1/installing.xml	2006-01-03 20:39:20 UTC (rev 655)
@@ -463,7 +463,7 @@
         influence its development, and need more detailed instructions
         on what MySQL needs to run better, send an email message to the
         MySQL <literal>internals</literal> mailing list. See
-        <xref linkend="mailing-list"/>.
+        <xref linkend="mailing-lists"/>.
       </para>
 
       <para>
@@ -1213,7 +1213,7 @@
               <ulink url="http://dev.mysql.com/"/>, we send out an
               announcement message to the <literal>mysql</literal> and
               <literal>announce</literal> mailing lists. See
-              <xref linkend="mailing-list"/>. The announcement message
+              <xref linkend="mailing-lists"/>. The announcement message
               contains a list of all changes to the release and any
               known problems with the release. The Known Problems
               section in the release notes has been needed for only a
@@ -1985,7 +1985,7 @@
           Anyone who has more optimal options for any of the preceding
           configurations listed can always mail them to the MySQL
           <literal>internals</literal> mailing list. See
-          <xref linkend="mailing-list"/>.
+          <xref linkend="mailing-lists"/>.
         </para>
 
         <para>
@@ -8550,7 +8550,7 @@
             you see diffs or code that you have a question about, do not
             hesitate to send email to the MySQL
             <literal>internals</literal> mailing list. See
-            <xref linkend="mailing-list"/>. If you think you have a
+            <xref linkend="mailing-lists"/>. If you think you have a
             better idea on how to do something, send an email message to
             the same address with a patch.
           </para>
@@ -9400,7 +9400,7 @@
         If you find something not working as expected, or you have
         suggestions about ways to improve the current build process on
         Windows, please send a message to the <literal>win32</literal>
-        mailing list. See <xref linkend="mailing-list"/>.
+        mailing list. See <xref linkend="mailing-lists"/>.
       </para>
 
       <section id="windows-vc-plus-plus-build">
@@ -13080,7 +13080,7 @@
         <command>mysqldump</command> to dump any tables that use
         full-text indexes and reload the dump file into the 3.23 server.
         This is necessary because 4.0 uses an improved format for
-        full-text indexing that is not backward compatible.
+        full-text indexing that is not backward-compatible.
       </para>
 
       <para>

Modified: trunk/refman-4.1/porting.xml
===================================================================
--- trunk/refman-4.1/porting.xml	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-4.1/porting.xml	2006-01-03 20:39:20 UTC (rev 655)
@@ -266,7 +266,7 @@
         distribution, the first thing you should do is to configure
         MySQL for debugging! (The second thing is to send mail to a
         MySQL mailing list and ask for help. See
-        <xref linkend="mailing-list"/>. Please use the
+        <xref linkend="mailing-lists"/>. Please use the
         <command>mysqlbug</command> script for all bug reports or
         questions regarding the MySQL version you are using!
       </para>
@@ -501,7 +501,7 @@
       <para>
         Include the above output in a mail generated with
         <command>mysqlbug</command> and mail this to the general MySQL
-        mailing list. See <xref linkend="mailing-list"/>.
+        mailing list. See <xref linkend="mailing-lists"/>.
       </para>
 
       <para>

Modified: trunk/refman-4.1/problems.xml
===================================================================
--- trunk/refman-4.1/problems.xml	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-4.1/problems.xml	2006-01-03 20:39:20 UTC (rev 655)
@@ -213,7 +213,7 @@
 
     <para>
       When sending a bug report, you should follow the outline described
-      in <xref linkend="asking-questions"/>.
+      in <xref linkend="bug-reports"/>.
     </para>
 
   </section>
@@ -1186,7 +1186,7 @@
       </para>
 
       <para>
-        See <xref linkend="asking-questions"/>.
+        See <xref linkend="bug-reports"/>.
       </para>
 
     </section>
@@ -4018,7 +4018,7 @@
           <para>
             Post the test file using <command>mysqlbug</command> to the
             general MySQL mailing list. See
-            <xref linkend="mailing-list"/>.
+            <xref linkend="mailing-lists"/>.
           </para>
         </listitem>
 

Modified: trunk/refman-4.1/renamed-nodes.txt
===================================================================
--- trunk/refman-4.1/renamed-nodes.txt	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-4.1/renamed-nodes.txt	2006-01-03 20:39:20 UTC (rev 655)
@@ -86,3 +86,8 @@
 spatial-extensions-in-mysql spatial-extensions
 column-types data-types
 other-vendor-column-types other-vendor-data-types
+mysql-information-sources information-sources
+questions information-sources
+asking-questions bug-reports
+mailing-list mailing-lists
+answering-questions mailing-list-use

Modified: trunk/refman-5.0/apis.xml
===================================================================
--- trunk/refman-5.0/apis.xml	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-5.0/apis.xml	2006-01-03 20:39:20 UTC (rev 655)
@@ -13101,7 +13101,7 @@
           <ulink url="http://dbi.perl.org/"/>. That site hosts a general
           DBI mailing list. MySQL AB hosts a list specifically about
           <literal>DBD::mysql</literal>; see
-          <xref linkend="mailing-list"/>.
+          <xref linkend="mailing-lists"/>.
         </para>
       </listitem>
 

Modified: trunk/refman-5.0/connector-odbc.xml
===================================================================
--- trunk/refman-5.0/connector-odbc.xml	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-5.0/connector-odbc.xml	2006-01-03 20:39:20 UTC (rev 655)
@@ -318,6 +318,7 @@
         For information about subscribing to MySQL mailing lists or to
         browse list archives, visit
         <ulink url="http://lists.mysql.com/"/>.
+See <xref linkend="mailing-lists"/>.
       </para>
 
       <para>
@@ -335,6 +336,7 @@
         Community support from experienced users is available through
         the MySQL Forums, located at
         <ulink url="http://forums.mysql.com"/>.
+See <xref linkend="forums"/>.
       </para>
 
     </section>
@@ -393,7 +395,7 @@
       <para>
         If you find out something is wrong, please only send the
         relevant rows (maximum 40 rows) to the <literal>myodbc</literal>
-        mailing list. See <xref linkend="mailing-list"/>. Please never
+        mailing list. See <xref linkend="mailing-lists"/>. Please never
         send the whole MyODBC or ODBC log file!
       </para>
 

Modified: trunk/refman-5.0/database-administration.xml
===================================================================
--- trunk/refman-5.0/database-administration.xml	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-5.0/database-administration.xml	2006-01-03 20:39:20 UTC (rev 655)
@@ -22464,7 +22464,7 @@
         If you want to have the character set included in the MySQL
         distribution, mail a patch to the MySQL
         <literal>internals</literal> mailing list. See
-        <xref linkend="mailing-list"/>.
+        <xref linkend="mailing-lists"/>.
       </para>
 
     </section>

Modified: trunk/refman-5.0/extending-mysql.xml
===================================================================
--- trunk/refman-5.0/extending-mysql.xml	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-5.0/extending-mysql.xml	2006-01-03 20:39:20 UTC (rev 655)
@@ -34,7 +34,7 @@
       you are interested in MySQL internals, you should also subscribe
       to our <literal>internals</literal> mailing list. This list is
       relatively low traffic. For details on how to subscribe, please
-      see <xref linkend="mailing-list"/>. All developers at MySQL AB are
+      see <xref linkend="mailing-lists"/>. All developers at MySQL AB are
       on the <literal>internals</literal> list and we help other people
       who are working on the MySQL code. Feel free to use this list both
       to ask questions about the code and to send patches that you would
@@ -338,8 +338,8 @@
               If you have a question about the test suite, or have a
               test case to contribute, send an email message to the
               MySQL <literal>internals</literal> mailing list. See
-              <xref linkend="mailing-list"/>. As this list does not
-              accept attachments, you should ftp all the relevant files
+              <xref linkend="mailing-lists"/>. This list does not
+              accept attachments, so you should FTP all the relevant files
               to: <ulink url="ftp://ftp.mysql.com/pub/mysql/upload/"/>
             </para>
           </listitem>

Modified: trunk/refman-5.0/installing.xml
===================================================================
--- trunk/refman-5.0/installing.xml	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-5.0/installing.xml	2006-01-03 20:39:20 UTC (rev 655)
@@ -463,7 +463,7 @@
         influence its development, and need more detailed instructions
         on what MySQL needs to run better, send an email message to the
         MySQL <literal>internals</literal> mailing list. See
-        <xref linkend="mailing-list"/>.
+        <xref linkend="mailing-lists"/>.
       </para>
 
       <para>
@@ -1204,7 +1204,7 @@
               <ulink url="http://dev.mysql.com/"/>, we send out an
               announcement message to the <literal>mysql</literal> and
               <literal>announce</literal> mailing lists. See
-              <xref linkend="mailing-list"/>. The announcement message
+              <xref linkend="mailing-lists"/>. The announcement message
               contains a list of all changes to the release and any
               known problems with the release. The
               <emphasis role="bold">Known Problems</emphasis> section in
@@ -1982,7 +1982,7 @@
           Anyone who has more optimal options for any of the preceding
           configurations listed can always mail them to the MySQL
           <literal>internals</literal> mailing list. See
-          <xref linkend="mailing-list"/>.
+          <xref linkend="mailing-lists"/>.
         </para>
 
         <para>
@@ -8483,7 +8483,7 @@
             you see some funny diffs or code that you have a question
             about, do not hesitate to send email to the MySQL
             <literal>internals</literal> mailing list. See
-            <xref linkend="mailing-list"/>. Also, if you think you have
+            <xref linkend="mailing-lists"/>. Also, if you think you have
             a better idea on how to do something, send an email message
             to the same address with a patch.
           </para>
@@ -9293,7 +9293,7 @@
         If you find something not working as expected, or you have
         suggestions about ways to improve the current build process on
         Windows, please send a message to the <literal>win32</literal>
-        mailing list. See <xref linkend="mailing-list"/>.
+        mailing list. See <xref linkend="mailing-lists"/>.
       </para>
 
       <section id="windows-vc-plus-plus-build">

Modified: trunk/refman-5.0/porting.xml
===================================================================
--- trunk/refman-5.0/porting.xml	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-5.0/porting.xml	2006-01-03 20:39:20 UTC (rev 655)
@@ -266,7 +266,7 @@
         distribution, the first thing you should do is to configure
         MySQL for debugging! (The second thing is to send mail to a
         MySQL mailing list and ask for help. See
-        <xref linkend="mailing-list"/>. Please use the
+        <xref linkend="mailing-lists"/>. Please use the
         <command>mysqlbug</command> script for all bug reports or
         questions regarding the MySQL version you are using!
       </para>
@@ -501,7 +501,7 @@
       <para>
         Include the above output in a mail generated with
         <command>mysqlbug</command> and mail this to the general MySQL
-        mailing list. See <xref linkend="mailing-list"/>.
+        mailing list. See <xref linkend="mailing-lists"/>.
       </para>
 
       <para>

Modified: trunk/refman-5.0/problems.xml
===================================================================
--- trunk/refman-5.0/problems.xml	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-5.0/problems.xml	2006-01-03 20:39:20 UTC (rev 655)
@@ -213,7 +213,7 @@
 
     <para>
       When sending a bug report, you should follow the outline described
-      in <xref linkend="asking-questions"/>.
+      in <xref linkend="bug-reports"/>.
     </para>
 
   </section>
@@ -1186,7 +1186,7 @@
       </para>
 
       <para>
-        See <xref linkend="asking-questions"/>.
+        See <xref linkend="bug-reports"/>.
       </para>
 
     </section>
@@ -3978,7 +3978,7 @@
           <para>
             Post the test file using <command>mysqlbug</command> to the
             general MySQL mailing list. See
-            <xref linkend="mailing-list"/>.
+            <xref linkend="mailing-lists"/>.
           </para>
         </listitem>
 

Modified: trunk/refman-5.0/renamed-nodes.txt
===================================================================
--- trunk/refman-5.0/renamed-nodes.txt	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-5.0/renamed-nodes.txt	2006-01-03 20:39:20 UTC (rev 655)
@@ -383,3 +383,8 @@
 spatial-extensions-in-mysql spatial-extensions
 column-types data-types
 other-vendor-column-types other-vendor-data-types
+mysql-information-sources information-sources
+questions information-sources
+asking-questions bug-reports
+mailing-list mailing-lists
+answering-questions mailing-list-use

Modified: trunk/refman-5.1/apis.xml
===================================================================
--- trunk/refman-5.1/apis.xml	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-5.1/apis.xml	2006-01-03 20:39:20 UTC (rev 655)
@@ -13104,7 +13104,7 @@
           <ulink url="http://dbi.perl.org/"/>. That site hosts a general
           DBI mailing list. MySQL AB hosts a list specifically about
           <literal>DBD::mysql</literal>; see
-          <xref linkend="mailing-list"/>.
+          <xref linkend="mailing-lists"/>.
         </para>
       </listitem>
 

Modified: trunk/refman-5.1/connector-odbc.xml
===================================================================
--- trunk/refman-5.1/connector-odbc.xml	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-5.1/connector-odbc.xml	2006-01-03 20:39:20 UTC (rev 655)
@@ -318,6 +318,7 @@
         For information about subscribing to MySQL mailing lists or to
         browse list archives, visit
         <ulink url="http://lists.mysql.com/"/>.
+See <xref linkend="mailing-lists"/>.
       </para>
 
       <para>
@@ -335,6 +336,7 @@
         Community support from experienced users is available through
         the MySQL Forums, located at
         <ulink url="http://forums.mysql.com"/>.
+See <xref linkend="forums"/>.
       </para>
 
     </section>
@@ -393,7 +395,7 @@
       <para>
         If you find out something is wrong, please only send the
         relevant rows (maximum 40 rows) to the <literal>myodbc</literal>
-        mailing list. See <xref linkend="mailing-list"/>. Please never
+        mailing list. See <xref linkend="mailing-lists"/>. Please never
         send the whole MyODBC or ODBC log file!
       </para>
 

Modified: trunk/refman-5.1/database-administration.xml
===================================================================
--- trunk/refman-5.1/database-administration.xml	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-5.1/database-administration.xml	2006-01-03 20:39:20 UTC (rev 655)
@@ -22384,7 +22384,7 @@
         If you want to have the character set included in the MySQL
         distribution, mail a patch to the MySQL
         <literal>internals</literal> mailing list. See
-        <xref linkend="mailing-list"/>.
+        <xref linkend="mailing-lists"/>.
       </para>
 
     </section>

Modified: trunk/refman-5.1/extending-mysql.xml
===================================================================
--- trunk/refman-5.1/extending-mysql.xml	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-5.1/extending-mysql.xml	2006-01-03 20:39:20 UTC (rev 655)
@@ -34,7 +34,7 @@
       you are interested in MySQL internals, you should also subscribe
       to our <literal>internals</literal> mailing list. This list is
       relatively low traffic. For details on how to subscribe, please
-      see <xref linkend="mailing-list"/>. All developers at MySQL AB are
+      see <xref linkend="mailing-lists"/>. All developers at MySQL AB are
       on the <literal>internals</literal> list and we help other people
       who are working on the MySQL code. Feel free to use this list both
       to ask questions about the code and to send patches that you would
@@ -338,8 +338,8 @@
               If you have a question about the test suite, or have a
               test case to contribute, send an email message to the
               MySQL <literal>internals</literal> mailing list. See
-              <xref linkend="mailing-list"/>. As this list does not
-              accept attachments, you should ftp all the relevant files
+              <xref linkend="mailing-lists"/>. This list does not
+              accept attachments, so you should FTP all the relevant files
               to: <ulink url="ftp://ftp.mysql.com/pub/mysql/upload/"/>
             </para>
           </listitem>

Modified: trunk/refman-5.1/installing.xml
===================================================================
--- trunk/refman-5.1/installing.xml	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-5.1/installing.xml	2006-01-03 20:39:20 UTC (rev 655)
@@ -463,7 +463,7 @@
         influence its development, and need more detailed instructions
         on what MySQL needs to run better, send an email message to the
         MySQL <literal>internals</literal> mailing list. See
-        <xref linkend="mailing-list"/>.
+        <xref linkend="mailing-lists"/>.
       </para>
 
       <para>
@@ -1204,7 +1204,7 @@
               <ulink url="http://dev.mysql.com/"/>, we send out an
               announcement message to the <literal>mysql</literal> and
               <literal>announce</literal> mailing lists. See
-              <xref linkend="mailing-list"/>. The announcement message
+              <xref linkend="mailing-lists"/>. The announcement message
               contains a list of all changes to the release and any
               known problems with the release. The
               <emphasis role="bold">Known Problems</emphasis> section in
@@ -1982,7 +1982,7 @@
           Anyone who has more optimal options for any of the preceding
           configurations listed can always mail them to the MySQL
           <literal>internals</literal> mailing list. See
-          <xref linkend="mailing-list"/>.
+          <xref linkend="mailing-lists"/>.
         </para>
 
         <para>
@@ -8485,7 +8485,7 @@
             you see some funny diffs or code that you have a question
             about, do not hesitate to send email to the MySQL
             <literal>internals</literal> mailing list. See
-            <xref linkend="mailing-list"/>. Also, if you think you have
+            <xref linkend="mailing-lists"/>. Also, if you think you have
             a better idea on how to do something, send an email message
             to the same address with a patch.
           </para>
@@ -9295,7 +9295,7 @@
         If you find something not working as expected, or you have
         suggestions about ways to improve the current build process on
         Windows, please send a message to the <literal>win32</literal>
-        mailing list. See <xref linkend="mailing-list"/>.
+        mailing list. See <xref linkend="mailing-lists"/>.
       </para>
 
       <section id="windows-vc-plus-plus-build">

Modified: trunk/refman-5.1/porting.xml
===================================================================
--- trunk/refman-5.1/porting.xml	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-5.1/porting.xml	2006-01-03 20:39:20 UTC (rev 655)
@@ -266,7 +266,7 @@
         distribution, the first thing you should do is to configure
         MySQL for debugging! (The second thing is to send mail to a
         MySQL mailing list and ask for help. See
-        <xref linkend="mailing-list"/>. Please use the
+        <xref linkend="mailing-lists"/>. Please use the
         <command>mysqlbug</command> script for all bug reports or
         questions regarding the MySQL version you are using!
       </para>
@@ -501,7 +501,7 @@
       <para>
         Include the above output in a mail generated with
         <command>mysqlbug</command> and mail this to the general MySQL
-        mailing list. See <xref linkend="mailing-list"/>.
+        mailing list. See <xref linkend="mailing-lists"/>.
       </para>
 
       <para>

Modified: trunk/refman-5.1/problems.xml
===================================================================
--- trunk/refman-5.1/problems.xml	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-5.1/problems.xml	2006-01-03 20:39:20 UTC (rev 655)
@@ -213,7 +213,7 @@
 
     <para>
       When sending a bug report, you should follow the outline described
-      in <xref linkend="asking-questions"/>.
+      in <xref linkend="bug-reports"/>.
     </para>
 
   </section>
@@ -1186,7 +1186,7 @@
       </para>
 
       <para>
-        See <xref linkend="asking-questions"/>.
+        See <xref linkend="bug-reports"/>.
       </para>
 
     </section>
@@ -3967,7 +3967,7 @@
           <para>
             Post the test file using <command>mysqlbug</command> to the
             general MySQL mailing list. See
-            <xref linkend="mailing-list"/>.
+            <xref linkend="mailing-lists"/>.
           </para>
         </listitem>
 

Modified: trunk/refman-5.1/renamed-nodes.txt
===================================================================
--- trunk/refman-5.1/renamed-nodes.txt	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-5.1/renamed-nodes.txt	2006-01-03 20:39:20 UTC (rev 655)
@@ -86,3 +86,8 @@
 spatial-extensions-in-mysql spatial-extensions
 column-types data-types
 other-vendor-column-types other-vendor-data-types
+mysql-information-sources information-sources
+questions information-sources
+asking-questions bug-reports
+mailing-list mailing-lists
+answering-questions mailing-list-use

Modified: trunk/refman-common/information-sources.xml
===================================================================
--- trunk/refman-common/information-sources.xml	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-common/information-sources.xml	2006-01-03 20:39:20 UTC (rev 655)
@@ -7,33 +7,42 @@
   <!ENTITY % title.entities       SYSTEM "titles.en.ent">
   %title.entities;
 ]>
-<section id="mysql-information-sources">
+<section id="information-sources">
 
-  <title>&title-mysql-information-sources;</title>
+  <title>&title-information-sources;</title>
 
-  <remark role="todo">
-    Update the intro to provide an overview of all information
-    resources, including the user forums.
-  </remark>
+  <para>
+    This section lists sources of additional information that you may
+    find helpful, such as the MySQL mailing lists, user forums, and
+    Internet Relay Chat. It also provides information on how to report
+    bugs.
+  </para>
 
-  <section id="questions">
+  <section id="mailing-lists">
 
-    <title>&title-questions;</title>
+    <title>&title-mailing-lists;</title>
 
     <indexterm type="concept">
-      <primary>reporting</primary>
-      <secondary>errors</secondary>
+      <primary>MySQL mailing lists</primary>
     </indexterm>
 
     <indexterm type="concept">
-      <primary>errors</primary>
-      <secondary>reporting</secondary>
+      <primary>mailing lists</primary>
     </indexterm>
 
     <indexterm type="concept">
-      <primary>MySQL mailing lists</primary>
+      <primary>email lists</primary>
     </indexterm>
 
+    <indexterm type="concept">
+      <primary>net etiquette</primary>
+    </indexterm>
+
+    <indexterm type="concept">
+      <primary>mailing lists</primary>
+      <secondary>archive location</secondary>
+    </indexterm>
+
     <para>
       This section introduces the MySQL mailing lists and provides
       guidelines as to how the lists should be used. When you subscribe
@@ -42,1151 +51,1112 @@
       list.
     </para>
 
-    <section id="mailing-list">
+    <para>
+      To subscribe to or unsubscribe from any of the mailing lists
+      described in this section, visit
+      <ulink url="http://lists.mysql.com/"/>. For most of them, you can
+      select the regular version of the list where you get individual
+      messages, or a digest version where you get one large message per
+      day.
+    </para>
 
-      <title>&title-mailing-list;</title>
+    <para>
+      Please <emphasis>do not</emphasis> send messages about subscribing
+      or unsubscribing to any of the mailing lists, because such
+      messages are distributed automatically to thousands of other
+      users.
+    </para>
 
-      <indexterm type="concept">
-        <primary>mailing lists</primary>
-      </indexterm>
+    <para>
+      Your local site may have many subscribers to a MySQL mailing list.
+      If so, the site may have a local mailing list, so that messages
+      sent from <literal>lists.mysql.com</literal> to your site are
+      propagated to the local list. In such cases, please contact your
+      system administrator to be added to or dropped from the local
+      MySQL list.
+    </para>
 
-      <indexterm type="concept">
-        <primary>email lists</primary>
-      </indexterm>
+    <para>
+      If you wish to have traffic for a mailing list go to a separate
+      mailbox in your mail program, set up a filter based on the message
+      headers. You can use either the <literal>List-ID:</literal> or
+      <literal>Delivered-To:</literal> headers to identify list
+      messages.
+    </para>
 
-      <para>
-        To subscribe to or unsubscribe from any of the mailing lists
-        described in this section, visit
-        <ulink url="http://lists.mysql.com/"/>. For most of them, you
-        can select the regular version of the list where you get
-        individual messages, or a digest version where you get one large
-        message per day.
-      </para>
+    <para>
+      The MySQL mailing lists are as follows:
+    </para>
 
-      <para>
-        Please <emphasis>do not</emphasis> send messages about
-        subscribing or unsubscribing to any of the mailing lists,
-        because such messages are distributed automatically to thousands
-        of other users.
-      </para>
+    <itemizedlist>
 
-      <para>
-        Your local site may have many subscribers to a MySQL mailing
-        list. If so, the site may have a local mailing list, so that
-        messages sent from <literal>lists.mysql.com</literal> to your
-        site are propagated to the local list. In such cases, please
-        contact your system administrator to be added to or dropped from
-        the local MySQL list.
-      </para>
+      <listitem>
+        <para>
+          <literal>announce</literal>
+        </para>
 
-      <para>
-        If you wish to have traffic for a mailing list go to a separate
-        mailbox in your mail program, set up a filter based on the
-        message headers. You can use either the
-        <literal>List-ID:</literal> or <literal>Delivered-To:</literal>
-        headers to identify list messages.
-      </para>
+        <para>
+          This list is for announcements of new versions of MySQL and
+          related programs. This is a low-volume list to which all MySQL
+          users should subscribe.
+        </para>
+      </listitem>
 
-      <para>
-        The MySQL mailing lists are as follows:
-      </para>
+      <listitem>
+        <para>
+          <literal>mysql</literal>
+        </para>
 
-      <itemizedlist>
+        <para>
+          This is the main list for general MySQL discussion. Please
+          note that some topics are better discussed on the
+          more-specialized lists. If you post to the wrong list, you may
+          not get an answer.
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            <literal>announce</literal>
-          </para>
+      <listitem>
+        <para>
+          <literal>bugs</literal>
+        </para>
 
-          <para>
-            This list is for announcements of new versions of MySQL and
-            related programs. This is a low-volume list to which all
-            MySQL users should subscribe.
-          </para>
-        </listitem>
+        <para>
+          This list is for people who want to stay informed about issues
+          reported since the last release of MySQL or who want to be
+          actively involved in the process of bug hunting and fixing.
+          See <xref linkend="bug-reports"/>.
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            <literal>mysql</literal>
-          </para>
+      <listitem>
+        <para>
+          <literal>internals</literal>
+        </para>
 
-          <para>
-            This is the main list for general MySQL discussion. Please
-            note that some topics are better discussed on the
-            more-specialized lists. If you post to the wrong list, you
-            may not get an answer.
-          </para>
-        </listitem>
+        <para>
+          This list is for people who work on the MySQL code. This is
+          also the forum for discussions on MySQL development and for
+          posting patches.
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            <literal>bugs</literal>
-          </para>
+      <listitem>
+        <para>
+          <literal>mysqldoc</literal>
+        </para>
 
-          <para>
-            This list is for people who want to stay informed about
-            issues reported since the last release of MySQL or who want
-            to be actively involved in the process of bug hunting and
-            fixing. See <xref linkend="bug-reports"/>.
-          </para>
-        </listitem>
+        <para>
+          This list is for people who work on the MySQL documentation:
+          people from MySQL AB, translators, and other community
+          members.
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            <literal>internals</literal>
-          </para>
+      <listitem>
+        <para>
+          <literal>benchmarks</literal>
+        </para>
 
-          <para>
-            This list is for people who work on the MySQL code. This is
-            also the forum for discussions on MySQL development and for
-            posting patches.
-          </para>
-        </listitem>
+        <para>
+          This list is for anyone interested in performance issues.
+          Discussions concentrate on database performance (not limited
+          to MySQL), but also include broader categories such as
+          performance of the kernel, filesystem, disk system, and so on.
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            <literal>mysqldoc</literal>
-          </para>
+      <listitem>
+        <para>
+          <literal>packagers</literal>
+        </para>
 
-          <para>
-            This list is for people who work on the MySQL documentation:
-            people from MySQL AB, translators, and other community
-            members.
-          </para>
-        </listitem>
+        <para>
+          This list is for discussions on packaging and distributing
+          MySQL. This is the forum used by distribution maintainers to
+          exchange ideas on packaging MySQL and on ensuring that MySQL
+          looks and feels as similar as possible on all supported
+          platforms and operating systems.
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            <literal>benchmarks</literal>
-          </para>
+      <listitem>
+        <para>
+          <literal>java</literal>
+        </para>
 
-          <para>
-            This list is for anyone interested in performance issues.
-            Discussions concentrate on database performance (not limited
-            to MySQL), but also include broader categories such as
-            performance of the kernel, filesystem, disk system, and so
-            on.
-          </para>
-        </listitem>
+        <para>
+          This list is for discussions about the MySQL server and Java.
+          It is mostly used to discuss JDBC drivers such as MySQL
+          Connector/J.
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            <literal>packagers</literal>
-          </para>
+      <listitem>
+        <para>
+          <literal>win32</literal>
+        </para>
 
-          <para>
-            This list is for discussions on packaging and distributing
-            MySQL. This is the forum used by distribution maintainers to
-            exchange ideas on packaging MySQL and on ensuring that MySQL
-            looks and feels as similar as possible on all supported
-            platforms and operating systems.
-          </para>
-        </listitem>
+        <para>
+          This list is for all topics concerning the MySQL software on
+          Microsoft operating systems, such as Windows 9x, Me, NT, 2000,
+          XP, and 2003.
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            <literal>java</literal>
-          </para>
+      <listitem>
+        <para>
+          <literal>myodbc</literal>
+        </para>
 
-          <para>
-            This list is for discussions about the MySQL server and
-            Java. It is mostly used to discuss JDBC drivers, including
-            MySQL Connector/J.
-          </para>
-        </listitem>
+        <para>
+          This list is for all topics concerning connecting to the MySQL
+          server with ODBC.
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            <literal>win32</literal>
-          </para>
+      <listitem>
+        <para>
+          <literal>gui-tools</literal>
+        </para>
 
-          <para>
-            This list is for all topics concerning the MySQL software on
-            Microsoft operating systems, such as Windows 9x, Me, NT,
-            2000, XP, and 2003.
-          </para>
-        </listitem>
+        <para>
+          This list is for all topics concerning MySQL graphical user
+          interface tools such as <literal>MySQL Administrator</literal>
+          and <literal>MySQL Query Browser</literal>.
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            <literal>myodbc</literal>
-          </para>
+      <listitem>
+        <para>
+          <literal>cluster</literal>
+        </para>
 
-          <para>
-            This list is for all topics concerning connecting to the
-            MySQL server with ODBC.
-          </para>
-        </listitem>
+        <para>
+          This list is for discussion of MySQL Cluster.
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            <literal>gui-tools</literal>
-          </para>
+      <listitem>
+        <para>
+          <literal>dotnet</literal>
+        </para>
 
-          <para>
-            This list is for all topics concerning MySQL graphical user
-            interface tools, including <literal>MySQL
-            Administrator</literal> and <literal>MySQL Query
-            Browser</literal>.
-          </para>
-        </listitem>
+        <para>
+          This list is for discussion of the MySQL server and the .NET
+          platform. It is mostly related to MySQL Connector/Net.
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            <literal>cluster</literal>
-          </para>
+      <listitem>
+        <para>
+          <literal>plusplus</literal>
+        </para>
 
-          <para>
-            This list is for discussion of MySQL Cluster.
-          </para>
-        </listitem>
+        <para>
+          This list is for all topics concerning programming with the
+          C++ API for MySQL.
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            <literal>dotnet</literal>
-          </para>
+      <listitem>
+        <para>
+          <literal>perl</literal>
+        </para>
 
-          <para>
-            This list is for discussion of the MySQL server and the .NET
-            platform. Mostly related to the MySQL Connector/Net
-            provider.
-          </para>
-        </listitem>
+        <para>
+          This list is for all topics concerning Perl support for MySQL
+          with <literal>DBD::mysql</literal>.
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            <literal>plusplus</literal>
-          </para>
+    </itemizedlist>
 
-          <para>
-            This list is for all topics concerning programming with the
-            C++ API for MySQL.
-          </para>
-        </listitem>
+    <para>
+      If you're unable to get an answer to your questions from a MySQL
+      mailing list or forum, one option is to purchase support from
+      MySQL AB. This puts you in direct contact with MySQL developers.
+    </para>
 
-        <listitem>
-          <para>
-            <literal>perl</literal>
-          </para>
+    <para>
+      The following table shows some MySQL mailing lists in languages
+      other than English. These lists are not operated by MySQL AB.
+    </para>
 
-          <para>
-            This list is for all topics concerning the Perl support for
-            MySQL with <literal>DBD::mysql</literal>.
-          </para>
-        </listitem>
+    <itemizedlist>
 
-      </itemizedlist>
+      <listitem>
+        <para>
+          <literal><email>mysql-france-subscribe@stripped</email></literal>
+        </para>
 
-      <para>
-        If you're unable to get an answer to your questions from a MySQL
-        mailing list or forum, one option is to purchase support from
-        MySQL AB. This puts you in direct contact with MySQL developers.
-      </para>
+        <para>
+          A French mailing list.
+        </para>
+      </listitem>
 
-      <para>
-        The following table shows some MySQL mailing lists in languages
-        other than English. These lists are not operated by MySQL AB.
-      </para>
+      <listitem>
+        <para>
+          <literal><email>list@stripped</email></literal>
+        </para>
 
-      <itemizedlist>
+        <para>
+          A Korean mailing list. To subscribe, email <literal>subscribe
+          mysql your@stripped</literal> to this list.
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            <literal><email>mysql-france-subscribe@stripped</email></literal>
-          </para>
+      <listitem>
+        <para>
+          <literal><email>mysql-de-request@stripped</email></literal>
+        </para>
 
-          <para>
-            A French mailing list.
-          </para>
-        </listitem>
+        <para>
+          A German mailing list. To subscribe, email <literal>subscribe
+          mysql-de your@stripped</literal> to this list. You can
+          find information about this mailing list at
+          <ulink url="http://www.4t2.com/mysql/"/>.
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            <literal><email>list@stripped</email></literal>
-          </para>
+      <listitem>
+        <para>
+          <literal><email>mysql-br-request@stripped</email></literal>
+        </para>
 
-          <para>
-            A Korean mailing list. Email <literal>subscribe mysql
-            your@stripped</literal> to this list.
-          </para>
-        </listitem>
+        <para>
+          A Portuguese mailing list. To subscribe, email
+          <literal>subscribe mysql-br your@stripped</literal> to
+          this list.
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            <literal><email>mysql-de-request@stripped</email></literal>
-          </para>
+      <listitem>
+        <para>
+          <literal><email>mysql-alta@stripped</email></literal>
+        </para>
 
-          <para>
-            A German mailing list. Email <literal>subscribe mysql-de
-            your@stripped</literal> to this list. You can find
-            information about this mailing list at
-            <ulink url="http://www.4t2.com/mysql/"/>.
-          </para>
-        </listitem>
+        <para>
+          A Spanish mailing list. To subscribe, email <literal>subscribe
+          mysql your@stripped</literal> to this list.
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            <literal><email>mysql-br-request@stripped</email></literal>
-          </para>
+    </itemizedlist>
 
-          <para>
-            A Portuguese mailing list. Email <literal>subscribe mysql-br
-            your@stripped</literal> to this list.
-          </para>
-        </listitem>
+    <section id="mailing-list-use">
 
-        <listitem>
-          <para>
-            <literal><email>mysql-alta@stripped</email></literal>
-          </para>
+      <title>&title-mailing-list-use;</title>
 
-          <para>
-            A Spanish mailing list. Email <literal>subscribe mysql
-            your@stripped</literal> to this list.
-          </para>
-        </listitem>
-
-      </itemizedlist>
-
-    </section>
-
-    <section id="asking-questions">
-
-      <title>&title-asking-questions;</title>
-
       <indexterm type="concept">
         <primary>net etiquette</primary>
       </indexterm>
 
       <indexterm type="concept">
-        <primary>mailing lists</primary>
-        <secondary>archive location</secondary>
+        <primary>questions</primary>
+        <secondary>answering</secondary>
       </indexterm>
 
       <indexterm type="concept">
-        <primary>searching</primary>
-        <secondary>MySQL Web pages</secondary>
+        <primary>answering questions</primary>
+        <secondary>etiquette</secondary>
       </indexterm>
 
-      <para>
-        Before posting a bug report or question, please do the
-        following:
-      </para>
-
-      <itemizedlist>
-
-        <listitem>
-          <para>
-            Start by searching the MySQL online manual at
-            <ulink url="&base-url-docs;"/>. We try to keep the manual up
-            to date by updating it frequently with solutions to newly
-            found problems. The change history
-            (<ulink url="&base-url-docs;mysql/en/News.html"/>) can be
-            particularly useful since it is quite possible that a newer
-            version contains a solution to your problem.
-          </para>
-        </listitem>
-
-        <listitem>
-          <para>
-            Search in the bugs database at
-            <ulink url="http://bugs.mysql.com/"/> to see whether the bug
-            has been reported and fixed.
-          </para>
-        </listitem>
-
-        <listitem>
-          <para>
-            Search the MySQL mailing list archives at
-            <ulink url="http://lists.mysql.com/"/>.
-          </para>
-        </listitem>
-
-        <listitem>
-          <para>
-            You can also use <ulink url="http://www.mysql.com/search/"/>
-            to search all the Web pages (including the manual) that are
-            located at the MySQL AB Web site.
-          </para>
-        </listitem>
-
-      </itemizedlist>
-
-      <para>
-        If you can't find an answer in the manual or the archives, check
-        with your local MySQL expert. If you still can't find an answer
-        to your question, please follow the guidelines on sending mail
-        to a MySQL mailing list, outlined in the next section, before
-        contacting us.
-      </para>
-
-    </section>
-
-    <section id="bug-reports">
-
-      <title>&title-bug-reports;</title>
-
       <indexterm type="concept">
-        <primary>bugs</primary>
-        <secondary>reporting</secondary>
+        <primary>mailing lists</primary>
+        <secondary>guidelines</secondary>
       </indexterm>
 
-      <indexterm type="concept">
-        <primary>reporting</primary>
-        <secondary>bugs</secondary>
-      </indexterm>
-
-      <indexterm type="concept">
-        <primary>problems</primary>
-        <secondary>reporting</secondary>
-      </indexterm>
-
-      <indexterm type="concept">
-        <primary>errors</primary>
-        <secondary>reporting</secondary>
-      </indexterm>
-
-      <indexterm type="concept">
-        <primary><command>mysqlbug</command> script</primary>
-      </indexterm>
-
-      <indexterm type="concept">
-        <primary>creating</primary>
-        <secondary>bug reports</secondary>
-      </indexterm>
-
-      <indexterm type="concept">
-        <primary>scripts</primary>
-        <secondary><command>mysqlbug</command></secondary>
-      </indexterm>
-
-      <indexterm type="concept">
-        <primary>bugs.mysql.com</primary>
-      </indexterm>
-
-      <indexterm type="concept">
-        <primary>bugs database</primary>
-      </indexterm>
-
       <para>
-        The normal place to report bugs is
-        <ulink url="http://bugs.mysql.com/"/>, which is the address for
-        our bugs database. This database is public, and can be browsed
-        and searched by anyone. If you log in to the system, you can
-        enter new reports.
+        Please don't post mail messages from your browser with HTML mode
+        turned on. Many users don't read mail with a browser.
       </para>
 
       <para>
-        Writing a good bug report takes patience, but doing it right the
-        first time saves time both for us and for yourself. A good bug
-        report, containing a full test case for the bug, makes it very
-        likely that we will fix the bug in the next release. This
-        section helps you write your report correctly so that you don't
-        waste your time doing things that may not help us much or at
-        all.
+        When you answer a question sent to a mailing list, if you
+        consider your answer to have broad interest, you may want to
+        post it to the list instead of replying directly to the
+        individual who asked. Try to make your answer general enough
+        that people other than the original poster may benefit from it.
+        When you post to the list, please make sure that your answer is
+        not a duplication of a previous answer.
       </para>
 
       <para>
-        We encourage everyone to use the <command>mysqlbug</command>
-        script to generate a bug report (or a report about any problem).
-        <command>mysqlbug</command> can be found in the
-        <filename>scripts</filename> directory (source distribution) and
-        in the <filename>bin</filename> directory under your MySQL
-        installation directory (binary distribution). If you are unable
-        to use <command>mysqlbug</command> (for example, if you are
-        running on Windows), it is still vital that you include all the
-        necessary information noted in this section (most importantly, a
-        description of the operating system and the MySQL version).
+        Try to summarize the essential part of the question in your
+        reply. Don't feel obliged to quote the entire original message.
       </para>
 
       <para>
-        The <command>mysqlbug</command> script helps you generate a
-        report by determining much of the following information
-        automatically, but if something important is missing, please
-        include it with your message. Please read this section carefully
-        and make sure that all the information described here is
-        included in your report.
+        When answers are sent to you individually and not to the mailing
+        list, it is considered good etiquette to summarize the answers
+        and send the summary to the mailing list so that others may have
+        the benefit of responses you received that helped you solve your
+        problem.
       </para>
 
-      <para>
-        Preferably, you should test the problem using the latest
-        production or development version of MySQL Server before
-        posting. Anyone should be able to repeat the bug by just using
-        <literal>mysql test &lt; script_file</literal> on the included
-        test case or by running the shell or Perl script that is
-        included in the bug report.
-      </para>
+    </section>
 
-      <para>
-        All bugs posted in the bugs database at
-        <ulink url="http://bugs.mysql.com/"/> are corrected or
-        documented in the next MySQL release. If only minor code changes
-        are needed to correct a problem, we may also post a patch that
-        fixes the problem.
-      </para>
+  </section>
 
-      <para>
-        If you have found a sensitive security bug in MySQL, you can
-        send email to <email>security@stripped</email>.
-      </para>
+  <section id="forums">
 
-      <para>
-        If you have a repeatable bug report, please report it to the
-        bugs database at <ulink url="http://bugs.mysql.com/"/>. Note
-        that even in this case it's good to run the
-        <command>mysqlbug</command> script first to find information
-        about your system. Any bug that we are able to repeat has a high
-        chance of being fixed in the next MySQL release.
-      </para>
+    <title>&title-forums;</title>
 
-      <para>
-        To report other problems, you can use one of the MySQL mailing
-        lists.
-      </para>
+    <indexterm type="concept">
+      <primary>Forums</primary>
+    </indexterm>
 
-      <para>
-        Remember that it is possible for us to respond to a message
-        containing too much information, but not to one containing too
-        little. People often omit facts because they think they know the
-        cause of a problem and assume that some details don't matter. A
-        good principle is this: If you are in doubt about stating
-        something, state it. It is faster and less troublesome to write
-        a couple more lines in your report than to wait longer for the
-        answer if we must ask you to provide information that was
-        missing from the initial report.
-      </para>
+    <para>
+      The forums at <ulink url="http://forums.mysql.com"/> are an
+      important community resource. A variety of forums is available,
+      grouped into these general categories:
+    </para>
 
-      <para>
-        The most common errors made in bug reports are (a) not including
-        the version number of the MySQL distribution used, and (b) not
-        fully describing the platform on which the MySQL server is
-        installed (including the platform type and version number). This
-        is highly relevant information, and in 99 cases out of 100, the
-        bug report is useless without it. Very often we get questions
-        like, <quote>Why doesn't this work for me?</quote> Then we find
-        that the feature requested wasn't implemented in that MySQL
-        version, or that a bug described in a report has been fixed in
-        newer MySQL versions. Sometimes the error is platform-dependent;
-        in such cases, it is next to impossible for us to fix anything
-        without knowing the operating system and the version number of
-        the platform.
-      </para>
+    <itemizedlist>
 
-      <para>
-        If you compiled MySQL from source, remember also to provide
-        information about your compiler, if it is related to the
-        problem. Often people find bugs in compilers and think the
-        problem is MySQL-related. Most compilers are under development
-        all the time and become better version by version. To determine
-        whether your problem depends on your compiler, we need to know
-        what compiler you use. Note that every compiling problem should
-        be regarded as a bug and reported accordingly.
-      </para>
+      <listitem>
+        <para>
+          Migration
+        </para>
+      </listitem>
 
-      <para>
-        It is most helpful when a good description of the problem is
-        included in the bug report. That is, give a good example of
-        everything you did that led to the problem and describe, in
-        exact detail, the problem itself. The best reports are those
-        that include a full example showing how to reproduce the bug or
-        problem. See <xref linkend="reproduceable-test-case"/>.
-      </para>
+      <listitem>
+        <para>
+          MySQL Usage
+        </para>
+      </listitem>
 
-      <para>
-        If a program produces an error message, it is very important to
-        include the message in your report. If we try to search for
-        something from the archives using programs, it is better that
-        the error message reported exactly matches the one that the
-        program produces. (Even the lettercase should be observed.) You
-        should never try to reproduce from memory what the error message
-        was; instead, copy and paste the entire message into your
-        report.
-      </para>
+      <listitem>
+        <para>
+          MySQL Connectors
+        </para>
+      </listitem>
 
-      <para>
-        If you have a problem with Connector/ODBC (MyODBC), please try
-        to generate a trace file and send it with your report. See
-        <xref linkend="myodbc-bug-report"/>.
-      </para>
+      <listitem>
+        <para>
+          Programming Languages
+        </para>
+      </listitem>
 
-      <para>
-        Please remember that many of the people who read your report do
-        so using an 80-column display. When generating reports or
-        examples using the <command>mysql</command> command-line tool,
-        you should therefore use the <option>--vertical</option> option
-        (or the <literal>\G</literal> statement terminator) for output
-        that would exceed the available width for such a display (for
-        example, with the <literal>EXPLAIN SELECT</literal> statement;
-        see the example later in this section).
-      </para>
+      <listitem>
+        <para>
+          Tools
+        </para>
+      </listitem>
 
-      <indexterm type="concept">
-        <primary>bug reports</primary>
-        <secondary>criteria for</secondary>
-      </indexterm>
+      <listitem>
+        <para>
+          3rd-Party Applications
+        </para>
+      </listitem>
 
-      <para>
-        Please include the following information in your report:
-      </para>
+      <listitem>
+        <para>
+          Storage Engines
+        </para>
+      </listitem>
 
-      <itemizedlist>
+      <listitem>
+        <para>
+          MySQL Technology
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            The version number of the MySQL distribution you are using
-            (for example, MySQL 4.0.12). You can find out which version
-            you are running by executing <command>mysqladmin
-            version</command>. The <command>mysqladmin</command> program
-            can be found in the <filename>bin</filename> directory under
-            your MySQL installation directory.
-          </para>
-        </listitem>
+      <listitem>
+        <para>
+          SQL Standards
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            The manufacturer and model of the machine on which you
-            experience the problem.
-          </para>
-        </listitem>
+      <listitem>
+        <para>
+          Business
+        </para>
+      </listitem>
 
-        <listitem>
-          <para>
-            The operating system name and version. If you work with
-            Windows, you can usually get the name and version number by
-            double-clicking your My Computer icon and pulling down the
-            <quote>Help/About Windows</quote> menu. For most Unix-like
-            operating systems, you can get this information by executing
-            the command <literal>uname -a</literal>.
-          </para>
-        </listitem>
+    </itemizedlist>
 
-        <listitem>
-          <para>
-            Sometimes the amount of memory (real and virtual) is
-            relevant. If in doubt, include these values.
-          </para>
-        </listitem>
+  </section>
 
-        <listitem>
-          <para>
-            If you are using a source distribution of the MySQL
-            software, the name and version number of the compiler used
-            are needed. If you have a binary distribution, the
-            distribution name is needed.
-          </para>
-        </listitem>
+  <section id="irc">
 
-        <listitem>
-          <para>
-            If the problem occurs during compilation, include the exact
-            error messages and also a few lines of context around the
-            offending code in the file where the error occurs.
-          </para>
-        </listitem>
+    <title>&title-irc;</title>
 
-        <listitem>
-          <para>
-            If <command>mysqld</command> died, you should also report
-            the query that crashed <command>mysqld</command>. You can
-            usually find this out by running <command>mysqld</command>
-            with query logging enabled, and then looking in the log
-            after <command>mysqld</command> crashes See
-            <xref linkend="using-log-files"/>.
-          </para>
-        </listitem>
+    <indexterm type="concept">
+      <primary>IRC</primary>
+    </indexterm>
 
-        <listitem>
-          <para>
-            If a database table is related to the problem, include the
-            output from <command>mysqldump --no-data
-            <replaceable>db_name</replaceable>
-            <replaceable>tbl_name</replaceable></command>. This is very
-            easy to do and is a powerful way to get information about
-            any table in a database. The information helps us create a
-            situation matching the one you have experienced.
-          </para>
-        </listitem>
+    <indexterm type="concept">
+      <primary>Internet Relay Chat</primary>
+    </indexterm>
 
-        <listitem>
-          <para>
-            For speed-related bugs or problems with
-            <literal>SELECT</literal> statements, you should always
-            include the output of <literal>EXPLAIN SELECT ...</literal>,
-            and at least the number of rows that the
-            <literal>SELECT</literal> statement produces. You should
-            also include the output from <literal>SHOW CREATE TABLE
-            <replaceable>tbl_name</replaceable></literal> for each
-            involved table. The more information you give about your
-            situation, the more likely it is that someone can help you.
-          </para>
+    <para>
+      In addition to the various MySQL mailing lists, you can find
+      experienced community people on Internet Relay Chat (IRC). These
+      are the best networks/channels currently known to us:
+    </para>
 
-          <para>
-            The following is an example of a very good bug report. It
-            should be posted with the <command>mysqlbug</command>
-            script. The example uses the <command>mysql</command>
-            command-line tool. Note the use of the <literal>\G</literal>
-            statement terminator for statements whose output width would
-            otherwise exceed that of an 80-column display device.
-          </para>
+    <para>
+      <emphasis role="bold">freenode</emphasis> (see
+      <ulink url="http://www.freenode.net/"/> for servers)
+    </para>
 
-<programlisting>
-mysql&gt; <userinput>SHOW VARIABLES;</userinput>
-mysql&gt; <userinput>SHOW COLUMNS FROM ...\G</userinput>
-       &lt;output from SHOW COLUMNS&gt;
-mysql&gt; <userinput>EXPLAIN SELECT ...\G</userinput>
-       &lt;output from EXPLAIN&gt;
-mysql&gt; <userinput>FLUSH STATUS;</userinput>
-mysql&gt; <userinput>SELECT ...;</userinput>
-       &lt;A short version of the output from SELECT,
-       including the time taken to run the query&gt;
-mysql&gt; <userinput>SHOW STATUS;</userinput>
-       &lt;output from SHOW STATUS&gt;
-</programlisting>
-        </listitem>
+    <itemizedlist>
 
-        <listitem>
-          <para>
-            If a bug or problem occurs while running
-            <command>mysqld</command>, try to provide an input script
-            that reproduces the anomaly. This script should include any
-            necessary source files. The more closely the script can
-            reproduce your situation, the better. If you can make a
-            reproducible test case, you should post it on
-            <ulink url="http://bugs.mysql.com/"/> for high-priority
-            treatment.
-          </para>
+      <listitem>
+        <para>
+          <literal>#mysql</literal> is primarily for MySQL questions,
+          but other database and general SQL questions are welcome.
+          Questions about PHP, Perl, or C in combination with MySQL are
+          also common.
+        </para>
+      </listitem>
 
-          <para>
-            If you can't provide a script, you should at least include
-            the output from <command>mysqladmin variables
-            extended-status processlist</command> in your mail to
-            provide some information on how your system is performing.
-          </para>
-        </listitem>
+    </itemizedlist>
 
-        <listitem>
-          <para>
-            If you can't produce a test case with only a few rows, or if
-            the test table is too big to be mailed to the mailing list
-            (more than 10 rows), you should dump your tables using
-            <command>mysqldump</command> and create a
-            <filename>README</filename> file that describes your
-            problem.
-          </para>
+    <remark role="todo">
+      Update following paragraph, as the win32 version is no longer
+      free.
+    </remark>
 
-          <para>
-            Create a compressed archive of your files using
-            <command>tar</command> and <command>gzip</command> or
-            <command>zip</command>, and use FTP to transfer the archive
-            to <ulink url="ftp://ftp.mysql.com/pub/mysql/upload/"/>.
-            Then enter the problem into our bugs database at
-            <ulink url="http://bugs.mysql.com/"/>.
-          </para>
-        </listitem>
+    <para>
+      If you are looking for IRC client software to connect to an IRC
+      network, take a look at <literal>xChat</literal>
+      (<ulink url="http://www.xchat.org/"/>). X-Chat (GPL licensed) is
+      available for Unix as well as for Windows platforms (a free
+      Windows build of X-Chat is available at
+      <ulink url="http://www.silverex.org/download/"/>).
+    </para>
 
-        <listitem>
-          <para>
-            If you think that the MySQL server produces a strange result
-            from a query, include not only the result, but also your
-            opinion of what the result should be, and an account
-            describing the basis for your opinion.
-          </para>
-        </listitem>
+  </section>
 
-        <listitem>
-          <para>
-            When giving an example of the problem, it's better to use
-            the variable names, table names, and so on that exist in
-            your actual situation than to come up with new names. The
-            problem could be related to the name of a variable or table.
-            These cases are rare, perhaps, but it is better to be safe
-            than sorry. After all, it should be easier for you to
-            provide an example that uses your actual situation, and it
-            is by all means better for us. In case you have data that
-            you don't want to show to others, you can use FTP to
-            transfer it to
-            <ulink url="ftp://ftp.mysql.com/pub/mysql/upload/"/>. If the
-            information is really top secret and you don't want to show
-            it even to us, then go ahead and provide an example using
-            other names, but please regard this as the last choice.
-          </para>
-        </listitem>
+  <section id="bug-reports">
 
-        <listitem>
-          <para>
-            Include all the options given to the relevant programs, if
-            possible. For example, indicate the options that you use
-            when you start the <command>mysqld</command> server as well
-            as the options that you use to run any MySQL client
-            programs. The options to programs such as
-            <command>mysqld</command> and <command>mysql</command>, and
-            to the <command>configure</command> script, are often keys
-            to answers and are very relevant. It is never a bad idea to
-            include them. If you use any modules, such as Perl or PHP,
-            please include the version numbers of those as well.
-          </para>
-        </listitem>
+    <title>&title-bug-reports;</title>
 
-        <listitem>
-          <para>
-            If your question is related to the privilege system, please
-            include the output of <command>mysqlaccess</command>, the
-            output of <command>mysqladmin reload</command>, and all the
-            error messages you get when trying to connect. When you test
-            your privileges, you should first run
-            <command>mysqlaccess</command>. After this, execute
-            <command>mysqladmin reload version</command> and try to
-            connect with the program that gives you trouble.
-            <command>mysqlaccess</command> can be found in the
-            <filename>bin</filename> directory under your MySQL
-            installation directory.
-          </para>
-        </listitem>
+    <indexterm type="concept">
+      <primary>reporting</primary>
+      <secondary>errors</secondary>
+    </indexterm>
 
-        <listitem>
-          <para>
-            If you have a patch for a bug, do include it. But don't
-            assume that the patch is all we need, or that we can use it,
-            if you don't provide some necessary information such as test
-            cases showing the bug that your patch fixes. We might find
-            problems with your patch or we might not understand it at
-            all; if so, we can't use it.
-          </para>
+    <indexterm type="concept">
+      <primary>errors</primary>
+      <secondary>reporting</secondary>
+    </indexterm>
 
-          <para>
-            If we can't verify exactly what the purpose of the patch is,
-            we won't use it. Test cases help us here. Show that the
-            patch handles all the situations that may occur. If we find
-            a borderline case (even a rare one) where the patch won't
-            work, it may be useless.
-          </para>
-        </listitem>
+    <indexterm type="concept">
+      <primary>searching</primary>
+      <secondary>MySQL Web pages</secondary>
+    </indexterm>
 
-        <listitem>
-          <para>
-            Guesses about what the bug is, why it occurs, or what it
-            depends on are usually wrong. Even the MySQL team can't
-            guess such things without first using a debugger to
-            determine the real cause of a bug.
-          </para>
-        </listitem>
+    <indexterm type="concept">
+      <primary>bug reports</primary>
+      <secondary>criteria for</secondary>
+    </indexterm>
 
-        <listitem>
-          <para>
-            Indicate in your bug report that you have checked the
-            reference manual and mail archive so that others know you
-            have tried to solve the problem yourself.
-          </para>
-        </listitem>
+    <indexterm type="concept">
+      <primary>bugs</primary>
+      <secondary>reporting</secondary>
+    </indexterm>
 
-        <listitem>
-          <para>
-            If you get a <literal>parse error</literal>, please check
-            your syntax closely. If you can't find something wrong with
-            it, it's extremely likely that your current version of MySQL
-            Server doesn't support the syntax you are using. If you are
-            using the current version and the manual at
-            <ulink url="&base-url-docs;"/> doesn't cover the syntax you
-            are using, MySQL Server doesn't support your query. In this
-            case, your only options are to implement the syntax yourself
-            or email <email>licensing@stripped</email> and ask for an
-            offer to implement it.
-          </para>
+    <indexterm type="concept">
+      <primary>reporting</primary>
+      <secondary>bugs</secondary>
+    </indexterm>
 
-          <para>
-            If the manual covers the syntax you are using, but you have
-            an older version of MySQL Server, you should check the MySQL
-            change history to see when the syntax was implemented. In
-            this case, you have the option of upgrading to a newer
-            version of MySQL Server. See <xref linkend="news"/>.
-          </para>
-        </listitem>
+    <indexterm type="concept">
+      <primary>problems</primary>
+      <secondary>reporting</secondary>
+    </indexterm>
 
-        <listitem>
-          <para>
-            If your problem is that your data appears corrupt or you get
-            errors when you access a particular table, you should first
-            check and then try to repair your tables with <literal>CHECK
-            TABLE</literal> and <literal>REPAIR TABLE</literal> or with
-            <command>myisamchk</command>. See
-            <xref linkend="database-administration"/>.
-          </para>
+    <indexterm type="concept">
+      <primary>errors</primary>
+      <secondary>reporting</secondary>
+    </indexterm>
 
-          <para>
-            If you are running Windows, please verify the value of
-            <literal>lower_case_table_names</literal> using the
-            <literal>SHOW VARIABLES LIKE
-            'lower_case_table_names'</literal> command.
-          </para>
-        </listitem>
+    <indexterm type="concept">
+      <primary>creating</primary>
+      <secondary>bug reports</secondary>
+    </indexterm>
 
-        <listitem>
-          <para>
-            If you often get corrupted tables, you should try to find
-            out when and why this happens. In this case, the error log
-            in the MySQL data directory may contain some information
-            about what happened. (This is the file with the
-            <filename>.err</filename> suffix in the name.) See
-            <xref linkend="error-log"/>. Please include any relevant
-            information from this file in your bug report. Normally
-            <command>mysqld</command> should <emphasis>never</emphasis>
-            crash a table if nothing killed it in the middle of an
-            update. If you can find the cause of
-            <command>mysqld</command> dying, it's much easier for us to
-            provide you with a fix for the problem. See
-            <xref linkend="what-is-crashing"/>.
-          </para>
-        </listitem>
+    <indexterm type="concept">
+      <primary>bugs.mysql.com</primary>
+    </indexterm>
 
-        <listitem>
-          <para>
-            If possible, download and install the most recent version of
-            MySQL Server and check whether it solves your problem. All
-            versions of the MySQL software are thoroughly tested and
-            should work without problems. We believe in making
-            everything as backward-compatible as possible, and you
-            should be able to switch MySQL versions without difficulty.
-            See <xref linkend="which-version"/>.
-          </para>
-        </listitem>
+    <indexterm type="concept">
+      <primary>bugs database</primary>
+    </indexterm>
 
-      </itemizedlist>
+    <indexterm type="concept">
+      <primary><command>mysqlbug</command> script</primary>
+    </indexterm>
 
-      <indexterm type="concept">
-        <primary>technical support</primary>
-        <secondary>mailing address</secondary>
-      </indexterm>
+    <indexterm type="concept">
+      <primary>scripts</primary>
+      <secondary><command>mysqlbug</command></secondary>
+    </indexterm>
 
-      <indexterm type="concept">
-        <primary>support</primary>
-        <secondary>mailing address</secondary>
-      </indexterm>
+    <para>
+      Before posting a bug report about a problem, please try to verify
+      that it is a bug and that it has not been reported already:
+    </para>
 
-      <indexterm type="concept">
-        <primary>customer support</primary>
-        <secondary>mailing address</secondary>
-      </indexterm>
+    <itemizedlist>
 
-      <indexterm type="concept">
-        <primary>mailing address</primary>
-        <secondary>for customer support</secondary>
-      </indexterm>
+      <listitem>
+        <para>
+          Start by searching the MySQL online manual at
+          <ulink url="&base-url-docs;"/>. We try to keep the manual up
+          to date by updating it frequently with solutions to newly
+          found problems. The change history
+          (<ulink url="&base-url-docs;mysql/en/news.html"/>) can be
+          particularly useful since it is quite possible that a newer
+          version contains a solution to your problem.
+        </para>
 
-      <para>
-        If you are a support customer, please cross-post the bug report
-        to <email>mysql-support@stripped</email> for higher-priority
-        treatment, as well as to the appropriate mailing list to see
-        whether someone else has experienced (and perhaps solved) the
-        problem.
-      </para>
+        <para>
+          If you get a parse error for a SQL statement, please check
+          your syntax closely. If you can't find something wrong with
+          it, it's extremely likely that your current version of MySQL
+          Server doesn't support the syntax you are using. If you are
+          using the current version and the manual doesn't cover the
+          syntax that you are using, MySQL Server doesn't support your
+          statement. In this case, your options are to implement the
+          syntax yourself or email <email>licensing@stripped</email>
+          and ask for an offer to implement it.
+        </para>
 
-      <para>
-        For information on reporting bugs in MyODBC, see
-        <xref linkend="myodbc-bug-report"/>.
-      </para>
+        <para>
+          If the manual covers the syntax you are using, but you have an
+          older version of MySQL Server, you should check the MySQL
+          change history to see when the syntax was implemented. In this
+          case, you have the option of upgrading to a newer version of
+          MySQL Server.
+        </para>
+      </listitem>
 
-      <para>
-        For solutions to some common problems, see
-        <xref linkend="problems"/>.
-      </para>
+      <listitem>
+        <para>
+          For solutions to some common problems, see
+          <xref linkend="problems"/>.
+        </para>
+      </listitem>
 
-      <para>
-        When answers are sent to you individually and not to the mailing
-        list, it is considered good etiquette to summarize the answers
-        and send the summary to the mailing list so that others may have
-        the benefit of responses you received that helped you solve your
-        problem.
-      </para>
+      <listitem>
+        <para>
+          Search in the bugs database at
+          <ulink url="http://bugs.mysql.com/"/> to see whether the bug
+          has been reported and fixed.
+        </para>
+      </listitem>
 
-    </section>
+      <listitem>
+        <para>
+          Search the MySQL mailing list archives at
+          <ulink url="http://lists.mysql.com/"/>. See
+          <xref linkend="mailing-lists"/>.
+        </para>
+      </listitem>
 
-    <section id="answering-questions">
+      <listitem>
+        <para>
+          You can also use <ulink url="http://www.mysql.com/search/"/>
+          to search all the Web pages (including the manual) that are
+          located at the MySQL AB Web site.
+        </para>
+      </listitem>
 
-      <title>&title-answering-questions;</title>
+    </itemizedlist>
 
-      <indexterm type="concept">
-        <primary>net etiquette</primary>
-      </indexterm>
+    <para>
+      If you can't find an answer in the manual or the archives, check
+      with your local MySQL expert. If you still can't find an answer to
+      your question, please use the following guidelines for reporting
+      the bug.
+    </para>
 
-      <indexterm type="concept">
-        <primary>questions</primary>
-        <secondary>answering</secondary>
-      </indexterm>
+    <para>
+      The normal way to report bugs is to visit
+      <ulink url="http://bugs.mysql.com/"/>, which is the address for
+      our bugs database. This database is public, and can be browsed and
+      searched by anyone. If you log in to the system, you can enter new
+      reports.
+    </para>
 
-      <indexterm type="concept">
-        <primary>answering questions</primary>
-        <secondary>etiquette</secondary>
-      </indexterm>
+    <para>
+      If you have found a sensitive security bug in MySQL, you can send
+      email to <email>security@stripped</email>.
+    </para>
 
-      <indexterm type="concept">
-        <primary>mailing lists</primary>
-        <secondary>guidelines</secondary>
-      </indexterm>
+    <para>
+      To report other problems, you can use one of the MySQL mailing
+      lists. <xref linkend="mailing-lists"/>.
+    </para>
 
-      <para>
-        If you consider your answer to have broad interest, you may want
-        to post it to the mailing list instead of replying directly to
-        the individual who asked. Try to make your answer general enough
-        that people other than the original poster may benefit from it.
-        When you post to the list, please make sure that your answer is
-        not a duplication of a previous answer.
-      </para>
+    <para>
+      Writing a good bug report takes patience, but doing it right the
+      first time saves time both for us and for yourself. A good bug
+      report, containing a full test case for the bug, makes it very
+      likely that we will fix the bug in the next release. This section
+      helps you write your report correctly so that you don't waste your
+      time doing things that may not help us much or at all. Please read
+      this section carefully and make sure that all the information
+      described here is included in your report.
+    </para>
 
-      <para>
-        Try to summarize the essential part of the question in your
-        reply; don't feel obliged to quote the entire original message.
-      </para>
+    <para>
+      If you have no Web access, you can generate a bug report by using
+      the <command>mysqlbug</command> script described at the end of
+      this section.
+    </para>
 
-      <para>
-        Please don't post mail messages from your browser with HTML mode
-        turned on. Many users don't read mail with a browser.
-      </para>
+    <para>
+      Preferably, you should test the problem using the latest
+      production or development version of MySQL Server before posting.
+      Anyone should be able to repeat the bug by just using
+      <literal>mysql test &lt; script_file</literal> on the included
+      test case or by running the shell or Perl script that you include
+      in the bug report. Any bug that we are able to repeat has a high
+      chance of being fixed in the next MySQL release.
+    </para>
 
-    </section>
+    <para>
+      All bugs posted in the bugs database at
+      <ulink url="http://bugs.mysql.com/"/> are corrected or documented
+      in the next MySQL release. If only minor code changes are needed
+      to correct a problem, we may also post a patch that fixes the
+      problem.
+    </para>
 
-  </section>
+    <para>
+      Remember that it is possible for us to respond to a message
+      containing too much information, but not to one containing too
+      little. People often omit facts because they think they know the
+      cause of a problem and assume that some details don't matter. A
+      good principle is this: If you are in doubt about stating
+      something, state it. It is faster and less troublesome to write a
+      couple more lines in your report than to wait longer for the
+      answer if we must ask you to provide information that was missing
+      from the initial report.
+    </para>
 
-  <section id="irc">
+    <para>
+      The most common errors made in bug reports are (a) not including
+      the version number of the MySQL distribution that you use, and (b)
+      not fully describing the platform on which the MySQL server is
+      installed (including the platform type and version number). These
+      are highly relevant pieces of information, and in 99 cases out of
+      100, the bug report is useless without them. Very often we get
+      questions like, <quote>Why doesn't this work for me?</quote> Then
+      we find that the feature requested wasn't implemented in that
+      MySQL version, or that a bug described in a report has been fixed
+      in newer MySQL versions. Sometimes the error is
+      platform-dependent. In such cases, it is next to impossible for us
+      to fix anything without knowing the operating system and the
+      version number of the platform.
+    </para>
 
-    <title>&title-irc;</title>
+    <para>
+      If you compiled MySQL from source, remember also to provide
+      information about your compiler if it is related to the problem.
+      Often people find bugs in compilers and think the problem is
+      MySQL-related. Most compilers are under development all the time
+      and become better version by version. To determine whether your
+      problem depends on your compiler, we need to know what compiler
+      you use. Note that every compiling problem should be regarded as a
+      bug and reported accordingly.
+    </para>
 
-    <indexterm type="concept">
-      <primary>IRC</primary>
-    </indexterm>
+    <para>
+      It is most helpful when a good description of the problem is
+      included in the bug report. That is, give a good example of
+      everything you did that led to the problem and describe, in exact
+      detail, the problem itself. The best reports are those that
+      include a full example showing how to reproduce the bug or
+      problem. See <xref linkend="reproduceable-test-case"/>.
+    </para>
 
-    <indexterm type="concept">
-      <primary>Internet Relay Chat</primary>
-    </indexterm>
+    <para>
+      If a program produces an error message, it is very important to
+      include the message in your report. If we try to search for
+      something from the archives, it is better that the error message
+      reported exactly matches the one that the program produces. (Even
+      the lettercase should be observed.) It is best to copy and paste
+      the entire error message into your report. You should never try to
+      reproduce the message from memory.
+    </para>
 
     <para>
-      In addition to the various MySQL mailing lists, you can find
-      experienced community people on <literal>IRC</literal>
-      (<literal>Internet Relay Chat</literal>). These are the best
-      networks/channels currently known to us:
+      If you have a problem with Connector/ODBC (MyODBC), please try to
+      generate a trace file and send it with your report. See
+      <xref linkend="myodbc-bug-report"/>.
     </para>
 
+    <para>
+      If your report includes long query output lines from test cases
+      that you run with the <command>mysql</command> command-line tool,
+      you can make the output more readable by using the
+      <option>--vertical</option> option or the <literal>\G</literal>
+      statement terminator. The <literal>EXPLAIN SELECT</literal>
+      example later in this section demonstrates the use of
+      <literal>\G</literal>.
+    </para>
+
+    <para>
+      Please include the following information in your report:
+    </para>
+
     <itemizedlist>
 
       <listitem>
         <para>
-          <emphasis role="bold">freenode</emphasis> (see
-          <ulink url="http://www.freenode.net/"/> for servers)
+          The version number of the MySQL distribution you are using
+          (for example, MySQL 5.0.19). You can find out which version
+          you are running by executing <command>mysqladmin
+          version</command>. The <command>mysqladmin</command> program
+          can be found in the <filename>bin</filename> directory under
+          your MySQL installation directory.
         </para>
+      </listitem>
 
-        <itemizedlist>
+      <listitem>
+        <para>
+          The manufacturer and model of the machine on which you
+          experience the problem.
+        </para>
+      </listitem>
 
-          <listitem>
-            <para>
-              <literal>#mysql</literal> Primarily MySQL questions, but
-              other database and general SQL questions are welcome.
-              Questions about PHP, Perl or C in combination with MySQL
-              are also common.
-            </para>
-          </listitem>
+      <listitem>
+        <para>
+          The operating system name and version. If you work with
+          Windows, you can usually get the name and version number by
+          double-clicking your My Computer icon and pulling down the
+          <quote>Help/About Windows</quote> menu. For most Unix-like
+          operating systems, you can get this information by executing
+          the command <literal>uname -a</literal>.
+        </para>
+      </listitem>
 
-        </itemizedlist>
+      <listitem>
+        <para>
+          Sometimes the amount of memory (real and virtual) is relevant.
+          If in doubt, include these values.
+        </para>
       </listitem>
 
-    </itemizedlist>
+      <listitem>
+        <para>
+          If you are using a source distribution of the MySQL software,
+          include the name and version number of the compiler that you
+          used. If you have a binary distribution, include the
+          distribution name.
+        </para>
+      </listitem>
 
-    <remark role="todo">
-      Update following paragraph, as the win32 version is no longer
-      free.
-    </remark>
+      <listitem>
+        <para>
+          If the problem occurs during compilation, include the exact
+          error messages and also a few lines of context around the
+          offending code in the file where the error occurs.
+        </para>
+      </listitem>
 
-    <para>
-      If you are looking for IRC client software to connect to an IRC
-      network, take a look at <literal>xChat</literal>
-      (<ulink url="http://www.xchat.org/"/>). X-Chat (GPL licensed) is
-      available for Unix as well as for Windows platforms (a free
-      Windows build of X-Chat is available at
-      <ulink url="http://www.silverex.org/download/"/>).
-    </para>
+      <listitem>
+        <para>
+          If <command>mysqld</command> died, you should also report the
+          statement that crashed <command>mysqld</command>. You can
+          usually get this information by running
+          <command>mysqld</command> with query logging enabled, and then
+          looking in the log after <command>mysqld</command> crashes See
+          <xref linkend="using-log-files"/>.
+        </para>
+      </listitem>
 
-  </section>
+      <listitem>
+        <para>
+          If a database table is related to the problem, include the
+          output from <command>mysqldump --no-data
+          <replaceable>db_name</replaceable>
+          <replaceable>tbl_name</replaceable> &gt;
+          <replaceable>file_name</replaceable></command>. This is very
+          easy to do and is a powerful way to get information about any
+          table in a database. The <command>mysqldump</command> command
+          generates a file that you can upload to be attached to the bug
+          report. The information helps us create a situation matching
+          the one that you have experienced.
+        </para>
+      </listitem>
 
-  <section id="forums">
+      <listitem>
+        <para>
+          For performance-related bugs or problems with
+          <literal>SELECT</literal> statements, you should always
+          include the output of <literal>EXPLAIN SELECT ...</literal>,
+          and at least the number of rows that the
+          <literal>SELECT</literal> statement produces. You should also
+          include the output from <literal>SHOW CREATE TABLE
+          <replaceable>tbl_name</replaceable></literal> for each table
+          that is involved. The more information you provide about your
+          situation, the more likely it is that someone can help you.
+        </para>
 
-    <title>&title-forums;</title>
+        <para>
+          The following is an example of a very good bug report. The
+          statements are run using the <command>mysql</command>
+          command-line tool. Note the use of the <literal>\G</literal>
+          statement terminator for statements that would otherwise
+          provide very long output lines that are difficult to read.
+        </para>
 
-    <indexterm type="concept">
-      <primary>Forums</primary>
-    </indexterm>
+<programlisting>
+mysql&gt; <userinput>SHOW VARIABLES;</userinput>
+mysql&gt; <userinput>SHOW COLUMNS FROM ...\G</userinput>
+       <replaceable>&lt;output from SHOW COLUMNS&gt;</replaceable>
+mysql&gt; <userinput>EXPLAIN SELECT ...\G</userinput>
+       <replaceable>&lt;output from EXPLAIN&gt;</replaceable>
+mysql&gt; <userinput>FLUSH STATUS;</userinput>
+mysql&gt; <userinput>SELECT ...;</userinput>
+       <replaceable>&lt;A short version of the output from SELECT,
+       including the time taken to run the query&gt;</replaceable>
+mysql&gt; <userinput>SHOW STATUS;</userinput>
+       <replaceable>&lt;output from SHOW STATUS&gt;</replaceable>
+</programlisting>
+      </listitem>
 
-    <para>
-      The latest community support resource are the forums at
-      <ulink url="http://forums.mysql.com"/>.
-    </para>
+      <listitem>
+        <para>
+          If a bug or problem occurs while running
+          <command>mysqld</command>, try to provide an input script that
+          reproduces the anomaly. This script should include any
+          necessary source files. The more closely the script can
+          reproduce your situation, the better. If you can make a
+          reproducible test case, you should upload it to be attached to
+          the bug report.
+        </para>
 
-    <para>
-      There are a variety of forums available, grouped in the following
-      general categories:
-    </para>
+        <para>
+          If you can't provide a script, you should at least include the
+          output from <command>mysqladmin variables extended-status
+          processlist</command> in your report to provide some
+          information on how your system is performing.
+        </para>
+      </listitem>
 
-    <itemizedlist>
+      <listitem>
+        <para>
+          If you can't produce a test case with only a few rows, or if
+          the test table is too big to be included in the bug report
+          (more than 10 rows), you should dump your tables using
+          <command>mysqldump</command> and create a
+          <filename>README</filename> file that describes your problem.
+          Create a compressed archive of your files using
+          <command>tar</command> and <command>gzip</command> or
+          <command>zip</command>, and use FTP to transfer the archive to
+          <ulink url="ftp://ftp.mysql.com/pub/mysql/upload/"/>. Then
+          enter the problem into our bugs database at
+          <ulink url="http://bugs.mysql.com/"/>.
+        </para>
+      </listitem>
 
       <listitem>
         <para>
-          Migration
+          If you believe that the MySQL server produces a strange result
+          from a statement, include not only the result, but also your
+          opinion of what the result should be, and an explanation
+          describing the basis for your opinion.
         </para>
       </listitem>
 
       <listitem>
         <para>
-          MySQL Usage
+          When you provide an example of the problem, it's better to use
+          the table names, variable names, and so forth that exist in
+          your actual situation than to come up with new names. The
+          problem could be related to the name of a table or variable.
+          These cases are rare, perhaps, but it is better to be safe
+          than sorry. After all, it should be easier for you to provide
+          an example that uses your actual situation, and it is by all
+          means better for us. If you have data that you don't want to
+          be visible to others in the bug report, you can use FTP to
+          transfer it to
+          <ulink url="ftp://ftp.mysql.com/pub/mysql/upload/"/>. If the
+          information is really top secret and you don't want to show it
+          even to us, then go ahead and provide an example using other
+          names, but please regard this as the last choice.
         </para>
       </listitem>
 
       <listitem>
         <para>
-          MySQL Connectors
+          Include all the options given to the relevant programs, if
+          possible. For example, indicate the options that you use when
+          you start the <command>mysqld</command> server, as well as the
+          options that you use to run any MySQL client programs. The
+          options to programs such as <command>mysqld</command> and
+          <command>mysql</command>, and to the
+          <command>configure</command> script, are often key to
+          resolving problems and are very relevant. It is never a bad
+          idea to include them. If you problem includes a programm
+          written in a language such as Perl or PHP, please include the
+          language processor's version number, as well as the version
+          for any modules that the program uses. For example, if you
+          have a Perl script that uses the <literal>DBI</literal> and
+          <literal>DBD::mysql</literal> modules, include the version for
+          Perl, <literal>DBI</literal>, and
+          <literal>DBD::mysql</literal>.
         </para>
       </listitem>
 
       <listitem>
         <para>
-          Programming Languages
+          If your question is related to the privilege system, please
+          include the output of <command>mysqlaccess</command>, the
+          output of <command>mysqladmin reload</command>, and all the
+          error messages you get when trying to connect. When you test
+          your privileges, you should first run
+          <command>mysqlaccess</command>. After this, execute
+          <command>mysqladmin reload version</command> and try to
+          connect with the program that gives you trouble.
+          <command>mysqlaccess</command> can be found in the
+          <filename>bin</filename> directory under your MySQL
+          installation directory.
         </para>
       </listitem>
 
       <listitem>
         <para>
-          Tools
+          If you have a patch for a bug, do include it. But don't assume
+          that the patch is all we need, or that we can use it, if you
+          don't provide some necessary information such as test cases
+          showing the bug that your patch fixes. We might find problems
+          with your patch or we might not understand it at all. If so,
+          we can't use it.
         </para>
+
+        <para>
+          If we can't verify exactly what the purpose of the patch is,
+          we won't use it. Test cases help us here. Show that the patch
+          handles all the situations that may occur. If we find a
+          borderline case (even a rare one) where the patch won't work,
+          it may be useless.
+        </para>
       </listitem>
 
       <listitem>
         <para>
-          3rd-Party Applications
+          Guesses about what the bug is, why it occurs, or what it
+          depends on are usually wrong. Even the MySQL team can't guess
+          such things without first using a debugger to determine the
+          real cause of a bug.
         </para>
       </listitem>
 
       <listitem>
         <para>
-          Storage Engines
+          Indicate in your bug report that you have checked the
+          reference manual and mail archive so that others know you have
+          tried to solve the problem yourself.
         </para>
       </listitem>
 
       <listitem>
         <para>
-          MySQL Technology
+          If your problem is that your data appears corrupt or you get
+          errors when you access a particular table, you should first
+          check your tables and then try to repair them with
+          <literal>CHECK TABLE</literal> and <literal>REPAIR
+          TABLE</literal> or with <command>myisamchk</command>. See
+          <xref linkend="database-administration"/>.
         </para>
+
+        <para>
+          If you are running Windows, please verify the value of
+          <literal>lower_case_table_names</literal> using the
+          <literal>SHOW VARIABLES LIKE
+          'lower_case_table_names'</literal> command.
+        </para>
       </listitem>
 
       <listitem>
         <para>
-          SQL Standards
+          If you often get corrupted tables, you should try to find out
+          when and why this happens. In this case, the error log in the
+          MySQL data directory may contain some information about what
+          happened. (This is the file with the <filename>.err</filename>
+          suffix in the name.) See <xref linkend="error-log"/>. Please
+          include any relevant information from this file in your bug
+          report. Normally <command>mysqld</command> should
+          <emphasis>never</emphasis> crash a table if nothing killed it
+          in the middle of an update. If you can find the cause of
+          <command>mysqld</command> dying, it's much easier for us to
+          provide you with a fix for the problem. See
+          <xref linkend="what-is-crashing"/>.
         </para>
       </listitem>
 
       <listitem>
         <para>
-          Business
+          If possible, download and install the most recent version of
+          MySQL Server and check whether it solves your problem. All
+          versions of the MySQL software are thoroughly tested and
+          should work without problems. We believe in making everything
+          as backward-compatible as possible, and you should be able to
+          switch MySQL versions without difficulty. See
+          <xref linkend="which-version"/>.
         </para>
       </listitem>
 
     </itemizedlist>
 
+    <indexterm type="concept">
+      <primary>technical support</primary>
+      <secondary>mailing address</secondary>
+    </indexterm>
+
+    <indexterm type="concept">
+      <primary>support</primary>
+      <secondary>mailing address</secondary>
+    </indexterm>
+
+    <indexterm type="concept">
+      <primary>customer support</primary>
+      <secondary>mailing address</secondary>
+    </indexterm>
+
+    <indexterm type="concept">
+      <primary>mailing address</primary>
+      <secondary>for customer support</secondary>
+    </indexterm>
+
+    <para>
+      If you are a support customer, please cross-post the bug report to
+      <email>mysql-support@stripped</email> for higher-priority
+      treatment, as well as to the appropriate mailing list to see
+      whether someone else has experienced (and perhaps solved) the
+      problem.
+    </para>
+
+    <para>
+      If you have no Web access and cannot report a bug by visiting
+      <ulink url="http://bugs.mysql.com/"/>, you can use the
+      <command>mysqlbug</command> script to generate a bug report (or a
+      report about any problem). <command>mysqlbug</command> can be
+      found in the <filename>scripts</filename> directory (source
+      distribution) and in the <filename>bin</filename> directory under
+      your MySQL installation directory (binary distribution). If you
+      are unable to use <command>mysqlbug</command> (for example, if you
+      are running on Windows), it is still vital that you include all
+      the necessary information noted in this section (most importantly,
+      a description of the operating system and the MySQL version).
+    </para>
+
+    <para>
+      The <command>mysqlbug</command> script helps you generate a report
+      by determining much of the following information automatically,
+      but if something important is missing, please include it with your
+      message.
+    </para>
+
   </section>
 
 </section>

Modified: trunk/refman-common/titles.en.ent
===================================================================
--- trunk/refman-common/titles.en.ent	2006-01-03 20:38:12 UTC (rev 654)
+++ trunk/refman-common/titles.en.ent	2006-01-03 20:39:20 UTC (rev 655)
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8"?>
+<?xml version="0.0" encoding="utf-8"?>
 <!--
   This file contains entities for which the value is the same for every
   version of the manual.  Entities for which the value differs per
@@ -43,14 +43,12 @@
 <!ENTITY title-ansi-diff-triggers "Stored Procedures and Triggers">
 <!ENTITY title-ansi-diff-views "Views">
 <!ENTITY title-ansi-mode "Running MySQL in ANSI Mode">
-<!ENTITY title-answering-questions "Guidelines for Answering Questions on the Mailing List">
 <!ENTITY title-any-in-some-subqueries "Subqueries with <literal>ANY</literal>, <literal>IN</literal>, and <literal>SOME</literal>">
 <!ENTITY title-apache "Using MySQL with Apache">
 <!ENTITY title-apis "APIs and Libraries">
 <!ENTITY title-application-password-use "Implications of Password Hashing Changes for Application Programs">
 <!ENTITY title-archive-storage-engine "The <literal>ARCHIVE</literal> Storage Engine">
 <!ENTITY title-arithmetic-functions "Arithmetic Operators">
-<!ENTITY title-asking-questions "Asking Questions or Reporting Bugs">
 <!ENTITY title-asp "ASP and MySQL with MyODBC">
 <!ENTITY title-automatic-start "Starting and Stopping MySQL Automatically">
 <!ENTITY title-backing-up "Backing Up and Recovering an <literal>InnoDB</literal> Database">
@@ -193,7 +191,7 @@
 <!ENTITY title-cj-jdbc-reference "JDBC Reference">
 <!ENTITY title-cj-jdbc-upgrading-issues "JDBC-Specific Issues When Upgrading to MySQL Server 4.1 or Newer">
 <!ENTITY title-cj-replication-connection "Using Master/Slave Replication with ReplicationConnection">
-<!ENTITY title-cj-reporting-bugs "How to Report Bugs or Problems">
+<!ENTITY title-cj-reporting-bugs "How to Report Connector/J Bugs or Problems">
 <!ENTITY title-cj-retrieve-autoinc "Retrieving AUTO_INCREMENT Column Values">
 <!ENTITY title-cj-retrieve-multiresults "Retrieving Multiple ResultSets from a Statement or CallableStatement">
 <!ENTITY title-cj-spring-config "Using Connector/J with Spring">
@@ -464,6 +462,7 @@
 <!ENTITY title-information-functions "Information Functions">
 <!ENTITY title-information-schema "The <literal>INFORMATION_SCHEMA</literal> Database">
 <!ENTITY title-information-schema-tables "<literal>INFORMATION_SCHEMA</literal> Tables">
+<!ENTITY title-information-sources "MySQL Information Sources">
 <!ENTITY title-innodb "The <literal>InnoDB</literal> Storage Engine">
 <!ENTITY title-innodb-adaptive-hash "Adaptive Hash Indexes">
 <!ENTITY title-innodb-and-autocommit "<literal>InnoDB</literal> and <literal>AUTOCOMMIT</literal>">
@@ -577,7 +576,7 @@
 <!ENTITY title-introduction "General Information">
 <!ENTITY title-introduction-to-odbc "Introduction to ODBC">
 <!ENTITY title-invoking-programs "Invoking MySQL Programs">
-<!ENTITY title-irc "MySQL Community Support on IRC (Internet Relay Chat)">
+<!ENTITY title-irc "MySQL Community Support on Internet Relay Chat (IRC)">
 <!ENTITY title-is-null-optimization "How MySQL Optimizes <literal>IS NULL</literal>">
 <!ENTITY title-isam-storage-engine "The <literal>ISAM</literal> Storage Engine">
 <!ENTITY title-isamchk-for-manpage "ISAM table-maintenance utility">
@@ -638,7 +637,8 @@
 <!ENTITY title-mac-os-x-10-x "Mac OS X 10.x (Darwin)">
 <!ENTITY title-mac-os-x-installation "Installing MySQL on Mac OS X">
 <!ENTITY title-mac-os-x-server "Mac OS X Server 1.2 (Rhapsody)">
-<!ENTITY title-mailing-list "The MySQL Mailing Lists">
+<!ENTITY title-mailing-list-use "Guidelines for Using the Mailing Lists">
+<!ENTITY title-mailing-lists "MySQL Mailing Lists">
 <!ENTITY title-maintenance-schedule "Setting Up a Table Maintenance Schedule">
 <!ENTITY title-making-trace-files "Creating Trace Files">
 <!ENTITY title-manual-conventions "Conventions Used in This Manual">
@@ -825,16 +825,16 @@
 <!ENTITY title-mysql-cluster-quick "Quick Test Setup of MySQL Cluster">
 <!ENTITY title-mysql-cluster-replication "MySQL Cluster Replication">
 <!ENTITY title-mysql-cluster-replication-abbreviations "Abbreviations and Symbols">
+<!ENTITY title-mysql-cluster-replication-auto-sync "Automating Synchronization of the Slave to the Master binlog">
+<!ENTITY title-mysql-cluster-replication-backups "MySQL Cluster Backups With Replication">
+<!ENTITY title-mysql-cluster-replication-failover "Implementing Failover with MySQL Cluster">
 <!ENTITY title-mysql-cluster-replication-general "Assumptions and General Requirements">
 <!ENTITY title-mysql-cluster-replication-issues "Known Issues">
-<!ENTITY title-mysql-cluster-replication-schema "Replication Schema and Tables">
 <!ENTITY title-mysql-cluster-replication-preparation "Preparing the Cluster for Replication">
+<!ENTITY title-mysql-cluster-replication-schema "Replication Schema and Tables">
+<!ENTITY title-mysql-cluster-replication-schema-discovery "Initiating Discovery of Schema Changes">
 <!ENTITY title-mysql-cluster-replication-starting "Starting Replication (Single Replication Channel)">
 <!ENTITY title-mysql-cluster-replication-two-channels "Using Two Replication Channels">
-<!ENTITY title-mysql-cluster-replication-failover "Implementing Failover with MySQL Cluster">
-<!ENTITY title-mysql-cluster-replication-backups "MySQL Cluster Backups With Replication">
-<!ENTITY title-mysql-cluster-replication-auto-sync "Automating Synchronization of the Slave to the Master binlog">
-<!ENTITY title-mysql-cluster-replication-schema-discovery "Initiating Discovery of Schema Changes">
 <!ENTITY title-mysql-cluster-restore "How to Restore a Cluster Backup">
 <!ENTITY title-mysql-cluster-roadmap "MySQL Cluster Development Roadmap">
 <!ENTITY title-mysql-cluster-sci-definition "MySQL Cluster SCI Transport Connections">
@@ -896,7 +896,6 @@
 <!ENTITY title-mysql-hex-string "<literal>mysql_hex_string()</literal>">
 <!ENTITY title-mysql-indexes "How MySQL Uses Indexes">
 <!ENTITY title-mysql-info "<literal>mysql_info()</literal>">
-<!ENTITY title-mysql-information-sources "MySQL Information Sources">
 <!ENTITY title-mysql-init "<literal>mysql_init()</literal>">
 <!ENTITY title-mysql-insert-id "<literal>mysql_insert_id()</literal>">
 <!ENTITY title-mysql-install-db "Problems Running <command>mysql_install_db</command>">
@@ -1347,10 +1346,10 @@
 <!ENTITY title-pluggable-storage-unplugging "Unplugging a Storage Engine">
 <!ENTITY title-plugin-api "The MySQL Plugin Interface">
 <!ENTITY title-plugin-api-characteristics "Characteristics of the Plugin Interface">
-<!ENTITY title-plugin-full-text-plugins "Full-Text Parser Plugins">
 <!ENTITY title-plugin-api-general "General Plugin Structures and Functions">
 <!ENTITY title-plugin-api-type-specific "Type-Specific Plugin Structures and Functions">
 <!ENTITY title-plugin-creating "Creating a Plugin Library">
+<!ENTITY title-plugin-full-text-plugins "Full-Text Parser Plugins">
 <!ENTITY title-plugin-writing "Writing Plugins">
 <!ENTITY title-point-in-time-recovery "Point-in-Time Recovery">
 <!ENTITY title-point-in-time-recovery-positions "Specifying Positions for Recovery">
@@ -1397,7 +1396,6 @@
 <!ENTITY title-query-results "What Results You Can Get from a Query">
 <!ENTITY title-query-speed "Optimizing <literal>SELECT</literal> Statements and Other Queries">
 <!ENTITY title-query-timeout "How to Set the QueryTimeout Value for ODBC Connections?">
-<!ENTITY title-questions "MySQL Mailing Lists">
 <!ENTITY title-quick-install "Source Installation Overview">
 <!ENTITY title-quick-standard-installation "Standard MySQL Installation Using a Binary Distribution">
 <!ENTITY title-range-access-multi-part "Range Access Method for Multiple-Part Indexes">
@@ -1421,7 +1419,7 @@
 <!ENTITY title-replace-for-manual "A String-Replacement Utility">
 <!ENTITY title-replication "Replication in MySQL">
 <!ENTITY title-replication-auto-increment "Auto-Increment in Multi-Master Replication">
-<!ENTITY title-replication-bugs "Reporting Replication Bugs">
+<!ENTITY title-replication-bugs "How to Report Replication Bugs or Problems">
 <!ENTITY title-replication-compatibility "Replication Compatibility Between MySQL Versions">
 <!ENTITY title-replication-faq "Replication FAQ">
 <!ENTITY title-replication-features "Replication Features and Known Problems">
@@ -1439,7 +1437,7 @@
 <!ENTITY title-replication-upgrade "Upgrading a Replication Setup">
 <!ENTITY title-replication-upgrade-4-0 "Upgrading Replication to 4.0 or 4.1">
 <!ENTITY title-replication-upgrade-5-0 "Upgrading Replication to 5.0">
-<!ENTITY title-reporting-mysqltest-bugs "Reporting Bugs in the MySQL Test Suite">
+<!ENTITY title-reporting-mysqltest-bugs "How to Report Bugs in the MySQL Test Suite">
 <!ENTITY title-reproduceable-test-case "Making a Test Case If You Experience Table Corruption">
 <!ENTITY title-request-access "Access Control, Stage 2: Request Verification">
 <!ENTITY title-reserved-words "Treatment of Reserved Words in MySQL">

Thread
svn commit - mysqldoc@docsrva: r655 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-commonpaul3 Jan