-
All replies
-
Helpful answers
-
Mar 31, 2015 12:11 PM in response to krylovdxby Tom Gewecke,★HelpfulApple stupidly removed the ability to adjust incoming or outgoing encodings in Mail starting with OS X 10.9. There is nothing you can do to fix that except to use webmail or another mail app. Or you could try switching your OS language to Russian, but not sure that would help.
-
Mar 31, 2015 11:01 AM in response to krylovdxby pmiles,Check your settings in System Preferences > Language & Region... the order of the languages in this list affects which language it will attempt to use first and second, et al.
OS X: Changing the language shown in menus and dialogs - Apple Support
-
-
Mar 31, 2015 12:10 PM in response to krylovdxby Tom Gewecke,★Helpfulkrylovdx wrote:
The system language is russian.
Have you tried with the system language set to English?
-
-
Mar 31, 2015 12:10 PM in response to krylovdxby Tom Gewecke,★HelpfulCould you do View > Message > Raw Source on that email and copy/paste in an email to me (tom at bluesky dot org)? I will see whether there is an error in the message causing the problem.
-
Mar 31, 2015 11:48 AM in response to Tom Geweckeby krylovdx,at is @, isn't it?
if it's true I sent it(:
-
Mar 31, 2015 12:10 PM in response to krylovdxby Tom Gewecke,★HelpfulYou sent me the raw source of this web page. I need the raw source of that particular message from the Mail app.
-
-
Mar 31, 2015 12:08 PM in response to krylovdxby Tom Gewecke,★HelpfulThe person who sent the message used this encoding: charset="ks_c_5601-1987". That is some ancient stuff for Korean, not Russian. The sender should fix it.
-
Mar 31, 2015 12:10 PM in response to Tom Geweckeby krylovdx,Thanks, Tom, I will tell the sender to fix it!!
I was afraid that all letters should be received in strange encoding, but now I am calm(:
Thanks one more time!
-
Jun 21, 2015 10:29 AM in response to krylovdxby sukfromny,I have same issues with text encoding after I upgraded to Yosemite. Then I solved it by pure chance :-)
Forward the e-mails that you cannot read to yourself and see what happens. It worked for me with Korean and Chinese.
-
Jul 20, 2015 4:05 AM in response to krylovdxby 91koff,I have the same issue. Upgrading to El Capitan didn't solve the problem.
Bug requests in Feedback Assistant tool: for Yosemite #523042 (28 Feb 2015), for El Capitan Public Beta #966229 (20 Jul 2015)
And it's not a problem with sender's encoding.
There are the steps to reproduce the problem:
Environment:
Language&Region
Preferred Language
- English - Primary
- Russian
Region
- Russia - Russian
List sort order
- Russian
Keyboard
Text
- Correct spelling automatically = true
- Spelling = Automatic by Language
- Use smart quotes and dashes = true
Use case scenario:
1. Mail.app is running, 1 exchange account is active (exchange 2010 server)
2. Somebody sends an email in Russian using MS Outlook 2010 or 2013 that have a certain symbol in text that can be inserted in email’s text field in Outlook like this:
2.1 insert > symbol
2.2 type «space» button
2.3 Outlook autocorrection transforms the > symbol into the symbol that looks like the UNICODE sysmbol U+27A2 (usually people do so to show the quoted text)
3. Received email in Mail.app can’t be read because of bad encoding interpretation. All text looks like:
ŽąŽāŽÝŽåŽéŽÚŽÝŽāŽãŽî ŽáŽāŽÝŽåŽéŽÚŽäŽî ŽāŽäŽÓŽÖŽä ŽßŽŅ ŽáŽāŽâŽāŽã?
instead of
Получилось получить ответ на порос?
If this email is forwarded using Mail.app to somebody with Outlook 2010/2013 on Windows, received email on other side will have the same look as at Mail.app like this:
ŽąŽāŽÝŽåŽéŽÚŽÝŽāŽãŽî ŽáŽāŽÝŽåŽéŽÚŽäŽî ŽāŽäŽÓŽÖŽä ŽßŽŅ ŽáŽāŽâŽāŽã?
And YES, somehow encoding in RAW message switches from UTF-8 (default for Mail.app) or KOI8-R (default for Outlook in Windows) to Korean charset="ks_c_5601-1987".
It seems to me it's a bug in Mail.app when communicating with Outlook as Exchange client.
-
Jul 20, 2015 4:14 AM in response to 91koffby Tom Gewecke,91koff wrote:
And YES, somehow encoding in RAW message switches from UTF-8 (default for Mail.app) or KOI8-R (default for Outlook in Windows) to Korean charset="ks_c_5601-1987".
When you use View > Message > Raw Source in Mail on the original incoming, does it already have the junk Korean encoding? If so, then it must be Exchange that is messing it up. Mail cannot change the raw source of an incoming message.

