Start the task described by “EPUB generator comparison” by controlling the sample: compare generators by source return and an identical second build rather than first-build speed. The controlled case is the same two-chapter manuscript, metadata, and order in every candidate. A pass must demonstrate this outcome: complete the article-specific sample with separate evidence for source input, saved settings, first structure, chapter-name revision, second structure. The excluded range is stated separately: purchase price, processing-speed rankings, and KDP acceptance.
Decision: Compare generators by source return and an identical second build rather than first-build speed
Use every required field as a blocker. A candidate with an unverified source input or second structure stays on hold, even if its unrelated features look attractive.
The article-specific evidence card has these fields: source input, saved settings, first structure, chapter-name revision, second structure. Do not count the following excluded range as evidence: purchase price, processing-speed rankings, and KDP acceptance.
The acceptance case for this search
Give every generator the same two-chapter manuscript, metadata, and reading order. Inspect the first EPUB, rename only chapter two in the authoritative source, and inspect nav and spine in the second build. Re-entering every setting, editing the package directly, or leaving the old chapter name in the second navigation is a blocker.
This case addresses the failure behind the search: losing the authoritative input or acceptance evidence while trying to compare generators by source return and an identical second build rather than first-build speed. 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.
Five actions from source to result
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. Give every candidate the same copy. Attach the observed source input evidence to this step.
- 2. Set metadata and chapter order. Attach the observed saved settings evidence to this step.
- 3. Generate and inspect build one. Attach the observed first structure evidence to this step.
- 4. Rename only chapter two in source. Attach the observed chapter-name revision evidence to this step.
- 5. Generate build two and compare nav with spine. Attach the observed second structure evidence to this step.
The result card
Do not infer one row from another. Record pass, revision, or not tested beside the actual target, date, output path or artifact ID.
- Source input — expected state: written before the run; hold the row if settings must be re-entered.
- Saved settings — expected state: written before the run; hold the row if the package is edited directly.
- First structure — expected state: written before the run; hold the row if the old chapter name remains in build-two navigation.
- Chapter-name revision — expected state: written before the run; hold the row if settings must be re-entered.
- Second structure — expected state: written before the run; hold the row if the package is edited directly.
Failures that need separate returns
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. Settings must be re-entered; preserve the failed artifact.
- 2. The package is edited directly; change only the responsible condition.
- 3. The old chapter name remains in build-two navigation; return to the named source.
Rune Studio as a bounded candidate
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 the same two-chapter manuscript, metadata, and order in every candidate passed this article's acceptance card.
Rune Studio is a plausible candidate when fewer source, setting, or reference handoffs help you compare generators by source return and an identical second build rather than first-build speed. Use another tool or destination check for the excluded range stated here: purchase price, processing-speed rankings, and KDP acceptance.
Next action
For the search phrase “EPUB generator comparison,” the conclusion is to compare generators by source return and an identical second build rather than first-build speed. The result is accepted only when the record establishes this outcome: complete the article-specific sample with separate evidence for source input, saved settings, first structure, chapter-name revision, second structure.
Begin here: prepare one two-chapter sample and a two-build comparison sheet. If settings must be re-entered, 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.
