>> So if we want to do a round trip conversion between >> EUC-JP and UTF-8, we have to choose either U+FF5E OR U+301C. We have >> chosen U+FF5E. If we change the mapping, many existing applications >> would break. > > I heard a request a few times for an additional one-directional conversion > from U+301C to EUC-JP (0xa1c1). It should not break existing applications. > We already have non-round trip conversions for IBM and NEC extended > characters in SJIS. The policy seems not so strict for me.
Doesn't breaking round-trip conversion between EUC-JP and UTF-8 itself break backward compatibility? I think what we can do best here is, adding new encoding and default conversion. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
