I wrote documentation today for the script tool we're using internally to develop #KitsuneTails. I think it's kinda clever. It allows writers to write normal looking scripts which are parsed for dialogue and converted into partial C# code files. Then coders (read: me) can finish out the partial implementation of the scenes by adding all the non-dialogue character actions and triggering sequences of dialogue with a single line of code where appropriate
And since the localization framework I created pulls localizable text out of a C# assembly it all goes automatically into a nice CSV for localizers. I even emit sorting information so that localizers will see dialogue in the order it occurs in the script
It's a really nice lil workflow and it really let's us iterate on the script a lot because it's trivial to rebuild. All I gotta do is do a plaintext Google Docs download and run a batch file if there isn't a change in sequences or scenes
@eniko A developer who writes documentation, metaprograms for inclusivity through multinational localization; a godde…
:notices CSV, claws go up a la Red Dwarf's Cat, hisses, and flees the room:
y no gettext message catalog love? I've got tooling (even GUI) which speaks that, and my translators can work with it. 😶
Now I need to investigate GILT (globalization, internationalization, localization, translation) in C# more deeply. See if there are any ideas to… uh… "borrow".
@alice you'd be lucky to get a localizer to even use a CSV file. Usually I wind up having to turn that into a properly unicode formatted excel spreadsheet
@eniko@alice Do the localizers get to insert sound files for localized voice acting? As I understand, the base localized voice acting is in English, but my immediate thought is if people wanted to add voice acting for other languages as well as text translations?
Add comment