Foreign language characters

8

8twr

I receive emails from a Korean customer that have a mix of English and Korean
characters, and question marks between sentences. I am using Windows 2000
(SP4) with Outlook 2003 (SP3), at "Tools", "Options", settings are;
International Options, Encoding Options - Auto Select Encoding On, Preferred
Encoding - set at Western European (Windows). I have tried several settings
with the same result - any ideas?
 
P

Pat Willener

What is the encoding of the incoming messages. Also, what message types
(HTML or plain text)?
 
P

Pat Willener

Check the message headers (View -> Options -> Internet headers) what the
actual encoding is (Content-Type:text/plain; charset= ).
 
8

8twr

This is what it shows:

Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C8B48E.07327F13"
 
B

Brian Tillman

8twr said:
This is what it shows:

Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C8B48E.07327F13"
Click to expand...

There should be other Content-Type headers as well. One of those should
have the charset value on it.
 
8

8twr

Brian,

This is everything in the Internet Headers - I don't see charset listed:

Return-path: <[email protected]>
Envelope-to: (e-mail address removed)
Delivery-date: Mon, 12 May 2008 20:10:22 -0400
Received: from impinc03.yourhostingaccount.com ([10.1.13.103]
helo=impinc03.yourhostingaccount.com)
by mailscan12.yourhostingaccount.com with esmtp (Exim)
id 1Jvi62-0003Cq-MK
for (e-mail address removed); Mon, 12 May 2008 20:10:22 -0400
Received: from selexfe032.hanjingroup.net ([59.15.10.3])
by impinc03.yourhostingaccount.com with NO UCE
id QoAL1Z05c03w48T03oAMra; Mon, 12 May 2008 20:10:22 -0400
X-EN-OrigIP: 59.15.10.3
X-EN-IMPSID: QoAL1Z05c03w48T03oAMra
Received: from KESELMBX002.hanjingroup.net ([10.100.151.35]) by
selexfe032.hanjingroup.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 13 May
2008 09:12:15 +0900
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C8B48E.07327F13"
Subject: RE: Remittance Advice From Korean Air
Date: Tue, 13 May 2008 09:10:17 +0900
Message-ID:
<B7CD98B924CBD941A8798D7A4258306BCFF35F@KESELMBX002.hanjingroup.net>
Content-Transfer-Encoding: 7bit
In-Reply-To:
<B7CD98B924CBD941A8798D7A4258306B1793BC@KESELMBX002.hanjingroup.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Remittance Advice From Korean Air
Thread-Index: Aciei3dYFbjtPDfxSBiHX2NnrAlb2ATWQKRwABIWQGAAmC+dUA==
From: "LEE KWANG RO" <[email protected]>
To: =?ks_c_5601-1987?B?x9Swx8HWKFBQQixIQUhNIEtVTiBKT08p?=
<[email protected]>
Cc: <[email protected]>
Importance: normal
Priority: normal
X-OriginalArrivalTime: 13 May 2008 00:12:15.0560 (UTC)
FILETIME=[FFD50C80:01C8B48D]
 
P

Pat Willener

That explains it; the sender did not specify any Korean encoding, such
as 'iso-2022-kr'. It is the sender's responsibility to specify the
correct encoding. Once you have received it with broken multibyte
characters, there is not much you can do to retrieve the unbroken code.

You can try to edit the message, then specify the Korean encoding, but
it is unlikely that it will actually fix the broken characters.
Brian,

This is everything in the Internet Headers - I don't see charset listed:

Return-path: <[email protected]>
Envelope-to: (e-mail address removed)
Delivery-date: Mon, 12 May 2008 20:10:22 -0400
Received: from impinc03.yourhostingaccount.com ([10.1.13.103]
helo=impinc03.yourhostingaccount.com)
by mailscan12.yourhostingaccount.com with esmtp (Exim)
id 1Jvi62-0003Cq-MK
for (e-mail address removed); Mon, 12 May 2008 20:10:22 -0400
Received: from selexfe032.hanjingroup.net ([59.15.10.3])
by impinc03.yourhostingaccount.com with NO UCE
id QoAL1Z05c03w48T03oAMra; Mon, 12 May 2008 20:10:22 -0400
X-EN-OrigIP: 59.15.10.3
X-EN-IMPSID: QoAL1Z05c03w48T03oAMra
Received: from KESELMBX002.hanjingroup.net ([10.100.151.35]) by
selexfe032.hanjingroup.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 13 May
2008 09:12:15 +0900
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C8B48E.07327F13"
Subject: RE: Remittance Advice From Korean Air
Date: Tue, 13 May 2008 09:10:17 +0900
Message-ID:
<B7CD98B924CBD941A8798D7A4258306BCFF35F@KESELMBX002.hanjingroup.net>
Content-Transfer-Encoding: 7bit
In-Reply-To:
<B7CD98B924CBD941A8798D7A4258306B1793BC@KESELMBX002.hanjingroup.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Remittance Advice From Korean Air
Thread-Index: Aciei3dYFbjtPDfxSBiHX2NnrAlb2ATWQKRwABIWQGAAmC+dUA==
From: "LEE KWANG RO" <[email protected]>
To: =?ks_c_5601-1987?B?x9Swx8HWKFBQQixIQUhNIEtVTiBKT08p?=
<[email protected]>
Cc: <[email protected]>
Importance: normal
Priority: normal
X-OriginalArrivalTime: 13 May 2008 00:12:15.0560 (UTC)
FILETIME=[FFD50C80:01C8B48D]

Brian Tillman said:
There should be other Content-Type headers as well. One of those should
have the charset value on it.
Click to expand...
Click to expand...
 
8

8twr

I didn't mention it before, but a colleague receives a copy of the same
message and it comes through clean. Does this mean he has a different
version of Outlook, or has different settings?

Pat Willener said:
That explains it; the sender did not specify any Korean encoding, such
as 'iso-2022-kr'. It is the sender's responsibility to specify the
correct encoding. Once you have received it with broken multibyte
characters, there is not much you can do to retrieve the unbroken code.

You can try to edit the message, then specify the Korean encoding, but
it is unlikely that it will actually fix the broken characters.
Brian,

This is everything in the Internet Headers - I don't see charset listed:

Return-path: <[email protected]>
Envelope-to: (e-mail address removed)
Delivery-date: Mon, 12 May 2008 20:10:22 -0400
Received: from impinc03.yourhostingaccount.com ([10.1.13.103]
helo=impinc03.yourhostingaccount.com)
by mailscan12.yourhostingaccount.com with esmtp (Exim)
id 1Jvi62-0003Cq-MK
for (e-mail address removed); Mon, 12 May 2008 20:10:22 -0400
Received: from selexfe032.hanjingroup.net ([59.15.10.3])
by impinc03.yourhostingaccount.com with NO UCE
id QoAL1Z05c03w48T03oAMra; Mon, 12 May 2008 20:10:22 -0400
X-EN-OrigIP: 59.15.10.3
X-EN-IMPSID: QoAL1Z05c03w48T03oAMra
Received: from KESELMBX002.hanjingroup.net ([10.100.151.35]) by
selexfe032.hanjingroup.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 13 May
2008 09:12:15 +0900
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C8B48E.07327F13"
Subject: RE: Remittance Advice From Korean Air
Date: Tue, 13 May 2008 09:10:17 +0900
Message-ID:
<B7CD98B924CBD941A8798D7A4258306BCFF35F@KESELMBX002.hanjingroup.net>
Content-Transfer-Encoding: 7bit
In-Reply-To:
<B7CD98B924CBD941A8798D7A4258306B1793BC@KESELMBX002.hanjingroup.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Remittance Advice From Korean Air
Thread-Index: Aciei3dYFbjtPDfxSBiHX2NnrAlb2ATWQKRwABIWQGAAmC+dUA==
From: "LEE KWANG RO" <[email protected]>
To: =?ks_c_5601-1987?B?x9Swx8HWKFBQQixIQUhNIEtVTiBKT08p?=
<[email protected]>
Cc: <[email protected]>
Importance: normal
Priority: normal
X-OriginalArrivalTime: 13 May 2008 00:12:15.0560 (UTC)
FILETIME=[FFD50C80:01C8B48D]

Brian Tillman said:
This is what it shows:

Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C8B48E.07327F13"
There should be other Content-Type headers as well. One of those should
have the charset value on it.
Click to expand...
Click to expand...
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

MS Office Outlook Foreign Language Input 1
My folders are written in another language 2
Unable to change encoding to Unicode (UTF-8) manually in Hotmail 3
Reply Subject Header - RE: 4
Character Change in Sent Mail 17
foreign language encoding 1
Names in contacts; "non english" language 1
converting language 1

Top