Garbled chapters and broken images are cheaper to stop before EPUB export than to diagnose afterward. Create one preflight table with two chapter rows and two image rows. Chapters require known encoding and zero unconvertible characters; images require file presence and a correct relative reference. Export is blocked until every required field is complete. After export, connect the prepared inputs to the manifest, packaged resources, and reader display.
Create four input rows on one preflight
Use C01, C02, img01, and img02. Chapter rows contain source path, encoding, and unconvertible-character count. Image rows contain file path, relative reference, and the chapter that uses the image.
An illustrative table might show C01 as UTF-8 with zero warnings, C02 as a separately converted Shift-JIS copy, and two images with matching relative paths. Replace every example with measured project data.
Close the chapter gate
Stop a chapter row when encoding is unknown. Convert only on a copy, use a separate UTF-8 name, and require a repeated zero count before approving that input.
Human approval controls context-sensitive replacements. Clearing a warning without a semantic basis does not satisfy the chapter gate.
Close the image gate
For each image, verify the exact file, case-sensitive name, extension, directory, and manuscript reference. A file somewhere in the project is not enough.
Record the using chapter and reference location. Image editing and color management are outside this preflight; the question is whether the correct resource can enter the EPUB.
Block export on any incomplete field
Read the four rows before export. Unknown, pending, and unresolved fields all stop the operation. A passing chapter cannot fill an image cell, and file presence cannot fill a reference cell.
Write the exact blocker on its row, such as unknown C02 encoding or mismatched img02 href. The responsible input can then be repaired before a package is generated.
Inspect the manifest after export
Once preflight has zero blanks, export the EPUB and locate img01 and img02 in the manifest. Confirm that the packaged resources exist under the referenced paths.
Open the target pages in a reader. The preflight row, manifest item, packaged file, and visible image must all point to the same image ID.
Keep product evidence and general inspection separate
Rune Studio's documented Japanese encoding detection, unconvertible-character warnings, and save blocking can support the chapter rows.
Image presence, relative references, manifest entries, and reader display are general EPUB resource checks. Combining them in one table does not turn them into one proprietary capability.
Distinguish this release gate from two-lane diagnosis
STUDIO-093 separates text and image records to diagnose owners and return paths. This article combines ready inputs into one pre-export permission and asks whether every row is complete.
When a defect appears, repair its source row, but grant export only from the completed table as a whole.
Conclusion: close four rows before export
Build the two-chapter and two-image table, fill measured values, and do not export while any required field remains pending.
After export, connect the manifest and reader evidence to the same image IDs. A zero-blank preflight prevents uncertain text and resource references from becoming a harder package-level problem.
