Worst decision ever: "Translate exceptions in .Net"?
-
Oops. I thought I'm at the lounge... Can I move this topic?
-
Should exceptions be visible to user? I don't think so. Does showing a "raw" exception help the user to fix the problem? In 90% of cases, no. Exceptions are for programmers. If you don't have basic knowledge of English, it will be hard to write good software (read specifications, tutorials etc. would be a big problem). So why the heck does MS think it's a good idea to translate exception-messages? Ever tried googling a German (Italian, French, Japanese... ) exception-message? On a non-English OS you get language specific exceptions and it's a nightmare to figure out what the English message of this exception "could" be. PLEASE MS: Stop translating exceptions!! Sorry for my English.... der Vorgang ist aufgrund des aktuellen Zustands des Objektes unültig.
Worst decision? Propably not, but I agree with you it kind of sucks. On other hand I would bet my 5 pennies there are more than a few Japanese and French developers who prefer it like that. Who knows, perhaps it's just Microsofts' passive aggressive approach to enforce better error and exception handling :D.
Mislim, dakle jeo sam.
-
Should exceptions be visible to user? I don't think so. Does showing a "raw" exception help the user to fix the problem? In 90% of cases, no. Exceptions are for programmers. If you don't have basic knowledge of English, it will be hard to write good software (read specifications, tutorials etc. would be a big problem). So why the heck does MS think it's a good idea to translate exception-messages? Ever tried googling a German (Italian, French, Japanese... ) exception-message? On a non-English OS you get language specific exceptions and it's a nightmare to figure out what the English message of this exception "could" be. PLEASE MS: Stop translating exceptions!! Sorry for my English.... der Vorgang ist aufgrund des aktuellen Zustands des Objektes unültig.
Yes after receiving bug reports in different languages. I had to translate in google translator then search for it on google. Really annoying. But I think I should use English resources when sending the bug report from user. I understand your pain though.
TVMU^P[[IGIOQHG^JSH`A#@`RFJ\c^JPL>;"[,*/|+&WLEZGc`AFXc!L %^]*IRXD#@GKCQ`R\^SF_WcHbORY87֦ʻ6ϣN8ȤBcRAV\Z^&SU~%CSWQ@#2 W_AD`EPABIKRDFVS)EVLQK)JKQUFK[M`UKs*$GwU#QDXBER@CBN% R0~53%eYrd8mt^7Z6]iTF+(EWfJ9zaK-iTV.C\y<pjxsg-b$f4ia>
----------------------------------------------- 128 bit encrypted signature, crack if you can
-
Should exceptions be visible to user? I don't think so. Does showing a "raw" exception help the user to fix the problem? In 90% of cases, no. Exceptions are for programmers. If you don't have basic knowledge of English, it will be hard to write good software (read specifications, tutorials etc. would be a big problem). So why the heck does MS think it's a good idea to translate exception-messages? Ever tried googling a German (Italian, French, Japanese... ) exception-message? On a non-English OS you get language specific exceptions and it's a nightmare to figure out what the English message of this exception "could" be. PLEASE MS: Stop translating exceptions!! Sorry for my English.... der Vorgang ist aufgrund des aktuellen Zustands des Objektes unültig.
http://unlocalize.com/[^] /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
http://unlocalize.com/[^] /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
:thumbsup:
Wrong is evil and must be defeated. - Jeff Ello
-
http://unlocalize.com/[^] /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
Awesome! Thanks a lot!
-
Should exceptions be visible to user? I don't think so. Does showing a "raw" exception help the user to fix the problem? In 90% of cases, no. Exceptions are for programmers. If you don't have basic knowledge of English, it will be hard to write good software (read specifications, tutorials etc. would be a big problem). So why the heck does MS think it's a good idea to translate exception-messages? Ever tried googling a German (Italian, French, Japanese... ) exception-message? On a non-English OS you get language specific exceptions and it's a nightmare to figure out what the English message of this exception "could" be. PLEASE MS: Stop translating exceptions!! Sorry for my English.... der Vorgang ist aufgrund des aktuellen Zustands des Objektes unültig.
It's horrible. I've had to work with French exceptions for a Dutch client once (I'm Dutch too) because for some reason their network admin didn't know how to change the language :sigh: And in the Netherlands a lot of people install their OS in English too, but a lot have the Dutch install too (I've had both, switched to English when I started programming). So now I had Exception, for the same customer, in Dutch, English and French X| Even worse for Crystal Reports (as if CR isn't bad enough they also localize error messages)... There's even websites that translate error messages for you.
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
I propose moving this to the Lounge. On topic: Ganz meine Meinung. That's one of the reasons why I run Windows with the English language pack as a German developer.
Upvoted. Same for me: Italians translations are the best way to MISunderstand the computer world... Just an exceptions: Italian language keeps the English for many computer terms such as "mouse", "computer", "driver", etc. When someone (clearly NON-Italian native) translates them as well, the result is simply awful yet funny at the same time.
-
Should exceptions be visible to user? I don't think so. Does showing a "raw" exception help the user to fix the problem? In 90% of cases, no. Exceptions are for programmers. If you don't have basic knowledge of English, it will be hard to write good software (read specifications, tutorials etc. would be a big problem). So why the heck does MS think it's a good idea to translate exception-messages? Ever tried googling a German (Italian, French, Japanese... ) exception-message? On a non-English OS you get language specific exceptions and it's a nightmare to figure out what the English message of this exception "could" be. PLEASE MS: Stop translating exceptions!! Sorry for my English.... der Vorgang ist aufgrund des aktuellen Zustands des Objektes unültig.
Couldn't agree more. In my opinion (and I did express that every time I could to Microsoft) they should reduce localizing efforts anyway. Of course it makes sense to localize the help. But it does not make sense to localize certain expressions. Renaming stuff where the terminology is basically English does not make sense. People learning the localized (e.g. German) versions will be confused once they want to master the subject, people who have already mastered the subject will feel lost by using a localized system. The worst thing I've ever experienced is Microsoft Excel. Who (really, who?!) had the brilliant (sarcasm!) idea to localize the function names? Microsoft - we are not in the 80s any more. People know words like "Settings" or even applications like "Firefox".
-
Couldn't agree more. In my opinion (and I did express that every time I could to Microsoft) they should reduce localizing efforts anyway. Of course it makes sense to localize the help. But it does not make sense to localize certain expressions. Renaming stuff where the terminology is basically English does not make sense. People learning the localized (e.g. German) versions will be confused once they want to master the subject, people who have already mastered the subject will feel lost by using a localized system. The worst thing I've ever experienced is Microsoft Excel. Who (really, who?!) had the brilliant (sarcasm!) idea to localize the function names? Microsoft - we are not in the 80s any more. People know words like "Settings" or even applications like "Firefox".
Yes, Excel is another favorite! I remember that we had an issue with a French customer when we tried to select the appropriate Excel-sheet. The sheet names are also translated :(
