Re: [HACKERS] Inconsistent Conversion Names
Oleg Bartunov writes: Someone said that the conversion table is actually koi8r + koi8u, being different from IANA's koi8_r. Not sure though. I found mention in the archives by Oleg B. that it is in fact koi8_r. on my system (linux) I have ru_RU.KOI8-R locale. We're not talking about your system. :-) Do you know whether PostgreSQL's conversion tables cover koi8-r or koi8-u or both? The documentation contains contradicting information about that. Actually, since we use the officially provided Unicode conversion tables, we should know what they cover. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Inconsistent Conversion Names
Tatsuo Ishii writes: The conversion named SJIS is different from IANA's shift_jis. It actually matches Windows-31J in IANA, which is too ugly to being emploied as our conversion name, IMO. OK I agree with win1250 - windows_1250, win1251 - windows_1251, but do not agree with renaming win866. There's no windows_866 in IANA. Maybe that should be ibm866? Is it ibm866 or are you wondering yourself? Someone said that the conversion table is actually koi8r + koi8u, being different from IANA's koi8_r. Not sure though. I found mention in the archives by Oleg B. that it is in fact koi8_r. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Inconsistent Conversion Names
On Thu, 19 Sep 2002, Peter Eisentraut wrote: Tatsuo Ishii writes: The conversion named SJIS is different from IANA's shift_jis. It actually matches Windows-31J in IANA, which is too ugly to being emploied as our conversion name, IMO. OK I agree with win1250 - windows_1250, win1251 - windows_1251, but do not agree with renaming win866. There's no windows_866 in IANA. Maybe that should be ibm866? Is it ibm866 or are you wondering yourself? it's a total mess. I know CP866, CP-866,IBM866,IBM_866 IANA isn't a standard but a recommendation. glibc uses name mangling, so KOI8-R - koi8r Someone said that the conversion table is actually koi8r + koi8u, being different from IANA's koi8_r. Not sure though. I found mention in the archives by Oleg B. that it is in fact koi8_r. on my system (linux) I have ru_RU.KOI8-R locale. Regards, Oleg _ Oleg Bartunov, sci.researcher, hostmaster of AstroNet, Sternberg Astronomical Institute, Moscow University (Russia) Internet: [EMAIL PROTECTED], http://www.sai.msu.su/~megera/ phone: +007(095)939-16-83, +007(095)939-23-83 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Inconsistent Conversion Names
I thought you had named the conversion functions after the IANA names. I found the following inconsistencies, however: sjis should be shift_jis The conversion named SJIS is different from IANA's shift_jis. It actually matches Windows-31J in IANA, which is too ugly to being emploied as our conversion name, IMO. win1250 should be windows_1250 (similarly 866, 1251) I agree with win1250 - windows_1250, win1251 - windows_1251, but do not agree with renaming win866. There's no windows_866 in IANA. Maybe that should be ibm866? koi8r should be koi8_r Someone said that the conversion table is actually koi8r + koi8u, being different from IANA's koi8_r. Not sure though. -- Tatsuo Ishii ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
