[uf-dev] problems with testcases

[☻Mike Samuel]

On 1/17/07, microformats-dev-request at microformats.org >
------------------------------
>
> Message: 6
> Date: Tue, 16 Jan 2007 15:15:04 -0800
> From: Ryan King <ryan at technorati.com>
> Subject: Re: [uf-dev] problems with testcases
> > 3) calendar-del.ics is missing the location specified in calendar-
> > del.html
>
> Feature, not a bug. This is a somewhat undocumented feature– that
> items inside <del> elements are ignored.

ah.  cool.

> > 4) calendar-fragment is missing a couple events.
>
> Yeah, I'm not sure what's going on there, hence the @TODO note in the
> files.
> > 7) missing categories in component-vevent-del
>
> See above, re: <del>

got it.  I'll put my understanding of the proper output in the patch,
and you can use or ignore it as you like.

> ------------------------------
>
> Message: 7
> Date: Wed, 17 Jan 2007 09:52:44 +0000
> From: brian suda <brian.suda at gmail.com>
> Subject: Re: [uf-dev] problems with testcases
> To: "A list for people developing tools with microformats."
>         <microformats-dev at microformats.org>
> Message-ID: <45ADF1EC.90001 at gmail.com>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> ☻Mike Samuel wrote:
> > 8) unnecessary escaping of ; in content line values.  e.g. description
> > in component-vevent-description-value-in-subelements-2.  RFC 2425
> > defines a value as ...
> I think i found the discrepancy on why description is escaped in the
> test suite. According to RFC 2445, which is what hCalendar is basied off
> of, Description is of type TEXT. Text is further defined as:
>
> 4.3.11 Text
>
>    Value Name: TEXT
>
> Purpose This value type is used to identify values that contain human
>    readable text.
>
>    Formal Definition: The character sets supported by this revision of
>    iCalendar are UTF-8 and US ASCII thereof. The applicability to other
>    character sets is for future work. The value type is defined by the
>    following notation.
>
>      text       = *(TSAFE-CHAR / ":" / DQUOTE / ESCAPED-CHAR)
>      ; Folded according to description above
>
>      ESCAPED-CHAR = "\\" / "\;" / "\," / "\N" / "\n")
>         ; \\ encodes \, \N or \n encodes newline
>         ; \; encodes ;, \, encodes ,
>
>
>    The "TEXT" property values may also contain special characters that
>    are used to signify delimiters, such as a COMMA character for lists
>    of values or a SEMICOLON character for structured values. In order to
>    support the inclusion of these special characters in "TEXT" property
>    values, they MUST be escaped with a BACKSLASH character.
>
> So it looks like the escaping of the ';' is the correct behavior when
> dealing with RFC 2445.

Ah, good point.

mike