Regarding translation, it's done on the fly for mob names, as the vast majority of trash translations don't exist in Babble. Basically, deDE targets a mob, enGB says "I don't have a deDE translation for deDE's target", asks deDE about it, deDE replies with their mob name and both store the translation. I overhauled this system yesterday due to a number of problems resulting from race conditions; I'm -hoping- you should find it a lot more stable as of r42552.
masanbol, I'd recommend that your folks hold off on updating till a 1.0 Final release is made if the current development schedule is too aggressive for them - my own guild has made the same determination, and really, I think it's better for everyone. There's no sense in having people running out of date versions that likely contain critical bugs and which invalidate most of the test results
Void Reaver's module seems to not be working; I observed that myself on Sunday. I was working on translation stuff last night, but I'm planning to get the VR module fixed up tonight.
I haven't heard reports of Threat failing to report to KTM, but I'll also test that tonight; any additional info you can provide would be useful.
The "Incompatible" flag is set when I check in a change that contains significant bugfixes that affect the interoperability of Threat clients. Basically, if you're running r300 and I set the incompatible flag on r325 because I made a change in 325 that means that 300 may or may not properly talk to 325, then 300 is flagged as "incompatible" as a warning that that user should upgrade, as their client may contain bugs that will hinder your ability to work with your client.