Re: Explanations not clear

2024-05-13 Thread Jeff Davis
That explains the mechanism but detracts from the examples. Another option is to say that all the examples in the table are using ka-shifted for illustration purposes. I like this option, but it's a bit awkward because it refers to something that hasn't been explained yet. It's also

Re: Documenting more pitfalls of non-default collations?

2024-06-11 Thread Jeff Davis
ave a section in the docs on "case folding" to describe the right way to use it. That still leaves one caveat: the handling of dotted- and dotless-i. But one caveat is a lot easier to keep track of. Regards, Jeff Davis

Re: Initcap works differently with different locale providers

2025-07-30 Thread Jeff Davis
uld not be relied upon (at least for ICU; maybe for all providers). If you want specific word boundary rules, write your own function. Regards, Jeff Davis [1] https://unicode-org.github.io/icu-docs/apidoc/dev/icu4c/stringoptions_8h.html#a4975f537b9960f0330b233061ef0608d

Re: Initcap works differently with different locale providers

2025-08-04 Thread Jeff Davis
w-up patches? Or, just revert the change and I can make the improvements in master. Regards, Jeff Davis

Re: Initcap works differently with different locale providers

2025-08-06 Thread Jeff Davis
this, since it was not a bug > fix.  And it turns out it was incomplete.  I think we should revert > all > the backpatches and iterate on getting the documentation the way we > want > in master. +1. Regards, Jeff Davis

Re: Initcap works differently with different locale providers

2025-08-20 Thread Jeff Davis
On Mon, 2025-08-18 at 00:44 +0300, Alexander Korotkov wrote: > I'd like to propose a new version of patch. Nit: it only uses the title case in ICU or builtin PG_UNICODE_FAST. Regards, Jeff Davis