| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Oscar Carlberg <oscar(dot)carlberg(at)fortnox(dot)se>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: ICU, locale and collation question |
| Date: | 2023-05-09 15:24:09 |
| Message-ID: | e581e338-deea-2901-aa37-bf882077c377@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 09.05.23 08:54, Oscar Carlberg wrote:
> Our initdb setup would then look like this for compatibility;
> -E 'UTF-8'
> --locale-provider=icu
> --icu-locale=sv-SE-x-icu
> --lc_monetary=sv_SE.UTF-8
> --lc-numeric=sv_SE.UTF-8
> --lc-time=sv_SE.UTF-8
> --lc-messages=en_US.UTF-8
>
> Should we still provide createdb with --lc-collate=C and --lc-ctype=C,
> or should we set those to sv_SE.UTF-8 as well?
You should set those to something other than C. It doesn't matter much
what exactly, so what you have there is fine.
Setting it to C would for example affect the ability of the text search
functionality to detect words containing non-ASCII characters.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steven Lembark | 2023-05-09 21:11:04 | Re: Return rows in input array's order? |
| Previous Message | Laurenz Albe | 2023-05-09 13:31:19 | Re: ICU, locale and collation question |