C5.15.4Convert-to-text reflow can wreck spatial layoutdesignresearch

Reflow after converting handwriting to text can scramble the writer's original spatial layout

Aliases: convert reflow · spatial layout · ink layout

What it is

Position on a handwritten page is information: a question in the left column, an answer in the right, a circled formula, an arrow to a figure. Converted to flowing text, the engine strings characters in reading order, and reflow tears those spatial relations apart. If post-editing defaults to “become an article”, layout intent is gone. That is not a wrong character; it is the layout contract replaced by prose.

Why it happens

Flowing text has one insertion order. Multiple columns, side notes, casual arrows, and words wrapping a figure are not in that model. Recognizers usually detect lines, then concatenate left-to-right (or by script direction); a side note is spliced into the main column or dropped at the end of a paragraph. Drawings and ink structure have no characters and vanish or become garbage. Writers use space as structure (indent as hierarchy, juxtaposition as contrast); after convert, only spaces and line breaks remain, and hierarchy flattens. Ways to keep layout: region boxes (this block stays positioned text), not converting some regions at all, or stacking converted glyphs on the original coordinates (what-you-saw characters that do not flow). Flow is kinder to search and assistive tech; positioned text is truer to a handout—people need to choose per block, not one page-wide switch.

Studying it

Convert notes that contain two columns, side notes, and figure labels. Compare flowing full text, positioned regions, and leaving graphics unconverted. Have the original writer point at “this meaning is gone”.

Independent variables: layout policy (flow / positioned / mixed), whether line detection keeps columns. Dependent measures: retained structural relations (columns, arrows, indents), whether search still works, losses the author names.

Where it stops holding

A diary written left-to-right is almost unharmed by flow. A table recognised as a table is an upgrade, not damage. Pure search use can sacrifice layout. Print pagination versus screen reflow is another layer; do not mix it with ink coordinates.

Applying it

  • Default to converting detected blocks: flow inside a block, keep coordinates between blocks. Offer “whole page becomes one article” as an explicit option.
  • Leave drawings, arrows, and circles unconverted, or convert them to objects, not letters.
  • Overlay a convert preview on the original page so people can see whether columns were concatenated wrongly.
  • How to check: a two-column Q&A must not put answers inside question lines. Side notes should stay aside or be marked as their own block. Concatenating into one article should require the whole-page flow option and be undoable back to positioned.

Related

  • Same group: C5.15.1 Recognised text stays editable like typed text · C5.15.2 Keep ink–text correspondence to revert to the original · C5.15.3 Batch correction costs more than per-character confirm
  • Adjacent: C5.16 Switching Between Handwriting and Typing · C5.07 Division of Labor Between Pen and Finger
  • Search: reflow · spatial layout · ink regions

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/C5.15.4