apple-text-core-text

To get glyph-level metrics and positions when TextKit 2 lacks glyph APIs, use Core Text APIs like CTLine and CTRun. These allow you to inspect per-glyph bounds and compute precise positions for an attributed string during custom typesetting.

Yes, you can access OpenType features and font tables using CTFont on iOS and macOS. Core Text allows you to retrieve detailed font metrics and inspect font tables directly for custom typography pipelines, bridging with UIFont or NSFont as needed.

The best way to implement precise hit-testing for custom text layouts is by applying Core Text APIs. Using CTFrame, CTLine, and CTRun provides robust hit-testing capabilities across Apple platforms where TextKit 2 APIs are insufficient.

You need Core Text instead of TextKit 2 for custom typesetting when you require direct access to glyph-level rendering, font table inspection, or per-glyph positioning. Core Text exposes these low-level APIs which TextKit 2 does not provide.

To bridge UIFont or NSFont to CTFont for custom rendering, you utilize Core Text interoperability functions. This bridging allows you to pass standard UIKit or AppKit font objects into Core Text pipelines to maintain consistent font metrics across iOS and macOS.

Yes, Core Text supports per-glyph rendering across iOS and macOS. By leveraging CTLine, CTRun, and CTFrame, you can achieve fine-grained rendering control and inspect individual glyph bounds for your custom text rendering scenarios.