<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: What is &#8220;interoperable TTML&#8221;?</title>
	<atom:link href="http://blog.gingertech.net/2012/09/18/what-is-interoperable-ttml/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.gingertech.net/2012/09/18/what-is-interoperable-ttml/</link>
	<description>Silvia&#039;s blog</description>
	<lastBuildDate>Mon, 20 May 2013 17:30:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: John Birch</title>
		<link>http://blog.gingertech.net/2012/09/18/what-is-interoperable-ttml/comment-page-1/#comment-42214</link>
		<dc:creator>John Birch</dc:creator>
		<pubDate>Tue, 08 Jan 2013 11:40:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gingertech.net/?p=1733#comment-42214</guid>
		<description>EBU-TT is not intended (or promoted) as a format for players to decode (although technically it can be used this way). The primary targeted use of EBU-TT files is for document exchange between broadcasters, distributors etc. and captioneers / subtitlers. It is an authoring / exchange format for subtitles and captions, rather than a presentation format. This is why &#039;features&#039; like images and scrolling are not present in EBU-TT - scrolling and DVB bitmaps are aspects of the presentation. not the content. 

EBU-TT is expected to be converted (by a broadcaster or distributor) into SMPTE-TT, SRT, WEB-VTT, line 21 closed captions etc. It is a precursor to the &#039;distribution&#039; format, but deliberately based on DFXP to take advantage of the framework already established, and to make it easier to perform these anticipated &#039;publishing&#039; conversions.</description>
		<content:encoded><![CDATA[<p>EBU-TT is not intended (or promoted) as a format for players to decode (although technically it can be used this way). The primary targeted use of EBU-TT files is for document exchange between broadcasters, distributors etc. and captioneers / subtitlers. It is an authoring / exchange format for subtitles and captions, rather than a presentation format. This is why &#8216;features&#8217; like images and scrolling are not present in EBU-TT &#8211; scrolling and DVB bitmaps are aspects of the presentation. not the content. </p>
<p>EBU-TT is expected to be converted (by a broadcaster or distributor) into SMPTE-TT, SRT, WEB-VTT, line 21 closed captions etc. It is a precursor to the &#8216;distribution&#8217; format, but deliberately based on DFXP to take advantage of the framework already established, and to make it easier to perform these anticipated &#8216;publishing&#8217; conversions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Kemp</title>
		<link>http://blog.gingertech.net/2012/09/18/what-is-interoperable-ttml/comment-page-1/#comment-37509</link>
		<dc:creator>John Kemp</dc:creator>
		<pubDate>Fri, 21 Sep 2012 13:42:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gingertech.net/?p=1733#comment-37509</guid>
		<description>I have just implemented SMPTE TT support for a project I&#039;ve been working on. In our case, we produce video for online delivery with captions already embedded in the video. Some vendors we work with claim that they cannot themselves extract the captions  from the video, or display them as-is from the video, and require us to provide SMPTE TT as well as the actual video. Since this is required for compliance with regulations, I make the simplest possible SMPTE TT file. It contains only timecode and captions, with no layout information. I&#039;d expect that will be one approach,and the other will be to use the SMPTE extension to store the caption blobs from the video without reformatting to produce the XML-formatted data.</description>
		<content:encoded><![CDATA[<p>I have just implemented SMPTE TT support for a project I&#8217;ve been working on. In our case, we produce video for online delivery with captions already embedded in the video. Some vendors we work with claim that they cannot themselves extract the captions  from the video, or display them as-is from the video, and require us to provide SMPTE TT as well as the actual video. Since this is required for compliance with regulations, I make the simplest possible SMPTE TT file. It contains only timecode and captions, with no layout information. I&#8217;d expect that will be one approach,and the other will be to use the SMPTE extension to store the caption blobs from the video without reformatting to produce the XML-formatted data.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
