- From: <bugzilla@jessica.w3.org>
- Date: Thu, 11 Apr 2013 23:45:05 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21667 --- Comment #4 from Eric Carlson <eric.carlson@apple.com> --- (In reply to comment #3) > I wasn't aware there were so many different categories of subtitles: > http://en.wikipedia.org/wiki/Subtitle_%28captioning%29#Categories > > However, it seems that the general distinction is between "forced" and > "narrative" subtitles. I think it is appropriate to define a @kind="forced" > or @kind="forcedSubtitles". It seems to me that the other categories are > covered by these two. It also seems to me that it's possible to have several > forced subtitle tracks in the same language required to be on (see the > "forced" and the "titles only" examples in the above link). So this is > different from normal subtitle tracks. > > How is the browser expected to identify the language for which it has to > display forced subtitles? Would that be the language setting of the browser? > Would we continue to have @default on such tracks in case the browser > doesn't know which language track to choose? > I believe it should be the language of the video's primary audio track, because forced subtitles are enabled in a situation where the user can presumably understand the dialog being spoken in that language (they have not indicated a preference for captions or subtitles). > [Aside: I noticed there are 3D positioned subtitles - might this be > something that we need to consider introducing into WebVTT?] > Lets wait and see how popular that is. Forced subtitles are already widely used, so I think we need to deal with them now. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 11 April 2013 23:45:07 UTC