401
edits
Accessibility/Video a11y Study08: Difference between revisions
Jump to navigation
Jump to search
Accessibility/Video a11y Study08 (view source)
Revision as of 08:40, 5 February 2009
, 5 February 2009added link
(added links) |
(added link) |
||
| Line 124: | Line 124: | ||
Ogg currently supports CMML and Kate as text codecs. | Ogg currently supports CMML and Kate as text codecs. | ||
Just like out-of-band time-aligned text come in multiple formats, in-line text codecs do, too. The study undertaken by Mozilla motivated the Xiph community to define a framework for mapping any type of text codec into Ogg through the so-called OggText mapping. A first implementation of this format exists for encapsulating srt files into Ogg. | Just like out-of-band time-aligned text come in multiple formats, in-line text codecs do, too. The study undertaken by Mozilla motivated the Xiph community to define a framework for mapping any type of text codec into Ogg through the so-called [http://wiki.xiph.org/index.php/OggText OggText mapping]. A first implementation of this format exists for encapsulating srt files into Ogg. | ||
In a Web framework (such as Firefox) it may not make sense to support all possible in-line text codecs. Instead, it may be useful to only support one comprehensive format, or at most a simple format (like srt) and a comprehensive format (like TDHT or Kate). Then, an existing format can be transcoded to one of these two formats for in-line encoding and Web delivery. For example, DFXP could be mapped to TDHT before encapsulation into Ogg. | In a Web framework (such as Firefox) it may not make sense to support all possible in-line text codecs. Instead, it may be useful to only support one comprehensive format, or at most a simple format (like srt) and a comprehensive format (like TDHT or Kate). Then, an existing format can be transcoded to one of these two formats for in-line encoding and Web delivery. For example, DFXP could be mapped to TDHT before encapsulation into Ogg. | ||