Yes, it is. However, if you don't include search keys in the text presented to the user, it isn't going help when you get a dialog that says (FTA): Sterownik

Yes, it is. However, if you don't include search keys in the text presented to the user, it isn't going help when you get a dialog that says (FTA): Sterownik ekranu przestał działać, ale odzyskał sprawność. That's missing something at the beginning or end that allows a search engine to say "aha! this is looking for this error message, which in English is this". This is a hard problem, at the same time; the translated log files[1] from work look something like this: 2009-12-13 14:21 BACK-E-00234 <text here, with optional parameter values> The key piece is "BACK-E-00234" (it's from the BACK module, it's an Error, and it's message 00234). When we have messages to display to the user in a dialog, we don't show that key information (or have a way of getting to it) because it's ugly. It's unlikely that the message mentioned in the article was hard-coded to Polish; instead the author is arguing about users and the searchability of non-English error messages. To increase the searchability, you need to include key details (e.g., "BACK-E-00234") that make the message significantly uglier to read. One possible way around this is to make sure your error dialogs are selectable/copyable (maybe put a button to do this), but on copy silently insert the search key details. [1] Our untranslated log files look more like: <M ID="234" T="2009-12-13T14:21:00.00000" S="E" M="BACK">...parameter tags here...</M>