Have you considered what to do the day there is an update to the game?
If I was to maintain changed text files, the way I would do it would be to use git. First I would make a branch for the unmodified game files (let's call it original). Next I would clone it and call the clone branch voice. Updates would then be committed to voice.
On game update, switch to original, overwrite the files with the new ones and commit. Next switch to voice and merge original into voice. This will copy all the changes into your version while keeping your own changes. If there is a merge conflict, it will have to be resolved manually, but as I understand it, that should only happen if the text changed, hence the voice file should be updated anyway.
Sure this might not be trivial to do if you never used git before, but being able to merge in updated game files in a few minutes could be a valid reason to learn how to use git. Also it's generally a good idea as it keeps old versions so if you mess up and destroy a script file, git will be able to retrieve an old version.