Client crashes when importing translation file
December 29th, 2011
Earlier today, my attempts to import a translation file (in text format; not a language module) were met with this error message - equally persistent as it was uninformative:
which, after a while, was replaced with this:
Luckily, the error message turned out to be overly drastic, and the client was still running after I clicked Close program. It took me some time to figure out what had caused this problem. In the end, I was able to reproduce the problem with a tiny two-line translation file:
As you can see, the file erroneously contains the same “signature” (T11024193-F6-P8629-A1043-L30) twice. When editing the file before, I had forgotten to change the language code in the second line. Be sure to check for lines like these if you can’t seem to import a translation file! 
January 9th, 2012 at 11:19 am
Jan,
I suggest to report this as a bug to MS
January 9th, 2012 at 2:42 pm
You are probably right, Luc, although I don’t think dealing with invalid input, or code robustness issues in general, are a particularly high priority for the platform team. After all, correctly formed translation files can be imported without any problem.