head	1.11;
access;
symbols
	REL7_1_BETA2:1.10
	REL7_1:1.10
	REL7_0_PATCHES:1.10.0.2
	REL7_0:1.9
	REL6_5_PATCHES:1.8.0.2
	REL6_5:1.8
	REL6_4:1.4.0.2;
locks; strict;
comment	@# @;


1.11
date	2001.01.09.04.40.31;	author ishii;	state dead;
branches;
next	1.10;

1.10
date	2000.05.20.13.40.13;	author ishii;	state Exp;
branches
	1.10.2.1;
next	1.9;

1.9
date	2000.03.24.01.37.11;	author ishii;	state Exp;
branches;
next	1.8;

1.8
date	99.07.11.22.59.26;	author ishii;	state Exp;
branches;
next	1.7;

1.7
date	99.04.13.09.29.46;	author ishii;	state Exp;
branches;
next	1.6;

1.6
date	99.02.02.18.51.20;	author momjian;	state Exp;
branches;
next	1.5;

1.5
date	98.12.18.18.01.09;	author momjian;	state Exp;
branches;
next	1.4;

1.4
date	98.07.24.03.31.03;	author scrappy;	state Exp;
branches
	1.4.2.1;
next	1.3;

1.3
date	98.06.16.07.29.15;	author momjian;	state Exp;
branches;
next	1.2;

1.2
date	98.04.27.17.06.55;	author scrappy;	state Exp;
branches;
next	1.1;

1.1
date	98.03.15.07.37.53;	author scrappy;	state Exp;
branches;
next	;

1.4.2.1
date	98.12.18.18.01.35;	author momjian;	state Exp;
branches;
next	;

1.10.2.1
date	2000.05.28.04.28.55;	author ishii;	state Exp;
branches;
next	;


desc
@@


1.11
log
@README.mb has been unified into SGML documents.
@
text
@PostgreSQL 7.0 multi-byte (MB) support README	  Mar 22 2000

						Tatsuo Ishii
						ishii@@postgresql.org
		  http://www.sra.co.jp/people/t-ishii/PostgreSQL/

0. Introduction

The MB support is intended for allowing PostgreSQL to handle
multi-byte character sets such as EUC(Extended Unix Code), Unicode and
Mule internal code. With the MB enabled you can use multi-byte
character sets in regexp ,LIKE and some other functions. The default
encoding system chosen is determined while initializing your
PostgreSQL installation using initdb(1). Note that this can be
overridden when you create a database using createdb(1) or by using a
create database SQL command. So you could have multiple databases with
each different encoding system.

MB also fixes some problems concerning with 8-bit single byte
character sets including ISO8859. (I would not say all of problems
have been fixed. I just confirmed that the regression test ran fine
and a few French characters could be used with the patch. Please let
me know if you find any problem while using 8-bit characters)

1. How to use

run configure with a multibyte option:

	% ./configure --enable-multibyte[=encoding_system]

where the encoding_system is one of:

	SQL_ASCII		ASCII
	EUC_JP			Japanese EUC
	EUC_CN			Chinese EUC
	EUC_KR			Korean EUC
	EUC_TW			Taiwan EUC
	UNICODE			Unicode(UTF-8)
	MULE_INTERNAL		Mule internal
	LATIN1			ISO 8859-1 English and some European languages
	LATIN2			ISO 8859-2 English and some European languages
	LATIN3			ISO 8859-3 English and some European languages
	LATIN4			ISO 8859-4 English and some European languages
	LATIN5			ISO 8859-5 English and some European languages
	KOI8			KOI8-R
	WIN			Windows CP1251
	ALT			Windows CP866

Example:

	% ./configure --enable-multibyte=EUC_JP

If the encoding system is omitted (./configure --enable-multibyte),
SQL_ASCII is assumed.

2. How to set the encoding

initdb command defines the default encoding for a PostgreSQL
installation. For example:

	% initdb -E EUC_JP

sets the default encoding to EUC_JP(Extended Unix Code for Japanese).
Note that you can use "--encoding" instead of "-E" if you like longer
option string:-) If no -E or --encoding option is given, the encoding
specified at the compile time is used.

You can create a database with a different encoding.

	% createdb -E EUC_KR korean

will create a database named "korean" with EUC_KR encoding. The
another way to accomplish this is to use a SQL command:

	CREATE DATABASE korean WITH ENCODING = 'EUC_KR';

The encoding for a database is represented as "encoding" column in the
pg_database system catalog. You can see that by using -l or \l of psql
command.

$ psql -l
            List of databases
   Database    |  Owner  |   Encoding    
---------------+---------+---------------
 euc_cn        | t-ishii | EUC_CN
 euc_jp        | t-ishii | EUC_JP
 euc_kr        | t-ishii | EUC_KR
 euc_tw        | t-ishii | EUC_TW
 mule_internal | t-ishii | MULE_INTERNAL
 regression    | t-ishii | SQL_ASCII
 template1     | t-ishii | EUC_JP
 test          | t-ishii | EUC_JP
 unicode       | t-ishii | UNICODE
(9 rows)

3. Automatic encoding translation between backend and frontend

PostgreSQL supports an automatic encoding translation between backend
and frontend for some encodings.

  encoding of backend			available encoding of frontend
  --------------------------------------------------------------------
	EUC_JP				EUC_JP, SJIS
  
	EUC_TW				EUC_TW, BIG5
  
  	LATIN2				LATIN2, WIN1250
  
	LATIN5				LATIN5, WIN, ALT
  
	MULE_INTERNAL			EUC_JP, SJIS, EUC_KR, EUC_CN, 
					EUC_TW, BIG5, LATIN1 to LATIN5, 
					WIN, ALT, WIN1250

To enable the automatic encoding translation, you have to tell
PostgreSQL the encoding you would like to use in frontend. There are
several ways to accomplish this.

o using \encoding command in psql

\encoding allows you to change frontend encoding on the fly. For
example, to change the encoding to SJIS, type:

	\encoding SJIS

o using libpq functions

\encoding actually calls PQsetClientEncoding() for its purpose.

  int PQsetClientEncoding(PGconn *conn, const char *encoding)

conn is a connection to the backend, and encoding is an encoding you
want to use. If it successfully sets the encoding, it returns 0,
otherwise -1. The current encoding for this connection can be shown by
using:

  int PQclientEncoding(const PGconn *conn)

Note that it returns the "encoding id," not the encoding symbol string
such as "EUC_JP." To convert an encoding id to an encoding symbol, you
can use:

char *pg_encoding_to_char(int encoding_id)

o using PGCLIENTENCODING

If an environment variable PGCLIENTENCODING is defined in the
frontend, an automatic encoding translation is done by the backend.

o using SET CLIENT_ENCODING TO command

Setting the frontend side encoding can be done a SQL command:

	SET CLIENT_ENCODING TO 'encoding';

Also you can use SQL92 syntax "SET NAMES" for this purpose:

	SET NAMES 'encoding';

To query the current the frontend encoding:

	SHOW CLIENT_ENCODING;

To return to the default encoding:

	RESET CLIENT_ENCODING;

4. About Unicode

An automatic encoding translation between Unicode and any other
encodings is not supported (yet). 

5. What happens if the translation is not possible?

Suppose you choose EUC_JP for the backend, LATIN1 for the frontend,
then some Japanese characters could not be translated into LATIN1. In
this case, a letter cannot be represented in the LATIN1 character set,
would be transformed as:

	(HEXA DECIMAL)

6. References

These are good sources to start learning various kind of encoding
systems.

ftp://ftp.ora.com/pub/examples/nutshell/ujip/doc/cjk.inf
	Detailed explanations of EUC_JP, EUC_CN, EUC_KR, EUC_TW
	appear in section 3.2.

Unicode: http://www.unicode.org/
	The homepage of UNICODE.

	RFC 2044
	UTF-8 is defined here.

5. History

May 20, 2000
	* SJIS UDC (NEC selection IBM kanji) support contributed
	  by Eiji Tokuya
	* Changes above will appear in 7.0.1

Mar 22, 2000
	* Add new libpq functions PQsetClientEncoding, PQclientEncoding
	* ./configure --with-mb=EUC_JP
	  now deprecated. use 
	  ./configure --enable-multibyte=EUC_JP
	  instead
  	* Add SQL_ASCII regression test case
	* Add SJIS User Defined Character (UDC) support
	* All of above will appear in 7.0

July 11, 1999
	* Add support for WIN1250 (Windows Czech) as a client encoding
	  (contributed by Pavel Behal)
	* fix some compiler warnings (contributed by Tomoaki Nishiyama)

Mar 23, 1999
	* Add support for KOI8(KOI8-R), WIN(CP1251), ALT(CP866)
	  (thanks Oleg Broytmann for testing)
	* Fix problem with MB and locale

Jan 26, 1999
	* Add support for Big5 for fronend encoding
	  (you need to create a database with EUC_TW to use Big5)
	* Add regression test case for EUC_TW
	  (contributed by Jonah Kuo <jonahkuo@@mail.ttn.com.tw>)

Dec 15, 1998
	* Bugs related to SQL_ASCII support fixed

Nov 5, 1998
	* 6.4 release. In this version, pg_database has "encoding"
	  column that represents the database encoding

Jul 22, 1998
	* determine encoding at initdb/createdb rather than compile time
	* support for PGCLIENTENCODING when issuing COPY command
	* support for SQL92 syntax "SET NAMES"
	* support for LATIN2-5
	* add UNICODE regression test case
	* new test suite for MB
	* clean up source files

Jun 5, 1998
	* add support for the encoding translation between the backend
	  and the frontend
	* new command SET CLIENT_ENCODING etc. added
	* add support for LATIN1 character set
	* enhance 8 bit cleaness

April 21, 1998 some enhancements/fixes
	* character_length(), position(), substring() are now aware of 
	  multi-byte characters
	* add octet_length()
	* add --with-mb option to configure
	* new regression tests for EUC_KR
  	  (contributed by "Soonmyung. Hong" <hong@@lunaris.hanmesoft.co.kr>)
	* add some test cases to the EUC_JP regression test
	* fix problem in regress/regress.sh in case of System V
	* fix toupper(), tolower() to handle 8bit chars

Mar 25, 1998 MB PL2 is incorporated into PostgreSQL 6.3.1

Mar 10, 1998 PL2 released
	* add regression test for EUC_JP, EUC_CN and MULE_INTERNAL
	* add an English document (this file)
	* fix problems concerning 8-bit single byte characters

Mar 1, 1998 PL1 released

Appendix:

[Here is a good documentation explaining how to use WIN1250 on
Windows/ODBC from Pavel Behal. Please note that Installation step 1)
is not necceary in 6.5.1 -- Tatsuo]

Version: 0.91 for PgSQL 6.5
Author: Pavel Behal
Revised by: Tatsuo Ishii
Email: behal@@opf.slu.cz
Licence: The Same as PostgreSQL

Sorry for my Eglish and C code, I'm not native :-)

!!!!!!!!!!!!!!!!!!!!!!!!! NO WARRANTY !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Instalation:
------------
1) Change three affected files in source directories 
    (I don't have time to create proper patch diffs, I don't know how)
2) Compile with enabled locale and multibyte set to LATIN2
3) Setup properly your instalation, do not forget to create locale
   variables in your profile (environment). Ex. (may not be exactly true):
	LC_ALL=cs_CZ.ISO8859-2
	LC_COLLATE=cs_CZ.ISO8859-2
	LC_CTYPE=cs_CZ.ISO8859-2
	LC_MONETARY=cs_CZ.ISO8859-2
	LC_NUMERIC=cs_CZ.ISO8859-2
	LC_TIME=cs_CZ.ISO8859-2
4) You have to start the postmaster with locales set!
5) Try it with Czech language, it have to sort
5) Install ODBC driver for PgSQL into your M$ Windows
6) Setup properly your data source. Include this line in your ODBC
   configuration dialog in field "Connect Settings:" :
	SET CLIENT_ENCODING = 'WIN1250';
7) Now try it again, but in Windows with ODBC.

Description:
------------
- Depends on proper system locales, tested with RH6.0 and Slackware 3.6,
  with cs_CZ.iso8859-2 loacle
- Never try to set-up server multibyte database encoding to WIN1250,
  always use LATIN2 instead. There is not WIN1250 locale in Unix
- WIN1250 encoding is useable only for M$W ODBC clients. The characters are
  on thy fly re-coded, to be displayed and stored back properly
 
Important:
----------
- it reorders your sort order depending on your LC_... setting, so don't be
  confused with regression tests, they don't use locale
- "ch" is corectly sorted only in some newer locales (Ex. RH6.0)
- you have to insert money as '162,50' (with comma in aphostrophes!)
- not tested properly
@


1.10
log
@Multibyte documentations update
@
text
@@


1.10.2.1
log
@Change date of documents.
@
text
@d1 1
a1 1
PostgreSQL 7.0.1 multi-byte (MB) support README	  May 20 2000
@


1.9
log
@Update multi-byte support README
@
text
@d199 5
@


1.8
log
@document updated for 6.5.1
@
text
@d1 1
a1 1
postgresql 6.5.1 multi-byte (MB) support README	  July 11 1999
d4 1
a4 1
						t-ishii@@sra.co.jp
d12 1
a12 1
character sets in regexp ,LIKE and some functions. The default
d15 3
a17 3
overridden when you create a database using createdb(1) or create
database SQL command. So you could have multiple databases with
different encoding systems.
d27 1
a27 1
run configure with the mb option:
d29 1
a29 1
	% configure --with-mb=encoding_system
d31 1
a31 1
where encoding_system is one of:
d51 1
a51 1
	% configure --with-mb=EUC_JP
d53 2
a54 2
If MB is disabled, nothing is changed except better supporting for
8-bit single byte character sets.
d56 1
a56 1
2. How to set encoding
d61 1
a61 1
	% initdb -e EUC_JP
d64 2
a65 2
Note that you can use "-pgencoding" instead of "-e" if you like longer
option string:-) If no -e or -pgencoding option is given, the encoding
d78 2
a79 1
pg_database system catalog.
d81 14
a94 31
	datname      |datdba|encoding|datpath      
	-------------+------+--------+-------------
	template1    |  1739|       1|template1    
	postgres     |  1739|       0|postgres     
	euc_jp       |  1739|       1|euc_jp       
	euc_kr       |  1739|       3|euc_kr       
	euc_cn       |  1739|       2|euc_cn       
	unicode      |  1739|       5|unicode      
	mule_internal|  1739|       6|mule_internal

A number in the encoding column is "encoding id" and can be translated
to the encoding name using pg_encoding command.

	$ pg_encoding 1
	EUC_JP

If an argument to pg_encoding is not a number, then it is regarded as
an encoding name and pg_encoding will return the encoding id.

	$ pg_encoding EUC_JP
	1

3. PGCLIENTENCODING

If an environment variable PGCLIENTENCODING is defined on the
frontend, automatic encoding translation is done by the backend. For
example, if the backend has been compiled with MB=EUC_JP and
PGCLIENTENCODING=SJIS(Shift JIS: yet another Japanese encoding
system), then any SJIS strings coming from the frontend would be
translated to EUC_JP before going into the parser. Outputs from the
backend would be translated to SJIS of course.
d96 1
a96 1
Supported encodings for PGCLIENTENCODING are:
d98 46
a143 17
	SQL_ASCII		ASCII
	EUC_JP			Japanese EUC
	SJIS			Yet another Japanese encoding
	EUC_CN			Chinese EUC
	EUC_KR			Korean EUC
	EUC_TW			Taiwan EUC
	BIG5			Traditional Chinese
	MULE_INTERNAL		Mule internal
	LATIN1			ISO 8859-1 English and some European languages
	LATIN2			ISO 8859-2 English and some European languages
	LATIN3			ISO 8859-3 English and some European languages
	LATIN4			ISO 8859-4 English and some European languages
	LATIN5			ISO 8859-5 English and some European languages
	KOI8			KOI8-R
	WIN			Windows CP1251
	ALT			Windows CP866
	WIN1250			Windows CP1250 (Czech)
d145 1
a145 5
Note that UNICODE is not supported(yet). Also note that the
translation is not always possible. Suppose you choose EUC_JP for the
backend, LATIN1 for the frontend, then some Japanese characters cannot
be translated into latin. In this case, a letter cannot be represented
in the Latin character set, would be transformed as:
d147 2
a148 1
	(HEXA DECIMAL)
d150 1
a150 1
3. SET CLIENT_ENCODING TO command
d152 1
a152 2
Actually setting the frontend side encoding information is done by a
new command:
d156 1
a156 3
where encoding is one of the encodings those can be set to
PGCLIENTENCODING. Also you can use SQL92 syntax "SET NAMES" for this
purpose:
d168 6
a173 2
This would reset the frontend encoding to same as the backend
encoding, thus no encoding translation would be performed.
d175 8
a182 1
4. References
d198 10
@


1.7
log
@Document updation for 6.5
@
text
@d1 1
a1 1
postgresql 6.5 multi-byte (MB) support README	  Mar 23 1999
d46 2
a47 2
	WIN			CP1251
	ALT			CP866
d128 3
a130 2
	WIN			CP1251
	ALT			CP866
d181 5
d239 54
@


1.6
log
@Included patches make some enhancements to the multi-byte support.

o allow to use Big5 (a Chinese encoding used in Taiwan) as a client
  encoding. In this case the server side encoding should be EUC_TW

o add EUC_TW and Big5 test cases to the regression and the mb test
  (contributed by Jonah Kuo)

o fix mistake in include/mb/pg_wchar.h. An encoding id for EUC_TW was
  not correct (was 3 and now is 4)

o update documents (doc/README.mb and README.mb.jp)

o update psql helpfile (bin/psql/psqlHelp.h)

--
Tatsuo Ishii
t-ishii@@sra.co.jp
@
text
@d1 1
a1 1
postgresql 6.5 multi-byte (MB) support README	  Jan 26 1999
d12 6
a17 5
character sets in regexp ,LIKE and some functions. The encoding system
chosen is determined when initializing your PostgreSQL installation
using initdb(1). Note that this can be overridden when creating a
database using createdb(1) or create database SQL command. So you
could have multiple databases with different encoding system.
d45 3
d120 1
a120 1
	BIG5			Traditional chinese
d127 3
d133 1
a133 1
backend, LATIN1 for the frotend, then some Japanese characters cannot
d161 1
a161 1
encoding, thus no endoing translation would be performed.
d180 5
d186 1
a186 1
	* Add support Big5 for fronend encoding
@


1.5
log
@Included are patches for doc/README.mb and README.mb.jp.
Please apply to both trees.
--
Tatsuo Ishii
@
text
@d1 1
a1 1
postgresql 6.4 multi-byte (MB) support README	  Dec 16 1998
d116 1
d172 6
@


1.4
log
@
I really hope that I haven't missed anything in this one...

From: t-ishii@@sra.co.jp

Attached are patches to enhance the multi-byte support.  (patches are
against 7/18 snapshot)

* determine encoding at initdb/createdb rather than compile time

Now initdb/createdb has an option to specify the encoding. Also, I
modified the syntax of CREATE DATABASE to accept encoding option. See
README.mb for more details.

For this purpose I have added new column "encoding" to pg_database.
Also pg_attribute and pg_class are changed to catch up the
modification to pg_database.  Actually I haved added pg_database_mb.h,
pg_attribute_mb.h and pg_class_mb.h. These are used only when MB is
enabled. The reason having separate files is I couldn't find a way to
use ifdef or whatever in those files. I have to admit it looks
ugly. No way.

* support for PGCLIENTENCODING when issuing COPY command

commands/copy.c modified.

* support for SQL92 syntax "SET NAMES"

See gram.y.

* support for LATIN2-5
* add UNICODE regression test case
* new test suite for MB

New directory test/mb added.

* clean up source files

Basic idea is to have MB's own subdirectory for easier maintenance.
These are include/mb and backend/utils/mb.
@
text
@d1 1
a1 1
postgresql 6.4 multi-byte (MB) support README	  Jul 22 1998
d14 1
a14 1
using initdb(1). Note that this can be overrided when creating a
d26 1
a26 5
create src/Makefile.custom with a line including:

	MB=encoding_system

or run configure with the mb option:
d32 1
a46 5
	% cat Makefile.custom
	MB=EUC_JP

	or

d73 25
d110 1
d171 7
@


1.4.2.1
log
@Included are patches for doc/README.mb and README.mb.jp.
Please apply to both trees.
--
Tatsuo Ishii
@
text
@d1 1
a1 1
postgresql 6.4 multi-byte (MB) support README	  Dec 16 1998
d14 1
a14 1
using initdb(1). Note that this can be overridden when creating a
d26 5
a30 1
run configure with the mb option:
a35 1
	SQL_ASCII		ASCII
d50 5
a80 25
The encoding for a database is represented as "encoding" column in the
pg_database system catalog.

	datname      |datdba|encoding|datpath      
	-------------+------+--------+-------------
	template1    |  1739|       1|template1    
	postgres     |  1739|       0|postgres     
	euc_jp       |  1739|       1|euc_jp       
	euc_kr       |  1739|       3|euc_kr       
	euc_cn       |  1739|       2|euc_cn       
	unicode      |  1739|       5|unicode      
	mule_internal|  1739|       6|mule_internal

A number in the encoding column is "encoding id" and can be translated
to the encoding name using pg_encoding command.

	$ pg_encoding 1
	EUC_JP

If an argument to pg_encoding is not a number, then it is regarded as
an encoding name and pg_encoding will return the encoding id.

	$ pg_encoding EUC_JP
	1

a92 1
	SQL_ASCII		ASCII
a152 7

Dec 15, 1998
	* Bugs related to SQL_ASCII support fixed

Nov 5, 1998
	* 6.4 release. In this version, pg_database has "encoding"
	  column that represents the database encoding
@


1.3
log
@Hi, here are the patches to enhance existing MB handling. This time
I have implemented a framework of encoding translation between the
backend and the frontend. Also I have added a new variable setting
command:

SET CLIENT_ENCODING TO 'encoding';

Other features include:
	Latin1 support more 8 bit cleaness

See doc/README.mb for more details. Note that the pacthes are
against May 30 snapshot.

Tatsuo Ishii
@
text
@d1 1
a1 1
postgresql 6.4 multi-byte (MB) support README	  Jun 5 1998
d13 4
a16 1
chosen is determined at the compile time.
d42 5
a46 1
	LATIN1			ISO 8859-1 English and some European laguages
d60 22
a81 1
2. PGCLIENTENCODING
d99 5
a103 1
	LATIN1			ISO 8859-1 English and some European laguages
d121 6
a126 1
PGCLIENTENCODING.  To query the current the frontend encoding:
d154 10
a163 1
Jun 5, 1988
@


1.2
log
@From: t-ishii@@sra.co.jp

Hi, here are patches I promised (against 6.3.2):

* character_length(), position(), substring() are now aware of
          multi-byte characters
* add octet_length()
* add --with-mb option to configure
* new regression tests for EUC_KR
  (contributed by "Soonmyung. Hong" <hong@@lunaris.hanmesoft.co.kr>)
* add some test cases to the EUC_JP regression test
* fix problem in regress/regress.sh in case of System V
* fix toupper(), tolower() to handle 8bit chars

note that:

o  patches for both configure.in and configure are
included. maybe the one for configure is not necessary.

o pg_proc.h was modified to add octet_length(). I used OIDs
(1374-1379) for that. Please let me know if these numbers are not
appropriate.
@
text
@d1 1
a1 1
postgresql 6.3 multi-byte (MB) support README	  April 21 1998
d7 1
a7 1
Introduction
d21 1
a21 1
How to use
d39 1
d53 48
a100 1
References
d115 8
a122 1
History
@


1.1
log
@From: t-ishii@@sra.co.jp

Included are patches intended for allowing PostgreSQL to handle
multi-byte charachter sets such as EUC(Extende Unix Code), Unicode and
Mule internal code. With the MB patch you can use multi-byte character
sets in regexp and LIKE. The encoding system chosen is determined at
the compile time.

To enable the MB extension, you need to define a variable "MB" in
Makefile.global or in Makefile.custom. For further information please
take a look at README.mb under doc directory.

(Note that unlike "jp patch" I do not use modified GNU regexp any
more. I changed Henry Spencer's regexp coming with PostgreSQL.)
@
text
@d1 1
a1 1
postgresql 6.3 multi-byte(MB) patch PL2 README	  Mar 10 1998
d9 5
a13 5
MB patch is intended for allowing PostgreSQL to handle multi-byte
charachter sets such as EUC(Extende Unix Code), Unicode and Mule
internal code. With the MB patch you can use multi-byte character sets
in regexp and LIKE. The encoding system chosen is determined at the
compile time.
d15 1
a15 1
The patch also fixes some problems concerning with 8-bit single byte
d23 1
a23 2
After applying the MB patch, create src/Makefile.custom with a line
including:
d25 5
a29 1
MB=encoding_system
d33 6
a38 6
EUC_JP			Japanese EUC
EUC_CN			Chinese EUC
EUC_KR			Korean EUC
EUC_TW			Taiwan EUC
UNICODE			Unicode(UTF-8)
MULE_INTERNAL		Mule internal
d42 4
a45 2
% cat Makefile.custom
MB=EUC_JP
d47 3
a49 1
If MB is not defined, nothing is changed except better supporting for
d68 13
@
