|
Size: 232
Comment: dot syntax block
|
← Revision 3 as of 2010-05-23 11:05:02 ⇥
Size: 2207
Comment: all about VASTT
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| VASTT is a lightweight editor written by zalas for handling the translation of game script files. | 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. |
| Line 5: | Line 5: |
| {{{#!dot | {{{#!GraphViz dot |
| Line 7: | Line 7: |
| a; b; c; d; e; |
rankdir=TB; |
| Line 13: | Line 9: |
| a -> b -> c; b -> d; |
native [label="Native scripts" color=grey]; vastt_importer [label="VASTT importer" shape=box color=grey]; vastt_exporter [label="VASTT exporter" shape=box color=blue]; vastt_xml [label="Untranslated VASTT XML" color=blue]; vastt [label="VASTT" shape=box color=blue]; vastt_xml_translated [label="Translated VASTT XML" color=blue]; native_translated [label="Translated native-format script files" color=grey]; native_original [label="Untranslated native-format script files" color=grey]; arctool [label="arctool" shape=box color=grey]; origScript [label="Original Script.dat file" color=grey]; transScript [label="Translated Script.dat"]; native -> vastt_importer -> vastt_xml; vastt_xml -> vastt -> vastt_xml_translated; native_original -> vastt_exporter [style=dotted]; vastt_xml_translated -> vastt_exporter -> native_translated; origScript -> arctool [style=dotted]; native_translated -> arctool -> transScript; |
| Line 17: | Line 31: |
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 |
VASTT
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