Re: (Re-)coding problems forwarding calendar attachment

["Bjørn Mork" <bmork@dod.no>]

Katsumi Yamaoka <yamaoka@jpl.org> writes:
>>>>>> Bjørn Mork wrote:
>
>> This all looks good to me.  According to RFC2445, the default charset
>> for an iCalendar object is UTF-8, and the text within the object looks
>> like valid UTF-8 to me.
>
> I've modified Gnus so as to use UTF-8 by default for decoding
> text/calender parts.

Probably good, but may cause problems with pre-RFC (version 1.0)
text/calendar parts.  Let's hope everybody using those were sending
strict US-ASCII (possibly using QP to encode other charsets)

> It is because Gnus doesn't decode the text/calendar part since
> Gnus doesn't know the default charset for it, and inserts raw
> UTF-8 data in the message buffer.

I don't get the question anymore. Thanks.

But it still doesn't work.  The attachment is encoded as
quoted-printable and gets this header:

 Content-Type: text/calendar; charset=iso-8859-1; name=meeting.ics
 Content-Transfer-Encoding: quoted-printable

But it is not converted from utf-8, so that 'æ' is coded as '=C3=A6',
'å' as '=C3=A5' etc. 

Everything would have been fine if Gnus had just used

 Content-Type: text/calendar; charset=utf-8; name=meeting.ics
 Content-Transfer-Encoding: quoted-printable


Any idea where this confusion comes from?



Bjørn
-- 
I don't want to hear about your prostitute.