On Fri, 2023-03-10 at 10:59 +0100, Peter Eisentraut wrote:
> I think originally the locale forced the encoding. With ICU, we have
> a
> choice. We could either stick to the encoding suggested by the OS,
> or
> pick our own.
We still need LC_COLLATE and LC_CTYPE to match the database encoding
though. If we get those from the environment (which are connected to an
encoding), then I think we need to get the encoding from the
environment, too, right?
> Arguably, if we are going to nudge toward ICU, maybe we should nudge
> toward UTF-8 as well.
The OSes are already doing a pretty good job of that. Regardless, we
need to remove the dependence on LC_CTYPE and LC_COLLATE when the
provider is ICU first (we're close to that point but not quite there).
Regards,
Jeff Davis
