When you search a chapter for “Saeki Makoto,” headings, ruby delimiters, and image directives can interrupt the sentences around each match if every token looks alike. This guide keeps character-name search at the center and colors only EPUB notation so that each name occurrence can be read in context. It does not color the character name itself.
The example is one 1,500-character chapter with five occurrences of Saeki Makoto, three level-two headings, four ruby expressions, two image directives, and four ordinary lookalike strings. Completion means reading all five name contexts, separating notation from ordinary symbols, and checking the notation result independently before output.
Search for Saeki Makoto and fix five locations first
Search for “Saeki Makoto” and record one sentence before and after each of the five matches. Add the occurrence order, speaker, and purpose of the name. If a match is the base text of ruby, record its reading on the same row.
Do not edit notation during this first pass. Separating the name-reading pass from the notation pass keeps a spelling decision from becoming a markup decision. If only four matches appear, check alternate spellings and search options before continuing.
Separate EPUB notation from prose
Heading markers, ruby delimiters, and image directives have structural roles that differ from ordinary prose. Syntax coloring should make those ranges easy to recognize and move them out of the reading path around each name match.
Do not use a color name as the acceptance rule because themes can change. Record the source range, notation type, and surrounding name context. Keep Saeki Makoto in the normal manuscript treatment.
Exclude ordinary lookalikes with a six-line sample
Build six short lines: one heading, one ruby expression, one image directive, and three ordinary sentences containing lookalikes such as #1, 《Reference》, and [Draft 2]. Only the first three lines should receive notation treatment.
If 《Reference》 becomes ruby or #1 inside prose becomes a heading, revise the source notation or coloring condition. A colored range is only a locator; it does not prove that the notation is correct.
Read every search match with its surrounding sentence
Return to the five name matches and open them in order. Read one sentence on each side and compare the form, subject, and speaker with the character sheet. Visually separated notation should reduce interruptions without changing the name.
Send a possible misspelling to the character sheet. Record an unclosed ruby delimiter as a separate notation repair. Do not solve either problem by assigning the character name a syntax color.
Return to the query and notation when five matches do not appear
Four results call for checking a spaced spelling such as “Saeki Makoto,” a ruby base, or an approved short form. Six results call for checking whether the character sheet example, image alternative text, or an editorial note entered the search scope. Do not widen the scope merely to force the expected count. Return to the five prose occurrences promised by the example.
When a result lands inside notation, do not skip it based on color alone. In a ruby expression, count Saeki Makoto as the base-text occurrence and do not count its reading as a second name. If an image’s alternative text contains the same name, classify it separately from prose. These distinctions give a different return point to a missing occurrence, an alternate spelling, and a misunderstood notation range.
Check coloring and output separately
Editor color identifies source structure; it does not prove the finished EPUB. Check heading hierarchy, ruby base text and reading, and image alternative text and destination in preview or generated output.
The current macOS version of Rune Studio colors its supported Markdown-style and product-specific notation, including headings, ruby, images, links, quotations, lists, tables, code, and page breaks, and converts that notation for preview and EPUB XHTML. This is a bounded feature set, not complete support for every Markdown extension.
A hands-on output check converted headings, ruby, a table, and code into XHTML without leaving the source notation behind. The specific editor colors and editor-to-preview round trip in this article have not been observed. Record color behavior and conversion results in separate columns on your system.
Keep proper-noun lists and repeated-word revision separate
If the goal is to highlight the character name itself, use a proper-noun workflow tied to a character, place, and term authority. If the issue is a word such as “quiet” appearing too often nearby, use repeated-word and caution-term revision.
This guide searches for Saeki Makoto and reads five contexts. It colors only the EPUB notation that interrupts that reading. It does not decide accepted character forms or rewrite prose through the same color rule.
Conclusion: search the name and move notation aside
First fix the five Saeki Makoto matches. Then use the six-line sample to separate heading, ruby, and image notation from ordinary lookalikes. Finally, read the surrounding sentences and judge name decisions separately from notation repairs.
Review the supported notation on the Rune Studio product page. Keep the setting only if all five name contexts can be read, ordinary symbols remain prose, and the converted structure matches the intended result.
