When a 450,000-character manuscript may contain an encoding conflict, do not start with a full conversion. Preserve the source, record size and encoding separately, prove that text near the end is searchable, reproduce the conflict in a short extract, and only then repair a full working copy.
Size and encoding are separate diagnoses
Slow display, one extremely long line, broad search scope, and an incompatible output character can all feel like a “large-file problem.” Record raw count, detected encoding, line endings, and one fixed search result on separate lines. That makes it possible to see which property changed.
A controlled file above 300,000 characters was identified as large, read as UTF-8 with LF, and returned one match for a marker near the end. Those observations do not rank performance across Macs or prove that autosave completed.
Prove that the end of the manuscript is present
Place or identify a unique phrase near the final pages and search for it. One match confirms that the end is inside the searchable scope without requiring a manual scroll through hundreds of thousands of characters.
This is a completeness check, not a meaning check. Read the surrounding sentence after the search lands there.
Reproduce the encoding conflict in a short extract
Copy a few hundred characters around the suspected glyph into a disposable file and try the required output encoding there. A controlled run failed with the unsupported character present and reopened as Shift_JIS after an intentional replacement.
The exact red highlight, save-blocking dialog, and autosave-resume display were not confirmed in that run. Preserve the original independently and treat any visible warning as an additional checkpoint rather than a guaranteed backup mechanism.
Repair the full working copy and reopen it
Once the replacement is approved, edit the same location in a duplicate of the full manuscript. Require zero unresolved encoding conflicts, save under a new name, close the tab, and reopen the file. Recheck raw count, encoding, line endings, and the end marker.
If any one value changes unexpectedly, stop editing the saved result and return to the pre-save copy. A large-file workflow needs clear rollback points more than it needs a one-click promise.
For this workflow, a large text editor is useful only when its result can be checked after saving. Treat the reopened copy, reference lines, and expected count as the acceptance evidence, rather than responsiveness alone.
Choose a tool for the real bottleneck
Rune Studio fits writers who need manuscript context beside encoding, count, and search. It is not a performance benchmark or a byte-recovery utility. Review current scope on the Rune Studio product page. Start by choosing one end marker and one short conflict extract before opening the delivery copy for changes.