|
1 |
| -<!-- $Header: /cvsroot/pgsql/doc/src/sgml/charset.sgml,v 2.36 2003/05/15 15:50:18 petere Exp $ --> |
| 1 | +<!-- $Header: /cvsroot/pgsql/doc/src/sgml/charset.sgml,v 2.37 2003/08/04 04:03:03 tgl Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="charset">
|
4 | 4 | <title>Localization</>
|
|
7 | 7 | This chapter describes the available localization features from the
|
8 | 8 | point of view of the administrator.
|
9 | 9 | <productname>PostgreSQL</productname> supports localization with
|
10 |
| - three approaches: |
| 10 | + two approaches: |
11 | 11 |
|
12 | 12 | <itemizedlist>
|
13 | 13 | <listitem>
|
|
23 | 23 | Providing a number of different character sets defined in the
|
24 | 24 | <productname>PostgreSQL</productname> server, including
|
25 | 25 | multiple-byte character sets, to support storing text in all
|
26 |
| - kinds of languages, and providing character set recoding between |
| 26 | + kinds of languages, and providing character set translation between |
27 | 27 | client and server.
|
28 | 28 | </para>
|
29 | 29 | </listitem>
|
30 |
| - |
31 |
| - <listitem> |
32 |
| - <para> |
33 |
| - Single-byte character recoding provides a more light-weight |
34 |
| - solution for users of multiple, yet single-byte character sets. |
35 |
| - </para> |
36 |
| - </listitem> |
37 | 30 | </itemizedlist>
|
38 | 31 | </para>
|
39 | 32 |
|
@@ -884,75 +877,6 @@ RESET CLIENT_ENCODING;
|
884 | 877 |
|
885 | 878 | </sect1>
|
886 | 879 |
|
887 |
| - |
888 |
| - <sect1 id="recode"> |
889 |
| - <title>Single-Byte Character Set Recoding</> |
890 |
| - |
891 |
| - <para> |
892 |
| - You can set up this feature with the <option>--enable-recode</> option |
893 |
| - to <filename>configure</>. This option was formerly described as |
894 |
| - <quote>Cyrillic recode support</> which doesn't express all its |
895 |
| - power. It can be used for <emphasis>any</> single-byte character |
896 |
| - set recoding. |
897 |
| - </para> |
898 |
| - |
899 |
| - <para> |
900 |
| - This method uses a file <filename>charset.conf</> file located in |
901 |
| - the data directory for configuration. It's a typical |
902 |
| - configuration text file where spaces and newlines separate fields |
903 |
| - and records and <literal>#</> starts a comment. Three key words with the |
904 |
| - following syntax are recognized here: |
905 |
| -<synopsis> |
906 |
| -BaseCharset <replaceable>server_charset</> |
907 |
| -RecodeTable <replaceable>from_charset</> <replaceable>to_charset</> <replaceable>file_name</> |
908 |
| -HostCharset <replaceable>host_spec</> <replaceable>host_charset</> |
909 |
| -</synopsis> |
910 |
| - </para> |
911 |
| - |
912 |
| - <para> |
913 |
| - <token>BaseCharset</> defines the character set of the database server. |
914 |
| - All character set names are only used for mapping inside of |
915 |
| - <filename>charset.conf</> so you can freely use typing-friendly |
916 |
| - names. |
917 |
| - </para> |
918 |
| - |
919 |
| - <para> |
920 |
| - <token>RecodeTable</> records specify conversion tables between |
921 |
| - server and client. The file name is relative to the |
922 |
| - data directory. The table file format is very |
923 |
| - simple. There are no key words, and character mappings are represented by a |
924 |
| - pair of decimal or hexadecimal (prefixed by <literal>0x</>) values on single |
925 |
| - lines: |
926 |
| -<synopsis> |
927 |
| -<replaceable>char_value</> <replaceable>converted_char_value</> |
928 |
| -</synopsis> |
929 |
| - In the <filename>src/data/</> directory in the source distribution you can find an |
930 |
| - example <filename>charset.conf</> and a few recoding tables. |
931 |
| - </para> |
932 |
| - |
933 |
| - <para> |
934 |
| - <token>HostCharset</> records define the client character set by IP |
935 |
| - address. You can use a single IP address, an IP mask range starting |
936 |
| - from the given address or an IP interval (e.g., <literal>127.0.0.1</>, |
937 |
| - <literal>192.168.1.100/24</>, <literal>192.168.1.20-192.168.1.40</>). |
938 |
| - </para> |
939 |
| - |
940 |
| - <para> |
941 |
| - The <filename>charset.conf</> file is always processed to the |
942 |
| - end, so you can easily specify exceptions from preceding rules. |
943 |
| - </para> |
944 |
| - |
945 |
| - <para> |
946 |
| - As this solution is based on the client's IP address there are |
947 |
| - obviously some restrictions as well. You cannot use different |
948 |
| - character sets on the same host at the same time. It is also |
949 |
| - inconvenient when you boot your client hosts into multiple |
950 |
| - operating systems. Nevertheless, when these restrictions are not |
951 |
| - limiting and you do not need multibyte characters then it is a |
952 |
| - simple and effective solution. |
953 |
| - </para> |
954 |
| - </sect1> |
955 |
| - |
956 | 880 | </chapter>
|
957 | 881 |
|
958 | 882 | <!-- Keep this comment at the end of the file
|
|
0 commit comments