How to handle translation of exception message?

Question

I don't really know the best way to handle exception in an multi-language application.

Where should I handle the translation of the error message (Exception.Message)?

Shall I translate the message in the ctor as soon as I throw the exception?

throw new MyException("Error message", Resource.MyException_TranslatedMessage);

Or do I throw the exception and I use a home made helper that will find the error message using the type of the exception in the logic of the View?

try
{
    //...
}
catch(Exception ex)
{
    myLabel.Text = new ExceptionTranslator(ex).Translate();
}

Or, does Microsoft offer a tool or a mechanism to do that?

In a word: what are the good practices to handle exception messages translation?

Tip: never expose exceptions to user :) better try to make your own messages translated by your translation manager — Kamil Budziewski, Aug 01 '13 at 12:27

Steven · Accepted Answer · 2015-05-11T10:17:16.123

16

Most exceptions are there for technical purposes, unless your operations and maintenance crew are also located in different countries, those exceptions should simply have messages in the language of the people who write and maintain the application.

The .NET framework contains localized exception messages. For me as a developer, that's very annoying, since the exception messages in my local language (Dutch) don't mean as much as the original English exception messages. However, it seems reasonable for Microsoft to localize those framework exception messages, since their target audience can be located anywhere.

Some types of exceptions however, are explicitly thrown to be displayed to the user. These are your ValidationException or BusinessLayerException. Their clear contract is to be displayed to the user. Of course you should localize those exception messages, but instead of translating them, it's often much better and easier to pull the exception message from a localized resource when throwing the exception:

throw new ValidationException(Resources.InvalidUserName);

edited May 11 '15 at 10:17

answered Aug 01 '13 at 12:33

Steven

166,672
24
332
435

Just a question: How do you log this into a file when the application is configured in Chinese (language I don't understand at all ;)). – JiBéDoublevé Aug 02 '13 at 13:35
Exceptions that are shown to the user (i.e. ValidationException) are not logged. They are not errors, but you use them to quickly and safely break out of an operation. Only technical exceptions should typically be logged. – Steven Aug 02 '13 at 18:15
such a good idea to have two types of exceptions: developer and end-user exceptions, thought doesn't seem a bit confusing as the general understanding of exception are merely for technical use? – Abdulkarim Kanaan Jun 06 '18 at 08:19

score 2 · Answer 2 · answered Aug 01 '13 at 12:28

Much better to only translate it when it needs to be displayed, IMHO. This applies to any localisable string, not just error messages.

Ideally, the logic of the code shouldn't care about the content - or language - of the message, it's only interested in the type of the exception. It's only the presentation layer that (might) need to display it in the local language.

score 1 · Answer 3 · answered Aug 01 '13 at 12:32

1

The external code should not translate messages

throw new MyException("Error message", Resource.MyException_TranslatedMessage);

This is best solution in my mind

answered Aug 01 '13 at 12:32

Viacheslav Smityukh

5,652
4
24
42

How to handle translation of exception message?

3 Answers3

Linked