- Jan 1, 2018
- 2,544
- 15,731
In version 0.13 the dialogues are not compatible with the previous ones. First they were grouped in the 0001.dat and 0002.dat files, and now there are 21 unicode text files. What makes the thing more complex is that before each line corresponded a dialogue while now they are grouped ... How to complicate the simple things ...
If it is possible I would be very happy for the German 0.13 version! Please please
Here my translate for Brazilian Portuguese. Just past the files from 7z to folder data and replace all. For 0.13.0.007.
- May 26, 2017
- 1,448
- 359
- Jan 1, 2018
- 2,544
- 15,731
Here the very first release translated into Italian of 0.13.
It's raw and with untrusted translations of Google translate.
I plan to make at least one second (with the major corrections) and possibly a third one with details.
I had to do a php procedure to get there. In practice, I did this:
1) For each of the 21 text files, I read the contents in an array.
2) Isolate the Russian part from the English part, taking the text after the division symbol (Pipe).
3) I put on google translate the obtained list of the English part.
4) I get the translation that, unfortunately, very often, introduces several errors that prevent its use. In particular
often skips lines or introduces new ones by misaligning the English list from the translated one.
5) It is therefore necessary to carefully check that the correct line corresponds to each English line.
6) I load the two arrays (English and Italian) and for each original line I look for the English part, which, if found, I replace with the Italian one.
Unfortunately it is a very long procedure and there is also the problem that we need to save the data in Unicode encoding but php produces a lot
typos during the rescue. Not even pointing to the Russian charset (ISO-8859-1) solves a lot.
This procedure, however, saves the original html tags that are 3: <i> (italic), <b> (bold) and <color> (color).
If you like it, do not forget to put a like ...
It's raw and with untrusted translations of Google translate.
I plan to make at least one second (with the major corrections) and possibly a third one with details.
I had to do a php procedure to get there. In practice, I did this:
1) For each of the 21 text files, I read the contents in an array.
2) Isolate the Russian part from the English part, taking the text after the division symbol (Pipe).
3) I put on google translate the obtained list of the English part.
4) I get the translation that, unfortunately, very often, introduces several errors that prevent its use. In particular
often skips lines or introduces new ones by misaligning the English list from the translated one.
5) It is therefore necessary to carefully check that the correct line corresponds to each English line.
6) I load the two arrays (English and Italian) and for each original line I look for the English part, which, if found, I replace with the Italian one.
Unfortunately it is a very long procedure and there is also the problem that we need to save the data in Unicode encoding but php produces a lot
typos during the rescue. Not even pointing to the Russian charset (ISO-8859-1) solves a lot.
This procedure, however, saves the original html tags that are 3: <i> (italic), <b> (bold) and <color> (color).
If you like it, do not forget to put a like ...
- May 26, 2017
- 1,448
- 359