Pretty sure the reason is a simple one. If you look at the history of open source in the OS on the Apple open source page, you'll notice they pretty much bump the ICU version they use annually. Although unlikely, ICU might change in ways that breaks your app. They don't want to support ICU directly. It's a pretty tough API in C or C++
You could always build your own version and bundle it. If you download the open source version they post you'll get the right settings. It's not easy to build it right, but it's doable and you can link to one you build and bundle in your app. Linking to theirs would leave them beholden to a fast outdated version to support your app. Sent from my iPhone > On 6 Oct 2016, at 18:32, Gary L. Wade <garyw...@desisoftsystems.com> wrote: > > My experience has been that last year (iOS 9 and OS X 10.11) Apple made ICU a > private framework worthy of rejection from its App Store if you used its APIs > directly. I encountered this because like in years past when Apple did not > provide ICU through a higher-level framework, we were encouraged to call ICU > directly, and that's when I supplied a signature to translate between > 2-letter and 3-letter language codes to work around the no-headers issue, > which I needed to support a 3rd party services requirement. However, the app > was rejected as using a private API. I was going to challenge it, but my > management decided we should hard code the mappings. > -- > Gary L. Wade (Sent from my iPad) > http://www.garywade.com/ > >> On Oct 6, 2016, at 1:22 AM, Gerriet M. Denkmann <g...@mdenkmann.de> wrote: >> >> The Icu stuff (57.1) is included in macOS 12. >> >> There is: >> /usr/lib/libicucore.A.dylib >> >> and Xcode has: >> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/lib/libicucore.tbd >> >> >> But I cannot find the headers. >> >> Gerriet. >> >> >> _______________________________________________ >> >> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) >> >> Please do not post admin requests or moderator comments to the list. >> Contact the moderators at cocoa-dev-admins(at)lists.apple.com >> >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/cocoa-dev/garywade%40desisoftsystems.com >> >> This email sent to garyw...@desisoftsystems.com > > > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com > > This email sent to dangerwillrobinsondan...@gmail.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
