To add ruby safely, select the base characters, enter the reading, and verify that the original word still exists after insertion. Finishing one word at a time is usually faster than preparing a large reading list and later repairing shifted selections.
This guide is deliberately narrow: it adds one reading to one difficult term. Mixed Japanese markup and the choice between ruby and emphasis belong to separate articles.
Define the base before the reading
Use the word 黎明 with the reading れいめい. Select only the two base characters, excluding punctuation and particles. If the word appears many times, test the first occurrence before considering the rest.
Complete one insertion
- Duplicate the target paragraph.
- Select exactly
黎明. - Choose ruby insertion and enter
れいめい. - Read the edited source and confirm that
黎明remains. - Check the reading in preview.
Rune Studio provides a ruby insertion tool. Testing completed so far confirms one completed insertion on 漢字. It does not yet confirm a seven-target run with exclusions or a full enumeration of ruby elements in generated XHTML. This article therefore avoids claims about reliable batch insertion.
Recover from a shifted range
If punctuation becomes part of the base, undo that occurrence and select again. If the base disappears, compare with the untouched paragraph rather than trying to reconstruct it from the markup. If the notation appears literally in preview, confirm that the current file and preview mode support the notation.
Stop bulk work when pronunciation depends on context, a name boundary is unclear, or ruby already exists. Mark those entries for individual review.
Repeat the smallest proof on another day
Before adopting the single ruby insertion, close the project and repeat the smallest useful path later. Record the untouched paragraph, exact base characters, intended reading, and preview result. A result that depends on memory or an already-open preview is not yet a dependable routine.
Keep one untouched copy and change a single condition per retry. If the second run differs, identify whether the source, operation, or inspection changed before expanding the scope. This rehearsal is also the point to keep batch ruby processing clearly labeled as unverified rather than filling the gap with an assumption.
The next practical step for the single ruby insertion is to prepare the smallest useful copy and write down its expected result before touching the production manuscript. Extend this particular workflow only after the observed result matches.
Conclusion
Ruby entry stays manageable when the base, reading, and result are closed as one small task. Rune Studio has a verified one-word insertion in testing so far; broader target coverage remains untested. Start with one copied paragraph and expand only after the base text survives. See Rune Studio’s ruby tools
