pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Finnerty, Jim <jfinnert@amazon.com>
To: Robert Haas <robertmhaas@gmail.com>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Julien Rouhaud <rjuju123@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Cc: Daniel Verite <daniel@manitou-mail.org>
Subject: Re: ICU for global collation
Date: Tue, 15 Mar 2022 19:47:09 +0000
Message-ID: <3D155AD2-1500-40CC-9003-465FE6280B6A@amazon.com> (raw)
In-Reply-To: <CA+Tgmobw227bwuHk6kwjriFQUofnZoAQhL1j3eYJyCcNO8u4MA@mail.gmail.com>
References: <a6f807c2-2d11-2cf6-a524-cfbec56e7d5b@enterprisedb.com>
	<20220118040246.dewl5pain2gkv2iv@jrouhaud>
	<171c5f7c-43ee-dbe9-31f9-5e3eb06a54cf@enterprisedb.com>
	<e381e36c-c7a2-2ec0-dbb4-da1dab3f0941@enterprisedb.com>
	<20220121135119.ywszwl4353v5dzh5@jrouhaud>
	<e2061949-f731-fd60-8b0b-3bae75095b4f@enterprisedb.com>
	<20220121161331.xn7fhtfg5j2ucilb@jrouhaud>
	<87e93704-b7f7-71f6-161d-8713e6334ed3@enterprisedb.com>
	<704405ed-f1fa-d2a7-b9f9-48a07fb45648@enterprisedb.com>
	<96a50803-72ba-8eec-948a-d87608ac15a0@enterprisedb.com>
	<20220305083830.lpz3k3yku5lmm5xs@jrouhaud>
	<42ce518d-1426-fa9e-1fcc-de090cd55331@enterprisedb.com>
	<CA+Tgmoaqb+3nAMgHVoSWeHu-58hBzfDevqmZOy2-HuDZJgkCzQ@mail.gmail.com>
	<ecac910c-d3d3-1d39-1040-2021f3551c69@enterprisedb.com>
	<CA+Tgmobw227bwuHk6kwjriFQUofnZoAQhL1j3eYJyCcNO8u4MA@mail.gmail.com>

Can we get some more consistent terminology around the term "locale"?

In ICU, the "locale" is just the first part of what we can pass to the "locale" parameter in CREATE COLLATION - the part before the optional '@' delimiter.  The ICU locale does not include the secondary or tertiary properties, so it is usually just the country and the language, e.g. en_US (or en-US), but it can also be something like es_TRADITIONAL for traditional Spanish.  

I think it would be an improvement in clarity if we consistently use the term 'locale' to mean the same thing that ICU means by that term, and not to have the thing that we call the "locale" also include collation modifiers, or to imply that a locale is the same thing as a collation.

    /Jim






view thread (111+ messages)  latest in thread

Message-ID: <3D155AD2-1500-40CC-9003-465FE6280B6A@amazon.com>
Permalink:  ../3D155AD2-1500-40CC-9003-465FE6280B6A@amazon.com/
Also on:    postgresql.org/message-id/3D155AD2-1500-40CC-9003-465FE6280B6A@amazon.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: jfinnert@amazon.com, robertmhaas@gmail.com, peter.eisentraut@enterprisedb.com, rjuju123@gmail.com, daniel@manitou-mail.org
  Subject: Re: ICU for global collation
  In-Reply-To: <3D155AD2-1500-40CC-9003-465FE6280B6A@amazon.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox