<?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: Image Viewer Updates &#8211; Print Current View Now Available</title>
	<atom:link href="http://blogs.ancestry.com/ancestry/2011/12/22/image-viewer-updates-print-current-view-now-available/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ancestry.com/ancestry/2011/12/22/image-viewer-updates-print-current-view-now-available/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=image-viewer-updates-print-current-view-now-available</link>
	<description>The official blog of Ancestry.com</description>
	<lastBuildDate>Sun, 19 May 2013 09:17:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Monika</title>
		<link>http://blogs.ancestry.com/ancestry/2011/12/22/image-viewer-updates-print-current-view-now-available/#comment-54211</link>
		<dc:creator>Monika</dc:creator>
		<pubDate>Thu, 05 Jan 2012 06:49:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=6774#comment-54211</guid>
		<description>Happy New Year to you all!  Not quite, quite on the same subject (what else is new? :-)) I have, for weeks, had problems when printing a profile page.  The data to the right (which lists the parents, spouses and children) is all &quot;smooched&quot; together.  Called tech support.  The first time they told me that they were aware of the problem and were working on it!  The next time they asked me what browser I have (it was Internet Explorer 8).  So, they suggested I switch to Firefox, which I did!  The right side of my page still comes out all &quot;smooched&quot; together.  Any advice?</description>
		<content:encoded><![CDATA[<p>Happy New Year to you all!  Not quite, quite on the same subject (what else is new? <img src='http://blogs.ancestry.com/ancestry/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> ) I have, for weeks, had problems when printing a profile page.  The data to the right (which lists the parents, spouses and children) is all &#8220;smooched&#8221; together.  Called tech support.  The first time they told me that they were aware of the problem and were working on it!  The next time they asked me what browser I have (it was Internet Explorer 8).  So, they suggested I switch to Firefox, which I did!  The right side of my page still comes out all &#8220;smooched&#8221; together.  Any advice?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trevor Rix</title>
		<link>http://blogs.ancestry.com/ancestry/2011/12/22/image-viewer-updates-print-current-view-now-available/#comment-54206</link>
		<dc:creator>Trevor Rix</dc:creator>
		<pubDate>Wed, 04 Jan 2012 01:35:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=6774#comment-54206</guid>
		<description>I am still finding that the Beta Image Viewer is so slow that it is unusable. What is the minimum computer specification required to run the Beta Image Viewer as fast as the current Enhanced Viewer please?</description>
		<content:encoded><![CDATA[<p>I am still finding that the Beta Image Viewer is so slow that it is unusable. What is the minimum computer specification required to run the Beta Image Viewer as fast as the current Enhanced Viewer please?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: swayaminfotech</title>
		<link>http://blogs.ancestry.com/ancestry/2011/12/22/image-viewer-updates-print-current-view-now-available/#comment-54202</link>
		<dc:creator>swayaminfotech</dc:creator>
		<pubDate>Mon, 02 Jan 2012 10:01:31 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=6774#comment-54202</guid>
		<description>Thanks for sharing....</description>
		<content:encoded><![CDATA[<p>Thanks for sharing&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BEE</title>
		<link>http://blogs.ancestry.com/ancestry/2011/12/22/image-viewer-updates-print-current-view-now-available/#comment-54189</link>
		<dc:creator>BEE</dc:creator>
		<pubDate>Thu, 29 Dec 2011 16:47:42 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=6774#comment-54189</guid>
		<description>The Image Viewer is great, but what a pain having to use the computer back button instead of a &quot;return to&quot; button on ancestry!
My wish for all continues to be a Very Happy, Healthy, Peaceful and Prosperous New Year!</description>
		<content:encoded><![CDATA[<p>The Image Viewer is great, but what a pain having to use the computer back button instead of a &#8220;return to&#8221; button on ancestry!<br />
My wish for all continues to be a Very Happy, Healthy, Peaceful and Prosperous New Year!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BEE</title>
		<link>http://blogs.ancestry.com/ancestry/2011/12/22/image-viewer-updates-print-current-view-now-available/#comment-54170</link>
		<dc:creator>BEE</dc:creator>
		<pubDate>Sat, 24 Dec 2011 12:26:37 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=6774#comment-54170</guid>
		<description>Wishing everyone a Very Blessed Christmas, Happy Hanukkah, and a Very Happy, Healthy and Peaceful New Year!</description>
		<content:encoded><![CDATA[<p>Wishing everyone a Very Blessed Christmas, Happy Hanukkah, and a Very Happy, Healthy and Peaceful New Year!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Hatchett</title>
		<link>http://blogs.ancestry.com/ancestry/2011/12/22/image-viewer-updates-print-current-view-now-available/#comment-54168</link>
		<dc:creator>Andy Hatchett</dc:creator>
		<pubDate>Sat, 24 Dec 2011 03:53:17 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=6774#comment-54168</guid>
		<description>Kelly Re: #3

Ancestry is not and never has been the LDS. If that shows your level of research skills I&#039;d Really love to get a crack at your tree- I&#039;ll be I can find a minimum of 50 errors within an hour.

Now- I suggest you get back to your .. ahem... &#039;research&#039;</description>
		<content:encoded><![CDATA[<p>Kelly Re: #3</p>
<p>Ancestry is not and never has been the LDS. If that shows your level of research skills I&#8217;d Really love to get a crack at your tree- I&#8217;ll be I can find a minimum of 50 errors within an hour.</p>
<p>Now- I suggest you get back to your .. ahem&#8230; &#8216;research&#8217;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carol A. H.</title>
		<link>http://blogs.ancestry.com/ancestry/2011/12/22/image-viewer-updates-print-current-view-now-available/#comment-54167</link>
		<dc:creator>Carol A. H.</dc:creator>
		<pubDate>Sat, 24 Dec 2011 03:21:04 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=6774#comment-54167</guid>
		<description>#3 Kelly:

This blog is from Ancestry.com, not the LDS Familysearch.org site.  But Ancestry is guilty of bad family connecting in the old One World Trees.

Any other bad tree connections in Ancestry is the responsibility of the individual tree owners.  Ancestry does *NOT* check for accuracy of trees.  Neither does the LDS site.  ALL IS UP TO THE USER TO CHECK FOR ACCURACY.  DOCUMENT YOUR SOURCES YOURSELF.  That&#039;s what quality genealogy is all about.  You do the research.  Don&#039;t copy blindly.</description>
		<content:encoded><![CDATA[<p>#3 Kelly:</p>
<p>This blog is from Ancestry.com, not the LDS Familysearch.org site.  But Ancestry is guilty of bad family connecting in the old One World Trees.</p>
<p>Any other bad tree connections in Ancestry is the responsibility of the individual tree owners.  Ancestry does *NOT* check for accuracy of trees.  Neither does the LDS site.  ALL IS UP TO THE USER TO CHECK FOR ACCURACY.  DOCUMENT YOUR SOURCES YOURSELF.  That&#8217;s what quality genealogy is all about.  You do the research.  Don&#8217;t copy blindly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Long time member</title>
		<link>http://blogs.ancestry.com/ancestry/2011/12/22/image-viewer-updates-print-current-view-now-available/#comment-54166</link>
		<dc:creator>Long time member</dc:creator>
		<pubDate>Sat, 24 Dec 2011 03:07:28 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=6774#comment-54166</guid>
		<description>The plain Advanced Viewer works better than your beta version.  Much faster.  Much clearer images.  The scroll bars are there (but I don&#039;t use them) as well as the little hand cursor which is very smooth and fast.  

The little hand cursor in the beta version is jerky and slower.  I have Windows XP and IE8.</description>
		<content:encoded><![CDATA[<p>The plain Advanced Viewer works better than your beta version.  Much faster.  Much clearer images.  The scroll bars are there (but I don&#8217;t use them) as well as the little hand cursor which is very smooth and fast.  </p>
<p>The little hand cursor in the beta version is jerky and slower.  I have Windows XP and IE8.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laurel Presser</title>
		<link>http://blogs.ancestry.com/ancestry/2011/12/22/image-viewer-updates-print-current-view-now-available/#comment-54165</link>
		<dc:creator>Laurel Presser</dc:creator>
		<pubDate>Fri, 23 Dec 2011 16:37:03 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=6774#comment-54165</guid>
		<description>I would like it if you would still include verticle and horizontal scroll bars.  I understand that we can pan across and up and down by grabbing the image with the mouse, but there are times, especially when I&#039;m moving from one edge of the image to the other - for example, from the middle or bottom of a census page to the top to read the column headings - when it&#039;s much easier to use a scroll bar than by grabbing and pulling.

If the scroll bars are, in fact, still there, I cannot see them</description>
		<content:encoded><![CDATA[<p>I would like it if you would still include verticle and horizontal scroll bars.  I understand that we can pan across and up and down by grabbing the image with the mouse, but there are times, especially when I&#8217;m moving from one edge of the image to the other &#8211; for example, from the middle or bottom of a census page to the top to read the column headings &#8211; when it&#8217;s much easier to use a scroll bar than by grabbing and pulling.</p>
<p>If the scroll bars are, in fact, still there, I cannot see them</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelly Bauer</title>
		<link>http://blogs.ancestry.com/ancestry/2011/12/22/image-viewer-updates-print-current-view-now-available/#comment-54164</link>
		<dc:creator>Kelly Bauer</dc:creator>
		<pubDate>Fri, 23 Dec 2011 15:58:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=6774#comment-54164</guid>
		<description>Why do you the LDS make up connections in family trees and then illeagly publish the? How family family trees have you the LDS stole and illeagle published? Now you charge people to look up all your misinformation. I have been doing this research for over 30 years. I have been to Salt Lake and know for a fact you have made many invalid connections in my family. I refuse to correct all your wrong assumed and made up info.You LDS people shhould be assamed of how and what you represent in the world of genealogy!!!!!</description>
		<content:encoded><![CDATA[<p>Why do you the LDS make up connections in family trees and then illeagly publish the? How family family trees have you the LDS stole and illeagle published? Now you charge people to look up all your misinformation. I have been doing this research for over 30 years. I have been to Salt Lake and know for a fact you have made many invalid connections in my family. I refuse to correct all your wrong assumed and made up info.You LDS people shhould be assamed of how and what you represent in the world of genealogy!!!!!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
