- Oct 30, 2020
- 664
- 763
I didn't notice at all, If it's machine translation its very high quality then
- Thread starter Shadesishere
- Start date
- Sep 25, 2021
- 111
- 304
I have been using v4.3.31, let me upload here just in case someone needs it, even though prob won't work with Wolf3
You don't have permission to view the spoiler content.
Log in or register now.
- Apr 14, 2019
- 1,086
- 3,012
There is still the Wolf Editor for the engine itself, though that would take searching out each line and manually replacing the text. With the engine update, you'll need a 3.x version of the editor, but thankfully someone has translated the basics of the engine here. Takes a bit to get used to, but there's a search engine for both map and common events, so you can use the extracted text from Translator++ to then find it in the code and replace it.
- Oct 30, 2020
- 664
- 763
- Dec 5, 2020
- 1,639
- 12,491
soooo, if i'm understanding right, the translator++ just isn't updated enough to deal with the new elements of the newest WolfRPG version?
- Dec 5, 2020
- 1,639
- 12,491
It's worse than that, trying to edit the 1.3.1 translation borks it too, I suspect this is due to translate++ being updated and something just not working as intended.
either way, dev of Translate++ is aware of the issue.
Welp, guess I'm an npc for this specific game then.
heck, I don't even have eyes in this game ¯\_(ツ)_/¯
Ah, so regardless, translator++ needs a fix in order to not bork itself when doing anything WolfRPG related, as whatever they did with their update screwed itself over.
so now the real question is, do we wait paitiently for that fix, or do we try other tools and pray they can get the job done properly?
- Dec 4, 2019
- 6,543
- 8,587
It's an unwritten rule that H protags must never reveal their eyes in their normal state.
- Oct 30, 2020
- 664
- 763
Hi Shade, In case you're interested, I made a script that can convert translator++ csv files to a json file. This json file can be loaded by MTool.
The idea is to export your translator++ project as .csv files using one of the options below (export whole project or export selected content), this process will export the csv files into a "Data" folder.
Then the `script.py` from the attached file can be placed alongside the "Data" folder and once it's executed (Running "python script.py"), a "TrsData.json" file will be created. This file can be placed in the game folder and loaded with MTool.
Export selected content may be needed as some sections (such as CommonEvent/264-272) will throw an error and stop the exporting process of the project, at least on my end:
The script creates a json file like so:
This json file will mostly work, but some translations will require a quick fix to make sure the key value matches with what MTool expects. For example if I export the "text to be translated" from 1.4.1 using MTool (Trasnlate tab -> Export the text needs to be translated), in the json file created i get:
"」を手に入れた。": "」を手に入れた。"
While the json file generated from translator++ is something like:
"@1\n「\\cself[8]」を手に入れた。": "Translated text"
So here the idea is that MTool expects "」を手に入れた。" as a key, so "@1\n「\\cself[8]" should be removed and the final result should be:
"」を手に入れた。": "Translated text""
This process of fixing translation should be quick using "Find and replace" from a text editor.
I hope this helps. In the attached file I uploaded the `script.py` file needed along with a README.md file with extra instructions. Also the zip file contains a sample "Data" and "TrsData.json" file.
Proof that it works:
Also, if you decide to go with MTool, I can make another script to automatically create a json file for the new untranslated lines from 1.4.1+ so you can focus on translating only the differences between versions, then you can just copy paste the result into "TrsData.json". If you upload the "TrsData.json" with the current translation I'll make the script as soon as possible.
Last edited:
- Oct 30, 2020
- 664
- 763
- May 2, 2020
- 55
- 42
Man i Iike reading the community efforts going on here
- Dec 30, 2020
- 1,154
- 8,375
I imagine that when you say the one that colors, do you mean me?Just wanted to thank all the translator and the one that colors this astounding game. Thank you guys.
Dont push yourselves too hard. Rest when you need to or talk to us to avoid getting burned out.
I must confess since I no longer have a weekly update promise, I have felt calmer.
I feel that making an effort to meet deadlines affects the final result, there is nothing better than going at your own pace and putting your heart into your work, that kind of dedication will be seen in the final result.
You're right, it's quite comforting to see that more people like this game so much that they take the time to work on it.
- Dec 5, 2020
- 1,639
- 12,491
It's a damned shame that most of the tools I use for the translations need updating, especially as I set time aside for this entire week...
right now I'm going to work on the assumption that Translator++ will be updated, so I will concentrate translating what I can, with the assumption that I can quickly move the data over once the issues are resolved. not being able to access the databases of the game is annoying, as I cannot see a reason why Translate++ doesn't recognise them.
I will also be looking into other methods such as Mtool as other people have suggested.
right now I'm going to work on the assumption that Translator++ will be updated, so I will concentrate translating what I can, with the assumption that I can quickly move the data over once the issues are resolved. not being able to access the databases of the game is annoying, as I cannot see a reason why Translate++ doesn't recognise them.
I will also be looking into other methods such as Mtool as other people have suggested.
