> Outlook is a pretty typical Windows application and a pretty typical Mail
> client. It is usually pretty good at reading the MIME tags on a message
> and assigning the appropriate character set to the message.
> Since the message you received apparently had no such tag, it was treated
> as ASCII.
> This is the problem for Notepad. Your "ASCII" is treated, I believe, like
> the "DOS" code page in Win2K (aka the OEM code page). This results in a
> character set conversion in Notepad from code page 437 (presuming that
> your're running US Windows) or code page 850 (if you're running a
> different Western European Windows) to CP1252, scrambling the Arabic
> characters pretty thoroughly. Nothing you do in Notepad after that will
Interestingly enough, in this case Outlook and notepad are behaving
appropriately once the message is there.... they are preserving the
(incorrect) encoding. The bug or problem is that the encoding was indeed
wrong in the first place -- a new twist on the old GIGO rule.
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:21:06 EDT