1- postgresql 6.5 multi-byte (MB) support READMEJan 26 1999
1+ postgresql 6.5 multi-byte (MB) support READMEMar 23 1999
22
33Tatsuo Ishii
44t-ishii@sra.co.jp
@@ -9,11 +9,12 @@ postgresql 6.5 multi-byte (MB) support README Jan 26 1999
99The MB support is intended for allowing PostgreSQL to handle
1010multi-byte character sets such as EUC(Extended Unix Code), Unicode and
1111Mule internal code. With the MB enabled you can use multi-byte
12- character sets in regexp ,LIKE and some functions. The encoding system
13- chosen is determined when initializing your PostgreSQL installation
14- using initdb(1). Note that this can be overridden when creating a
15- database using createdb(1) or create database SQL command. So you
16- could have multiple databases with different encoding system.
12+ character sets in regexp ,LIKE and some functions. The default
13+ encoding system chosen is determined while initializing your
14+ PostgreSQL installation using initdb(1). Note that this can be
15+ overridden when you create a database using createdb(1) or create
16+ database SQL command. So you could have multiple databases with
17+ different encoding systems.
1718
1819MB also fixes some problems concerning with 8-bit single byte
1920character sets including ISO8859. (I would not say all of problems
@@ -41,6 +42,9 @@ where encoding_system is one of:
4142LATIN3ISO 8859-3 English and some European languages
4243LATIN4ISO 8859-4 English and some European languages
4344LATIN5ISO 8859-5 English and some European languages
45+ KOI8KOI8-R
46+ WINCP1251
47+ ALTCP866
4448
4549Example:
4650
@@ -113,17 +117,20 @@ Supported encodings for PGCLIENTENCODING are:
113117EUC_CNChinese EUC
114118EUC_KRKorean EUC
115119EUC_TWTaiwan EUC
116- BIG5Traditionalchinese
120+ BIG5TraditionalChinese
117121MULE_INTERNALMule internal
118122LATIN1ISO 8859-1 English and some European languages
119123LATIN2ISO 8859-2 English and some European languages
120124LATIN3ISO 8859-3 English and some European languages
121125LATIN4ISO 8859-4 English and some European languages
122126LATIN5ISO 8859-5 English and some European languages
127+ KOI8KOI8-R
128+ WINCP1251
129+ ALTCP866
123130
124131Note that UNICODE is not supported(yet). Also note that the
125132translation is not always possible. Suppose you choose EUC_JP for the
126- backend, LATIN1 for thefrotend , then some Japanese characters cannot
133+ backend, LATIN1 for thefrontend , then some Japanese characters cannot
127134be translated into latin. In this case, a letter cannot be represented
128135in the Latin character set, would be transformed as:
129136
@@ -151,7 +158,7 @@ To return to the default encoding:
151158RESET CLIENT_ENCODING;
152159
153160This would reset the frontend encoding to same as the backend
154- encoding, thus noendoing translation would be performed.
161+ encoding, thus noencoding translation would be performed.
155162
1561634. References
157164
@@ -170,8 +177,13 @@ Unicode: http://www.unicode.org/
170177
1711785. History
172179
180+ Mar 23, 1999
181+ * Add support for KOI8(KOI8-R), WIN(CP1251), ALT(CP866)
182+ (thanks Oleg Broytmann for testing)
183+ * Fix problem with MB and locale
184+
173185Jan 26, 1999
174- * Add support Big5 for fronend encoding
186+ * Add supportfor Big5 for fronend encoding
175187 (you need to create a database with EUC_TW to use Big5)
176188* Add regression test case for EUC_TW
177189 (contributed by Jonah Kuo <jonahkuo@mail.ttn.com.tw>)