Added to open list:
o allow installed encodings and locales rather than just
hardcoded ones
and
o update encoding list to include win1250
o synchonize supported encodings and docs
---------------------------------------------------------------------------
Aleksander Kmetec wrote:
> Dave Page wrote:
> >>initdb.log says:
> >>initdb: "WIN1250" is not a valid server encoding name
> >
> > OK, it would seem that some of the encodings listed in
> > src/backend/utils/mb/encnames.c are not listed as supported on
> > http://developer.postgresql.org/docs/postgres/multibyte.html (that
> > includes win1250). I have limited the list to exactly what's in the
> > documentation.
>
> I've also noticed a problem with locales.
>
> Installer uses a static list of locales copied from MSDN. Because of
> this, not all locales installed on the current system are listed as
> available. Also, if you only supply a locale name to initdb, then the
> default encoding for that locale is used as value for lc_* settings
> (German_Germany.1252, Slovenian_Slovenia.1250, ...). This causes errors
> in sorting order and wrong return values for locale dependant functions
> when your database encoding differs from locale encoding.
>
> If there's nobody else working on this yet, I can try doing it myself,
> since I already have a piece of code which retrieves all installed
> locales and code pages for the current system.
>
> Regards, Aleksander
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073