Skip site navigation (1) Skip section navigation (2)

Re: Added Encoding

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: pgman(at)candle(dot)pha(dot)pa(dot)us
Cc: e-tokuya(at)sankyo-unyu(dot)co(dot)jp, pgsql-patches(at)postgresql(dot)org
Subject: Re: Added Encoding
Date: 2001-11-26 01:43:48
Message-ID: 20011126104348F.t-ishii@sra.co.jp (view raw or flat)
Thread:
Lists: pgsql-patches
> > It was made to cope with encoding such as an Asian bloc in 7.2Beta2.
> > 
> > Added ServerEncoding
> > 	Korean (JOHAB), Thai (WIN874),
> > 	Vietnamese (TCVN), Arabic (WIN1256)
> > 
> > Added ClientEncoding
> > 	Simplified Chinese (GBK), Korean (UHC)
> > 
> > 
> > http://www.sankyo-unyu.co.jp/Pool/postgresql-7.2b2.newencoding.diff.tar.gz
> > (608K)
> 
> Looks good.  I need some people to review this for me.

For me they look good too. The only missing part is a
documentation. I will ask him to write it up. If he couldn't, I will
do it for him.

> The diff is 3mb
> but appears to address only additions to multibyte.  I have attached a
> list of files it modifies.  Also, look at the sizes of the mb/
> directory.  It is getting large:
> 	
> 	4       ./CVS
> 	6       ./Unicode/CVS
> 	3433    ./Unicode
> 	6197    .

Yes. We definitely need the on-the-fly encoding addition capability:
i.e. CREATE CHRACTER SET in the future...
--
Tatsuo Ishii


In response to

Responses

pgsql-patches by date

Next:From: Bruce MomjianDate: 2001-11-26 01:54:10
Subject: Re: Added Encoding
Previous:From: Bruce MomjianDate: 2001-11-26 00:34:03
Subject: Re: Support for QNX6, POSIX IPC and PTHREAD-style locking

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group