Treat the search question “create EPUB from text file” as an evidence problem: verify source boundaries and save conditions before conversion and return every correction to source. The controlled case is a 3,000-word UTF-8/LF sample with three headings, blank lines, and deliberate section breaks. A pass must demonstrate this outcome: turn plain text into a conversion-ready source with stable chapter boundaries and encoding. The excluded range is stated separately: OCR, PDF extraction, and reverse conversion of an existing EPUB are excluded.
Decision: Verify source boundaries and save conditions before conversion and return every correction to source
Define the stop line on a recoverable copy. Evidence for encoding must exist before the run can advance to regeneration.
The article-specific evidence card has these fields: encoding, line endings, chapter boundaries, paragraphs, navigation inclusion, regeneration. Do not count the following excluded range as evidence: OCR, PDF extraction, and reverse conversion of an existing EPUB are excluded.
Use the topic-specific specimen
Use a 3,000-word UTF-8/LF sample with three headings, blank lines, and deliberate section breaks. The decisive fields are encoding, line endings, chapter boundaries, paragraphs, navigation inclusion, regeneration; keep the three stop conditions visible throughout the run.
This case addresses the failure behind the search: converting an unstructured text file and repairing chapter and paragraph damage afterward. 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.
The path to the inspected 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. Record encoding and line endings on a copy. Attach the observed encoding evidence to this step.
- 2. Freeze headings and page breaks. Attach the observed line endings evidence to this step.
- 3. Review blank lines in context. Attach the observed chapter boundaries evidence to this step.
- 4. Generate and compare chapters with navigation. Attach the observed paragraphs evidence to this step.
- 5. Rename one chapter in source and regenerate. Attach the observed navigation inclusion evidence to this step.
Inspect these fields independently
Do not infer one row from another. Record pass, revision, or not tested beside the actual target, date, output path or artifact ID.
- Encoding — expected state: written before the run; hold the row if the original is overwritten during conversion.
- Line endings — expected state: written before the run; hold the row if bulk cleanup removes intentional breaks.
- Chapter boundaries — expected state: written before the run; hold the row if a chapter name is repaired only inside the EPUB.
- Paragraphs — expected state: written before the run; hold the row if the original is overwritten during conversion.
- Navigation inclusion — expected state: written before the run; hold the row if bulk cleanup removes intentional breaks.
- Regeneration — expected state: written before the run; hold the row if a chapter name is repaired only inside the EPUB.
Second-pass rejection rules
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. The original is overwritten during conversion; change only the responsible condition.
- 2. Bulk cleanup removes intentional breaks; return to the named source.
- 3. A chapter name is repaired only inside the EPUB; preserve the failed artifact.
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 a 3,000-word UTF-8/LF sample with three headings, blank lines, and deliberate section breaks passed this article's acceptance card.
Rune Studio is a plausible candidate when fewer source, setting, or reference handoffs help you verify source boundaries and save conditions before conversion and return every correction to source. Use another tool or destination check for the excluded range stated here: OCR, PDF extraction, and reverse conversion of an existing EPUB are excluded.
What to do today
For the search phrase “create EPUB from text file,” the conclusion is to verify source boundaries and save conditions before conversion and return every correction to source. The result is accepted only when the record establishes this outcome: turn plain text into a conversion-ready source with stable chapter boundaries and encoding.
Begin here: label chapter IDs and save conditions on a 3,000-word copy. If the original is overwritten during conversion, 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.
