Tom Lane wrote:
> Dave Page <dpage@postgresql.org> writes:
>> However, setlocale() will also accept other valid combinations on
>> Windows, which initdb will not, for example:
>> "English_United Kingdom.28591" (Latin1)
>> Is there any reason not to accept other combinations that setlocale() is
>> happy with?
>
> Are you certain that that acceptance actually represents support?
> Have you checked that it rejects combinations involving real code
> pages (ie, NOT 65001) that don't really work with the locale?
It fails with ones that Microsoft have decided don't belong in my
language group and therefore aren't installed. It accepts all the others
I've tried, but then from the sample I've looked, they all have
0-9a-zA-Z in them so I guess they're all capable of handling English.
Regards, Dave.