12564 2011-04-27 15:10:39 +0000 This, for me is definately the way to go with text tracks. Since the text is embedded in the media file "In-Band" it means the content never gets lost. This is how we treat audio with video and is how DVD treated text too. Some devices such as iOS may not 2011-08-04 05:14:08 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#sourcing-in-band-text-tracks P3 normal --- 1 contributor ian ayg mike philipj public-html-admin public-html-wg-issue-tracking silviapfeiffer1 public-html-bugzilla oldest_to_newest 47740 0 contributor 2011-04-27 15:10:39 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html Section: http://www.whatwg.org/specs/web-apps/current-work/#sourcing-in-band-text-tracks Comment: This, for me is definately the way to go with text tracks. Since the text is embedded in the media file "In-Band" it means the content never gets lost. This is how we treat audio with video and is how DVD treated text too. Some devices such as iOS may not support another layer of external text which is another reason why this is such a great method for covering all playback methods. At the end of the day if a user can view via browser, download, move to another device and the text track follows just as audio and video do, then why break them apart ? That's my penny's worth. Posted from: 189.97.124.33 User agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 47763 1 silviapfeiffer1 2011-04-28 07:37:11 +0000 Having text tracks separate is also useful, in particular: * if you are trying to index a lot of videos by their text tracks and just want to download the text, not the extensive video data, * if you are auto-translating a text track, * if you are keeping the text in a DB on the server and serving it with two or three different video formats, * if you have a large number of translations of the text track and don't want to always transfer all of the text tracks to the user, * if you want to provide text services on top of video that is being served by somebody else (though in this case you need some security mechanism.) I'm sure I have forgotten a few further user cases. The issue is: both external and in-band text tracks are useful and appear in the wild, so HTML supports both. There is no need to restrict users/authors/publishers to a single means of doing things. 50274 2 ayg 2011-06-24 19:13:18 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: As far as I understand the issue, there's significant demand and use-cases for out-of-band text tracks, and implementers are interested in supporting them. Thus a specification is needed to ensure that implementers all support the same format. If you don't think implementers should spend their time on out-of-band tracks, I suggest you take it up with them, so that no specification is needed; this kind of decision is not made by specification editors. Authors who prefer to use in-band tracks can do that instead -- nothing's stopping them. 53467 3 mike 2011-08-04 05:14:08 +0000 mass-move component to LC1