Bug 35825 - iOS function CTFontManagerCreateFontDescriptorsFromURL has no C# wrapper
Summary: iOS function CTFontManagerCreateFontDescriptorsFromURL has no C# wrapper
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: XI 9.1 (iOS 9.1)
Hardware: Macintosh Mac OS
: Normal enhancement
Target Milestone: (C7)
Assignee: Manuel de la Peña [MSFT]
Depends on:
Reported: 2015-11-12 19:08 UTC by Peter Golde
Modified: 2016-06-03 13:55 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Peter Golde 2015-11-12 19:08:35 UTC
There does not appear to be a Xamarin.iOS wrapper for the CoreText function CTFontManagerCreateFontDescriptorsFromURL. This is documented at: https://developer.apple.com/library/ios//documentation/Carbon/Reference/CoreText_FontManager_Ref/index.html and marked as available in iOS 7.0 and later.
Comment 2 Abhishek 2016-06-03 13:55:19 UTC
I have checked this issue with latest C7 build:
xamarin.ios- Now I am able to see CTFontManagerCreateFontDescriptorsFromURL under CTFontManager. Here is the screencast for the same: http://www.screencast.com/t/Uoc5mvmYrfPN

Hence closing this issue.