Punctuation spacing and paired punctuation
Read the punctuation and locale before adding or removing a space.
Understand the principle
Space-before and space-after questions are contextual. French high punctuation and guillemets need different review from English commas; supported Spanish questions/exclamations can require opening inverted punctuation. Numbers and technical strings can imitate prose boundaries.
Look in Typography. The publication concept and a plugin issue identifier are related, but are not interchangeable.
Compare the intent, not only the characters
Ready ,now
Ready, now · in ordinary English prose
Schematic teaching example, not a plugin screenshot or a promise of automatic correction.
Review it in Avellio 2.0
Inspect the exact character and paragraph language. Read the sentence boundary, not just a small snippet. For French, compare the supported regional policy and intended nonbreaking space; for Spanish, locate the real start of the question or exclamation. Read Found and Suggested when offered, or Review in context. Check Text locale; the recommendation itself changes no text. After an intentional manual edit, inspect again.
SPACE_BEFORE_PUNCTUATIONSpace after punctuationPUNC_SPACE_AFTERInverted punctuationINVERTED_PUNCTUATIONUse the selected finding’s actual evidence and offered actions. If no suitable supported action exists, make a justified manual decision in InDesign or retain the occurrence. After an edit, inspect again and check nearby composition.
Read the plugin recommendation
Review spacing before this punctuation using the text language conventions.
Read-only advice: verify meaning and locale, edit deliberately when justified, then inspect again.
Review whether a space is needed after this punctuation in context.
Read-only advice: verify meaning and locale, edit deliberately when justified, then inspect again.
Check where the question or exclamation begins before adding its opening mark.
Read-only advice: verify meaning and locale, edit deliberately when justified, then inspect again.
When the difference can be intentional
Decimals, URLs, email, abbreviations, quoted fragments and code must not be processed as ordinary sentence boundaries.
What should I verify after deciding?
Preserve meaning and the intended design. If you edited the document, obtain fresh results for the intended scope and policy. If you kept the occurrence, record a supported review decision when useful. A smaller filtered count is not proof of a repair.
Use it in a real workflow
Choose the right language policy
Make a language-sensitive finding understandable before deciding that punctuation, quotes or numbers are wrong.
Follow the workflow →