Skip site navigation (1) Skip section navigation (2)

Re: US-ASCII on Mac OS X

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Perry Smith <pedz(at)easesoftware(dot)net>, pgsql-ports(at)postgresql(dot)org
Subject: Re: US-ASCII on Mac OS X
Date: 2004-07-20 16:34:02
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-ports
Perry Smith wrote:
> I'm wondering how to solve this problem.  Should a "usascii" alias be
> added to encnames.c?

Probably not, considering that PostgreSQL does not really support 
US-ASCII as such.  (Supersets of US-ASCII are supported, but when you 
select a charset, you don't want a superset of that charset.)

> Should gnucash change "US-ASCII" into something else?


> Should I try and get Apple to change their code since it is
> not really a code page?

It is a code page (or an encoding, or a charset, or something or that 
sort).  Several operating systems seem to agree.

> Should I just remove the "ENCODING ..."
> phrase from the command that gnucash creates to create a database

I would probably create the database without an encoding specification 
and thus use the default encoding, since that will cooperate best with 
the character processing functions and the user's expectations in 
general.  Gnucash should, like any client, set the client encoding to 
its actual encoding used on the frontend, and then the encoding used on 
the server side does not need to be of concern.

> under the logic that postgres will using the encoding specified by
> the LANG variable by default anyway (which I'm just guessing is what
> it does)?

No, scrap that logic.  You need to set the client encoding yourself.

Peter Eisentraut

In response to


pgsql-ports by date

Next:From: Perry SmithDate: 2004-07-20 20:37:04
Subject: Re: US-ASCII on Mac OS X
Previous:From: Perry SmithDate: 2004-07-20 15:49:03
Subject: US-ASCII on Mac OS X

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group