You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This month’s release includes a big change with CoreText now leveraging DirectWrite behind the scene instead of FreeType. This implementation offers several key advantages over the previous one:
Windows DirectWrite API supports measuring, drawing, and hit-testing of multi-format text
DirectWrite also provides a low-level glyph rendering API for developers who want to perform their own layout and Unicode-to-glyph processing
DirectWrite handles text in all supported languages for global and localized applications
Once we’ll have moved our CoreGraphics stack to Direct2D (more details about this coming change here), CoreText will be able to use hardware accelerated text rendering. For now, CoreText uses IWICBitmap to render text
Most of DirectWrite constructs to format and layout text map pretty well with CoreText. This lets us back most of the CoreText objects with DirectWrite object, allowing us to interact with DirectWrite in the backend without affecting the user facing CoreText APIs. You can find all the details about this change in the spec available here.
The text was updated successfully, but these errors were encountered:
This month’s release includes a big change with CoreText now leveraging DirectWrite behind the scene instead of FreeType. This implementation offers several key advantages over the previous one:
Most of DirectWrite constructs to format and layout text map pretty well with CoreText. This lets us back most of the CoreText objects with DirectWrite object, allowing us to interact with DirectWrite in the backend without affecting the user facing CoreText APIs. You can find all the details about this change in the spec available here.
The text was updated successfully, but these errors were encountered: