specifically, the CN (common name) parameter, e.g.
ORGANIZER;CN=John Doe,Eng:mailto:jd@some.com
The RFC is vague on this, IMHO. It is very clear about property values of type TEXT, but for this parameter it just says "The parameter value is text". Anyways, the escaping specified for TEXT type doesn't seem complete for parameter values (e.g. ':' is not escaped).
thanks a lot!
Davka,
Yes, parameter values can be escaped by surrounding the value in double-quotes. Parameter values must be escaped if they contain any of the following characters:
It is illegal to have a double quote
"
character inside parameter values, so they should be deleted (or otherwise removed from the parameter value).So, with your above example, the correct escaping is this:
Note that once the first (unquoted) colon
:
is encountered, parsing engines treat the rest as the property value. It is legal to use the colon:
character inside property values, so the colon inmailto:jd@some.com
doesn't need to be escaped.We can break the line into it's parts:
ORGANIZER
- property name;
- parameter delimiterCN
- parameter name=
- parameter value delimiter"John Doe,Eng"
- parameter value:
- property value delimitermailto:jd@some.com
- property valueHere's a quote from RFC 5545 Section 3.2 that explains when parameter values are surrounded with double-quotes, and tells us double-quotes are illegal in parameter values:
It's important to note that parameters can technically contain multiple values. A comma is used to separate these multiple values:
(from Section 3.2.11 of RFC 5545:)
Not all iCalendar engines will accept multiple values on all parameters, but the following parameters SHOULD allow multiple values (according to the RFC):
Regards,
-Doug