| From: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
|---|---|
| To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
| Cc: | parker(dot)han(at)outlook(dot)com, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: 回复: May "PostgreSQL server side GB18030 character set support" reconsidered? |
| Date: | 2020-10-06 02:15:35 |
| Message-ID: | 20201006.111535.752511901399890715.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> Hmm ... interesting idea, basically invent our own modified version
> of GB18030 (or SJIS?) for backend-internal storage. But I'm not
> sure how to make it work without enlarging the string, which'd defeat
> the OP's argument. It looks to me like the second-byte code space is
> already pretty full in both encodings.
But as he already admitted, actually GB18030 is 4 byte encoding, rather
than 2 bytes. So maybe we could find a way to map original GB18030 to
ASCII-safe GB18030 using 4 bytes.
As for SJIS, no big demand for the encoding in Japan these days. So I
think we can leave it as it is.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2020-10-06 03:11:42 | Re: 回复: May "PostgreSQL server side GB18030 character set support" reconsidered? |
| Previous Message | Han Parker | 2020-10-06 01:46:25 | 回复: 回复: May "PostgreSQL server side GB18030 character set support" reconsidered? |