Foreign language characters

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

8twr - 13 May 2008 19:33 GMT

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?

Reply to this Message

Roady [MVP] - 13 May 2008 19:47 GMT

Are you using a UNICODE formatted pst-file?
See http://www.msoutlook.info/question/111

Signature

Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

http://www.msoutlook.info/
Real World Questions, Real World Answers

-----

> I receive emails from a Korean customer that have a mix of English and
> Korean
[quoted text clipped - 5 lines]
> settings
> with the same result - any ideas?

Reply to this Message

8twr - 13 May 2008 20:52 GMT

Using UNICODE.

> Are you using a UNICODE formatted pst-file?
> See http://www.msoutlook.info/question/111
[quoted text clipped - 8 lines]
> > settings
> > with the same result - any ideas?

Reply to this Message

Pat Willener - 14 May 2008 06:09 GMT

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

> 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?

Reply to this Message

8twr - 14 May 2008 18:52 GMT

The incoming message is encoded "Korean (Auto-Select), plain text.

> What is the encoding of the incoming messages. Also, what message types
> (HTML or plain text)?
[quoted text clipped - 5 lines]
> > Encoding - set at Western European (Windows). I have tried several settings
> > with the same result - any ideas?

Reply to this Message

Pat Willener - 15 May 2008 05:08 GMT

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

> The incoming message is encoded "Korean (Auto-Select), plain text.
>
[quoted text clipped - 7 lines]
>>> Encoding - set at Western European (Windows). I have tried several settings
>>> with the same result - any ideas?

Reply to this Message

8twr - 15 May 2008 15:50 GMT

This is what it shows:

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

> Check the message headers (View -> Options -> Internet headers) what the
> actual encoding is (Content-Type:text/plain; charset= ).
[quoted text clipped - 10 lines]
> >>> Encoding - set at Western European (Windows). I have tried several settings
> >>> with the same result - any ideas?

Reply to this Message

Brian Tillman - 15 May 2008 19:09 GMT

> 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.

Signature

Brian Tillman [MVP-Outlook]

Reply to this Message

8twr - 15 May 2008 22:27 GMT

Brian,

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

Return-path: <krlee@koreanair.com>
Envelope-to: terry@dascoeng.com
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 terry@dascoeng.com; 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" <krlee@koreanair.com>
To: =?ks_c_5601-1987?B?x9Swx8HWKFBQQixIQUhNIEtVTiBKT08p?=
<kjhahm@koreanair.com>
Cc: <terry@dascoeng.com>
Importance: normal
Priority: normal
X-OriginalArrivalTime: 13 May 2008 00:12:15.0560 (UTC)
FILETIME=[FFD50C80:01C8B48D]

> > This is what it shows:
> >
[quoted text clipped - 3 lines]
> There should be other Content-Type headers as well. One of those should
> have the charset value on it.

Reply to this Message

Pat Willener - 16 May 2008 04:36 GMT

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,
>
[quoted text clipped - 47 lines]
>> There should be other Content-Type headers as well. One of those should
>> have the charset value on it.

Reply to this Message

8twr - 20 May 2008 20:59 GMT

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?

> 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
[quoted text clipped - 55 lines]
> >> There should be other Content-Type headers as well. One of those should
> >> have the charset value on it.

Reply to this Message