Perhaps an issue on the collation page?

Started by PG Bug reporting formalmost 3 years ago2 messagesdocs
Jump to latest
#1PG Bug reporting form
noreply@postgresql.org

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/15/collation.html
Description:

This page states:

Observe how in the traditional ICU locale naming system, the root locale
is selected by an empty string.

CREATE COLLATION latinlast (provider = icu, locale =
'en-u-kr-grek-latn');
CREATE COLLATION latinlast (provider = icu, locale =
'en@colReorder=grek-latn');

Neither of the locales are empty strings.

#2Laurenz Albe
laurenz.albe@cybertec.at
In reply to: PG Bug reporting form (#1)
Re: Perhaps an issue on the collation page?

On Wed, 2023-04-26 at 21:20 +0000, PG Doc comments form wrote:

Page: https://www.postgresql.org/docs/15/collation.html

This page states:

  Observe how in the traditional ICU locale naming system, the root locale
is selected by an empty string.

  CREATE COLLATION latinlast (provider = icu, locale =
'en-u-kr-grek-latn');
  CREATE COLLATION latinlast (provider = icu, locale =
'en@colReorder=grek-latn');

Neither of the locales are empty strings.

The sentence with the "empty string" refers to the example that was before:

CREATE COLLATION "und-u-co-emoji-x-icu" (provider = icu, locale = '@collation=emoji');

There is nothing, that is an ampty string, before the "@".

Yours,
Laurenz Albe