Re: Locale, Encoding

From: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
To: "'jm(dot)poure(at)freesurf(dot)fr'" <jm(dot)poure(at)freesurf(dot)fr>, pgadmin-hackers(at)postgresql(dot)org
Subject: Re: Locale, Encoding
Date: 2002-02-26 11:27:35
Message-ID: FED2B709E3270E4B903EB0175A49BCB104761C@dogbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

> -----Original Message-----
> From: Jean-Michel POURE [mailto:jm(dot)poure(at)freesurf(dot)fr]
> Sent: 26 February 2002 11:01
> To: pgadmin-hackers(at)postgresql(dot)org
> Subject: [pgadmin-hackers] Locale, Encoding
>
>
> > LCID is the Windows Locale ID
> > If it's not important, ignore it.
>
> Locales and encodings are different:
> Locale : "fr_fr",
> Encoding : "Latin1".
>
> I guess LCID is not a locale but a font ID. What should $M
> express locales
> using IDs?
>
> Still I don't know if we should keep ServerEncodingID (Long) and
> ClientEncodingID (Long). I don't see how these numbers can be
> used. Do you?

No, and your probably right, we could drop them altogether and just keep the
text ones. We're already changing the name of the encoding string property
so changing the interface again ain't gonna hurt.

/D

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Jean-Michel POURE 2002-02-26 12:08:50 Re: Database->ServerEncoding, ClientEncoding
Previous Message Dave Page 2002-02-26 11:20:51 Re: Database->ServerEncoding, ClientEncoding