bk commit - mysqldoc@docsrva tree (Mike.Hillyer:1.2794)

[mhillyer]

Below is the list of changes that have just been committed into a local
mysqldoc repository of root. When root 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.2794 05/06/15 16:06:32 Mike.Hillyer@stripped +1 -0
  Merge bk://mysqldoc@stripped
  into www.openwin.org:/home/mysqldoc/mysqldoc

  Docs/manual.texi
    1.3004 05/06/15 16:06:30 Mike.Hillyer@stripped +0 -0
    Auto merged

# 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:	Mike.Hillyer
# Host:	www.openwin.org
# Root:	/home/mysqldoc/mysqldoc/RESYNC

--- 1.3003/Docs/manual.texi	2005-06-15 12:34:14 -06:00
+++ 1.3004/Docs/manual.texi	2005-06-15 16:06:30 -06:00
@@ -6518,6 +6518,10 @@
 and use @code{glibc}.
 To obtain RPM packages, see @ref{Getting MySQL}.
 
+MySQL AB does provide some platform-specific RPMs; the difference between a platform-specific
+RPM and a generic RPM is that the platform-specific RPMs are built on the targeted platform
+and are linked dynamically whereas the generic RPM is linked statically with LinuxThreads.
+
 @strong{Note}: RPM distributions of MySQL often are provided by other
 vendors.  Be aware that they may differ in features and capabilities from
 those built by MySQL AB, and that the instructions in this manual do not
@@ -45029,9 +45033,9 @@
 @ss{} = ss
 @end example
 
-Language-specific collations for the @code{utf8} character set are
-implemented only if the default order provided by @code{utf8_unicode_ci}
-does not work for a language well. For example, @code{utf8_unicode_ci}
+Language-specific collations for the utf8 character set are implemented
+only if the ordering with utf8_unicode_ci does not work well for
+a language. For example, @code{utf8_unicode_ci}
 works fine for German and French, so there is no need to create special
 @code{utf8} collations for these two languages.