This guide gives the search “how to build an EPUB file” a concrete finish line: treat visible pages and six internal package components as separate completion conditions. The controlled case is two chapters and one referenced image in a minimal EPUB project. A pass must demonstrate this outcome: complete the article-specific sample with separate evidence for mimetype and container, package document, body XHTML, navigation, spine, image reference. The excluded range is stated separately: fixed-layout production, audio, and DRM.
Decision: Treat visible pages and six internal package components as separate completion conditions
Close one checkpoint only when its input and result can be named. Reaching a build screen does not prove mimetype and container, image reference, or the stages between them.
The article-specific evidence card has these fields: mimetype and container, package document, body XHTML, navigation, spine, image reference. Do not count the following excluded range as evidence: fixed-layout production, audio, and DRM.
A specimen that exposes the real failure
Build a two-chapter sample with one referenced image and inspect six package elements: mimetype and container, the package document, body XHTML, navigation, spine, and image references. Rename one chapter in source and regenerate. A renamed ZIP, conflicting nav and spine order, or an unreferenced image is a failed result.
This case addresses the failure behind the search: losing the authoritative input or acceptance evidence while trying to treat visible pages and six internal package components as separate completion conditions. Name the source, working copy, and delivered or reopened result so that another editor can locate each one without relying on a filename such as final.
Operation order
Use the following product-independent sequence on the named sample. It is an acceptance method, not a claim that Rune Studio has already completed this particular case.
- 1. Prepare two chapters and an image in source. Attach the observed mimetype and container evidence to this step.
- 2. Generate under a new build ID. Attach the observed package document evidence to this step.
- 3. Inspect container and OPF. Attach the observed body XHTML evidence to this step.
- 4. Compare nav and spine order. Attach the observed navigation evidence to this step.
- 5. Verify the image reference and rebuild after renaming one chapter. Attach the observed spine evidence to this step.
Evidence to keep separate
Do not infer one row from another. Record pass, revision, or not tested beside the actual target, date, output path or artifact ID.
- Mimetype and container — expected state: written before the run; hold the row if a ZIP is only renamed to .epub.
- Package document — expected state: written before the run; hold the row if nav and spine orders conflict.
- Body XHTML — expected state: written before the run; hold the row if an image file exists without a body reference.
- Navigation — expected state: written before the run; hold the row if a ZIP is only renamed to .epub.
- Spine — expected state: written before the run; hold the row if nav and spine orders conflict.
- Image reference — expected state: written before the run; hold the row if an image file exists without a body reference.
Where this workflow must stop
A second pass is meaningful only when its source and changed condition remain identifiable. Keep the earlier result and append the retest instead of replacing the failed row.
- 1. A ZIP is only renamed to .epub; change only the responsible condition.
- 2. Nav and spine orders conflict; return to the named source.
- 3. An image file exists without a body reference; preserve the failed artifact.
When to shortlist Rune Studio
Current product documentation covers capabilities relevant when you need to preserve manuscript order and metadata, generate EPUB 3, and inspect the resulting structure. That scope can justify a trial, but it does not show that two chapters and one referenced image in a minimal EPUB project passed this article's acceptance card.
Rune Studio is a plausible candidate when fewer source, setting, or reference handoffs help you treat visible pages and six internal package components as separate completion conditions. Use another tool or destination check for the excluded range stated here: fixed-layout production, audio, and DRM.
The decision to keep
For the search phrase “how to build an EPUB file,” the conclusion is to treat visible pages and six internal package components as separate completion conditions. The result is accepted only when the record establishes this outcome: complete the article-specific sample with separate evidence for mimetype and container, package document, body XHTML, navigation, spine, image reference.
Begin here: prepare two chapters and a six-row package checklist. If a ZIP is only renamed to .epub, stop at that row and return to its source. Check the Rune Studio product page for the current Mac feature scope before applying the same acceptance card to a product trial.
