From: paul
Date: December 17 2005 7:29pm
Subject: svn commit - mysqldoc@docsrva: r583 - in trunk: . refman-5.1
List-Archive: http://lists.mysql.com/commits/213
Message-Id: <200512171929.jBHJTmJB031064@docsrva.mysql.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Author: paul
Date: 2005-12-17 20:29:48 +0100 (Sat, 17 Dec 2005)
New Revision: 583

Log:
 r4875@frost:  paul | 2005-12-17 13:29:31 -0600
 Incorporate Serg comments/fixes.


Modified:
   trunk/
   trunk/refman-5.1/extending-mysql.xml


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

Modified: trunk/refman-5.1/extending-mysql.xml
===================================================================
--- trunk/refman-5.1/extending-mysql.xml	2005-12-17 18:52:53 UTC (rev 582)
+++ trunk/refman-5.1/extending-mysql.xml	2005-12-17 19:29:48 UTC (rev 583)
@@ -1281,10 +1281,11 @@
           version number
           (<literal>MYSQL_FTPARSER_INTERFACE_VERSION</literal> for
           full-text parser plugins) and contains pointers to three
-          functions. Each each of these functions should point to a
-          function or be set to 0 if the function is not needed.
-          Normally, the <literal>parse</literal> member should be
-          non-zero or there is little reason for the plugin to exist.
+          functions. The <literal>init</literal> and
+          <literal>deinit</literal> members should point to a function
+          or be set to 0 if the function is not needed. The
+          <literal>parse</literal> member must point to the function
+          that performs the parsing.
         </para>
 
         <para>
@@ -1556,7 +1557,7 @@
                   <literal>mysql_add_word</literal> callback. To tell
                   the server what kind of token is being passed, the
                   plugin needs to fill in a
-                  <literal>MYSQL_FTPARSER_FULL_BOOLEAN_INFO</literal>
+                  <literal>MYSQL_FTPARSER_BOOLEAN_INFO</literal>
                   structure and pass a pointer to it.
                 </para>
               </listitem>
@@ -1664,7 +1665,13 @@
             <para>
               A weighting factor that determines how much a match for
               the word counts. It can be used to increase or decrease
-              the word's importance in relevance calculations.
+              the word's importance in relevance calculations. A value
+              of zero indicates no weight adjustment. Values greater
+              than or less than zero mean higher or lower weight,
+              respectively. The examples at
+              <xref linkend="fulltext-boolean"/> that use the
+              <literal>&lt;</literal> and <literal>&gt;</literal>
+              operators illustrate how weighting works.
             </para>
           </listitem>
 
@@ -1674,7 +1681,10 @@
             </para>
 
             <para>
-              The sign of the weighting factor.
+              The sign of the weighting factor. A negative value acts
+              like the <literal>~</literal> boolean-search operator,
+              which causes the word's contribution to the relevance to
+              be negative.
             </para>
           </listitem>
 
@@ -2052,7 +2062,7 @@
               only; it is not part of the plugin interface. The parser
               passes the parsing context pointer to
               <literal>add_word()</literal>, as well as a pointer to the
-              word and its length:
+              word and a length value:
             </para>
 
 <programlisting>
@@ -2073,11 +2083,11 @@
             <para>
               Compile the plugin library as a shared library and install
               it in the plugin directory. The procedure for compiling
-              shared objects vary from system to system. If the library
-              is named <literal>mypluglib</literal>, you should end up
-              with a shared object file that has a name something like
-              <filename>libmypluglib.so</filename>. The filename might
-              have a different extension on your system.
+              shared objects varies from system to system. If the
+              library is named <literal>mypluglib</literal>, you should
+              end up with a shared object file that has a name something
+              like <filename>libmypluglib.so</filename>. The filename
+              might have a different extension on your system.
             </para>
 
             <para>