Author: paul
Date: 2007-12-13 18:23:11 +0100 (Thu, 13 Dec 2007)
New Revision: 9292
Log:
r34243@arctic: paul | 2007-12-13 10:20:58 -0600
Fix typo. (PeterG)
Modified:
trunk/it/refman-5.1/internationalization.xml
trunk/pt/refman-5.1/internationalization.xml
trunk/refman-4.1/internationalization.xml
trunk/refman-5.0/internationalization.xml
trunk/refman-5.1/internationalization.xml
trunk/refman-6.0/internationalization.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:34205
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:28105
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:22582
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:34243
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:28105
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:22582
Modified: trunk/it/refman-5.1/internationalization.xml
===================================================================
--- trunk/it/refman-5.1/internationalization.xml 2007-12-13 16:33:20 UTC (rev 9291)
+++ trunk/it/refman-5.1/internationalization.xml 2007-12-13 17:23:11 UTC (rev 9292)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1288 bytes
@@ -2841,7 +2841,7 @@
The MySQL implementation of UCS-2 stores characters in
big-endian byte order and does not use a byte order mark (BOM)
at the beginning of UCS-2 values. Other database systems might
- use little-ending byte order or a BOM, in which case conversion
+ use little-endian byte order or a BOM, in which case conversion
of UCS-2 values will need to be performed when transferring data
between those systems and MySQL.
</para>
@@ -3550,7 +3550,7 @@
The MySQL implementation of UCS-2 stores characters in
big-endian byte order and does not use a byte order mark (BOM)
at the beginning of UCS-2 values. Other database systems might
- use little-ending byte order or a BOM, in which case
+ use little-endian byte order or a BOM, in which case
conversion of UCS-2 values will need to be performed when
transferring data between those systems and MySQL.
</para>
Modified: trunk/pt/refman-5.1/internationalization.xml
===================================================================
--- trunk/pt/refman-5.1/internationalization.xml 2007-12-13 16:33:20 UTC (rev 9291)
+++ trunk/pt/refman-5.1/internationalization.xml 2007-12-13 17:23:11 UTC (rev 9292)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1288 bytes
@@ -2841,7 +2841,7 @@
The MySQL implementation of UCS-2 stores characters in
big-endian byte order and does not use a byte order mark (BOM)
at the beginning of UCS-2 values. Other database systems might
- use little-ending byte order or a BOM, in which case conversion
+ use little-endian byte order or a BOM, in which case conversion
of UCS-2 values will need to be performed when transferring data
between those systems and MySQL.
</para>
@@ -3550,7 +3550,7 @@
The MySQL implementation of UCS-2 stores characters in
big-endian byte order and does not use a byte order mark (BOM)
at the beginning of UCS-2 values. Other database systems might
- use little-ending byte order or a BOM, in which case
+ use little-endian byte order or a BOM, in which case
conversion of UCS-2 values will need to be performed when
transferring data between those systems and MySQL.
</para>
Modified: trunk/refman-4.1/internationalization.xml
===================================================================
--- trunk/refman-4.1/internationalization.xml 2007-12-13 16:33:20 UTC (rev 9291)
+++ trunk/refman-4.1/internationalization.xml 2007-12-13 17:23:11 UTC (rev 9292)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1279 bytes
@@ -2666,7 +2666,7 @@
The MySQL implementation of UCS-2 stores characters in
big-endian byte order and does not use a byte order mark (BOM)
at the beginning of UCS-2 values. Other database systems might
- use little-ending byte order or a BOM, in which case conversion
+ use little-endian byte order or a BOM, in which case conversion
of UCS-2 values will need to be performed when transferring data
between those systems and MySQL.
</para>
@@ -3613,7 +3613,7 @@
The MySQL implementation of UCS-2 stores characters in
big-endian byte order and does not use a byte order mark (BOM)
at the beginning of UCS-2 values. Other database systems might
- use little-ending byte order or a BOM, in which case
+ use little-endian byte order or a BOM, in which case
conversion of UCS-2 values will need to be performed when
transferring data between those systems and MySQL.
</para>
Modified: trunk/refman-5.0/internationalization.xml
===================================================================
--- trunk/refman-5.0/internationalization.xml 2007-12-13 16:33:20 UTC (rev 9291)
+++ trunk/refman-5.0/internationalization.xml 2007-12-13 17:23:11 UTC (rev 9292)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1279 bytes
@@ -2844,7 +2844,7 @@
The MySQL implementation of UCS-2 stores characters in
big-endian byte order and does not use a byte order mark (BOM)
at the beginning of UCS-2 values. Other database systems might
- use little-ending byte order or a BOM, in which case conversion
+ use little-endian byte order or a BOM, in which case conversion
of UCS-2 values will need to be performed when transferring data
between those systems and MySQL.
</para>
@@ -3551,7 +3551,7 @@
The MySQL implementation of UCS-2 stores characters in
big-endian byte order and does not use a byte order mark (BOM)
at the beginning of UCS-2 values. Other database systems might
- use little-ending byte order or a BOM, in which case
+ use little-endian byte order or a BOM, in which case
conversion of UCS-2 values will need to be performed when
transferring data between those systems and MySQL.
</para>
Modified: trunk/refman-5.1/internationalization.xml
===================================================================
--- trunk/refman-5.1/internationalization.xml 2007-12-13 16:33:20 UTC (rev 9291)
+++ trunk/refman-5.1/internationalization.xml 2007-12-13 17:23:11 UTC (rev 9292)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1279 bytes
@@ -2842,7 +2842,7 @@
The MySQL implementation of UCS-2 stores characters in
big-endian byte order and does not use a byte order mark (BOM)
at the beginning of UCS-2 values. Other database systems might
- use little-ending byte order or a BOM, in which case conversion
+ use little-endian byte order or a BOM, in which case conversion
of UCS-2 values will need to be performed when transferring data
between those systems and MySQL.
</para>
@@ -3549,7 +3549,7 @@
The MySQL implementation of UCS-2 stores characters in
big-endian byte order and does not use a byte order mark (BOM)
at the beginning of UCS-2 values. Other database systems might
- use little-ending byte order or a BOM, in which case
+ use little-endian byte order or a BOM, in which case
conversion of UCS-2 values will need to be performed when
transferring data between those systems and MySQL.
</para>
Modified: trunk/refman-6.0/internationalization.xml
===================================================================
--- trunk/refman-6.0/internationalization.xml 2007-12-13 16:33:20 UTC (rev 9291)
+++ trunk/refman-6.0/internationalization.xml 2007-12-13 17:23:11 UTC (rev 9292)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1279 bytes
@@ -2843,7 +2843,7 @@
The MySQL implementation of UCS-2 stores characters in
big-endian byte order and does not use a byte order mark (BOM)
at the beginning of UCS-2 values. Other database systems might
- use little-ending byte order or a BOM, in which case conversion
+ use little-endian byte order or a BOM, in which case conversion
of UCS-2 values will need to be performed when transferring data
between those systems and MySQL.
</para>
@@ -3562,7 +3562,7 @@
The MySQL implementation of UCS-2 stores characters in
big-endian byte order and does not use a byte order mark (BOM)
at the beginning of UCS-2 values. Other database systems might
- use little-ending byte order or a BOM, in which case
+ use little-endian byte order or a BOM, in which case
conversion of UCS-2 values will need to be performed when
transferring data between those systems and MySQL.
</para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r9292 - in trunk: . it/refman-5.1 pt/refman-5.1 refman-4.1 refman-5.0 refman-5.1 refman-6.0 | paul | 13 Dec |
