Single-Line Font or Outline? Proof Repeated Small Text Before the Set
Zoom in before deciding that a font is single-line. Many apparently thin fonts are narrow closed outlines; line mode and fill mode will treat those shapes differently.
A thin font is not necessarily one path
A February 2026 LightBurn beginner asks how to lay out repetitive text and receives specific guidance that apparently single-line fonts may actually be very narrow outlines. The 2026 LightBurn thread preserves the original context.
Inspect geometry before repeated layout
| Geometry seen at high zoom | Line preview | Fill preview | Decision |
|---|---|---|---|
| one open center path | single trace | no meaningful area | use only if software supports it |
| narrow closed outline | two borders | solid narrow letter | choose appearance deliberately |
| overlapping letters | repeated travel possible | merged/dark region | clean geometry |
| missing font substitution | shape changes | shape changes | stop and restore approved font |
Proof one word at the smallest approved size
- Keep a copy with text converted or packaged according to the approved file workflow.
- Inspect one representative word at high zoom and in no-output preview.
- Proof the smallest approved size and widest name on an eligible compact blank with active supervision, effective exhaust, fire readiness, and immediate stop conditions.
- Time the actual repeated layout if schedule matters; do not extrapolate guaranteed throughput from one word.
Estimate repetition from the real file
A font that appears as a hairline at normal zoom may reveal two parallel contours around every letter. Line processing can trace both borders, while fill processing creates a small solid letter. Neither is automatically wrong; the intended look decides.
Compare icon treatment in the game-token geometry proof, then apply the approved font state to the live-event name-control workflow without silently switching files.
P2 limits for small repeated text
P2 can render compact text only within the chosen blank, font geometry, focus, and accepted proof. A repeated-text layout is not a promise of speed or universal legibility. Check the available P2 configuration while keeping font geometry and legibility acceptance in the job file.
Font-geometry questions
Why did the text become bolder after import?
The source may contain closed outlines, a substituted font, or a fill assignment. Inspect geometry rather than changing power first.
Can one proof cover every name?
Use the widest and thinnest real strings to expose fit and legibility limits.
Does a faster preview mean faster production?
Preview and timing help planning, but they do not guarantee machine throughput or accepted results.