On Sat, Dec 16, 2023 at 1:48 PM Jeremy Schneider
<schneider@ardentperf.com> wrote:
> On 12/14/23 7:12 AM, Jeff Davis wrote:
> > The concern over unassigned code points is misplaced. The application
> > may be aware of newly-assigned code points, and there's no way they
> > will be mapped correctly in Postgres if the provider is not aware of
> > those code points. The user can either proceed in using unassigned code
> > points and accept the risk of future changes, or wait for the provider
> > to be upgraded.
>
> This does not seem to me like a good way to view the situation.
>
> Earlier this summer, a day or two after writing a document, I was
> completely surprised to open it on my work computer and see "unknown
> character" boxes. When I had previously written the document on my home
> computer and when I had viewed it from my cell phone, everything was
> fine. Apple does a very good job of always keeping iPhones and MacOS
> versions up-to-date with the latest versions of Unicode and latest
> characters. iPhone keyboards make it very easy to access any character.
> Emojis are the canonical example here. My work computer was one major
> version of MacOS behind my home computer.
That "SQUARE ERA NAME REIWA" codepoint we talked about in one of the
multi-version ICU threads was an interesting case study. It's not an
emoji, it entered real/serious use suddenly, landed in a quickly
wrapped minor release of Unicode, and then arrived in locale
definitions via regular package upgrades on various OSes AFAICT (ie
didn't require a major version upgrade of the OS).
https://en.wikipedia.org/wiki/Reiwa_era#Announcement
https://en.wikipedia.org/wiki/Reiwa_era#Technology
https://unicode.org/versions/Unicode12.1.0/