Hi,
this is final version (I hope) of multibyte clean up.
All routines as input accept "more standard" encoding names, but all
names on outputs are back compatible.
New names is possible obtain only by:
database_character_set()
- returns database encoding name
character_set(int)
- convert encoding 'id' to encoding name
character_set(name)
- convert encoding 'name' to 'id'
The configure.in is not changed.
All encoding map files are renamed to standard and lower case names.
... and other changes described in last versions of this patch
Don't forget for CVS commit:
* following files are renamed:
src/utils/mb/Unicode/KOI8_to_utf8.map -->
src/utils/mb/Unicode/koi8r_to_utf8.map
src/utils/mb/Unicode/WIN_to_utf8.map -->
src/utils/mb/Unicode/win1251_to_utf8.map
src/utils/mb/Unicode/utf8_to_KOI8.map -->
src/utils/mb/Unicode/utf8_to_koi8r.map
src/utils/mb/Unicode/utf8_to_WIN.map -->
src/utils/mb/Unicode/utf8_to_win1251.map
* new file:
src/utils/mb/encname.c
* removed file:
src/utils/mb/common.c
Examples:
l2=# select getdatabaseencoding(), database_character_set();
getdatabaseencoding | database_character_set
---------------------+------------------------
LATIN2 | ISO-8859-2
(1 row)
l2=# select pg_encoding_to_char(5), character_set(5);
pg_encoding_to_char | character_set
---------------------+---------------
UNICODE | UTF-8
(1 row)
l2=# select pg_char_to_encoding('Latin2'), character_set('Latin2');
pg_char_to_encoding | character_set
---------------------+---------------
8 | 8
(1 row)
test=# select pg_char_to_encoding('ISO-8859-3'), character_set('Latin3');
pg_char_to_encoding | character_set
---------------------+---------------
9 | 9
(1 row)
Karel
--
Karel Zak <zakkr@zf.jcu.cz>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
