On 8/15/17 15:04, Peter Geoghegan wrote: > * "23.2.2.3. Copying Collations" suggests that the only use of CREATE > COLLATION is copying collations, which is far from true with ICU. We > should change that at the same time as this change is made. I think > that just changing the title would improve the overall flow of the > page.
I don't understand why that has to be changed and how. > * Maybe add an example of numeric ordering -- the "alphanumeric > invoice" case, where you want text containing numbers to have the > numbers sort as numbers iff the comparison is to be resolved when > comparing numbers. I think that that's really useful, and worth > specifically calling out. I definitely would have used that had it > been available ten years ago. done, quite useful > * Let's use "en-u-kr-others-digit" instead of "en-u-kr-latn-digit' in > the example. It makes no real difference to us English speakers, but > means that the example works the same for those that use a different > alphabet. It's more culturally neutral. I follow what you are saying, but that locale string is not accepted by CREATE COLLATION. > * If we end up having initdb put all locales rather than all > collations in pg_collation, which I think is very likely, then we can > put in a link to ICU's locale explorer web resource: > > https://ssl.icu-project.org/icu-bin/locexp?d_=en&_=en_HK > > This lets the user see exactly what they'll get from a base locale > using an intuitive interface (assuming it matches their CLDR version). done Patch has been posted to another thread. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
