I think it should be up to the developer to chose the default subtitles
they want. What if someone is trying to localize a page, and the default
subtitle is always English when they want Spanish? If not specified, the
default subtitle should be the language specified of the page or video.
But, if
Hi Jonathan,
All of what you're saying is indeed how it would work.
The existing mean of publishing subtitles and the developer choice to add a
@default attribute on a track that a developer wants activated by default
is not affected by a new @kind=forced. You can still do all the things that
In working with real-world content with in-band subtitle tracks, I have
realized that the spec doesn't accommodate forced subtitles. Forced subtitles
are used when a video has dialog or text in a language that is different from
the main language. For example in the Lord of the Rings, dialog
I think Eric is right - we need a new @kind=forced or
@kind=forcedSubtitles value on track elements, because they behave
differently from the subtitle kind:
* are not listed in a track menu
* are turned on by browser when no other subtitle or caption track is on
* multiple forced subtitles tracks
On Apr 11, 2013, at 3:54 PM, Silvia Pfeiffer silviapfeiff...@gmail.com wrote:
I think Eric is right - we need a new @kind=forced or
@kind=forcedSubtitles value on track elements, because they behave
differently from the subtitle kind:
* are not listed in a track menu
* are turned on by
