bk commit - mysqldoc@docsrva tree (stefan:1.2825)

[stefan]

Below is the list of changes that have just been committed into a local
mysqldoc repository of stefan. When stefan does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html

ChangeSet
  1.2825 05/06/20 10:26:50 stefan@stripped +3 -0
  functions.xml:
    Added a note on FULLTEXT restrictions with
    Chinese and alike, provide link to fulltext
    search page where that's explained in detail
    Sync with refman

  refman/functions.xml
    1.3 05/06/20 10:25:57 stefan@stripped +8 -0
    Added a note on FULLTEXT restrictions with
    Chinese and alike, provide link to fulltext
    search page where that's explained in detail

  refman-4.1/functions.xml
    1.3 05/06/20 10:25:46 stefan@stripped +8 -0
    Sync with refman

  refman-5.0/functions.xml
    1.3 05/06/20 10:25:31 stefan@stripped +8 -0
    Sync with refman

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	stefan
# Host:	apollon.site
# Root:	/home/stefan/bk/mysqldoc

--- 1.2/refman-4.1/functions.xml	2005-06-19 21:54:33 +02:00
+++ 1.3/refman-4.1/functions.xml	2005-06-20 10:25:46 +02:00
@@ -9887,6 +9887,14 @@
     </para></listitem>
 
     <listitem><para>
+     Languages such as Chinese, Japanese, and so forth don't have word
+     delimiters. You should be aware that the <literal>FULLTEXT</literal> parser
+     cannot determine where a word starts and where it ends in these languages.
+     Implications and workarounds are described in
+     <xref linkend="fulltext-search"/>.
+    </para></listitem>
+
+    <listitem><para>
      As of MySQL 4.1, the use of multiple character sets within a single
      table is supported. However, all columns in a
      <literal>FULLTEXT</literal> index must have the same character set

--- 1.2/refman-5.0/functions.xml	2005-06-19 21:54:16 +02:00
+++ 1.3/refman-5.0/functions.xml	2005-06-20 10:25:31 +02:00
@@ -9887,6 +9887,14 @@
     </para></listitem>
 
     <listitem><para>
+     Languages such as Chinese, Japanese, and so forth don't have word
+     delimiters. You should be aware that the <literal>FULLTEXT</literal> parser
+     cannot determine where a word starts and where it ends in these languages.
+     Implications and workarounds are described in
+     <xref linkend="fulltext-search"/>.
+    </para></listitem>
+
+    <listitem><para>
      As of MySQL 4.1, the use of multiple character sets within a single
      table is supported. However, all columns in a
      <literal>FULLTEXT</literal> index must have the same character set

--- 1.2/refman/functions.xml	2005-06-19 21:54:45 +02:00
+++ 1.3/refman/functions.xml	2005-06-20 10:25:57 +02:00
@@ -9887,6 +9887,14 @@
     </para></listitem>
 
     <listitem><para>
+     Languages such as Chinese, Japanese, and so forth don't have word
+     delimiters. You should be aware that the <literal>FULLTEXT</literal> parser
+     cannot determine where a word starts and where it ends in these languages.
+     Implications and workarounds are described in
+     <xref linkend="fulltext-search"/>.
+    </para></listitem>
+
+    <listitem><para>
      As of MySQL 4.1, the use of multiple character sets within a single
      table is supported. However, all columns in a
      <literal>FULLTEXT</literal> index must have the same character set