A highlight on “Mako” cannot decide whether it is a mistake for Saeki Makoto or an intentional form of address. This character-name color-coding workflow sends each candidate back to a character sheet, place map, or story glossary before assigning approved, intentional, or pending status. Hands-on verification established only that a Default highlight list exists in the current settings. Creating lists, choosing colors, and displaying eight names remain unverified.
Return the highlighted “Mako” to the character sheet
Begin with an authoritative character sheet, place list, and story glossary. Register Saeki Makoto, Shiranami, and Lighthouse Festival in separate lists. A highlight is not permission to replace text; it is a route back to the source that defines approved, intentional, or pending status.
Makoto, Saeki, and a nickname may identify one person, yet their acceptability depends on narrator, speaker, and scene. Color collects candidates but does not infer identity.
Keep three lists and three reasons
Connect character names to the character sheet, places to the map, and invented terms to the glossary. One large list hides the reason a word matters. Keep list names in the record because colors can change with themes and accessibility settings.
When one string has two roles, record both authorities. Define when a reviewed item leaves the active list so the warning set does not grow forever.
Seed intentional exceptions
Put a formal name in chapter one, a relationship-specific nickname in chapter two, and a former name in chapter three. Mark two expected variants before scanning. A one-character difference absent from the character sheet remains pending until speaker and scene are checked.
Record term, chapter, surrounding sentence, authority, classification, and reviewer. Turn fourteen colored matches into nine approved, two intentional, and three pending decisions.
Separate temporary and maintained highlighting
Temporary same-word highlighting answers one local question. A registered list maintains a project rule across chapters. The repeated-word and caution-term revision workflow covers nearby repetitions and general caution words, while this article stays with proper nouns that have external authority. The EPUB notation-coloring workflow colors EPUB notation instead of names.
These boundaries produce different source material, operation, evidence, and conclusion rather than a renamed highlighting tutorial.
Separate the observed settings read from unverified highlighting operations
Current macOS Rune Studio documentation describes multiple term lists, highlighting for terms in the selected list, and color and opacity settings. It does not state to decide whether a name is correct or whether two forms identify one character.
The August 14, 2026 hands-on verification check only read a Default highlight list from the current settings. It did not create multiple lists, change color or opacity, or highlight eight character names across three chapters. The three-sheet workflow is therefore an editorial method, not an article-specific Rune Studio pass.
Documentation says registered-term highlighting is disabled among heavy display features for files of 300,000 characters or more. Keep any eight-name product trial unverified until it is actually run. Review the documented scope on the Rune Studio product page. Automatic proofreading, identity inference, collaboration, EPUB syntax coloring, and general repetition review are excluded.
Bind eight character forms to stable identities
Give the eight characters stable IDs P01 through P08 instead of using display names as identifiers. If P03 has three sound forms—full name, given name, and a role name—bind them to P03 and record the scene condition for each. Do not create a global replacement rule. A role name may be an intentional exception that expresses who is speaking.
Start location IDs with L and story-term IDs with T. When the same surface word can be a place fragment or an ordinary noun, return to context and the authority sheet. Highlighting retrieves candidates; it does not settle meaning.
Keep repetition work outside this article
If the approved name appears five times in one paragraph, the spelling can still be correct. Approve the five references here and hand readability or repetition control to the repeated-word and caution-term revision workflow. By contrast, a second spelling that points to P03 and has no intentional-exception record remains pending in this workflow. Completion is evidence for eight character terms, five locations, six story terms, and two deliberate forms—not the total amount of color.
Disambiguate shared surnames with character IDs
When two characters share a surname, one colored string cannot identify the referent. Give the character sheet stable IDs such as P01 Saeki Makoto and P02 Saeki Shuji. For every surname-only occurrence, record speaker and intended ID. Matching text can still require two different editorial decisions.
Different strings such as Makoto and Mako will not be grouped automatically. This workflow registers explicit forms and leaves pronoun resolution or implicit reference to human reading. It does not promise semantic entity recognition.
Treat list changes as revision history
Record when a term is added or removed, which character-sheet version justified it, and which chapters were rescanned. New highlights after a list update are new candidates, not automatically proof of an earlier proofreading failure.
When carrying a list into another volume, remove absent characters and add volume-specific exceptions. The list is an index between manuscript and authority, not the authority itself.
Separate four causes before adding a registered term
When a proper noun is not highlighted, classify the cause as unregistered, alternate form, manuscript typo, or collision with an ordinary word. For a word that can be both a person and a plant, bind only the person occurrences to the character ID and preserve the plant use as an intentional exception.
After adding a form, recheck other entries with the same reading. Completion means that approved person uses are retrieved and ordinary-word uses remain explainable, not that more text has acquired color.
Conditions for returning the three term sheets to the manuscript
-
Keep separate character, place, and story-term lists with separate authorities
-
Do not merge formal names, nicknames, and former names automatically
-
Use stable character IDs when two people share a surname
-
Seed two intentional exceptions before scanning
-
Record missing authority as pending rather than an empty success
-
Store list name and classification instead of meaning by color alone
-
Record list revision date and character-sheet version
-
Account for disabled registered-term highlighting at 300,000 characters
-
Run replacement only after classification is complete
-
Leave general caution words and nearby repetition to the repeated-word and caution-term revision workflow
Return character-sheet changes to the manuscript safely
Create separate character, place, and story-term sheets. Assign each candidate a stable ID and one status: approved, intentional exception, or pending. Resolve one ambiguous ordinary-word collision, then hand general repetition control to the repeated-word and caution-term revision workflow. Do not perform automatic replacement in this workflow. Review the documented highlight scope on the Rune Studio product page without treating the unrun eight-name sample as observed evidence.
