<?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: Captions vs subtitles</title>
	<atom:link href="http://alastairc.ac/2006/09/captions-vs-subtitles/feed/" rel="self" type="application/rss+xml" />
	<link>http://alastairc.ac/2006/09/captions-vs-subtitles/</link>
	<description>Kything web interactions</description>
	<lastBuildDate>Mon, 21 Jun 2010 21:13:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Joe Clark</title>
		<link>http://alastairc.ac/2006/09/captions-vs-subtitles/comment-page-1/#comment-89447</link>
		<dc:creator>Joe Clark</dc:creator>
		<pubDate>Fri, 12 Sep 2008 19:04:30 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2006/09/captions-vs-subtitles/#comment-89447</guid>
		<description>Sign languages cannot be captioned. Only spoken languages (and sound effects, etc.) can be captioned.

This means, of course, that incidental vocalizations uttered by sign-language users can be captioned. And, in theory, must.

It also means that if you’re running a sign-language video and have an interpreter audible (or have cleaned up an interpreter’s translation and have an actor reading a script), you have to caption that. (Even if the translation is incorrect, BTW.)</description>
		<content:encoded><![CDATA[<p>Sign languages cannot be captioned. Only spoken languages (and sound effects, etc.) can be captioned.</p>
<p>This means, of course, that incidental vocalizations uttered by sign-language users can be captioned. And, in theory, must.</p>
<p>It also means that if you’re running a sign-language video and have an interpreter audible (or have cleaned up an interpreter’s translation and have an actor reading a script), you have to caption that. (Even if the translation is incorrect, BTW.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James James</title>
		<link>http://alastairc.ac/2006/09/captions-vs-subtitles/comment-page-1/#comment-23069</link>
		<dc:creator>James James</dc:creator>
		<pubDate>Wed, 03 Oct 2007 10:16:36 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2006/09/captions-vs-subtitles/#comment-23069</guid>
		<description>Nicolas

Good luck with your ASL -- but if you can squeeze it -- try having a peek at:

http://signwriting.org/

This is proof positive that there IS a written form of sign languge, not just American Sign Language, but virtually ANY country&#039;s sign language.  I was totally fascinated by it and it&#039;s Well worth a visit.</description>
		<content:encoded><![CDATA[<p>Nicolas</p>
<p>Good luck with your ASL &#8212; but if you can squeeze it &#8212; try having a peek at:</p>
<p><a href="http://signwriting.org/" rel="nofollow">http://signwriting.org/</a></p>
<p>This is proof positive that there IS a written form of sign languge, not just American Sign Language, but virtually ANY country&#8217;s sign language.  I was totally fascinated by it and it&#8217;s Well worth a visit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicholas Scyoc</title>
		<link>http://alastairc.ac/2006/09/captions-vs-subtitles/comment-page-1/#comment-23054</link>
		<dc:creator>Nicholas Scyoc</dc:creator>
		<pubDate>Wed, 03 Oct 2007 07:59:55 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2006/09/captions-vs-subtitles/#comment-23054</guid>
		<description>I think this is interesting because subtitles can be interesting because the fact that a word might mean two different things and someone who can not hear might not be able to understand the context of what was said without captions. Well I am taking elementary (ASL) 1
and American Sign Language is put together doing that all the time. They use the same sign for two different words. The cool thing is that they are similar words most of the time.</description>
		<content:encoded><![CDATA[<p>I think this is interesting because subtitles can be interesting because the fact that a word might mean two different things and someone who can not hear might not be able to understand the context of what was said without captions. Well I am taking elementary (ASL) 1<br />
and American Sign Language is put together doing that all the time. They use the same sign for two different words. The cool thing is that they are similar words most of the time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James James</title>
		<link>http://alastairc.ac/2006/09/captions-vs-subtitles/comment-page-1/#comment-22102</link>
		<dc:creator>James James</dc:creator>
		<pubDate>Mon, 17 Sep 2007 15:21:56 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2006/09/captions-vs-subtitles/#comment-22102</guid>
		<description>and as if purely by coincidence...

http://news.bbc.co.uk/1/hi/technology/6993326.stm

Tada</description>
		<content:encoded><![CDATA[<p>and as if purely by coincidence&#8230;</p>
<p><a href="http://news.bbc.co.uk/1/hi/technology/6993326.stm" rel="nofollow">http://news.bbc.co.uk/1/hi/technology/6993326.stm</a></p>
<p>Tada</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James James</title>
		<link>http://alastairc.ac/2006/09/captions-vs-subtitles/comment-page-1/#comment-22088</link>
		<dc:creator>James James</dc:creator>
		<pubDate>Mon, 17 Sep 2007 00:54:49 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2006/09/captions-vs-subtitles/#comment-22088</guid>
		<description>I have read Joe&#039;s stuff and I wonder why he doesn&#039;t follow through on his own logic as regards the difference between subtitles and captions.  

He asserts that BSL cannot be captioned:  http://joeclark.org/access/captioning/bpoc/SL.html

Well, in the proper order of things it [BSL]  first needs to be subtitled just as would be the case for French, for example because as Joe himself  says, foreign languages primarily need to be subtitled and thereafter they could be captioned.  

Okay I accept that some languages are harder to translate than others but that does not mean to say that BSL is _*Not*_ a &quot;language&quot;, per se simply because it is difficult to translate:  the fact is that it CAN be translated - and therefore subtitled (and as such, &quot;captioned&quot;).</description>
		<content:encoded><![CDATA[<p>I have read Joe&#8217;s stuff and I wonder why he doesn&#8217;t follow through on his own logic as regards the difference between subtitles and captions.  </p>
<p>He asserts that BSL cannot be captioned:  <a href="http://joeclark.org/access/captioning/bpoc/SL.html" rel="nofollow">http://joeclark.org/access/captioning/bpoc/SL.html</a></p>
<p>Well, in the proper order of things it [BSL]  first needs to be subtitled just as would be the case for French, for example because as Joe himself  says, foreign languages primarily need to be subtitled and thereafter they could be captioned.  </p>
<p>Okay I accept that some languages are harder to translate than others but that does not mean to say that BSL is _*Not*_ a &#8220;language&#8221;, per se simply because it is difficult to translate:  the fact is that it CAN be translated &#8211; and therefore subtitled (and as such, &#8220;captioned&#8221;).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart Johnston</title>
		<link>http://alastairc.ac/2006/09/captions-vs-subtitles/comment-page-1/#comment-1750</link>
		<dc:creator>Stuart Johnston</dc:creator>
		<pubDate>Fri, 20 Oct 2006 11:15:36 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2006/09/captions-vs-subtitles/#comment-1750</guid>
		<description>It is a point that has to be made because it isn&#039;t that obvious.  We went through a similar process at Graphico with accessible web alternatives for one of our customers.  We ended up applying Ofcom standards of audio description of XHTML.  It works.

http://www.crossedbrowser.co.uk/?p=13</description>
		<content:encoded><![CDATA[<p>It is a point that has to be made because it isn&#8217;t that obvious.  We went through a similar process at Graphico with accessible web alternatives for one of our customers.  We ended up applying Ofcom standards of audio description of XHTML.  It works.</p>
<p><a href="http://www.crossedbrowser.co.uk/?p=13" rel="nofollow">http://www.crossedbrowser.co.uk/?p=13</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
