<?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"
	>
<channel>
	<title>Comments for ScreenSteps Blog</title>
	<atom:link href="http://screensteps.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://screensteps.com/blog</link>
	<description>Information on ScreenSteps and ScreenSteps Live</description>
	<pubDate>Thu, 24 Jul 2008 00:16:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>Comment on ScreenSteps Live API Beta by gregdevore</title>
		<link>http://screensteps.com/blog/2008/07/screensteps-live-api-beta/#comment-135</link>
		<dc:creator>gregdevore</dc:creator>
		<pubDate>Mon, 14 Jul 2008 12:10:56 +0000</pubDate>
		<guid isPermaLink="false">http://screensteps.com/blog/?p=208#comment-135</guid>
		<description>&lt;p&gt;Your API key is what is used to authenticate you when accessing the API.    You do not use your username and password.  Only Administrators on your account have access to your API key and it should be kept secret since it is like your account password.  To see more information about how the API key is used to authenticate requests you can see the &lt;a href="http://screensteps.com/blog/2008/07/the-screensteps-live-api-developer-guide/" rel="nofollow"&gt;creenSteps Live Developer's Guide&lt;/a&gt;.  Does that answer your question?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Your API key is what is used to authenticate you when accessing the API.    You do not use your username and password.  Only Administrators on your account have access to your API key and it should be kept secret since it is like your account password.  To see more information about how the API key is used to authenticate requests you can see the <a href="http://screensteps.com/blog/2008/07/the-screensteps-live-api-developer-guide/" rel="nofollow">creenSteps Live Developer&#8217;s Guide</a>.  Does that answer your question?</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on ScreenSteps Live API Beta by Didier</title>
		<link>http://screensteps.com/blog/2008/07/screensteps-live-api-beta/#comment-130</link>
		<dc:creator>Didier</dc:creator>
		<pubDate>Sun, 13 Jul 2008 17:57:31 +0000</pubDate>
		<guid isPermaLink="false">http://screensteps.com/blog/?p=208#comment-130</guid>
		<description>&lt;p&gt;How do you give the login to your screenstepslive account if it requires one ?&lt;/p&gt;

&lt;p&gt;:-?&lt;/p&gt;

&lt;p&gt;Didier&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>How do you give the login to your screenstepslive account if it requires one ?</p>

<p> <img src='http://screensteps.com/blog/wp-includes/images/smilies/icon_confused.gif' alt=':-?' class='wp-smiley' /> </p>

<p>Didier</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on ScreenSteps 2.1 Public Beta: Post to Blog by ylmz</title>
		<link>http://screensteps.com/blog/2008/04/screensteps-21-public-beta-post-to-blog/#comment-124</link>
		<dc:creator>ylmz</dc:creator>
		<pubDate>Thu, 10 Jul 2008 17:36:31 +0000</pubDate>
		<guid isPermaLink="false">http://screensteps.com/blog/?p=117#comment-124</guid>
		<description>&lt;p&gt;I love it!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I love it!</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Posting to Drupal by Posting to Drupal</title>
		<link>http://screensteps.com/blog/2008/07/posting-to-drupal/#comment-123</link>
		<dc:creator>Posting to Drupal</dc:creator>
		<pubDate>Thu, 10 Jul 2008 16:53:00 +0000</pubDate>
		<guid isPermaLink="false">http://screensteps.com/blog/?p=207#comment-123</guid>
		<description>&lt;p&gt;[...] Go to the author&#8217;s original blog: Posting to Drupal [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Go to the author&#8217;s original blog: Posting to Drupal [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simplify Your Documentation by Richard McLaughlin</title>
		<link>http://screensteps.com/blog/2008/07/simplify-your-documentation/#comment-119</link>
		<dc:creator>Richard McLaughlin</dc:creator>
		<pubDate>Tue, 08 Jul 2008 08:07:25 +0000</pubDate>
		<guid isPermaLink="false">http://screensteps.com/blog/?p=168#comment-119</guid>
		<description>&lt;p&gt;I followed a link from Ed Rivis, the poster just before me, to your site. Great product, I am getting ready to start documenting something and will give your free download version a run.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I followed a link from Ed Rivis, the poster just before me, to your site. Great product, I am getting ready to start documenting something and will give your free download version a run.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simplify Your Documentation by Ed</title>
		<link>http://screensteps.com/blog/2008/07/simplify-your-documentation/#comment-118</link>
		<dc:creator>Ed</dc:creator>
		<pubDate>Tue, 08 Jul 2008 07:11:02 +0000</pubDate>
		<guid isPermaLink="false">http://screensteps.com/blog/?p=168#comment-118</guid>
		<description>&lt;p&gt;A great approach to creating manuals -- and also to creating standalone information products like ebooks as well! Thanks.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>A great approach to creating manuals &#8212; and also to creating standalone information products like ebooks as well! Thanks.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simplify Your Documentation by Glen Saville</title>
		<link>http://screensteps.com/blog/2008/07/simplify-your-documentation/#comment-117</link>
		<dc:creator>Glen Saville</dc:creator>
		<pubDate>Mon, 07 Jul 2008 19:57:42 +0000</pubDate>
		<guid isPermaLink="false">http://screensteps.com/blog/?p=168#comment-117</guid>
		<description>&lt;p&gt;Excellent tutorial, really useful!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Excellent tutorial, really useful!</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simplify Your Documentation by Bill Leddy</title>
		<link>http://screensteps.com/blog/2008/07/simplify-your-documentation/#comment-116</link>
		<dc:creator>Bill Leddy</dc:creator>
		<pubDate>Mon, 07 Jul 2008 19:04:48 +0000</pubDate>
		<guid isPermaLink="false">http://screensteps.com/blog/?p=168#comment-116</guid>
		<description>&lt;p&gt;Terrific!  Thanks for sharing this great approach.&lt;/p&gt;

&lt;p&gt;Bill&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Terrific!  Thanks for sharing this great approach.</p>

<p>Bill</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on New ScreenSteps 2.1 Public Beta by trevordevore</title>
		<link>http://screensteps.com/blog/2008/06/new-screensteps-21-public-beta/#comment-94</link>
		<dc:creator>trevordevore</dc:creator>
		<pubDate>Tue, 03 Jun 2008 14:06:12 +0000</pubDate>
		<guid isPermaLink="false">http://screensteps.com/blog/?p=122#comment-94</guid>
		<description>&lt;p&gt;When you open the PDF with the Google logo in Preview select "Actual Size" from the contextual menu that appears if you right-click within the viewing area. Your image should then display at the same size as it appears on the Google website. Oddly enough selecting "Actual Size" from the View menu does not give the same result.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>When you open the PDF with the Google logo in Preview select &#8220;Actual Size&#8221; from the contextual menu that appears if you right-click within the viewing area. Your image should then display at the same size as it appears on the Google website. Oddly enough selecting &#8220;Actual Size&#8221; from the View menu does not give the same result.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on New ScreenSteps 2.1 Public Beta by George Andrews</title>
		<link>http://screensteps.com/blog/2008/06/new-screensteps-21-public-beta/#comment-88</link>
		<dc:creator>George Andrews</dc:creator>
		<pubDate>Tue, 03 Jun 2008 04:41:53 +0000</pubDate>
		<guid isPermaLink="false">http://screensteps.com/blog/?p=122#comment-88</guid>
		<description>&lt;p&gt;Quote: "Images in PDF output are no longer fuzzy at actual size."&lt;/p&gt;

&lt;p&gt;Interestingly, I saw no improvement from the current release version to the beta. Here is my test: I opened Google in Safari (I'm on a Mac) and captured the logo and search box using your tool. I also made a copy using Grab and pasted it into Preview. I saved a PDF from ScreenSteps and saved a similar PDF from Preview.&lt;/p&gt;

&lt;p&gt;In both cases, the image displays larger than the original--even when actual size or 100% is specified. The images can be reduced to approximate the original size, but the degradation of the image, especially the smaller type, is still quite noticeable.&lt;/p&gt;

&lt;p&gt;I didn't try taking the screen capture through Adobe Acrobat to see what quality I could get there. I did try viewing both test files in both Preview and Adobe Reader. I could live with a bit of fuzziness if the size stayed correct. Google's usual logo is 276 X 110 pixels.  The PDF version seems to be about 30% to 40% larger.&lt;/p&gt;

&lt;p&gt;While the logo was on the clipboard, I pasted it into a new MS Word document and saw the same resizing issue when I saved it as a PDF. I'm guessing this is some common library call to generate PDF output that everyone uses that's wonky. Saving the document in native word format and re-opening it returns a perfect replica of the original screen grab.&lt;/p&gt;

&lt;p&gt;Bottom line: PDF as a format seems to have some unexpected (to me anyway) limitations.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Quote: &#8220;Images in PDF output are no longer fuzzy at actual size.&#8221;</p>

<p>Interestingly, I saw no improvement from the current release version to the beta. Here is my test: I opened Google in Safari (I&#8217;m on a Mac) and captured the logo and search box using your tool. I also made a copy using Grab and pasted it into Preview. I saved a PDF from ScreenSteps and saved a similar PDF from Preview.</p>

<p>In both cases, the image displays larger than the original&#8211;even when actual size or 100% is specified. The images can be reduced to approximate the original size, but the degradation of the image, especially the smaller type, is still quite noticeable.</p>

<p>I didn&#8217;t try taking the screen capture through Adobe Acrobat to see what quality I could get there. I did try viewing both test files in both Preview and Adobe Reader. I could live with a bit of fuzziness if the size stayed correct. Google&#8217;s usual logo is 276 X 110 pixels.  The PDF version seems to be about 30% to 40% larger.</p>

<p>While the logo was on the clipboard, I pasted it into a new MS Word document and saw the same resizing issue when I saved it as a PDF. I&#8217;m guessing this is some common library call to generate PDF output that everyone uses that&#8217;s wonky. Saving the document in native word format and re-opening it returns a perfect replica of the original screen grab.</p>

<p>Bottom line: PDF as a format seems to have some unexpected (to me anyway) limitations.</p>]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.306 seconds -->
