text encoding and multipart/* of digest mode
text encoding and multipart/* of digest mode
- Subject: text encoding and multipart/* of digest mode
- From: Chris Johnsen <email@hidden>
- Date: Wed, 12 Nov 2008 17:08:40 -0600
Sorry if this is getting too off topic. Maybe it will help clear up
some of the doubts about the list's digest mode.
Summary: MIME digests (multipart/digest) are available and seem to
preserve and convey content just fine (including Content-Type and
encoding from the original messages). If you use chevrons (or other
encoding-specific characters) and your MUA sends properly tagged
outgoing mail (supplying a valid transfer encoding and content-type +
content encoding), those subscribing via MIME digests will receive
your content just fine. It is still up to their MUA to display it
correctly, however.
On 2008 Nov 12, at 10:34, Paul Berkowitz wrote:
It's looking likely that the flaw may be in the list's digest
software that
is probably ignoring non-ascii characters and headers for some reason.
That's the only explanation that makes sense if Scott and other digest
readers saw question marks rather than chevrons when reading my
message
in the digest.
I saw chevrons in the version of the message included in the digest I
received.
Does the digest also display plain-text versions of HTML messages? If
there's anyone out there sending from some application that does
not send
multipart but HTML-only (I sure hope not, but you never know), that
must
make a horrible mess with all the markup source displayed.
Of course the digest does not actually display anything, but the one
I receive does seem to include all the original parts of multipart/
alternative messages. It is up to the MUA to pick the appropriate one
and display it.
applescript-users>), I have MIME digests turned on (it looks to be
the default, but I can not tell for sure). The digest that I receive
is 'fully multipart' and seems to contain almost all of each of the
original messages, including the alternatives of multipart/
alternative and attachments via multipart/mixed. The only obvious
things that are removed are the original headers that are not related
to the content (Received:, etc.). When I read the message from Paul
Berkowitz (3.5.1 below), my version of Mail.app (Version 2.1.3
(753.1); Mac OS X 10.4.11) displayed the chevrons just fine.
In a subsequent digest, the message from Scott Babcock that quoted
the above referenced message from Paul Berkowitz came across as
Content-Type: text/plain; charset="us-ascii" AND Content-Transfer-
Encoding: quoted-printable. In quoting the former message, the latter
message used question marks where the original, quoted message used
the chevrons.
Here is a partial breakdown of 'raw source' of my copy of
"AppleScript-Users Digest, Vol 5, Issue 604" that included the
initial chevron-using-message (3.5.1).
Content-Type: multipart/mixed
1. Content-Type: text/plain; charset="us-ascii"
(* digest header (list info) *)
2. Content-Type: text/plain; charset="us-ascii"
(* subject+author listing for messages in the digest *)
3. Content-Type: multipart/digest
(* messages *)
3.1. Content-Type: message/rfc822
(* Scott Babcock RE: accessing a property of an object in
AppleScript <46A76C76719C014A83752A1C54CE3B693661075E52@NA-EXMSG-
C125.redmond.corp.microsoft.com> *)
3.1.1. Content-Type: text/plain; charset="us-ascii" AND Content-
Transfer-Encoding: quoted-printable
3.2. Content-Type: message/rfc822
(* Luther Fuller Re: Help Book
<email@hidden> *)
3.2.1. Content-Type: text/plain; charset=US-ASCII; format=flowed;
delsp=yes AND Content-Transfer-Encoding: 7bit
.
.
.
3.5. Content-Type: message/rfc822
(* Xianyu_Ge Setup network use PPPOE <568FE568-ED30-4389-9FC0-
email@hidden> *)
3.5.1. Content-Type: multipart/alternative
3.5.1.1. Content-Type: text/plain; charset=US-ASCII; format=flowed;
delsp=yes AND Content-Transfer-Encoding: 7bit
3.5.1.2. Content-Type: text/html; charset=US-ASCII AND Content-
Transfer-Encoding: quoted-printable
3.6. Content-Type: message/rfc822
(* Paul Berkowitz Re: accessing a property of an object in
AppleScript *)
3.6.1. Content-Type: text/plain; charset="ISO-8859-1" AND Content-
Transfer-Encoding: quoted-printable
3.6.1. Body
Includes "Just use the proper =ABchevrons=BB and be done with
it." (i.e. quoted-printable codes AB and BB, the correct codes for
open and close chevrons encoded in ISO-8859-1 (iconv and hexdump
agree, anyway))
.
.
.
4. Content-Type: text/plain; charset="us-ascii"
(* digest footer (list address and URL) *)
--
Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden