Comic name proof

Proof the place where the name appears

A name that works in a spreadsheet may fail inside a speech balloon. Width, font, reading support and visual grouping affect what the reader perceives. This tool makes a horizontal text proof from approved strings. It is a limited layout check, not a judgment of the surrounding artwork or a replacement for a letterer’s page review.

Use dimensions from the actual panel

Enter the inner text width, not the balloon’s outside diameter. Choose a main text size of at least twelve pixels for this proof. In the browser, text uses measured font advances; the initial static example uses a labeled approximate fallback. Those two proofs can differ. Final output must be checked in the actual production font, resolution and writing direction. Vertical Japanese composition is not implemented in this horizontal worksheet.

Reading support has its own width

A short written form can have a long reading. The tool checks the supplied reading separately at half the main text size and flags excess width. It does not automatically reposition ruby or decide that shrinking everything is acceptable. When a proof overflows, enlarge or restructure the balloon, use a previously approved short reference, or revise the introduction. Keep the source identity intact.

Fictional example: the club roster panel

A club roster wraps two surnames into what looks like one person. The artist initially suggests shorter names. The letterer instead separates the entries and moves one introduction to the next beat. The approved names survive, and the story no longer appears to introduce a nonexistent combined character. The failure was spatial grouping, not a shortage of clever naming ideas.

Why a different repair changes the work

A full rename would require updating later dialogue and name badges. Enlarging the balloon could obscure a relevant expression. Moving an introduction changes pacing. Compare those costs with the storyboard rather than treating the fewest characters as the best result. The proof is evidence for a production discussion; it cannot identify the best artistic tradeoff by itself.

Keep the handoff precise

Export the approved string with a stable identity ID and the chosen display form. Mark invented reading examples as invented. Track signs, stamps and handwritten notes separately so a later rename does not miss text inside art. A mobile preview is another size condition within this workflow, not a separate naming task that deserves another thin page.

Build a proof from an approved record

Use the written form the creator has actually accepted, not a convenient temporary spelling. Add the reading only when it is supplied and approved for this fictional use. The workbench needs a stable ID so a later rename can be traced into artwork. Its layout proof should not turn an uncertain reading into an attested fact merely by displaying it neatly above the text.

Choose the local production font and the inner text width. The browser can measure font advances for the chosen rendering environment. The initial static case uses a labeled estimate so the page remains useful without JavaScript. A font-family name does not by itself prove that the exact intended font file is installed. If the browser substitutes another face, your final production proof still needs attention.

The tool compares a ruby span with an inline form. The span budget uses the wider of the written name and the half-size reading; the inline version adds the reading beside the name. These are different layout choices, not two names. Compare their widths at the same main text size before deciding which introduction the panel can support.

Inspect glyph support separately

If you have a verified character-coverage list for the production font, supply those characters in the manifest field. A character absent from that supplied list is flagged. Leaving the list empty means unverified, not supported. The site does not claim that a browser font-loading check certifies the presence of every glyph or that fallback rendering preserves every deliberate distinction.

This evidence boundary matters for unusual forms, private-use characters or a prop where two shapes carry different information. Retain the original text and record an approved substitution at the asset level. A missing character can be a production problem even when the name’s reading and meaning are fully established. Conversely, a visible glyph does not validate the name’s cultural plausibility.

Reproduce a constrained panel check

Begin with a width of 120px and a main text size of 22px. Enter two name records and inspect how the written forms wrap. Reduce only the width. The output should change its line structure or report overflow while the name and text size remain fixed. This is a test of a meaningful constraint, not another random suggestion.

Add a long reading to a short written form. The reading can exceed the span even when the main text fits. Compare the inline width rather than assume that moving the reading beside the name will always save space. An approved short reference may help, but only if the reader already knows whom it identifies. The introduction table can flag a name that has not yet been introduced at the selected chapter.

Add a prop row with an asset ID, character ID and current artwork text. If the artwork still shows an earlier name, the report lists a change. It does not redraw the image. The purpose is to prevent a script-only rename from leaving the old name on a badge or note that remains visible to readers.

Original fictional scene: the roster nobody drew

The writer thought the new club member had been introduced twice. The artist thought one character was missing. The letterer placed the page between them and pointed to the roster on the wall.

Two surnames had wrapped against one another. The next line, meant to be a second person, looked like the continuation of the first.

“Then shorten them,” the artist said. The panel was already crowded with a hand entering from the doorway and a notice the reader needed to see.

The writer started a replacement list. One surname belonged to a family already established in the previous chapter. Changing it would unsettle a later sibling reference. The other appeared on a name patch in three finished panels.

The letterer separated the roster entries and moved one spoken introduction to the next beat. The newcomer answered a question before the full name appeared. The hand in the doorway remained visible. The notice kept its place.

On the revised page, two people could be counted. No one had acquired a shorter legal identity merely to solve a line break.

When the translated proof arrived, the reading note made the second entry wider again. The team reopened the same panel decision rather than assume that the earlier approval covered every edition. This time an inline note worked in the adjacent caption, where the reader’s eye would reach it after the face.

The scene is an original fictional production example. Its naming consequence is specific: spatial grouping creates a nonexistent combined identity. Correcting layout restores the intended cast without sacrificing established relationships or prop continuity.

Why the smallest string is not always the best repair

A short name can be legible but narratively expensive. A wider balloon can solve the text and conceal an expression. A later introduction can improve the panel while delaying a clue. Compare those consequences rather than optimizing character count alone. The tool keeps the approved name fixed so you can see when the actual decision concerns layout or pacing.

If the two names are intentionally meant to be mistaken for one, the roster error could become a clue instead. The page would need to establish why a character makes that inference and when readers can correct it. A deliberate ambiguity belongs in the story plan and should be tested with the reveal. It is not automatically justified because the crowded proof happens to produce it.

If a family surname must change for a genuine story reason, use the prop-change list as part of a broader rename review. The lettering proof does not decide inheritance rules or edit all future pages. Its output gives the people responsible for art, script and localization a shared description of which surfaces need work.

Make the handoff usable at production scale

Export the proof manifest with identity IDs, written forms, readings, font assumptions, dimensions and unresolved glyph evidence. A screenshot alone can show appearance but lose the text and revision context. A JSON manifest alone can preserve strings while hiding a misleading visual arrangement. Use both where the decision depends on what the panel looks like.

Identify the actual viewport or print size at which the review occurred. A mobile preview is a condition of this same workflow, not a reason to create another thin naming page. Do not infer print readability from a large desktop proof. Equally, a low-resolution thumbnail may be a poor basis for renaming a character who is clear at the intended reading size.

Keep production annotations out of reader-facing art. A stable ID such as a is useful in the manifest but does not need to appear on the page. A private name, future title or unrevealed reading may be necessary to the artist while remaining inappropriate for a recap. The selected scene and introduction state help identify that distinction; the author still controls what is supplied as public text.

Before approval, examine the rendered page in reading order. Can the reader connect each label to the intended person? Does the reading support reveal information at the right moment? Is every missing-glyph warning resolved or explicitly held? Has the artwork, not just the script, received the chosen spelling? A proof becomes valuable when those decisions can be reviewed, not when every box is forced to report that it fits.

Does an empty glyph manifest mean the font is safe?

No. It means glyph coverage has not been established through that evidence field. Browser fallback may make text visible without preserving the exact intended form. Supply a coverage list actually checked for the production font, inspect missing characters and keep the original text. Do not turn a visible screenshot or a loaded font-family name into a universal glyph-support certificate.

Why can a short name fail its ruby proof?

The supplied reading can be wider than the written form, even at a smaller text size. The workbench compares the ruby span with an inline alternative so you can assess that tradeoff. It does not silently squeeze text until the warning disappears. Change the panel, use an approved reference or relocate the reading where the reading order still teaches the intended connection.

Does the prop list update my image files?

No. It identifies assets whose current text differs from the accepted name. The artist still needs to change and proof those assets. Keep the asset IDs in the handoff so a corrected script is not mistaken for a corrected page. The same principle applies to stamps, notes, uniforms and background signs: text inside an image is not fixed by a prose replacement.

Can one proof approve every edition and screen?

No. Font, size, reading support and context can change across print, mobile and localized versions. Reuse the identity record and layout method, but review the actual surfaces. A mobile width is a condition of this workflow rather than an independent naming product. Record which proof was inspected and which assumptions remain unverified before treating the production decision as closed.