| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: More message encoding woes |
| Date: | 2009-04-07 08:21:25 |
| Message-ID: | 49DB0D05.8070101@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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:
hlinnaka(at)heikkilaptop:~$ LC_ALL=fi_FI.UTF-8 gettext
gettext: ei riittävästi argumentteja
hlinnaka(at)heikkilaptop:~$ LC_ALL=fi_FI.LATIN1 gettext
gettext: missing arguments
hlinnaka(at)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.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergey Burladyan | 2009-04-07 09:14:26 | Re: XML only working in UTF-8 - Re: 8.4 open items list |
| Previous Message | Heikki Linnakangas | 2009-04-07 07:27:57 | Re: more on out-of-memory |