Author: jstephens
Date: 2009-10-24 14:54:57 +0200 (Sat, 24 Oct 2009)
New Revision: 17308
Log:
Fixes Docs Bug #47192
Modified:
trunk/refman-4.1/programs-client-core.xml
trunk/refman-5.0/internationalization.xml
trunk/refman-5.0/programs-client-core.xml
trunk/refman-5.1/internationalization.xml
trunk/refman-5.1/programs-client-core.xml
trunk/refman-5.4/internationalization.xml
trunk/refman-5.4/programs-client-core.xml
trunk/refman-5.5/internationalization.xml
trunk/refman-5.5/programs-client-core.xml
trunk/refman-6.0.sav/internationalization.xml
trunk/refman-6.0.sav/programs-client-core.xml
Modified: trunk/refman-4.1/programs-client-core.xml
===================================================================
--- trunk/refman-4.1/programs-client-core.xml 2009-10-24 11:36:44 UTC (rev 17307)
+++ trunk/refman-4.1/programs-client-core.xml 2009-10-24 12:54:57 UTC (rev 17308)
Changed blocks: 1, Lines Added: 16, Lines Deleted: 1; 1239 bytes
@@ -393,8 +393,23 @@
<para>
Use <replaceable>charset_name</replaceable> as the default
- character set. See <xref linkend="charset-configuration"/>.
+ character set for the client and connection.
</para>
+
+ <para>
+ A common issue that can occur when the operating system uses
+ <literal>utf8</literal> or another multi-byte character set
+ is that output from the <command>mysql</command> client is
+ formatted incorrectly, due to the fact that the MySQL client
+ uses the <literal>latin1</literal> character set by default.
+ You can usually fix such issues by using this option to
+ force the client to use the system character set instead.
+ </para>
+
+ <para>
+ See <xref linkend="charset-configuration"/>, for more
+ information.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-5.0/internationalization.xml
===================================================================
--- trunk/refman-5.0/internationalization.xml 2009-10-24 11:36:44 UTC (rev 17307)
+++ trunk/refman-5.0/internationalization.xml 2009-10-24 12:54:57 UTC (rev 17308)
Changed blocks: 1, Lines Added: 11, Lines Deleted: 1; 1160 bytes
@@ -6034,7 +6034,17 @@
</programlisting>
<para>
- This is normally unnecessary, however.
+ This is normally unnecessary. However, when
+ <literal role="sysvar">character_set_system</literal> differs from
+ <literal role="sysvar">character_set_server</literal> or
+ <literal role="sysvar">character_set_client</literal>, and you
+ input characters manually (as database object identifiers, column
+ values, or both), these may be displayed incorrectly in output
+ from the client or the output itself may be formatted incorrectly.
+ In such cases, starting the mysql client with
+ <option role="mysql">--default-character-set=<replaceable>system_character_set</replaceable></option>
+ — that is, setting the client character set to match the
+ system character set — should fix the problem.
</para>
</section>
Modified: trunk/refman-5.0/programs-client-core.xml
===================================================================
--- trunk/refman-5.0/programs-client-core.xml 2009-10-24 11:36:44 UTC (rev 17307)
+++ trunk/refman-5.0/programs-client-core.xml 2009-10-24 12:54:57 UTC (rev 17308)
Changed blocks: 1, Lines Added: 16, Lines Deleted: 1; 1239 bytes
@@ -426,8 +426,23 @@
<para>
Use <replaceable>charset_name</replaceable> as the default
- character set. See <xref linkend="charset-configuration"/>.
+ character set for the client and connection.
</para>
+
+ <para>
+ A common issue that can occur when the operating system uses
+ <literal>utf8</literal> or another multi-byte character set
+ is that output from the <command>mysql</command> client is
+ formatted incorrectly, due to the fact that the MySQL client
+ uses the <literal>latin1</literal> character set by default.
+ You can usually fix such issues by using this option to
+ force the client to use the system character set instead.
+ </para>
+
+ <para>
+ See <xref linkend="charset-configuration"/>, for more
+ information.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-5.1/internationalization.xml
===================================================================
--- trunk/refman-5.1/internationalization.xml 2009-10-24 11:36:44 UTC (rev 17307)
+++ trunk/refman-5.1/internationalization.xml 2009-10-24 12:54:57 UTC (rev 17308)
Changed blocks: 1, Lines Added: 11, Lines Deleted: 1; 1160 bytes
@@ -6032,7 +6032,17 @@
</programlisting>
<para>
- This is normally unnecessary, however.
+ This is normally unnecessary. However, when
+ <literal role="sysvar">character_set_system</literal> differs from
+ <literal role="sysvar">character_set_server</literal> or
+ <literal role="sysvar">character_set_client</literal>, and you
+ input characters manually (as database object identifiers, column
+ values, or both), these may be displayed incorrectly in output
+ from the client or the output itself may be formatted incorrectly.
+ In such cases, starting the mysql client with
+ <option role="mysql">--default-character-set=<replaceable>system_character_set</replaceable></option>
+ — that is, setting the client character set to match the
+ system character set — should fix the problem.
</para>
</section>
Modified: trunk/refman-5.1/programs-client-core.xml
===================================================================
--- trunk/refman-5.1/programs-client-core.xml 2009-10-24 11:36:44 UTC (rev 17307)
+++ trunk/refman-5.1/programs-client-core.xml 2009-10-24 12:54:57 UTC (rev 17308)
Changed blocks: 1, Lines Added: 16, Lines Deleted: 1; 1239 bytes
@@ -476,8 +476,23 @@
<para>
Use <replaceable>charset_name</replaceable> as the default
- character set. See <xref linkend="charset-configuration"/>.
+ character set for the client and connection.
</para>
+
+ <para>
+ A common issue that can occur when the operating system uses
+ <literal>utf8</literal> or another multi-byte character set
+ is that output from the <command>mysql</command> client is
+ formatted incorrectly, due to the fact that the MySQL client
+ uses the <literal>latin1</literal> character set by default.
+ You can usually fix such issues by using this option to
+ force the client to use the system character set instead.
+ </para>
+
+ <para>
+ See <xref linkend="charset-configuration"/>, for more
+ information.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-5.4/internationalization.xml
===================================================================
--- trunk/refman-5.4/internationalization.xml 2009-10-24 11:36:44 UTC (rev 17307)
+++ trunk/refman-5.4/internationalization.xml 2009-10-24 12:54:57 UTC (rev 17308)
Changed blocks: 1, Lines Added: 11, Lines Deleted: 1; 1160 bytes
@@ -6026,7 +6026,17 @@
</programlisting>
<para>
- This is normally unnecessary, however.
+ This is normally unnecessary. However, when
+ <literal role="sysvar">character_set_system</literal> differs from
+ <literal role="sysvar">character_set_server</literal> or
+ <literal role="sysvar">character_set_client</literal>, and you
+ input characters manually (as database object identifiers, column
+ values, or both), these may be displayed incorrectly in output
+ from the client or the output itself may be formatted incorrectly.
+ In such cases, starting the mysql client with
+ <option role="mysql">--default-character-set=<replaceable>system_character_set</replaceable></option>
+ — that is, setting the client character set to match the
+ system character set — should fix the problem.
</para>
</section>
Modified: trunk/refman-5.4/programs-client-core.xml
===================================================================
--- trunk/refman-5.4/programs-client-core.xml 2009-10-24 11:36:44 UTC (rev 17307)
+++ trunk/refman-5.4/programs-client-core.xml 2009-10-24 12:54:57 UTC (rev 17308)
Changed blocks: 1, Lines Added: 16, Lines Deleted: 1; 1239 bytes
@@ -466,8 +466,23 @@
<para>
Use <replaceable>charset_name</replaceable> as the default
- character set. See <xref linkend="charset-configuration"/>.
+ character set for the client and connection.
</para>
+
+ <para>
+ A common issue that can occur when the operating system uses
+ <literal>utf8</literal> or another multi-byte character set
+ is that output from the <command>mysql</command> client is
+ formatted incorrectly, due to the fact that the MySQL client
+ uses the <literal>latin1</literal> character set by default.
+ You can usually fix such issues by using this option to
+ force the client to use the system character set instead.
+ </para>
+
+ <para>
+ See <xref linkend="charset-configuration"/>, for more
+ information.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-5.5/internationalization.xml
===================================================================
--- trunk/refman-5.5/internationalization.xml 2009-10-24 11:36:44 UTC (rev 17307)
+++ trunk/refman-5.5/internationalization.xml 2009-10-24 12:54:57 UTC (rev 17308)
Changed blocks: 1, Lines Added: 11, Lines Deleted: 1; 1160 bytes
@@ -6423,7 +6423,17 @@
</programlisting>
<para>
- This is normally unnecessary, however.
+ This is normally unnecessary. However, when
+ <literal role="sysvar">character_set_system</literal> differs from
+ <literal role="sysvar">character_set_server</literal> or
+ <literal role="sysvar">character_set_client</literal>, and you
+ input characters manually (as database object identifiers, column
+ values, or both), these may be displayed incorrectly in output
+ from the client or the output itself may be formatted incorrectly.
+ In such cases, starting the mysql client with
+ <option role="mysql">--default-character-set=<replaceable>system_character_set</replaceable></option>
+ — that is, setting the client character set to match the
+ system character set — should fix the problem.
</para>
</section>
Modified: trunk/refman-5.5/programs-client-core.xml
===================================================================
--- trunk/refman-5.5/programs-client-core.xml 2009-10-24 11:36:44 UTC (rev 17307)
+++ trunk/refman-5.5/programs-client-core.xml 2009-10-24 12:54:57 UTC (rev 17308)
Changed blocks: 1, Lines Added: 16, Lines Deleted: 1; 1239 bytes
@@ -466,8 +466,23 @@
<para>
Use <replaceable>charset_name</replaceable> as the default
- character set. See <xref linkend="charset-configuration"/>.
+ character set for the client and connection.
</para>
+
+ <para>
+ A common issue that can occur when the operating system uses
+ <literal>utf8</literal> or another multi-byte character set
+ is that output from the <command>mysql</command> client is
+ formatted incorrectly, due to the fact that the MySQL client
+ uses the <literal>latin1</literal> character set by default.
+ You can usually fix such issues by using this option to
+ force the client to use the system character set instead.
+ </para>
+
+ <para>
+ See <xref linkend="charset-configuration"/>, for more
+ information.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-6.0.sav/internationalization.xml
===================================================================
--- trunk/refman-6.0.sav/internationalization.xml 2009-10-24 11:36:44 UTC (rev 17307)
+++ trunk/refman-6.0.sav/internationalization.xml 2009-10-24 12:54:57 UTC (rev 17308)
Changed blocks: 1, Lines Added: 11, Lines Deleted: 1; 1172 bytes
@@ -7307,7 +7307,17 @@
</programlisting>
<para>
- This is normally unnecessary, however.
+ This is normally unnecessary. However, when
+ <literal role="sysvar">character_set_system</literal> differs from
+ <literal role="sysvar">character_set_server</literal> or
+ <literal role="sysvar">character_set_client</literal>, and you
+ input characters manually (as database object identifiers, column
+ values, or both), these may be displayed incorrectly in output
+ from the client or the output itself may be formatted incorrectly.
+ In such cases, starting the mysql client with
+ <option role="mysql">--default-character-set=<replaceable>system_character_set</replaceable></option>
+ — that is, setting the client character set to match the
+ system character set — should fix the problem.
</para>
</section>
Modified: trunk/refman-6.0.sav/programs-client-core.xml
===================================================================
--- trunk/refman-6.0.sav/programs-client-core.xml 2009-10-24 11:36:44 UTC (rev 17307)
+++ trunk/refman-6.0.sav/programs-client-core.xml 2009-10-24 12:54:57 UTC (rev 17308)
Changed blocks: 1, Lines Added: 16, Lines Deleted: 1; 1251 bytes
@@ -489,8 +489,23 @@
<para>
Use <replaceable>charset_name</replaceable> as the default
- character set. See <xref linkend="charset-configuration"/>.
+ character set for the client and connection.
</para>
+
+ <para>
+ A common issue that can occur when the operating system uses
+ <literal>utf8</literal> or another multi-byte character set
+ is that output from the <command>mysql</command> client is
+ formatted incorrectly, due to the fact that the MySQL client
+ uses the <literal>latin1</literal> character set by default.
+ You can usually fix such issues by using this option to
+ force the client to use the system character set instead.
+ </para>
+
+ <para>
+ See <xref linkend="charset-configuration"/>, for more
+ information.
+ </para>
</listitem>
<listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r17308 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-5.4 refman-5.5 refman-6.0.sav | jon.stephens | 24 Oct |
