From b8cd6b4f25851554faffde256b136a41d2b75935 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Fri, 28 Jul 2006 15:33:17 +0000 Subject: [PATCH] Make it clearer that not every Postgres character set can be used as a server-side character set. --- doc/src/sgml/charset.sgml | 129 ++++++++++++++++++++++++-------------- 1 file changed, 83 insertions(+), 46 deletions(-) diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml index c25f72a73e..5c0ad1b040 100644 --- a/doc/src/sgml/charset.sgml +++ b/doc/src/sgml/charset.sgml @@ -1,4 +1,4 @@ - + Localization</> @@ -304,14 +304,13 @@ initdb --locale=sv_SE allows you to store text in a variety of character sets, including single-byte character sets such as the ISO 8859 series and multiple-byte character sets such as <acronym>EUC</> (Extended Unix - Code), UTF-8, and Mule internal code. All character sets can be - used transparently throughout the server. (If you use extension - functions from other sources, it depends on whether they wrote - their code correctly.) The default character set is selected while + Code), UTF-8, and Mule internal code. All supported character sets + can be used transparently by clients, but a few are not supported + for use within the server (that is, as a server-side encoding). + The default character set is selected while initializing your <productname>PostgreSQL</productname> database cluster using <command>initdb</>. It can be overridden when you - create a database using <command>createdb</command> or by using the - SQL command <command>CREATE DATABASE</>. So you can have multiple + create a database, so you can have multiple databases each with a different character set. </para> @@ -320,17 +319,18 @@ initdb --locale=sv_SE <para> <xref linkend="charset-table"> shows the character sets available - for use in the server. + for use in <productname>PostgreSQL</productname>. </para> <table id="charset-table"> <title>Server Character Sets - + Name Description Language + Server?