| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Proposal: Adding CP51932 encoding |
| Date: | 2007-03-30 13:02:26 |
| Message-ID: | 20070330.220226.132899725.t-ishii@sraoss.co.jp |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Here is a proposal to add a client side encoding CP51932. CP51932 is
an encoding for Japanese, defined by Microsoft. It is similar to
existing EUC_JP encoding but some characters are mapped
differently. Unfortunately for most Windows apps "EUC-JP" means
CP51932. As a result, for example, if a web page is encoded with
EUC-JP, web browsers will encode users' input as CP51932 and save data
to PostgreSQL database as CP51932, which is not what PostgreSQL
expects of course. Adding CP51932 <--> EUC_JP conversion should solve
the problem (CP51932 <--> UTF-8 and SJIS should be added too).
If there's no objection, patches for current will be posted for a
review (patches have been develpped by a Japanese developer, not me).
Comments and suggestions are welcome.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-03-30 15:01:27 | Re: Autovacuum vs statement_timeout |
| Previous Message | Hannu Krosing | 2007-03-30 12:14:17 | Re: Proposal: include PL/Proxy into core |