Greetings.
I will have to work on a project which asks to be published multiple times during the production process. To get a better grasp of the idea, imagine some sort of game, with lots of text and dialogues (and I mean lots), being divided into some sort of chapters (actually, not really, but that's for the explanation, that will do the trick). Every time a chapter is finished, the project is published as is. So each time, the game gets bigger, since it has the exact same content as before, plus the last finished chapter. So far, so good? Okay, so we continue. Now after each chapter is finished, some revisions on former chapters can occur (like removing or correcting errors, or even re-writing some parts differently), depending on the customers' reviews. The whole project fits in a single Articy Draft project.
Now comes the localization time. Every new update needs to be translated in a few languages. That means that after a new chapter is finished, every modification in former chapters has to be reflected in every languages, and the new chapter has to be translated from scratch. Any text that did not change must not be replaced or translated again. And that's where it becomes tricky.
When you have a full finished project, and you publish it, it's perfectly fine to translate out of an xml, json, or anything along those lines. But when you re-generate that xml or json every few times with modifications to some of the already existing text, plus some new text, how are you supposed to do? Let's say you are at chapter 3 in your development process. You generate the file, and translate everything, fine. Now you are at chapter 4, and you changed a few things in chapter 2. You generate the new file. How can you update the localized data in order to just re-translate what changed, and translate what's new, without having to bother the already translated content?
Being able to write multiple languages directly in Articy Draft would have done the trick, but it's not possible as far as I know. Is there a way I didn't think of that would allow to update the project with some new text (and modifications), and to just have to work on what changed in the localized versions of the files? Since those localized files have to be generated by duplicating-renaming the original file, I really don't see a way, yet.
As you can tell by the title, Unity will be part of the process, I don't know if it can help find an answer to be aware of that.
Any idea?
Maybe some script that compares the former version of the original xml with the updated one, and takes every unique id that corresponds to something that already existed and that didn't change, then using yet another script that use this id list in order to replace in the new localized file every line with those ideas with the former version of the same localized file? I'm sure it would do the thing, but I'm not competent in writing such a script (unless you can lead me to some lessons or tutorials which would get me there in no time). Or maybe is there a tool somewhere that would do just that already (even paid, as long as it's cheaper than the money I can put in it without selling my kidneys)?
Thank you and best regards!