When the problem described by “edit EPUB data safely” becomes confusing, return to this decision: separate one body edit from one spine-order edit. The controlled case is a three-chapter EPUB where one character in chapter one is corrected and chapters two and three are swapped. A pass must demonstrate this outcome: complete the article-specific sample with separate evidence for body difference, nav order, spine order, artifact ID, restoration. The excluded range is stated separately: direct editing inside an existing EPUB, cover work, and Japanese vertical layout.
Decision: Separate one body edit from one spine-order edit
Define the stop line on a recoverable copy. Evidence for body difference must exist before the run can advance to restoration.
The article-specific evidence card has these fields: body difference, nav order, spine order, artifact ID, restoration. Do not count the following excluded range as evidence: direct editing inside an existing EPUB, cover work, and Japanese vertical layout.
Keep this case tied to its source
Preserve the first EPUB, change one character in source, and generate a body-only second build. Then change only the reading-order record, generate a third build, and compare nav and spine before restoring the original order. Combining both changes, inspecting nav alone, or losing the original order prevents safe acceptance.
This case addresses the failure behind the search: losing the authoritative input or acceptance evidence while trying to separate one body edit from one spine-order edit. 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.
Actions to record in sequence
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. Preserve the baseline EPUB. Attach the observed body difference evidence to this step.
- 2. Change one character in source and build. Attach the observed nav order evidence to this step.
- 3. Inspect the body difference. Attach the observed spine order evidence to this step.
- 4. Change only the order record and rebuild. Attach the observed artifact ID evidence to this step.
- 5. Inspect nav and spine and restore the original order. Attach the observed restoration evidence to this step.
What each row must prove
Do not infer one row from another. Record pass, revision, or not tested beside the actual target, date, output path or artifact ID.
- Body difference — expected state: written before the run; hold the row if body and order change together.
- Nav order — expected state: written before the run; hold the row if only navigation is inspected.
- Spine order — expected state: written before the run; hold the row if the original chapter order cannot be restored.
- Artifact ID — expected state: written before the run; hold the row if body and order change together.
- Restoration — expected state: written before the run; hold the row if only navigation is inspected.
Stop conditions and repair routes
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. Body and order change together; return to the named source.
- 2. Only navigation is inspected; preserve the failed artifact.
- 3. The original chapter order cannot be restored; change only the responsible condition.
Rune Studio as a bounded candidate
Current product documentation covers capabilities relevant when you need to reduce handoffs between source editing, preview, metadata, navigation, cover, and EPUB export. That scope can justify a trial, but it does not show that a three-chapter EPUB where one character in chapter one is corrected and chapters two and three are swapped passed this article's acceptance card.
Rune Studio is a plausible candidate when fewer source, setting, or reference handoffs help you separate one body edit from one spine-order edit. Use another tool or destination check for the excluded range stated here: direct editing inside an existing EPUB, cover work, and Japanese vertical layout.
Conclusion
For the search phrase “edit EPUB data safely,” the conclusion is to separate one body edit from one spine-order edit. The result is accepted only when the record establishes this outcome: complete the article-specific sample with separate evidence for body difference, nav order, spine order, artifact ID, restoration.
Begin here: prepare three build IDs and the original order record. If body and order change together, 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.
