Ugh.PNG
[Hide] (13KB, 220x745) Stumbled on this thread a week or so ago and made a couple passes at translating here and there, finally made some headway, so I'll outline what I've managed so far. Also, I could fall out of contact, so forgive the wall of barely organized text, but hopefully it's at least descriptive enough as instruction.
Open AutoEtd.exe in DnSpy
Search for and document strings that you can find and want to translate (I ripped a few via OCR Capture2text and used DNspy's search functions to find that a lot of interface text is in Resources>AutoEtd.g/resources), once you have the text you want to translate...
Right click AutoEtd (top left in DNSpy), open in hex editor and search (ctrl+f) for the untranslated text (make sure it's set to search for String UTF-8), as an example, in the case of セーブ (which translates to save) you should be finding E3 82 BB E3 83 BC E3 83 96, use an online text to hex translator (also set to UTF-8) and insert your translation, in this case "Save", capitalized because it's a menu item, would be 53 61 76 65.
IMPORTANT#1: For above example, we found 53 61 76 65 83 BC E3 83 96 and are inserting 53 61 76 65, this will result in some extra characters at the end, but if you replace extras with 00, so 53 61 76 65 00 00 00 00 00 then it should be clean, HOWEVER, if the opposite happens, that is, if you have a longer translation hex sequence than the original hex, you will have to abbreviate and/or shorten your translation to fit, you can only substitute in the "space" that already exists, you can't change or shift anything else around.
Important#2: When searching via the hex view, you may find more instances than actually exist as text, this is more likely when searching smaller pieces of text. In these cases, and it would be wise to do this with every translated text anyway, translate one of them, save, run, and see if the text you try to translate is translated or not. If not, revert (if you leave DnSpy open you can undo/redo one hex at a time) and try the next instance and repeat.
Extra note:
>>48412
I'm unable to locate any of the text strings that are translated in this post, even the one ending in "MP", as well as any enemy names ripped from an adventure log export, so while some text can be translated through the method I've described (mostly UI I think), it's clearly not 100%.