Ru translation 3-618 (beta)

[Fonvight]

Tested on 3-618, was working long enough to mix up the version numbers in the linked PR. ( > <)

Done:

• Menus
• Strings
• Dialogs
• String files for translating SysDB №5 & №6.

Planned to add:

• UserDB of Basic RPG System.
• VariableDB of Basic RPG System.
• (Partially) SystemDB: Some parts are intentionally not translatable and left to be translated via (already done) string files.
• Common events of Basic RPG System (Currently wrestling with battle system bugs introduced during translation, no estimates for readiness).
• • All of above have to be added at the same time due to them being tightly interconnected with each other. That's why if one is not ready, none of above cannot be added. (Would be glad to be proven wrong though.)

Currently not planned for this project:

• Documentation: Personally I think that there is no need to translate already existing guides, and instead there should be written a new one, combining information from different sources and with a consideration of translation. It will both benefit the translators understanding of engine, give a reason to test and fix the system further and increase overall amount of searchable information about the engine.

Screenshots:

Note to add: Due to use of different software for working with RC files (Risoh editor vs. ("Recommended") Resource hacker), very likely that the currently described pipeline would not be able to compile the translation dll with included files. If required, I could describe the steps I personally use to compile the translation dll and even send one ready for use.

[WoditorTrans2000]

Hello! Thanks for make a pull resquest!
You translation is looking good!

About the different software you're using, I remember trying to use the Risoh editor, but I didn't get that far. So if you can, I'd like to know how to use it, so I can put it up as another way of doing a translation.

As this PR is a draft, are you going to add what you have planned or just the .rc and the two txt? Because if it's just the two, that's fine. You can make another PR in the future, when you've finished the basic RPG system.

[Fonvight]

Speaking of the steps to import the rc files via risoh:

1. Open the Editor.Lang.dll or Editor.exe (Whichever you're translating) in the Risoh editor. After that, you will see the list of the file contents in the left window.
2. Press the up-facing arrow in the interface. After that, you will have an opened import menu.
3. Select either of three files (Menu.rc, Dialog.rc or String.rc) and press Import. After this, if you open the corresponding fold on the left twice, you could see two files in one folder.
   3.1. If you get asked about replacing already existing entries, you can overwrite them. Likely that you will not have any files to remove in the next step.
   3.2. There is a possibility that you will get an error message during import. This can happen if the files we're trying to import have some formatting errors on incompabilities with the Risoh. If the error seems fixable, you could try to fix it yourself.
4. Clean up the extra files (Usually, original japanese ones) from fold. You can either open each one by hand, or try the included automation to do this for you.
   4.1. Without this step, there is a non-zero possibility that the applied translation would not display in the editor.
5. Repeat steps 3 and 4 untill you import all the files. After this step, you will have useable dll\exe.
6. Now you can drop dll in the editor's folder and open the editor to check whenever the translation applied correctly.

Please, take a note that Risoh cannot be used to work with embedded Zip files, since it refuses to replace them. And replacing the project Zips in the dll would not have an effect, which means that you will have to replace them in the editor.exe for change to take effect.

Speaking of the current PR state:
I'm considering to finish the work on the basic rpg system first before marking as ready. It's almost guaranteed that woditor will release some more updates in the time until I finish with this, but I'm pretty sure that's not my first time updating translation for minor releases. As for now, anyone interested in the current state of translation could try to assemble the useable version of editorlang themselves via instructions above.