Techniques
Text fit — wrapping, bounds and visible overflow
Text layout balances readable type with available geometry. Table cells wrap on screen while each data row remains one physical source line.
ddn@1New DDN source
Why use it?
Hand-tuning box sizes against text that keeps changing is the chore text_fit removes — with bounds and diagnostics so adaptation stays honest instead of silently clipping.
When it helps
Long labels, generated text, multilingual content — anywhere text length is not under the author's full control.
How to read it
- Inspect the complete label and the space available to it.
- Table columns may specify minimum width in default-font characters and maximum wrapped lines.
- Ellipsis marks clipped text; an unfit table uses the shaded-square indicator.
What you need
- The actual text
- Default font and size
- Width and line constraints
Things to check
- Do not use physical multiline source rows to force table wrapping.
- A readable preview at one zoom does not establish legibility in a smaller exported page.
Scope of this diagram
Text measurement and target output affect geometry. Semantic identity and relationships remain distinct from wrapping.
Work with the converted example
- Open the viewer and select
fitted. Inspect the rendered view and its source. - Open the designer. Keep the selected profile and inspect its legal palette and property controls.
- Change one displayed title or an appropriate data value. Apply the edit and check the resulting diagram.
- Run the verifier and review its diagnostics before moving complete content into review.
- Download your edited DDN source to retain the change.
The example uses the indentation-based ddn-next-1 dialect. The language guide explains reusable definitions, dotted data rows and explicit property blocks.