Re: ISSUE-223 (exclude comma from <string>): Should exclude COMMA from <string> in 8.3.12 [TTML 1.0]

I'm looking into this further as well, as I'm just now writing a validating
parser for this attribute. I agree that just COMMA isn't enough. We need to
handle the case where the unquoted family name consists of multiple
identifiers (not just one). Further we need to handle the CSS character
escaping rules, both in identifiers and in quoted strings.


On Thu, May 30, 2013 at 6:34 AM, Sean Hayes <Sean.Hayes@microsoft.com>wrote:

> I think it might be better to adopt the value syntax from CSS where
> family-name is a comma separated list of ID's or quoted strings, i.e. the
> comma is outside of the string and is thus allowed in the quoted string,
> identifiers however are much more restricted.
>
> <familyName>
>   : <identifier>
>   | <quotedString>
>
> <identifier> : [a-zA-Z0-9] ISO 10646 characters U+00A0 and higher, plus
> the hyphen (-) and the underscore (_); they cannot start with a digit, two
> hyphens, or a hyphen followed by a digit. Identifiers can also contain
> escaped characters and any ISO 10646 character as a numeric code.
>
> Sean.
>
> -----Original Message-----
> From: Timed Text Working Group Issue Tracker [mailto:sysbot+tracker@w3.org
> ]
> Sent: 30 May 2013 04:21
> To: public-tt@w3.org
> Subject: ISSUE-223 (exclude comma from <string>): Should exclude COMMA
> from <string> in 8.3.12 [TTML 1.0]
>
> ISSUE-223 (exclude comma from <string>): Should exclude COMMA from
> <string> in 8.3.12 [TTML 1.0]
>
> http://www.w3.org/AudioVideo/TT/tracker/issues/223
>
> Raised by: Glenn Adams
> On product: TTML 1.0
>
> The prose that defines <familyName> in 8.3.5 states that COMMA cannot
> appear in <string>, however 8.3.12, which defines <string>, does not
> exclude it in its syntax definition. Since <string> is only referenced by
> the definition of <familyName>, we should add this exclusion in the
> definition of <string>, so that it reads as:
>
> <string>
>   : ( char - { "\"" | "\'" | "," } )+
>
> And then add a note indicating that this syntax is only used by
> <familyName> which requires the exclusion of COMMA in order to parse
> <fontFamily> correctly.
>
>
>
>