In order to make that work I can do this two ways. I can reuse the engine from the Translator or write a second one. What I am thinking of doing is refactoring the Engine from the Translator and the usEN language files and moving them into the Sequence Editor with the Translator just containing the additional languages. This will increase the size of the Editor but wont increase the size of the core. ie If you disable the translator the core will still be its current snappy self. The additional language files will still remain optional.

By having the languages as a seperate addon that plugs into the editor, it means that we can create an errata file to be added into myMacros or similar for local problems. I dont play the game in every language ad while i have written a c# program to interrogate the Blizzard out of game API to get the language files there are things I miss. For example this morning Zalasir pointed out that the German translations missed Fiery Brand and Empower Wards. While I now have an export running, that process takes 4-5 hours and doesnt include Simplified Chinese. Where as adding somthing like

Lang[Key]["deDE"] {
[123456] = "Tuefelsklinge"
}
Lang[Hash]["deDE"] {
["Tuefelsklinge"] = 123456
}
Lang[Shadow]["deDE"] {
["tuefelsklinge"] = 123456
}

to a local file while waiting for the updater to complete makes resolution a few minutes rather than days.

Moved to 1.3