Re: 8.3 can't convert cyrillic text from 'iso-8859-5' to other cyrillic 8-bit encoding

Поиск
Список
Период
Сортировка
От Sergey Burladyan
Тема Re: 8.3 can't convert cyrillic text from 'iso-8859-5' to other cyrillic 8-bit encoding
Дата
Msg-id 200803180328.49937.eshkinkot@gmail.com
обсуждение исходный текст
Ответ на 8.3 can't convert cyrillic text from 'iso-8859-5' to other cyrillic 8-bit encoding  (Sergey Burladyan <eshkinkot@gmail.com>)
Ответы Re: 8.3 can't convert cyrillic text from 'iso-8859-5' to other cyrillic 8-bit encoding  ("Heikki Linnakangas" <heikki@enterprisedb.com>)
Список pgsql-bugs
Hi, all !

i'm find the problem.

src/backend/utils/mb/conversion_procs/cyrillic_and_mic/cyrillic_and_mic.c
does not have cyrillic letter 'IO' in ISO-8859-5 to mule internal code
translation table (function iso2mic(const unsigned char *l, unsigned char *p,
int len)). this is bug, because it is widely used and it is main letter like
A, B or C in english :) and it is exist in all russian cyrillic's encoding
(koi8-r, iso-8859-5, windows-1251, cp866).
for example, in russian, words 'all', 'hedgehog', 'Christmas-tree' and many
other must be written with it.

here is the patch for add it to ISO-8859-5 to mule internal code translation
table. i am don't know is this ok and do not brake any internal rule or
code ?

By the way, as i can understand you are using koi8-r encoding for internal
representation of cyrillic charsets - this is have also another problem. the
second "widely" used char is <U2116> NUMERO SIGN (many accountants and
managers use it :) in cyrillic windows world) and it is exist in
windows-1251, cp866 and iso-8859-5 encoding, but not in koi8-r...

---

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: BUG #3809: SSL "unsafe" private key permissions bug
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: BUG #3983: pgxs files still missing in win32 install (8.3.1)