Re: The charset issue
Mark Swanson <mark <at> WebServiceSolutions.com>
2003-03-03 03:25:14 GMT
On March 1, 2003 07:20 am, Andrea Campi wrote:
> On Fri, Feb 28, 2003 at 09:17:04AM -0500, Mark Swanson wrote:
> > On February 28, 2003 06:23 am, Andrea Campi wrote:
> > > Since the discussion has reached (IMO) a dead end, I'll voice my
> > > opinion. I am 1000% of Doug's opinion. Mark, you are presenting a
> > > non-compliant implementation as reason for changing RFC2445. Like it or
> > > not, an http
> > No Andrea. This is not why I am doing this at all.
> > Perhaps a summary of reasons will help:
> > 1. MIME is not the universe (to steal a phrase from John Stacke . 2445
> > states iCalendar objects are to work fine outside the MIME environment.
> > To quote from 2445, "the format in this memo is equally applicable for
> > use outside of a MIME message content type.".
> This is exactly the reason why I think no change is necessary. If
> you are in a MIME environment, use MIME. If you are not, you MUST
> use UTF-8. I think this is quite reasonable in fact.
I mostly quite like that.
Unfortunately 2445 does not agree with us.
Instead of a CHARSET property would you agree to rewording 2445 so UTF-8 MUST
be used if not in a MIME environment?
> > There are the obvious examples of using an iCalendar object outside the
> > MIME environment: http/ftp/custom protocols - even copying the iCalendar
> > object as presented by Outlook (in text format, which does not show the
> > MIME headers as part of the iCalendar object) to the clipboard. John