The short answer to EPUB gaiji unsupported characters
For EPUB gaiji unsupported characters, the practical rule is to list each candidate and make an editorial decision between a standard character, rewritten wording, or a documented image. This answers the search intent directly: protect the starting manuscript, make the risky action visible, and judge the saved file rather than the most reassuring screen.
This article uses reviewing private-use characters before EPUB export. That situation is narrow enough to test without exposing a complete book, yet realistic enough to reveal a wrong folder, selection, character, link, metadata value, or export choice.
The failure to prevent is mechanically substituting a lookalike and changing a proper noun. Keep that sentence beside the working copy. It gives the trial a concrete purpose and stops unrelated features from turning a focused test into a tour of the application.
Decide what each gaiji means before replacing it
A gaiji problem is editorial before it is technical. List every private-use or unsupported character with the surrounding word, its source, and the intended reading. A lookalike Unicode character may alter a person’s name or a historical term, so visual similarity alone is not a safe replacement rule.
For each candidate, choose among a standard character with the same meaning, a clearly documented wording change, or an image only when text cannot represent the necessary form. Record the chosen form and reason. That record lets a later edition repeat the decision instead of guessing from the rendered page.
Preserve bytes while testing encoding
Do not save over a file that has already been decoded incorrectly. Keep the source bytes unchanged and open duplicates under plausible encodings. The controlled comparison read identical wording from UTF-8, Shift_JIS, EUC-JP, UTF-16LE, and UTF-16BE files, with 39 or 40 characters as recorded, then read the active tab setting back as UTF-8.
That run proves encoding detection and setting readback for its own files. It did not overwrite deliberately mis-decoded text, recover corrupted binary data, perform OCR, or decide which alternative character is editorially correct. Those limits should appear beside the conversion record.
Search again after substitution
After approved replacements, save under a new name and reopen the file. Search for every original gaiji candidate, then search for the adopted forms. Read the proper nouns in context and export a short EPUB containing them. Package inspection can reveal missing resources, but visual review in the intended reader is still needed for glyph appearance.
Rune Studio can be tested for Japanese encoding detection and warnings around characters that cannot be represented safely. Use it to locate risk, not to automate linguistic decisions. Preserve the source and keep a substitution log outside the output file. Current Mac product information is on the Rune Studio official site.
Decide from a small production-like trial
Build the trial from a duplicate of material you understand. Record the filename, modification time, included chapters, and one explicit exclusion. Perform only the action needed for EPUB gaiji unsupported characters; do not repair newly discovered issues in the same pass.
After saving or exporting, close the view and open the result through its real path. Compare a known opening point, the place affected by the operation, and a final marker. If the article concerns EPUB, follow at least one navigation link into the referenced chapter as well.
When the readback differs, return to the first uncertain action. Change one factor on a fresh duplicate instead of stacking fixes on the handoff file. The method is successful only when you can explain what changed, what stayed outside scope, and how to recover the starting manuscript.
Conclusion
The next step for EPUB gaiji unsupported characters is simple: create the small duplicate for reviewing private-use characters before EPUB export, then list each candidate and make an editorial decision between a standard character, rewritten wording, or a documented image. Preserve the source, use a new output name, and inspect the reopened content before repeating the method on a full project.
Rune Studio is one candidate for this Mac workflow, not a substitute for editorial meaning, retailer requirements, or cross-reader visual review. Use the article-specific test above to decide whether its confirmed range matches your work.
Keep the date-named duplicate and your short decision note until the next publishing tool has opened the output successfully.
That final readback is where an attractive preview becomes a dependable file that another person can continue using.