Re: Supporting SJIS as a database encoding
От | Tsunakawa, Takayuki |
---|---|
Тема | Re: Supporting SJIS as a database encoding |
Дата | |
Msg-id | 0A3221C70F24FB45833433255569204D1F5E73D3@G01JPEXMBYT05 обсуждение исходный текст |
Ответ на | Re: Supporting SJIS as a database encoding (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>) |
Список | pgsql-hackers |
From: pgsql-hackers-owner@postgresql.org > [mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of Kyotaro > Thanks, by the way, there's another issue related to SJIS conversion. MS932 > has several characters that have multiple code points. By converting texts > in this encoding to and from Unicode causes a round-trop problem. For > example, > > 8754(ROMAN NUMERICAL I in NEC specials) > => U+2160(ROMAN NUMERICAL I) > => FA4A (ROMAN NUMERICA I in IBM extension) > > My counting said that 398 characters are affected by this kind of replacement. > Addition to that, "GAIJI" (Private usage area) is not allowed. Is this meet > your purpose? Supporting GAIJI is not a requirement as far as I know. Thank you for sharing information. # I realize my lack of knowledge about character sets... Regards Takayuki Tsunakawa
В списке pgsql-hackers по дате отправления: