Difference between revisions of "Cue Text, including replacements"

From CDOT Wiki
Jump to: navigation, search
(→‎Cue Text with Cue Components)
(→‎Cue Text is Incorrectly Formatted)
Line 202: Line 202:
 
We <i are</i> in New York City
 
We <i are</i> in New York City
 
</pre>
 
</pre>
 +
 +
<pre>
 +
WEBVTT
 +
00:11.000 --> 00:13.000
 +
We <iare</i> in New York City
 +
</pre>
 +
  
 
<pre>
 
<pre>
Line 216: Line 223:
  
 
<pre>
 
<pre>
−
WEBVTT  00:11.000 --> 00:13.000
+
WEBVTT   
 +
 
 +
00:11.000 --> 00:13.000
 +
We <i>are i> in New York City
 +
</pre>
 +
 
 +
 
 +
 
 +
 
 +
<pre>
 +
WEBVTT 
 +
 
 +
00:11.000 --> 00:13.000
 
We <i>are<i in New York City
 
We <i>are<i in New York City
 
</pre>
 
</pre>

Revision as of 13:00, 24 September 2012

Group 5 Members

Name IRC Nick Blog Github Account Wiki Page Twitter
Rick Eyre reyre http://epsilon812.wordpress.com RickEyre User:Errichard @epsilon812
Shayan Zafar Ahmad szahmad Shayan's Blog Shayan's GitHub User:Szahmad ShayanZafar
Michael Afidchao mdafidchao http://kypertrast.net/seneca mafidchao User:Mdafidchao None
Jordan Raffoul jbraffoul http://jbraffoul.wordpress.com jbraffoul User:Jbraffoul None

Cue Text Scope

WebVTT chapter title text is syntactically a subset of WebVTT cue text, and WebVTT cue text is syntactically a subset of WebVTT metadata text. Conformance checkers, when validating WebVTT files, may offer to restrict all cues to only having WebVTT chapter title text or WebVTT cue text as their cue payload; WebVTT metadata text cues are only useful for scripted applications (using the metadata text track kind).

A WebVTT file whose cues all have a cue payload that is WebVTT chapter title text is said to be a WebVTT file using chapter title text.

A WebVTT file whose cues all have a cue payload that is WebVTT cue text is said to be a WebVTT file using cue text. By definition, any file that is a WebVTT file using chapter title text is also a WebVTT file using cue text.

Specifications: http://dev.w3.org/html5/webvtt/#webvtt-metadata-text

Notes/Issues/Updates

Rick

Sept 24

  • Changed title headers
  • Began adding concrete tests

Shayan

Jordan

Micheal

Test Scenarios Identified

Base/Metadata tests

  • No cue text Jordan, Rick
  • No cue text with line feed character(s) Jordan, Rick
  • No cue text with carriage return character(s) Jordan, Rick
  • No cue text with a combination of line feed and carriage return character(s) Jordan, Rick
  • Simple one-line of cue text - no other components Rick
  • multiple-line text
    • line terminator in between

Chapter Title Text

  • Cue text consisting of only an ampersand escape character Rick Eyre
  • Cue text consisting of only a less than escape character Rick Eyre
  • Cue text consisting of only a greater than escape character Rick Eyre
  • Cue text consisting of only a left-to-right escape character Rick Eyre
  • Cue text consisting of only a right-to-left escape character Rick Eyre
  • Cue text consisting of only an nbsp escape character Rick Eyre
  • Cue text different combinations (vary tests for different components: multiple ampersands, all types of components, etc.)
    • 2+ components that are separated from each other with line terminators
  • Cue text including escape character(s)
    • Line terminators

Cue Text

Note that these may overlap with group 6 - text tags, we'll probably only need to cover the first 2.

We'll cover these for sure:

  • Cue text that uses a span tag
  • Cue text that uses 2+ span tags
    • Separated with line terminator

These should automatically be covered by the text tags testing as they create tests for each tag:

  • Cue text that uses a class span tag
  • Cue text that uses an italics span tag Rick Eyre
  • Cue text that uses a bold span tag Rick Eyre
  • Cue text that uses an underline span tag Rick Eyre
  • Cue text that uses a ruby span tag - Jordan Raffoul
  • Cue text that uses a voice span tag - Jordan Raffoul
  • Cue text that uses a timestamp tag

Concrete Tests

Good

No Cue Text

  • There will be multiple test files with combinations of carriage return characters and or line feed characters in combination.
WEBVTT 
00:11.000 --> 00:13.000

Basic Cue Text Span

  • Basic cue text with no modifiers
WEBVTT 
00:11.000 --> 00:13.000
We are in New York City

Basic Cue Text with Ampersand Escape Characters

WEBVTT 
00:11.000 --> 00:13.000
&lt;

WEBVTT 
00:11.000 --> 00:13.000
&gt;

WEBVTT 
00:11.000 --> 00:13.000
&amp;

WEBVTT 
00:11.000 --> 00:13.000
&nbsp;

WEBVTT 
00:11.000 --> 00:13.000
&lrm;

WEBVTT 
00:11.000 --> 00:13.000
&rlm;

Cue Text with Cue Components

Italic Cue Text

WEBVTT 
00:11.000 --> 00:13.000
We <i>are</i> in New York City

Bold Cue Text

WEBVTT 
00:11.000 --> 00:13.000
We <b>are</b> in New York City

Underline Cue Text

WEBVTT
00:11.000 --> 00:13.000
We <u>are</u> in New York City

Bad

Cue Text is Incorrectly Formatted

  • Using the <[valid cue text component]>[Text Payload]<[valid cue text component]/> notation
  • Italic Tag used in example
WEBVTT 
00:11.000 --> 00:13.000
We <i are</i> in New York City

WEBVTT 
00:11.000 --> 00:13.000
We <iare</i> in New York City



WEBVTT 
00:11.000 --> 00:13.000
We <i>are</i in New York City

WEBVTT 
00:11.000 --> 00:13.000
We <i>are<i> in New York City

WEBVTT  

00:11.000 --> 00:13.000
We <i>are i> in New York City




WEBVTT  

00:11.000 --> 00:13.000
We <i>are<i in New York City
Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=Cue_Text,_including_replacements&oldid=88389"