Taking a manuscript to EPUB in one Mac text editor is not about collecting the longest feature list. The practical test is whether long-form editing, a second proofing view, EPUB 3 export, and inspection of the exported file remain connected to one source manuscript.
This article uses only the rune Studio behaviour verified for this project. Cover-art creation, store-specific previewing, and KDP submission remain separate stages.
Define the finish line before choosing one tool
For this article, one-tool completion means that you can:
- Edit a long-form manuscript
- Split the working view and keep the source beside a check view
- Convert the verified ruby and emphasis-dot notation into EPUB output
- Export EPUB 3 and inspect the resulting file
rune Studio supports macOS 13 and later. This scope does not claim the same workflow on iPad, and it does not include Kindle Previewer or the KDP upload screen.
Stage 1: keep one manuscript as the source of truth
Decide which file receives every textual correction. The manuscript is the source; the EPUB is a generated result.
An edit made only inside an EPUB can disappear at the next export. Avoid maintaining separate drafting and EPUB copies of the prose. Put the correction in the source manuscript, generate again, and compare the new result.
Stage 2: connect editing and proofing views
The tested rune Studio workflow could add a view arrangement, change it to two columns, and link the views. This lets the source and a check view remain part of the same editing session.
The completion condition is not the number of panes. It is that a correction made while proofing still lands in the source manuscript. Reference material may sit elsewhere, but the editable source should remain unambiguous.
Stage 3: use only the verified publication notation
The operation test inserted the following notation into a Japanese manuscript and then confirmed its converted form in the exported EPUB:
- Ruby:
｜背負い袋《せおいぶくろ》 - Emphasis dots:
《《海》》
The ruby became the corresponding EPUB ruby element, and the emphasis dots received the export treatment recorded for the test. Those Japanese examples are explained here rather than replaced with different English-language features, because they are part of the verified one-tool workflow in the Japanese source article.
This article does not extend the evidence into unregistered page-break, image-insertion, metadata, volume, colophon, order, or navigation behaviour. The completion rule is narrower: keep the verified notation in the source manuscript and confirm its converted form after export.
Stage 4: export EPUB 3 and inspect the result
rune Studio provides EPUB 3 output and can inspect the inside of the finished file. Record export completion and inspection completion as separate facts.
At minimum, confirm:
- The export came from the source manuscript you just revised
- The representative ruby and emphasis-dot locations were converted in the result
- The internal inspection ran and its result was retained
A clean internal result does not guarantee KDP acceptance or identical rendering on every device. Keep Kindle Previewer as the publication-environment check.
Fix the return path for each finding
Return to the owner of the issue:
- Wording or typo → source manuscript
- Ruby or emphasis-dot difference → source notation
- Exported-content mismatch → compare source and output, then rebuild
- Difference visible only in Kindle Previewer → separate the EPUB interior from store conversion
Whatever changes, finish with another export and internal inspection. The value of one-tool production is a stable route back from a finding to the source and forward to a new EPUB.
Keep necessary external stages
Image editing, fixed-layout production, and store registration need their own tools. Define the one-tool boundary as manuscript through internally inspected EPUB, then keep store-specific previewing outside it.
That boundary shortens the workflow without claiming that one application completes every publication task.
Summary
- Judge one-tool production by a finish line from source editing through internal inspection
- Keep one manuscript as the source of truth
- Keep the verified ruby and emphasis-dot notation in the source and confirm it after export
- Export EPUB 3, inspect it, and retain Kindle Previewer as a separate stage
Start with one short manuscript containing the verified notation and complete two cycles of editing, EPUB export, and internal inspection. If the second cycle returns to the same source, the manuscript-to-EPUB workflow is genuinely connected.
See the current product scope on the Rune Studio product page.
