For the case behind “Markdown text editor supported syntax,” define the evidence first: test the exact six required markup forms from input through preview and XHTML. The controlled case is one sample containing one heading, bold span, list, table, image, and link. A pass must demonstrate this outcome: complete the article-specific sample with separate evidence for input markup, editing display, preview, EPUB XHTML, unsupported boundary. The excluded range is stated separately: full CommonMark compliance, plugin extensions, and arbitrary HTML safety.
Decision: Test the exact six required markup forms from input through preview and XHTML
Use every required field as a blocker. A candidate with an unverified input markup or unsupported boundary stays on hold, even if its unrelated features look attractive.
The article-specific evidence card has these fields: input markup, editing display, preview, EPUB XHTML, unsupported boundary. Do not count the following excluded range as evidence: full CommonMark compliance, plugin extensions, and arbitrary HTML safety.
The acceptance case for this search
Freeze exactly six required forms—one heading, bold span, list, table, image, and link—and give every editor the identical text. Check editing display, preview, and generated XHTML separately, while listing unsupported syntax explicitly. A generic supported label is not full Markdown compliance, and preview cannot prove EPUB output.
This case addresses the failure behind the search: losing the authoritative input or acceptance evidence while trying to test the exact six required markup forms from input through preview and XHTML. 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. Freeze the six required forms. Attach the observed input markup evidence to this step.
- 2. Give every candidate the same sample. Attach the observed editing display evidence to this step.
- 3. Inspect editing and preview. Attach the observed preview evidence to this step.
- 4. Generate and inspect XHTML. Attach the observed EPUB XHTML evidence to this step.
- 5. List unsupported forms explicitly. Attach the observed unsupported boundary 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.
- Input markup — expected state: written before the run; hold the row if supported is presented as full Markdown compliance.
- Editing display — expected state: written before the run; hold the row if preview is treated as EPUB evidence.
- Preview — expected state: written before the run; hold the row if unsupported syntax is silently replaced.
- EPUB XHTML — expected state: written before the run; hold the row if supported is presented as full Markdown compliance.
- Unsupported boundary — expected state: written before the run; hold the row if preview is treated as EPUB evidence.
Where this workflow must stop
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. Supported is presented as full Markdown compliance; change only the responsible condition.
- 2. Preview is treated as EPUB evidence; return to the named source.
- 3. Unsupported syntax is silently replaced; preserve the failed artifact.
When to shortlist Rune Studio
Current product documentation covers capabilities relevant when you need to insert the supported markup subset and connect it to preview and EPUB output. That scope can justify a trial, but it does not show that one sample containing one heading, bold span, list, table, image, and link passed this article's acceptance card.
Rune Studio is a plausible candidate when fewer source, setting, or reference handoffs help you test the exact six required markup forms from input through preview and XHTML. Use another tool or destination check for the excluded range stated here: full CommonMark compliance, plugin extensions, and arbitrary HTML safety.
The decision to keep
For the search phrase “Markdown text editor supported syntax,” the conclusion is to test the exact six required markup forms from input through preview and XHTML. The result is accepted only when the record establishes this outcome: complete the article-specific sample with separate evidence for input markup, editing display, preview, EPUB XHTML, unsupported boundary.
Begin here: write the exact six-form acceptance sample. If supported is presented as full Markdown compliance, 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.
