On Thu, Jan 15, 2009 at 12:21 PM, Steffen Kaiser <skdovecot@smail.inf.fh-brs.de> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 15 Jan 2009, Allan Cassaro wrote:
discover that is a error, not a response... With the patch, I can translate the error to my languange and avoid this...
Now consider this:
I assume you do not fluently speak Chinese
Somebody, who does, "translates the error to his language" and _you_ get the response.
I really hate the gibberish I get from MS Exchange translated into all the languages from all over the world and encoded into something like UTF7 without MIME.
Actually I don't know what's the most commonly understood term for "delivery failed" - maybe "ERROR:" - , but it should be plain English to avoid:
a) confusion for the rest of the world and b) problems you inherit in order to MIME-encode non-7bit characters in the header.
Bye,
Ok, I understood. But, this is a personal choice: translate or not to my language. Why exclude this choice? (l10n / i18n). Sorry, but this is a very requested feature from my users to me...
And now, for your consideration:
- The general rule is: My users speak portuguese and send e-mails in portuguese;
- The exception: **Some** users send e-mail in other languages (like Chinese) to some (and only to external) users...
Maybe, **some** (external) users will receive an error message that him will not understand. But 99,99999% of my (external AND internal) users will receive an error message that him will undestand.
So, why transform an "exception" in "general rule"? This not make sense to me. And why not give the mail adminstrator the choice?