e77eeff11c
* fix(fig): write text glyphs from the layout the renderer draws Text without saved glyphs was written to .fig with outlines from a character-by-character fallback: one unwrapped line at y = lineHeight, no alignment, advances in pixels. Figma lays saved text out from that data, so every wrapped OpenPencil label opened in Figma on one line, and since saved glyphs now draw before the paragraph, OpenPencil did the same after a reopen (#914). The Figma clipboard had a second writer with its own shaping that matched outlines to characters by index. One builder in @open-pencil/fig now writes derivedTextData for both. It keeps glyphs a layer already has and otherwise asks the export runtime to shape the text. Core shapes with the paragraph the renderer draws, so lines, alignment, and baselines match, and takes each outline from the glyph ID CanvasKit chose, so ligatures and contextual forms keep their shapes. CanvasKit does not say which font drew a run, so outlines are written only when the run's own font covers it; otherwise the layout is written without outlines and readers lay the text out themselves. Advances are in em units and the character offset map has one entry per character, as in Figma's files. The reader drops glyphs the earlier fallback wrote, recognised by its offset map one entry longer than the text with every glyph on the one written baseline, and any glyph set with a missing outline. * fix(scene-graph): reflow resized text instead of stretching its glyphs Resizing scaled a text layer's saved glyphs into the new box. That suits path text, whose glyphs follow its path, but flat text reflows, and with saved glyphs drawn before the paragraph a resized Figma text layer was drawn stretched. Scale glyphs only for path text, including baked path text that kept only rotated glyphs, and let the width change drop the rest. * docs(fig): describe how derived text is written Figma draws saved text from derivedTextData even when it has the font, so the export docs record which glyphs the shared writer keeps, shapes, or leaves without outlines, and the units it writes. The README names the runtime service by what it now does. * fix(fig): write text without glyphs when shaping fails Glyphs are derived data, so a shaper error must not fail the .fig save or Figma clipboard copy that writes them. The builder now writes the layer without glyphs and logs a warning; the clipboard used to swallow the error silently, which hid a font-provider mismatch. |
||
|---|---|---|
| .. | ||
| observations | ||
| architecture.md | ||
| document-sessions.md | ||
| export.md | ||
| instance-evaluation.md | ||
| materialization.md | ||
| README.md | ||
| source-model.md | ||
| validation.md | ||
FIG package architecture
These documents explain the .fig reader and its editing/export contracts.
They are package implementation documentation, not a release-status log.
Reading order
| Document | Question |
|---|---|
| Architecture | Which package owns each stage? |
| Source model | What are records, resources, and identities? |
| Instance evaluation | How do bindings and overrides resolve? |
| Materialization | How do occurrences become editable nodes? |
| Document sessions | How do incremental loads and recovery work? |
| Export | How are runtime identities and claims encoded? |
| Validation | What constitutes compatibility evidence? |
archive -> source model -> instance evaluation -> materialization
|
document sessions + editor actions
|
export
|
Figma validation
Status vocabulary
- Required invariant: a correctness constraint, whether or not all cases satisfy it yet.
- Implemented: behavior present in the linked modules and covered by the cited tests.
- Known limitation: a boundary not yet implemented or validated; not a supported fallback.
Every consumer uses this reader; the previous importer and its repair pipeline are gone, so there is one interpretation path, not a legacy mode. Remaining work is fidelity and performance acceptance against Figma, tracked per document as known limitations.
Keep temporary file keys, benchmark runs, experimental findings, and current blockers in
ignored scratch/ notes or the integration PR. Fixture provenance belongs alongside fixtures.
The public roadmap owns product-level direction.