> I wanted to allow WIN1250 as a server-side encoding, in light of the > Windows port. Now I wonder why there are client-only encodings at all. > Without knowing details, it seems the client-only encodings are all > "Windows world" encodings. So was the original reason not to allow > these as server encodings that the server doesn't run on Windows? If > so, should the category client-only encodings be abolished?
I think it's not just possible for some multi-byte encodings such as SJIS(Shift-JIS) and Big5. Currently PostgreSQL will not accept them because of they include special ASCII characters such as back slashes. -- Tatsuo Ishii ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
