Re: W-24 CAP Calendar CHARSET property issues

[Frank_Dawson@xxxxxxxxx]

>Should the default CHARSET be added to a calendar as an optional
>property?

Assume you mean Calendar Property? What about the case where the Calendar Property specifies "CHARSET:US-ASCII" and there is a component property with a ";LANGUAGE=<russian>" or whatever the country code-language combo is. Wouldn't there need to be the ability to set a character set on an individual property value? This would involve ISO 2022 style escapement or some such mechanism.

Yep. It is real ugly, but how else do you include multilingual textual information in a nominally "western European" calendar?

>I did not see any objections to this - change it to a 'Y' ?

Seems like this needs further discussion (see above) or should be resolved as NO, we don't add this property!

>Does this mean that if the property does not exist, the CUA
>may assume UTF-8?

If the above calendar property is added, then YES, the default would be UTF-8, per RFC 2445 default.