Label Support Matrix
Capability |
Support level |
Scope |
Diagnostics |
|---|---|---|---|
Point labels |
|
|
|
Batch point labels |
|
|
|
Line labels |
|
|
|
Curved labels |
|
|
|
Callouts |
|
|
|
Typography controls |
|
|
Invalid future controls must fail with typed diagnostics instead of no-op success. |
Decluttering controls |
|
|
Unsupported algorithm names return |
Atlas loading |
|
|
Future atlas validation may add |
Missing glyph diagnostics |
|
Known non-ASCII glyph gaps are reported before sending create commands to the viewer. |
|
Upside-down line handling |
|
Reverse line paths are normalized so glyph rotations stay upright, with |
Documentation boundary; no diagnostic for supported flat line handling. |
Terrain-elevated line labels |
|
Terrain sampling is not owned by feature |
|
Deterministic LabelPlan |
|
|
|
Advanced repeated line labels |
|
P2 product planning adds deterministic repeat-distance output where line geometry can be compiled; unavailable render integration remains diagnosed before render. |
|
Advanced curved labels and complex-script shaping |
|
Curved path text and HarfBuzz-compatible shaping are non-MVP-blocking unless prioritized with end-to-end tests. They must be diagnosed before render rather than treated as silent success. |
|
The feature 002 public workflow uses high-level ViewerHandle methods and
does not require raw IPC for basic label creation, configuration, line labels,
callouts, vector-overlay creation, or clear/remove workflows. Existing raw IPC
helpers remain an advanced compatibility surface, but they are not the MVP
label API truth contract.
Successful create calls return a stable id where users need update, inspect, remove, export, or review workflows. No label command should report success while doing nothing. Unsupported or unverified label behavior must produce typed diagnostics or explicit failure.