Reflow and text layout

Text wrapping seems like it should be simple, and then you meet a line that breaks $12.50 across two lines and changes what the reader sees.

DunneNote wraps at word-level break opportunities chosen so that meaning survives the break. The engine is delimiter-aware: it understands which characters are genuine separators and which only look like separators.

Units that never break

Certain sequences are glued together and treated as one unit:

• Decimal numbers. 3.14159 does not become 3. and 14159.
• Currency amounts. $12.50 stays whole.
• Similar composite values where splitting would change how the value reads.

When nothing fits

If a unit is too wide for the space available and there is no acceptable place to break it, the unit is kept intact and allowed to overflow. The alternative — breaking anyway — produces a line that is technically the right width and semantically wrong. Overflow is visible and obviously a layout problem. A silently mangled number is neither.

Everywhere text wraps

The same engine applies wherever text wraps: rich text bodies, grid cells and captions all get the same treatment, so a value does not break one way in a table and another way in a paragraph.