Thanks, should be fixed by 07e6c3270cad21adf2a52064b5b283defad79228

I consider it good practice to have the actual error message in english, and not translate it. Because they will most likely be reported on the forum, mailing list, and here, and an error message translated into an exotic language won't help Carl getting to the cause.

In this case, though, that has not happened. I guess the introduction, and the request to contact Carl should be translatable, and the technical error description should stay in english. Similarly for the log, if not better keep the log all english. Anyone with an interest in log reading should be able to understand enough english, and a log sent to Carl in greek or chinese probably won't help much. Even though he could probably translate it back to english from the .po files ;-)

The trouble for translators is that some strings in the po files might be used in the UI AND the log creating, and even if they are only used in the log creating or error message display, it is hard to identify these strings and their turning up there. At a time I was translating quite a few strings without thinking much about them, and only later saw they ended up in the log, but nowhere in the UI.

• Carsten

This problem appears not to be solved: it still exists in DOM 2.13.66