To insert alignment, quotes, and lists in a text editor, decide what each paragraph means, then apply one structure at a time. In a measured two-chapter Rune Studio sample, seven operations inserted three quotations, one unordered list, one ordered list, one centered line, and one right-aligned line. The generated XHTML contained the same 3–1–1–1–1 breakdown.
There is an important boundary. Rune Studio’s published documentation describes inserting these structures from the EPUB Markup panel or the Format menu. The measured run used nonvisual test controls that passed through the same notation conversion path; it did not exercise on-screen menu selection or show how a highlighted range behaves. This article separates documented interface behavior, measured source-to-XHTML results, and the checks you still need to perform in your installed version.
Choose structure by purpose, not appearance
Spaces and extra line breaks can imitate formatting on one screen, then drift when the font, viewport, or reading app changes. Classify the paragraph first.
| What you are writing | Structure to use | Fragile substitute |
|---|---|---|
| Speech or source material set apart from the body | Quotation | Indentation alone |
| Items with no required order | Unordered list | Manually typed symbols and spaces |
| Steps whose order matters | Ordered list | Numbers aligned with spaces |
| A standalone scene-break ornament | Center or other alignment | A row of leading spaces |
Do not use a quotation merely to create wider margins, and do not put list markers into quoted text unless the list is genuinely part of the quotation. Before formatting, you should be able to say whether the paragraph is borrowed material, a collection of items, an ordered procedure, or a standalone ornament.
Put seven targets in a two-chapter copy
The measured exercise used a dedicated copy rather than a working manuscript. Chapter 1 held two quotations, one unordered list, and one centered line. Chapter 2 held one quotation, one ordered list, and one right-aligned line.
| Chapter | Target | Source notation after insertion |
|---|---|---|
| Chapter 1 | Quotes 1 and 2 | > at the start of each line |
| Chapter 1 | Unordered list | - at the start of the line |
| Chapter 1 | Centered line | 《《center》》…《《/center》》 |
| Chapter 2 | Quote 3 | > at the start of the line |
| Chapter 2 | Ordered list | 1. at the start of the line |
| Chapter 2 | Right-aligned line | 《《right》》…《《/right》》 |
Each line was changed and read back before the next operation. That small scope matters: if a quotation marker captures the following paragraph or an alignment closing marker is missing, you can undo one operation without disturbing the rest of the sample.
The seven measured operations matched the XHTML
The three quote operations produced three source lines beginning with >. The unordered-list operation produced one - line, and the ordered-list operation produced one 1. line. The center and right operations each wrapped one line in their corresponding Rune notation.
After the two chapters were exported and the EPUB was unpacked, the XHTML contained three blockquote elements, one ul, one ol, one text_center occurrence, and one text_right occurrence. The body files also remained in source order as p001.xhtml followed by p002.xhtml. For this controlled sample, every inserted structure therefore had a corresponding output structure.
Those observations establish counts and chapter order, not an eternal class-name contract. A later version may express styling differently, and reading apps may render margins or centering differently. When you inspect XHTML, match the surrounding words as well as the element or class name.
Reproduce the workflow through the visible controls
Rune Studio’s feature documentation lists Quote, Unordered List, Ordered List, and left, center, and right alignment among the structures available from the EPUB Markup panel or Format menu. Use the smallest possible test in your own copy:
- Select one paragraph intended as a quotation.
- Choose the visible quotation command and confirm that the source gains
>only where intended. - Apply unordered list, ordered list, center, and right alignment to one target each.
- Open preview and check that body text, quotations, the two list types, and aligned ornaments remain distinct.
- Export an EPUB, confirm chapter order and navigation, then map the source passages to their XHTML output if you need structural proof.
Step 2 is your interface check. The measured run did not verify the exact on-screen label, highlighted-range behavior, or multi-line selection behavior. What it did verify is that single-line test operations produced the notation shown above and that the exported XHTML counts matched. Keeping those statements separate avoids treating documentation as a measured click result.
Check the package as well as the formatting
The same horizontal EPUB contained two body chapters, no inline images, one packaged cover image, and no missing resources. A navigation document and NCX were present, and the local package inspection returned valid=true.
That result means the tested chapters and cover formed a complete package for the local structural inspection. It does not promise retailer acceptance or identical rendering in every reading app. A useful sequence is source notation, Rune preview, generated XHTML, and finally the reading apps that matter to your release.
Who benefits from this method
The source-to-XHTML workflow is useful when you are preparing a long manuscript for EPUB and need to distinguish structural mistakes from rendering differences. If you are writing a short note that will only be read inside one editor, checking that editor’s preview may be enough. If your final output is fixed HTML, inspect that HTML rather than adding an EPUB step you do not need.
In every case, structure beats spacing. Quotes, lists, and alignment remain easier to repair when each one represents the paragraph’s actual job.
Conclusion
For text editor formatting with quotes and lists, work in a copy and insert one structure at a time. The measured seven-operation sample produced three quotations, one unordered list, one ordered list, one centered line, and one right-aligned line. Its XHTML matched with blockquote=3, ul=1, ol=1, text_center=1, and text_right=1, while preserving the two-chapter order.
The visible menu-selection experience remains a separate check. Open the documented EPUB Markup panel or Format menu in your version, apply a single command, and confirm the source notation before formatting a full manuscript. Current Mac product information is available on the Rune Studio website.