Text backend implementation boundary
Section titled “Text backend implementation boundary”Inno.Native.Text connects the managed text adapter to FreeType and HarfBuzz through the engine’s narrow native facade. Application code uses Inno.Text; host composition uses the managed adapter.
Native lifetime contract
Section titled “Native lifetime contract”The adapter owns each native runtime and its font faces. It keeps source and module ownership valid while shaping or rasterizing, checks transfer results and capacities, and releases native state after consumers finish. Native handles remain within this boundary; they are not persistent asset identities or script services.
Use shape text and rasterize glyphs for the engine’s logical-pixel and cluster conventions, and Text backend integration for provider composition and threading constraints.
Documentation scope
Section titled “Documentation scope”The native facade’s C ABI and generated bindings are implementation details and have no type/member reference here. The Text toolchain retains the engine’s actual preparation and deployment requirements.