Today I stumbled on an obstacle that could have very well jeopardized the Riivolution patch.
While doing some tests, both with the console and the new Riivolution feature of Dolphin, I realized some dialogs I had translated had stayed in Japanese.
After a few investigation, I came to the conclusion these dialogs were all stored in files which had weird names in Windows Explorer, as evidenced by the picture below:
After going further into the globality of the files (and there were quite a few), I came to the conclusion these files had their names in Japanese, but weren't displayed correctly (you can find the real names in files that refer to them if your hex editor displays characters in SHIFT-JS.
So I went backward, and opened the "reference files" in ISO-8859 (or "Latin"), which led me to identify the names I could see in the explorer.
I tried to rename the files with their Japanese names, but while Dolphin could display the text, the console couldn't
(incomplete list below)
Then I used a feature from Riivolution which is just MARVELOUS : for your information, you can add a "create" variable in the xml file (which tells Riivolution where the files to replace are on the disc), so that
if the software doesn't find the files, it "imports" the ones from the patch on the disc (not physically of course, but while the patch is in use).
That way, I was able to replace the "wrongly displayed" names of the files with "Western" ones, then change the references in the files, and Riivolution would actually understand that, instead of replacing a file by one named the same way, it had to use a different one!
So if any of you ever meets a difficulty like this with Japanese files that show gibberish for their names, this could be a way out!
As for me, I'll be changing the names of the files once and for all, so I can do my tests without worrying about this anymore.
Have a nice WE.
