Author: shinz
Date: 2005-12-07 16:06:14 +0100 (Wed, 07 Dec 2005)
New Revision: 511
Log:
Final edits to annotations about MySQL's version of latin1
Modified:
trunk/refman-4.1/charset.xml
trunk/refman-5.0/charset.xml
trunk/refman-5.1/charset.xml
Modified: trunk/refman-4.1/charset.xml
===================================================================
--- trunk/refman-4.1/charset.xml 2005-12-07 14:51:22 UTC (rev 510)
+++ trunk/refman-4.1/charset.xml 2005-12-07 15:06:14 UTC (rev 511)
@@ -3485,14 +3485,24 @@
</itemizedlist>
<para>
- <emphasis>Annotations regarding <literal>latin1</literal>:</emphasis>
- MySQL's <literal>latin1</literal> is the same as the Windows
- <literal>cp1252</literal> character set. This means it
- is the same as the official IANA (Internet Assigned Numbers Authority)
- <literal>latin1</literal>, but IANA <literal>latin1</literal> treats
- the code points between 0x80 and 0x9f as <quote>unused</quote>, while
- <literal>cp1252</literal>, and therefore MySQL's <literal>latin1</literal>,
- assign characters for those positions. For example, 0x80 is the Euro sign.
+ <emphasis>Annotations regarding
+ <literal>latin1</literal>:</emphasis> MySQL's
+ <literal>latin1</literal> is the same as the Windows
+ <literal>cp1252</literal> character set. This means it is the
+ same as the official <literal>ISO 8859-1</literal> or
+ IANA (Internet Assigned Numbers Authority)
+ <literal>latin1</literal>, but IANA <literal>latin1</literal>
+ treats the code points between 0x80 and 0x9f as
+ <quote>undefined</quote>, while <literal>cp1252</literal>, and
+ therefore MySQL's <literal>latin1</literal>, assign characters
+ for those positions. For example, 0x80 is the Euro sign.
+ For the <quote>undefined</quote> entries in
+ <literal>cp1252</literal>, MySQL translates
+ <literal>0x81</literal> to Unicode <literal>0x0081</literal>,
+ <literal>0x8d</literal> to <literal>0x008d</literal>,
+ <literal>0x8f</literal> to <literal>0x008f</literal>,
+ <literal>0x90</literal> to <literal>0x0090</literal>,
+ and <literal>0x9d</literal> to <literal>0x009d</literal>.
</para>
</section>
Modified: trunk/refman-5.0/charset.xml
===================================================================
--- trunk/refman-5.0/charset.xml 2005-12-07 14:51:22 UTC (rev 510)
+++ trunk/refman-5.0/charset.xml 2005-12-07 15:06:14 UTC (rev 511)
@@ -2810,14 +2810,24 @@
</itemizedlist>
<para>
- <emphasis>Annotations regarding <literal>latin1</literal>:</emphasis>
- MySQL's <literal>latin1</literal> is the same as the Windows
- <literal>cp1252</literal> character set. This means it
- is the same as the official IANA (Internet Assigned Numbers Authority)
- <literal>latin1</literal>, but IANA <literal>latin1</literal> treats
- the code points between 0x80 and 0x9f as <quote>unused</quote>, while
- <literal>cp1252</literal>, and therefore MySQL's <literal>latin1</literal>,
- assign characters for those positions. For example, 0x80 is the Euro sign.
+ <emphasis>Annotations regarding
+ <literal>latin1</literal>:</emphasis> MySQL's
+ <literal>latin1</literal> is the same as the Windows
+ <literal>cp1252</literal> character set. This means it is the
+ same as the official <literal>ISO 8859-1</literal> or
+ IANA (Internet Assigned Numbers Authority)
+ <literal>latin1</literal>, but IANA <literal>latin1</literal>
+ treats the code points between 0x80 and 0x9f as
+ <quote>undefined</quote>, while <literal>cp1252</literal>, and
+ therefore MySQL's <literal>latin1</literal>, assign characters
+ for those positions. For example, 0x80 is the Euro sign.
+ For the <quote>undefined</quote> entries in
+ <literal>cp1252</literal>, MySQL translates
+ <literal>0x81</literal> to Unicode <literal>0x0081</literal>,
+ <literal>0x8d</literal> to <literal>0x008d</literal>,
+ <literal>0x8f</literal> to <literal>0x008f</literal>,
+ <literal>0x90</literal> to <literal>0x0090</literal>,
+ and <literal>0x9d</literal> to <literal>0x009d</literal>.
</para>
</section>
Modified: trunk/refman-5.1/charset.xml
===================================================================
--- trunk/refman-5.1/charset.xml 2005-12-07 14:51:22 UTC (rev 510)
+++ trunk/refman-5.1/charset.xml 2005-12-07 15:06:14 UTC (rev 511)
@@ -2806,12 +2806,20 @@
<literal>latin1</literal>:</emphasis> MySQL's
<literal>latin1</literal> is the same as the Windows
<literal>cp1252</literal> character set. This means it is the
- same as the official IANA (Internet Assigned Numbers Authority)
+ same as the official <literal>ISO 8859-1</literal> or
+ IANA (Internet Assigned Numbers Authority)
<literal>latin1</literal>, but IANA <literal>latin1</literal>
treats the code points between 0x80 and 0x9f as
- <quote>unused</quote>, while <literal>cp1252</literal>, and
+ <quote>undefined</quote>, while <literal>cp1252</literal>, and
therefore MySQL's <literal>latin1</literal>, assign characters
for those positions. For example, 0x80 is the Euro sign.
+ For the <quote>undefined</quote> entries in
+ <literal>cp1252</literal>, MySQL translates
+ <literal>0x81</literal> to Unicode <literal>0x0081</literal>,
+ <literal>0x8d</literal> to <literal>0x008d</literal>,
+ <literal>0x8f</literal> to <literal>0x008f</literal>,
+ <literal>0x90</literal> to <literal>0x0090</literal>,
+ and <literal>0x9d</literal> to <literal>0x009d</literal>.
</para>
</section>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r511 - in trunk: refman-4.1 refman-5.0 refman-5.1 | stefan | 7 Dec |
