- Apr 29, 2017
- 15
- 13
I was thinking about using that approach, but while i was looking into it i noticed that even in the already existent locations there were come modifications from the v0.29. IT CAN WORK eh, it is just a warning.I'm working on taking all the v0.29 English translations from the Translation Project and putting them into v.30. Then we should only need to translate the new 12000 lines. But probably less than half of those lines have Russian text, so the problem isn't too bad. I just have no idea how to solve it, though, but I like your suggestion of giving volunteers smaller pieces to translate using google translate or something, we may get somewhere.
I myself translated entirely the v0.30 and posted the .qsp file a couple of pages behind, but the problem is that without a MT that can keep track of the definitions there can be no working version cause one time a word mean something and the next it means something else (it's the russian language from what i understood). If that happen inside the $data['...'] definitions it is over, and i my version that happened. right now i am translating every single definition (after using the v0.29 vocabulary) but it's a tedious work and it would be a foolish thing to do for every version. SO.. Basically the problem isn't solved, without QSPTools and a MT, you are looking at a really useless long work