Re: Locale, Encoding - Mailing list pgadmin-hackers

From Dave Page
Subject Re: Locale, Encoding
Date
Msg-id FED2B709E3270E4B903EB0175A49BCB104761C@dogbert.vale-housing.co.uk
Whole thread Raw
In response to Locale, Encoding  (Jean-Michel POURE <jm.poure@freesurf.fr>)
Responses Re: Locale, Encoding  (Jean-Michel POURE <jm.poure@freesurf.fr>)
List pgadmin-hackers

> -----Original Message-----
> From: Jean-Michel POURE [mailto:jm.poure@freesurf.fr]
> Sent: 26 February 2002 11:01
> To: pgadmin-hackers@postgresql.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

pgadmin-hackers by date:

Previous
From: Dave Page
Date:
Subject: Re: Database->ServerEncoding, ClientEncoding
Next
From: Jean-Michel POURE
Date:
Subject: Re: Locale, Encoding