[i18n] IMP 4: Korean user problems

Wed Jan 26 10:09:47 PST 2005

On Wed, 26 Jan 2005, Jan Schneider wrote:
> > D'oh - meant to mention that.  :)  Messages from IMP appear to work
> > correctly, but messages from other mailers do not.
> 
> Then they are most probably broken. Can you post the full headers of such a
> message?

Here's a working message:

---</headers>---
>From user at example.com  Tue Jan 25 14:54:41 2005
Return-Path: <user at example.com>
(Cut Received Headers & Message-ID)
Date: Tue, 25 Jan 2005 14:54:39 -0500
From: user at example.com
To: user2 at example.com
Subject: =?euc-kr?b?wPy03jo=?= RE: [?? ????] Brokenletters
MIME-Version: 1.0
Content-Type: text/plain;
        charset=EUC-KR
Content-Disposition: inlineq
User-Agent: Internet Messaging Program (IMP) H3 (4.0.1)
X-Scanned-By: MIMEDefang 2.49
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit
---</headers>---

...and a broken one:

---<headers>---
>From user3 at example.com  Tue Jan 25 15:41:47 2005
Return-Path: <user3 at example.com>
(Cut Received Headers & Message-ID)
From: <user3 at example.com>
To: <user2 at example.com>
Subject: =?ks_c_5601-1987?B?x8+zqrTUwMcgxvKwrcDMLi4u?=
Date: Tue, 25 Jan 2005 14:41:36 -0600
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_0022_01C502EB.F8DE8570"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Scanned-By: MIMEDefang 2.49

This is a multi-part message in MIME format.

------=_NextPart_000_0022_01C502EB.F8DE8570
Content-Type: text/plain;
        charset="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable

<contents>

------=_NextPart_000_0022_01C502EB.F8DE8570
Content-Type: text/html;
        charset="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable

<html part>
---</headers>---

Note that in the first (working) message, viewing the message in a
terminal, the characters look like:

¼¶°Ü ÁÖ¼Å¼ °¨»çÇÕ´Ï´Ù.

For the broken message, they look like:

=C7=CF=B3=AA=B4=D4=C0=C7

Two different kinds of encoding?

> It works fine in IMP 3 because we simply spit out the message as is. If
> the user happen to use the same charset with the interface that the
> message is sent it, it magically works.

Ah, got'cha.

> The headers would be sufficient, but the only valid solution would be to
> add a user preference that specifies a default charset if none is given
> in the email message. But noone was interested to develop such a feature
> or to pay someone to develop such a feature yet.

Well, if this is indeed the problem, I may have to look into that.  :)

-- 
Nate Carlson <natecars at real-time.com>   | Phone : (952)943-8700
http://www.real-time.com                | Fax   : (952)943-8500