Re: Bad Character
|From:||Mark Reed <markjreed@...>|
|Date:||Friday, September 28, 2007, 12:56|
It seems clear that Yvan's mailer uses a cascading automatic character
set selector, using the smallest char set that includes all the
characters in a given message, to maximize legibility in legacy,
non-Unicode-aware mail programs.
The ellipsis does not exist in ASCII or Latin-1 - but it does exist in
Windows-1252, which is a slight superset of Latin-1 because it uses
decimal codes 128-159 for characters instead of control codes.
The message as quoted by Yvan below is perfectly valid and has the
intended ellipsis char, so the charset confusion originated elsewhere.
On 9/28/07, KOENIG Yvan <koenig.yvan@...> wrote:
Mark J. Reed <markjreed@...>
> I was able to find my original message (the one I sent, not the same
> as I received it from the forum).
> I wonder how it may start with this header:
> Mime-Version: 1.0 (Apple Message framework v752.2)
> References: <3738A4B9-AE18-4CD7-9608-D13090EE5C11@...>
> Content-Type: text/plain;
> Message-Id: <3AE78F85-1B30-4AE3-9182-A12AD7036281@...>
> Content-Transfer-Encoding: quoted-printable
> From: KOENIG Yvan <koenig.yvan@...>
> Subject: =?WINDOWS-1252?Q?
> Date: Wed, 26 Sep 2007 13:51:34 +0200
> To: AppleScript List <applescript-users@...>
> as I never select Windows encoding myself.
> I'm not sure but maybe I used the "reply" button then edit the subject.
> I confirm: the original char was the macRoman char whose decimal code
> is 201.
> We get it using the improper ASCII character(201) in AppleScript.
> Yvan KOENIG
> Do not post admin requests to the list. They will be ignored.
> AppleScript-Users mailing list (email@example.com)
> Help/Unsubscribe/Update your Subscription:
> Archives: http://lists.apple.com/archives/applescript-users
> This email sent to firstname.lastname@example.org