A direct answer for EPUB TOC and chapter order
The safest answer to EPUB TOC and chapter order is to separate source chapter order, navigation labels, link targets, and spine order. The aim is not to run extra application commands. It is to prepare one modification whose original, selected content, and saved result remain clear after leaving the file and reading it back.
Use diagnosing an EPUB whose navigation and reading order disagree as the working situation. Duplicate the source with a date and leave the only original untouched. Log the master name, latest timestamp, selected documents, and one deliberate exclusion. That short note gives you a return point when the reopened document is surprising.
The mistake to avoid is re-encoding the entire book project before proving the problem is encoding-related. A normal-looking window is insufficient proof when the wrong folder, tab, encoding, chapter, or package was used. Accordingly, the saved deliverable must be opened again within the main procedure.
Do Not Overwrite The Source Encoding
Begin with a small copy built around diagnosing an EPUB whose navigation and reading order disagree. This exercise uses less material than a production book project on purpose. Place the main risk beside enough context to uncover an incorrect choice, while leaving the unchanged master untouched.
Write the intended finish in one sentence: “separate source chapter order, navigation labels, link targets, and spine order.” This sentence is useful because it names a measurable outcome instead of relying on a smooth impression. Another editor should repeat the review without interpreting your intention.
Keep the boundary visible as well: complete recovery of corrupted data, OCR, and binary repair are outside selected content. Put newly discovered out-of-selected content trouble into another work item. Expanding the current run midway makes it difficult to identify which action introduced the mismatch.
Compare Candidates On A Copy
For the initial run, load only the test copy for diagnosing an EPUB whose navigation and reading order disagree. Confirm the source before changing a setting. Use only the advertised step, inspect its impact, and create an output with a fresh name.
Exit the editing screen or archive preview when the procedure finishes. Afterward, open the stored item from its actual destination. Read a recognizable start, an altered location in the middle, and the ending token. An EPUB also needs navigation-to-content checks beyond its cover and opening section.
If comparison fails, restart from the first step whose state is unknown. Resist smoothing counts, repeatedly editing the deliverable, or continuing because only a few pages fail. Recreate the copy and modify just one setting. That brief pause is cheaper than rebuilding an overwritten source.
Read back The Named Result
The controlled run produced this observation: The dedicated sentence was opened from five encoding variants: UTF-8=UTF-8/LF/39 characters, Shift_JIS=Shift_JIS/LF/39 characters, EUC-JP=EUC-JP/LF/39 characters, UTF-16LE=UTF-16LE/LF/40 characters, UTF-16BE=UTF-16BE/LF/40 characters. The active tab then reported UTF-8 when its setting was read back. The reported values are tied to the exact input used. They do not become target counts for diagnosing an EPUB whose navigation and reading order disagree, because a real book has different sections, links, glyphs, and resources.
The documented limitation carries equal weight: The command-based verification read back the setting; the run did not overwrite a deliberately mis-decoded source. complete recovery of corrupted data, OCR, and binary repair are outside selected content. An empty reverse search can show removal, while semantic accuracy still needs reading. Local EPUB structure may pass while retailer acceptance and cross-reader rendering remain unproved.
Treat the number as a locator and then examine the actual passage. Open the altered text, referenced chapter, media path, metadata record, or page break. A person still makes the final decision whenever meaning or appearance matters.
Where Rune Studio fits the EPUB TOC and chapter order task
Rune Studio deserves consideration when you want to use Rune Studio’s documented Mac editing, workspace, notation, or EPUB workflow as a bounded candidate. Use one authentic problem for the trial from diagnosing an EPUB whose navigation and reading order disagree before bringing over an entire publication. What matters is whether evidence survives the route from editable source to stored deliverable.
This workflow suits writers who want editing and a bounded output verification in the same Mac workspace. It does not make complete recovery of corrupted data, OCR, and binary repair are outside selected content disappear. Keep a separate tool or review step for requirements outside the product boundary.
The latest product selected content is listed on the Rune Studio official site. While testing, skip features that do not affect this risk. Reproduce the one failure you most want to prevent, and confirm the source survives in recoverable form.
Failure recovery without damaging the book project
If the included material expands, stop changing the test document. Make a note of the newly discovered issue, finish or discard the current narrow run, and create a fresh copy for the wider question. The separation keeps causes connected to their effects.
When readback fails, resist converting the master source. Verification the reopened document path, file identity, encoding readback, link target, navigation destination, or package contents according to the topic. Resolve the earliest wrong state and redo the short procedure.
If the preview succeeds but the persisted item fails, judge the handoff by the persisted item. Preview feedback is helpful, but another application or reader consumes the saved file. Keep the display layer apart from the saved layer.
A practical conclusion for EPUB TOC and chapter order
For EPUB TOC and chapter order, the durable method is to separate source chapter order, navigation labels, link targets, and spine order. Preserve a dated version, write down the boundary, inspect changed passages, and read back the output ahead of full use.
Start with a small copy built around diagnosing an EPUB whose navigation and reading order disagree. Preserve the original, name the output clearly, and keep this limitation beside the reopened document: complete recovery of corrupted data, OCR, and binary repair are outside selected content. That small discipline changes one editor function into a reliable handoff practice.