When an editor highlights characters that cannot be written in the chosen encoding, the next task is editorial repair, not a blind replace-all. Read each location, decide what the character means, record the approved substitute, and then save a named copy. The repair is complete only after the copy reopens correctly with no unresolved characters.
A highlight tells you where, not what
An unsupported emoji may be decorative, while an uncommon character in a person’s name may be essential. Both can trigger the same compatibility problem. The editor can identify the location, but it cannot know whether to spell out an idea, use an ASCII symbol, retain UTF-8, or ask the author.
Treat each marked location as a decision waiting for context. Keep the original character, sentence, proposed change, and approver in a small change log. That prevents the same question from being answered differently in several chapters.
Sort five conflicts before editing
For a sample containing two emoji and three platform-dependent characters, classify the locations as safe to rewrite, requiring approval, or not replaceable. Decorative marks may have clear prose equivalents. Mathematical notation and names often require a policy decision. If one essential character has no approved substitute, stop the Shift_JIS delivery instead of forcing the save.
This distinction keeps the objective honest. Zero warnings achieved by deleting meaning is not success. Success means zero unresolved decisions plus a readable file that survives reopening.
Work through Rune Studio one location at a time
Choose the intended output encoding for the working copy and review every indicated location in its surrounding sentence. Edit one location, update the change log, and move to the next. Avoid replace-all even when two glyphs look identical; they may serve different roles in dialogue, names, or notation.
A controlled conversion failed while the unsupported character remained and reopened correctly as Shift_JIS after an intentional repair. That confirms the repair-and-reopen route. The exact red rendering and the graphical autosave-resume state were not part of that run, so verify those visible states in the installed application instead of treating them as already proven.
Reopen the saved bytes
After the conflict list reaches zero, use Save As and keep the source file. Close the result, reopen it with the target encoding, and visit all five changed locations. Also inspect the last paragraph. This catches a conversion that looked correct only because the editor still held the original Unicode text in memory.
If a location differs after reopening, return to the pre-save working copy. Do not stack more replacements on the damaged result. Compare the change log with the reopened text and isolate the first edit that did not survive.
Choose the tool by the kind of work
Rune Studio is useful when the conflicts must be judged in the surrounding manuscript. A batch compatibility scanner is more efficient when you only need an inventory across thousands of files. Neither tool can approve changes to names or specialist notation.
The practical finish line is an explained repair list, zero unresolved conflicts, and a separately named file that survives reopening. Review the current encoding scope on the Rune Studio product page, then rehearse the entire repair loop on a short duplicate before touching the delivery manuscript.