VASTT is a lightweight editor written by zalas for handling the translation of game script files. Below is a rough diagram of how the whole process fits together.
It looks complex, but it's not that bad. The header hacker/editor will usually handle the initial VASTT-import, which only needs to be done once.
- Commonly-used components are highlighted in blue
- Dashed lines indicate files that are used and included in a process, but you don't have to actually think about them at all
As a translator:
- you'll spend all your time in VASTT, dealing with untranslated VASTT XML files
- when you save your work, you're producing a translated VASTT XML file
As an editor, you deal with a small number of components:
- You'll spend most of your time in VASTT, correcting mistakes and making stuff sound better
- You'll save updates to translated VASTT XML files
- You'll also have a text-editor open, putting low-level hacks into the VASTT exporter
- You'll run a batchfile/Makefile regularly to run the exporter and arctool processes, so you can see the results of your changes