Check special characters in the actual exported manuscript using representative passages and a targeted search list. Compare each character’s appearance and meaning with the source, including captions and tables. If a font or export change fixes a missing glyph, review the affected layout again before considering the file ready for submission.
Identify characters that deserve a targeted check
A manuscript can appear normal in an editor while a small set of characters changes during export. Build a list from the book itself: accented names, scientific symbols, unusual punctuation, currency signs, or characters introduced by pasted source material. Do not rely on a generic checklist alone. The relevant risks depend on the actual language and notation the author uses.
Include front matter, tables, captions, footnotes, and answer explanations. These areas may use different styles or fonts from the main text. A character that renders correctly in a body paragraph can still fail in a bold heading or a small caption. Record representative locations for each important combination so the review covers more than one convenient example near the beginning of the book.
Compare appearance with intended meaning
Open the exported file and inspect the selected passages at a useful reading size. Look for empty boxes, substituted marks, missing accents, unexpected spacing, or characters that resemble the intended symbol but mean something else. Compare the result with the source and the author’s intended wording. A file can be visually tidy while containing a wrong character that changes a name or instruction.
For example, a measurement table may mix an ordinary letter with a symbol that looks similar in one font. Correcting the font will not repair a wrong character already present in the source. Establish whether the problem is the stored text, the selected font, or the export process before applying a fix. That distinction prevents repeated layout changes aimed at the wrong cause.
Review font handling for the publication format
Consult the current requirements for the intended format. KDP’s paperback submission guidance includes instructions on embedding fonts in the source file before submission. Follow the relevant guidance and check the resulting file rather than assuming that selecting an export preset proves the requirement has been met. A font-related warning from an inspection tool should be investigated in the context of the actual export.
Keep application-specific instructions separate from publication requirements. Different tools expose font settings differently, and some workflows may restrict what can be embedded or exported. Use the documentation for the application and font you actually use when resolving those details. Do not substitute a visually similar character or convert meaningful text into an image merely to hide an unresolved warning without considering the effect on readers and later editing.
Repair the source and test the affected styles
When the stored character is wrong, correct it in the editable manuscript and inspect related occurrences individually. A global replacement can damage passages where the same visible mark serves another purpose. When the font is the problem, choose an appropriate supported alternative within your workflow and test all styles that use the affected characters. Preserve the prior source until the revised export has been checked.
After a font change, inspect line breaks, table widths, heading placement, and page references. Different character widths can move content even when the text itself remains unchanged. The repair therefore needs both a character check and a layout check. Export again from the corrected source so the publication file and editable manuscript remain aligned instead of fixing only a detached output copy.
Keep evidence tied to the final file
Record the inspected export and the representative passages that passed review. If a later change alters fonts, styles, or export settings, repeat the affected checks. A report from an earlier file cannot establish that the final version preserves the same characters. Keep unresolved cases visible until you have a clear result or an appropriate alternative that has also been reviewed.
Finish by reading the affected passages normally. The reader should be able to understand the text without consulting the author’s source document or guessing which mark was intended. Automated file inspection can support this process, but it cannot determine every linguistic or subject-specific distinction. Where a symbol’s meaning requires specialized knowledge, use a reviewer who can evaluate that meaning as well as its appearance.
Frequently asked questions
Clear answers for this publishing decision.
Should I inspect every occurrence of an unusual character?
Use a targeted search to locate occurrences and review the contexts that matter, especially where styles or meanings differ. If you find a defect, inspect the other affected occurrences rather than assuming a single corrected example proves the whole manuscript is fixed.
Does embedding fonts guarantee correct text?
No. The source may already contain an incorrect character, and other export or layout issues may remain. Follow the applicable font requirements, then inspect the actual text and appearance in the publication file.
Can I replace an accented name with an unaccented version?
Do not change a person’s name simply to avoid diagnosing a rendering problem. Establish the correct spelling and repair the source, font, or export workflow as appropriate. Review the final result for both accuracy and readability.
How do I get from an idea and a brief to an editable manuscript I can finish?
Write the brief first, generate a structure you can edit, then draft and revise the manuscript in reviewable sections so one change never overwrites work you already approved.
Start a book project from a brief