From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
---|---|
To: | "Craig Ringer" <craig(at)postnewspapers(dot)com(dot)au> |
Cc: | "Kern Sibbald" <kern(at)sibbald(dot)com>, pgsql-general(at)postgresql(dot)org, "bacula-devel" <bacula-devel(at)lists(dot)sourceforge(dot)net>, "bacula-users" <bacula-users(at)lists(dot)sourceforge(dot)net> |
Subject: | Re: Catastrophic changes to PostgreSQL 8.4 |
Date: | 2009-12-03 11:18:31 |
Message-ID: | 939023cf-6ef5-4bfd-909f-7dc7fc235bbc@mm |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Craig Ringer wrote:
> While true in theory, in practice it's pretty unusual to have filenames
> encoded with an encoding other than the system LC_CTYPE on a modern
> UNIX/Linux/BSD machine.
It depends. In western Europe, where iso-8859-1[5] and utf8 are evenly used,
it's not unusual at all. You just have to extract an archive created by
someone who uses a different encoding than you. Since tar files don't carry
any information about the encoding of the filenames it contains, they come
out as they are, whatever LC_CTYPE is. The same problem exists for zip files.
Best regards,
--
Daniel
PostgreSQL-powered mail user agent and storage: http://www.manitou-mail.org
From | Date | Subject | |
---|---|---|---|
Next Message | Kern Sibbald | 2009-12-03 11:22:50 | Re: [Bacula-users] Catastrophic changes to PostgreSQL 8.4 |
Previous Message | Dave Page | 2009-12-03 10:48:22 | PostgreSQL@FOSDEM 2010 - Call for talks |
From | Date | Subject | |
---|---|---|---|
Next Message | Kern Sibbald | 2009-12-03 11:22:50 | Re: [Bacula-users] Catastrophic changes to PostgreSQL 8.4 |
Previous Message | Avi Rozen | 2009-12-03 10:35:29 | Re: [Bacula-users] Catastrophic changes to PostgreSQL 8.4 |