[Ietf-calsify] Section 4.1.2 Multiple Values: LANGUAGE parameter
bernard.desruisseaux at oracle.com
Wed Nov 15 06:23:16 PST 2006
We've had this discussion at the last WG meeting in San Diego.
The conclusion was that iCalendar wasn't designed to allow one to
specify property values and property parameter values in multiple
languages, and that one should use other mechanisms to provide
iCalendar data in multiple languages (e.g., multipart/alternative
with iMIP, HTTP content negotiation (RFC2295) with CalDAV).
Mike Douglass wrote:
> Would it make sense if all properties that can take a language parameter
> be allowed to appear multiple times?
> Currently I can internally support multiple languages for a vevent
> description but there's no legal way to export the entire data as ics.
> There's also no way via caldav for example to update more than one
> language in a single request
> RFC 2445 has the following properties with a language param:
> ATTENDEE (cn param)
> ORGANIZER (cn param)
> Bernard Desruisseaux wrote:
>> RFC 2445 allows some properties of TEXT value type to be specified
>> multiple times. In some cases (e.g., "TZNAME") it is specified that
>> the property can be specified more than once for specifying multiple
>> language variants of the property value.
>> I think section 4.1.2 Multiple Values should clarify how the
>> "LANGUAGE" parameter should be handled with multi-valued TEXT
>> For instance, in a "VJOURNAL" calendar component, can I have two
>> "DESCRIPTION" with "LANGUAGE=en", but only one "DESCRIPTION" with
>> "LANGUAGE=fr"? If so, should my client only display the one in
>> French, or should it display all three values?
>> Currently, I think it should display all three values...
>> Ietf-calsify mailing list
>> Ietf-calsify at osafoundation.org
More information about the Ietf-calsify