When you try to OPEN an attachment,
you must pass attachment to registered handler for the attachment. So
attachment is extracted and handed off. It is no longer in MIME envelope.
_____________________
Note: new email address
tom_ransdell@xxxxxxxxxxxxxxxx
Doug Royer <Doug@xxxxxxxxx> Sent by: owner-ietf-calendar@xxxxxxxxxxxx
03/03/2003 03:57 PM
Please respond to
"ietf-calendar@xxxxxxx" <ietf-calendar@xxxxxxx>
To
"ietf-calendar@xxxxxxx"
<ietf-calendar@xxxxxxx>
cc
Subject
Re: Charset
Robert_Ransdell@xxxxxxxxxxxxxxxx wrote:
>
> Does not matter since I have to look at attachment after it was
> de-attached.
Then that is the real problem not the fact that the object
does not have its original charset inside the object. You seem
to be talking about how you store the object in your application.
If you are electing to save it in its original charset then that
is fine. If you charset it to UTF-8, then you would not need it.
What do you do when you get a charset that you can not read without first
knowing the charset - after ripping off the MIME header?
It looks to me as if MIME and iCalendar is working as documented.
Otherwise you would not know that it was SHIFT-JIS. And that
is what iCalendar + iMIP is about - it is already 100% portable - correct?
So despite the fact that you want to add CHARSET to the object,
your telling me that as an interoperability protocol - you did
not need it. How you store object internally (which is what I seem
to think you are saying) is out of scope for this working group.