Linked by Thom Holwerda on Mon 2nd Jul 2012 18:19 UTC, submitted by anonymous
Permalink for comment 524889
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
Linked by Thom Holwerda on 04/15/13 22:44 UTC
More Features »
Sponsored Links



Member since:
2006-07-26
I would expect that every OS logs and displays the error (Haiku does as well, this is supplementary since writing to the disk may not be possible). Multilingual error messages are sort of useless.
I have no idea what the Dutch word for harddrive is, but I can google the error message and find out what's going wrong (especially with a nice QR code so I don't have to type it, and even nicer if I can do it while the system reboots). What wouldn't help me is translating an obscure error into English so I get nothing when I google for it. Or even worse, I'd need to decipher the slaughtered metaphor term that didn't survive three translations (e.g. "Wrong Mode" for a syntax error in a configuration file).
I am not against translating simple error messages, like "unable to contact server". But when you get more advance errors (e.g. a BSOD), then it needs to be in the language of development. Of course, if most computer jargon is in English then it's a silly to translate error messages into something that takes knowledge of two languages to understand.