- From: <bugzilla@jessica.w3.org>
- Date: Sun, 22 Mar 2015 00:07:33 +0000
- To: public-texttracks@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28259
Bug ID: 28259
Summary: [webvtt] Normalization and string identity issues
[I18N-ISSUE-425]
Product: TextTracks CG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: WebVTT
Assignee: dave.null@w3.org
Reporter: silviapfeiffer1@gmail.com
QA Contact: public-texttracks@w3.org
CC: philipj@opera.com, silviapfeiffer1@gmail.com
Feedback by Addison Phillips from W3C I18N group:
http://lists.w3.org/Archives/Public/public-tt/2015Mar/0058.html
I18N comment: https://www.w3.org/International/track/issues/425
http://www.w3.org/TR/webvtt1/#webvtt-file-structure
Various constructs such as 'cue identifier' are described as being:
--
...any sequence of one or more characters not containing the substring "-->"...
--
The document makes understood that this is a sequence of Unicode characters.
However, it leaves open the question of whether different Unicode character
sequences that represent the same semantic string identifier (see: Charmod [1]
and Charmod-Norm [2]) are considered "the same" or not. As currently written,
different UTF-8 byte sequences are considered distinct.
We would suggest that identifiers that use distinct code point sequences are
considered distinct (that is, that you are what we call a "non-normalizing
Specification"), which suggests that you include at least a health warning
about the dangers of using different character sequences.
[1] http://www.w3.org/TR/charmod/
[2] http://www.w3.org/TR/charmod-norm/
Particularly: http://www.w3.org/TR/charmod-norm/#formal-language and
http://www.w3.org/TR/charmod-norm/#non-normalizing
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 22 March 2015 00:07:35 UTC