Re: 回复: May "PostgreSQL server side GB18030 character set support" reconsidered?

>> 1. In this big data and mobile era, in the country with most population, 50% more disk energy consuming for Chinese characters (UTF-8 usually 3 bytes for a Chinese character, while GB180830 only 2 bytes) is indeed a harm to "Carbon Neutral", along with Polar ice melting.
>
> Really? I thought GB18030 uses up to 4 bytes.
> https://en.wikipedia.org/wiki/GB_18030#Encoding
>
> --Parker:
> More preciously description should be GB18030 use 2 or 4 bytes for Chinese characters.
> It's a bit complicated to explain with only words but easy with help of the following graph.
>
> Most frequently used 20902 Chinese characters and 984 symbols in GBK is encoded with 2 bytes, which is a subset of GB18030.

It does not sound fair argument unless you are going to implement only
GBK compatible part of GB18030.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp