TextFlow provides line breaking, bidirectional text, glyph shaping, font fallback, visual runs, and caret positioning. Caller-owned buffers make memory use explicit. The optional alloc feature provides a workspace that either grows private pipeline storage on demand or reserves fixed capacities before layout.
Used by
mirui uses TextFlow for bounded Unicode analysis, shaping, line layout, and caret placement with MIRX and OpenType font sources across software, GPU, and web renderers.
Demo
use TextFlow;
let text = "A small UI can still set type well.";
let lines = new
.map
.;
assert_eq!;
Explicit LF, CR and CRLF separators retain original UTF-8 offsets and produce line boundaries without font glyphs. Leading, consecutive and terminal separators retain blank lines and their caret positions. CRLF is one break with no intermediate caret. Layout, run and caret capacities remain caller-controlled.
Enable shaping and pass a font adapter implementing Typeface for positioned text:
use ;
use Typeface;
Glyphs are in visual order; cluster ranges address the original UTF-8 text. Width, line height, and coordinates use the font adapter's units. The site guides cover font data, mixed direction, overflow, and baseline placement.
Playground
The browser playground visualizes line breaks, Unicode clusters, bidi runs, positioned glyphs, carets, script providers, workspace limits, and spline-smoothed baseline placement. Glyph layout uses Lato Regular to show font-backed kerning and fi/fl ligatures. Baselines includes freehand curves, an Odyssey portrait example, and copyable Rust FlowPoint slices. Its scaffold generates compile-checked examples from the selected Cargo features using the released crate version. A budget panel shows reference WASM size, memory capacities, metered work, and browser-measured throughput.
Local development requires wasm-pack, Trunk, and the wasm32-unknown-unknown Rust target.
Open http://127.0.0.1:8137/. The display uses a synthetic glyph source; layout coordinates and errors come from TextFlow.
Text layout and shaping
#![no_std]by default with acore-only runtime.- Caller-owned buffers with explicit capacity and unsupported-text errors.
- Format-neutral
TypefaceandGlyphSourceinterfaces for TTF, OpenType, MIRX, flash-backed assets, and application-specific font stores. - Stable glyph IDs, UTF-8 cluster ranges, visual bidi runs, safe line boundaries, and caret positions.
- Borrowed per-line widths let shaped paragraphs follow baselines with different usable lengths.
- Optional baseline placement maps positioned glyphs and carets onto borrowed line, polyline, or indexed provider geometry using caller-owned frame buffers.
- Optional reusable heap workspace with element and byte limits, lazy growth or fixed pre-reserved capacities, and direct caller-owned output.
Embedded footprint
The ESP32-C3 demo runs bidirectional resolution, font selection, shaping, wrapping, visual reordering, glyph positioning, and caret generation without an allocator. One fixed-capacity LayoutScratch value owns all reusable working storage.
With alloc enabled, TextWorkspace::try_new_bounded(limits, capacity) reserves the private run, glyph, scratch-glyph, and line buffers before layout. Later requests beyond those capacities return a capacity error. Final glyphs, visual runs, lines, and carets still belong to the caller and need separately sized output slices; LayoutLimits::memory_bytes covers only the workspace's private buffers.
Measured with Rust 1.97.0, esp-hal 1.1.0, size optimization, LTO, one codegen unit, and aborting panics:
| ESP32-C3 release image | App partition | Static RAM (.data + .bss) |
|---|---|---|
| ESP-HAL baseline | 73,536 B | 808 B |
| Full TextFlow pipeline | 87,056 B | 824 B |
| TextFlow delta | 13,520 B | 16 B |
The demo's main stack frame is 2,272 B, including a 2,016 B LayoutScratch. Heap usage is 0 B. Run examples/esp32c3/measure.sh to rebuild both images and reproduce the Flash and static RAM comparison.
Feature flags
| Feature | Adds |
|---|---|
unicode |
Bounded grapheme, line-break, and script classification |
bidi |
Caller-buffer bidirectional paragraph resolution |
shaping |
Format-neutral shaping, fallback, line selection, and positioned output |
complex-shaping |
Bounded script providers with borrowed substitution and positioning data |
script-arabic |
Arabic joining forms, ligatures, cursive attachment, and mark positioning |
script-thai |
Thai cluster substitution and mark positioning |
script-devanagari |
Devanagari conjunct forms, pre-base matra reordering, and mark positioning |
alloc |
Reusable workspace with lazy growth or fixed pre-reserved private shaping storage |
Default features are empty. The current Unicode and shaping implementation intentionally supports a defined subset and returns capability errors for unsupported scripts, controls, clusters, and font features.
Font integration
A format adapter supplies Typeface for complete shaping or GlyphSource for scalar cmap, advance, .notdef, and pair-kerning access, together with its parser, table cache, raster lookup, storage access, and diagnostics. The complex-shaping feature adds ScriptTypeface, ScriptProvider, and ShapingData for sharing script behavior across borrowed font formats. script-arabic and script-thai expose the allocation-free scripts::ARABIC and scripts::THAI providers.