On Tuesday 07 April 2009 11:21:25 Heikki Linnakangas wrote: > Peter Eisentraut wrote: > > In practice you get either the GNU or the Solaris version of gettext, and > > at least the GNU version can cope with all the encoding names that the > > currently Windows-only code path produces. > > It doesn't. On my laptop running Debian testing: > > hlinn...@heikkilaptop:~$ LC_ALL=fi_FI.UTF-8 gettext > gettext: ei riittävästi argumentteja > hlinn...@heikkilaptop:~$ LC_ALL=fi_FI.LATIN1 gettext > gettext: missing arguments
That is because no locale by the name fi_FI.LATIN1 exists. > hlinn...@heikkilaptop:~$ LC_ALL=fi_FI.ISO-8859-1 gettext > gettext: ei riitt�v�sti argumentteja > > Using the name for the latin1 encoding in the currently Windows-only > mapping table, "LATIN1", you get no translation because that name is not > recognized by the system. Using the other name "ISO-8859-1", it works. > "LATIN1" is not listed in the output of locale -m either. You are looking in the wrong place. What we need is for iconv to recognize the encoding name used by PostgreSQL. iconv --list is the primary hint for that. The locale names provided by the operating system are arbitrary and unrelated. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
