Author: paul
Date: 2007-10-09 22:09:32 +0200 (Tue, 09 Oct 2007)
New Revision: 8042
Log:
r30884@polar: paul | 2007-10-09 15:08:21 -0500
Documented bugfixes:
Bug#26474: Add Sinhala script (Sri Lanka) collation to MySQL
Modified:
trunk/refman-5.2/charset.xml
trunk/refman-5.2/news-5.2.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:30857
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:25418
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:20005
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:30884
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:25418
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:20005
Modified: trunk/refman-5.2/charset.xml
===================================================================
--- trunk/refman-5.2/charset.xml 2007-10-09 19:08:57 UTC (rev 8041)
+++ trunk/refman-5.2/charset.xml 2007-10-09 20:09:32 UTC (rev 8042)
Changed blocks: 7, Lines Added: 29, Lines Deleted: 16; 4402 bytes
@@ -135,10 +135,11 @@
<para>
Suppose that we want to compare two string values,
<quote><literal>A</literal></quote> and
- <quote><literal>B</literal></quote>. The simplest way to do this is
- to look at the encodings: 0 for <quote><literal>A</literal></quote>
- and 1 for <quote><literal>B</literal></quote>. Because 0 is less
- than 1, we say <quote><literal>A</literal></quote> is less than
+ <quote><literal>B</literal></quote>. The simplest way to do this
+ is to look at the encodings: 0 for
+ <quote><literal>A</literal></quote> and 1 for
+ <quote><literal>B</literal></quote>. Because 0 is less than 1, we
+ say <quote><literal>A</literal></quote> is less than
<quote><literal>B</literal></quote>. What we've just done is apply
a collation to our character set. The collation is a set of rules
(only one rule in this case): <quote>compare the
@@ -149,8 +150,8 @@
<para>
But what if we want to say that the lowercase and uppercase
letters are equivalent? Then we would have at least two rules: (1)
- treat the lowercase letters <quote><literal>a</literal></quote> and
- <quote><literal>b</literal></quote> as equivalent to
+ treat the lowercase letters <quote><literal>a</literal></quote>
+ and <quote><literal>b</literal></quote> as equivalent to
<quote><literal>A</literal></quote> and
<quote><literal>B</literal></quote>; (2) then compare the
encodings. We call this a <firstterm>case-insensitive</firstterm>
@@ -968,8 +969,8 @@
<literal>05</literal> and <literal>5C</literal>) is a valid
multi-byte character. Hence, the first two bytes of the string
are interpreted as a single <literal>sjis</literal> character,
- and the <quote><literal>\</literal></quote> is not intrepreted as
- an escape character. The following
+ and the <quote><literal>\</literal></quote> is not intrepreted
+ as an escape character. The following
<quote><literal>n</literal></quote> (hex value
<literal>6E</literal>) is not interpreted as part of an escape
sequence. This is true even for the second string; the
@@ -3211,6 +3212,12 @@
<listitem>
<para>
+ <literal>ucs2_sinhala_ci</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>ucs2_slovak_ci</literal>
</para>
</listitem>
@@ -3347,6 +3354,12 @@
<listitem>
<para>
+ <literal>utf8_sinhala_ci</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>utf8_slovak_ci</literal>
</para>
</listitem>
@@ -3410,9 +3423,9 @@
</para>
<para>
- The <literal>ucs2_hungarian_ci</literal> and
- <literal>utf8_hungarian_ci</literal> collations were added in
- MySQL 5.1.5.
+ The <literal>ucs2_sinhala_ci</literal> and
+ <literal>utf8_sinhala_ci</literal> collations were added in
+ MySQL 5.2.6.
</para>
<indexterm>
@@ -3545,12 +3558,12 @@
modern Spanish and traditional Spanish, respectively. In both
collations, <quote><literal>ñ</literal></quote> (n-tilde) is a
separate letter between <quote><literal>n</literal></quote> and
- <quote><literal>o</literal></quote>. In addition, for traditional
- Spanish, <quote><literal>ch</literal></quote> is a separate
- letter between <quote><literal>c</literal></quote> and
+ <quote><literal>o</literal></quote>. In addition, for
+ traditional Spanish, <quote><literal>ch</literal></quote> is a
+ separate letter between <quote><literal>c</literal></quote> and
<quote><literal>d</literal></quote>, and
- <quote><literal>ll</literal></quote> is a separate letter between
- <quote><literal>l</literal></quote> and
+ <quote><literal>ll</literal></quote> is a separate letter
+ between <quote><literal>l</literal></quote> and
<quote><literal>m</literal></quote>
</para>
Modified: trunk/refman-5.2/news-5.2.xml
===================================================================
--- trunk/refman-5.2/news-5.2.xml 2007-10-09 19:08:57 UTC (rev 8041)
+++ trunk/refman-5.2/news-5.2.xml 2007-10-09 20:09:32 UTC (rev 8042)
Changed blocks: 3, Lines Added: 62, Lines Deleted: 4; 3172 bytes
@@ -30,6 +30,66 @@
<filename>refman-common</filename> directory.
</remark>
+ <section id="news-5-2-6">
+
+ <title>Changes in release 5.2.6 (Not yet released: Alpha)</title>
+
+ <para role="release-level">
+ This is a new Alpha development release, fixing recently
+ discovered bugs.
+ </para>
+
+ <para role="release-non-production">
+ <emphasis role="bold">NOTE:</emphasis> This Alpha release, as any
+ other pre-production release, should not be installed on
+ <emphasis>production</emphasis> level systems or systems with
+ critical data. It is good practice to back up your data before
+ installing any new version of software. Although MySQL has worked
+ very hard to ensure a high level of quality, protect your data by
+ making a backup as you would for any software beta release. Please
+ refer to our bug database at <ulink url="http://bugs.mysql.com/"/>
+ for more details about the individual bugs fixed in this version.
+ </para>
+
+ <para>
+ This section documents all changes and bug fixes that have been
+ applied since the last official MySQL release. If you would like
+ to receive more fine-grained and personalized <emphasis>update
+ alerts</emphasis> about fixes that are relevant to the version and
+ features you use, please consider subscribing to <emphasis>MySQL
+ Network</emphasis> (a commercial MySQL offering). For more details
+ please see <ulink url="&base-url-enterprise;advisors.html"/>.
+ </para>
+
+ <para>
+ Functionality added or changed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Sinhala collations <literal>utf8_sinhala_ci</literal> and
+ <literal>ucs2_sinhala_ci</literal> were added for the
+ <literal>utf8</literal> and <literal>ucs2</literal> character
+ sets. (Bug #26474)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+<!--
+ <para>
+ Bugs fixed:
+ </para>
+
+ <itemizedlist>
+
+ </itemizedlist>
+-->
+
+ </section>
+
<section id="news-5-2-5">
<title>Changes in release 5.2.5 (Not yet released: Alpha)</title>
@@ -58,8 +118,7 @@
alerts</emphasis> about fixes that are relevant to the version and
features you use, please consider subscribing to <emphasis>MySQL
Network</emphasis> (a commercial MySQL offering). For more details
- please see
- <ulink url="&base-url-enterprise;advisors.html"/>.
+ please see <ulink url="&base-url-enterprise;advisors.html"/>.
</para>
<para>
@@ -145,8 +204,7 @@
alerts</emphasis> about fixes that are relevant to the version and
features you use, please consider subscribing to <emphasis>MySQL
Network</emphasis> (a commercial MySQL offering). For more details
- please see
- <ulink url="&base-url-enterprise;advisors.html"/>.
+ please see <ulink url="&base-url-enterprise;advisors.html"/>.
</para>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r8042 - in trunk: . refman-5.2 | paul | 9 Oct |
