icu VS MacOSX-SDKs

If you want graphemes, something lile libgrapheme might suit you. If just code points, then the utf8.h from ICU can work, but you can also roll your own if needed.

OP, is this money in the context of storing and counting money, or money in the context of internationalization and localization? For the latter, you probably want bindings to icu or the x/text/currency package.

https://github.com/unicode-org/icu/pull/2213

This affects all packages that have icu as a dependency, one of them being Node.js.

https://github.com/nodejs/node/issues/37271

I discovered this the hard way when some code malfunctioned shortly after daylight savings time kicked in.

No clue! It seems like a very deep rabbit hole to go down. You can start here: https://github.com/unicode-org/icu Version 72 I believe is when this was changed.

Installing icu4c from https://github.com/unicode-org/icu/releases/tag/release-71-1 and put the path in "--with-icu-lib"

wget https://github.com/unicode-org/icu/archive/release-58-3.tar.gz

You need something like icu. https://github.com/unicode-org/icu

ICU, which ships as part of the core internationalization and localization frameworks of every major operating system, has a facility for transliterating keyboards! This is how you can type in Roman characters and get Devanagari in text, or enter pinyin and get Han characters. You can compose a Hiragana to Latin transliteration — but it’s a stretch to get actual English words this way.

We are making really good progress and will have a prototype in the next month or so. See the Github issues for Linux[1] and Windows[2]

[0] https://github.com/phracker/MacOSX-SDKs/blob/master/MacOSX10...

[1] https://github.com/withfig/fig/issues/34

[2] https://github.com/withfig/fig/issues/35

Ah, really? :/ I was only trying to help as I’ve needed some in the past and the repos I’ve found before have been up for years (eg https://github.com/phracker/MacOSX-SDKs) with no apparent issues, but may not have had the latest SDKs. I assume if Apple had an issue they’d contact me? Of course I’d remove it immediately if asked.

Another approach for this is to explore the format through Apple's tools for building dictionaries – as they still provide a "Dictionary Development Kit" in Xcode's downloadable "Additional Tools" package (which has documentation for the XML format).

It turns out that dictionary bundles are entirely supported by system APIs in CoreServices! The APIs are private, but Apple accidentally shipped a header file with documentation for them in the 10.7 SDK [1].

[1] https://github.com/phracker/MacOSX-SDKs/blob/master/MacOSX10...

You still need the target SDK extracted from XCode: https://github.com/phracker/MacOSX-SDKs