<?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: Getting Rid of that Awful “Content Preparation Progress” in Adobe Reader	</title>
	<atom:link href="https://blog.henrypoon.com/blog/2010/10/26/getting-rid-of-that-awful-content-preparation-progress-in-adobe-reader/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.henrypoon.com/blog/2010/10/26/getting-rid-of-that-awful-content-preparation-progress-in-adobe-reader/</link>
	<description></description>
	<lastBuildDate>Sun, 25 Aug 2019 23:37:46 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: hp		</title>
		<link>https://blog.henrypoon.com/blog/2010/10/26/getting-rid-of-that-awful-content-preparation-progress-in-adobe-reader/#comment-88</link>

		<dc:creator><![CDATA[hp]]></dc:creator>
		<pubDate>Wed, 08 Dec 2010 23:20:51 +0000</pubDate>
		<guid isPermaLink="false">http://henrypoon.mooo.com/blog/getting-rid-of-that-awful-%e2%80%9ccontent-preparation-progress%e2%80%9d-in-adobe-reader#comment-88</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://blog.henrypoon.com/blog/2010/10/26/getting-rid-of-that-awful-content-preparation-progress-in-adobe-reader/#comment-87&quot;&gt;Jørgen R. Næumann&lt;/a&gt;.

Ohh that definitely is better.  No more dealing with even the page by page loading.  Thanks for this!
Based on the solution, I&#039;m guessing there&#039;s no way to disable these plugins through the software.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://blog.henrypoon.com/blog/2010/10/26/getting-rid-of-that-awful-content-preparation-progress-in-adobe-reader/#comment-87">Jørgen R. Næumann</a>.</p>
<p>Ohh that definitely is better.  No more dealing with even the page by page loading.  Thanks for this!<br />
Based on the solution, I&#8217;m guessing there&#8217;s no way to disable these plugins through the software.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jørgen R. Næumann		</title>
		<link>https://blog.henrypoon.com/blog/2010/10/26/getting-rid-of-that-awful-content-preparation-progress-in-adobe-reader/#comment-87</link>

		<dc:creator><![CDATA[Jørgen R. Næumann]]></dc:creator>
		<pubDate>Wed, 08 Dec 2010 12:47:23 +0000</pubDate>
		<guid isPermaLink="false">http://henrypoon.mooo.com/blog/getting-rid-of-that-awful-%e2%80%9ccontent-preparation-progress%e2%80%9d-in-adobe-reader#comment-87</guid>

					<description><![CDATA[Even better solution:

...Program Files...AdobeReader 9.0Readerplug_ins
there are 3 files you should delete (or maybe just rar them so you still got them in case something goes wrong)
Accessibility.api, MakeAccessible.api, ReadOutLoud.api
(if that gives troubles, just delete the files with the same name and .xxx where xxx stands for a certain language too)

OR - if you&#039;re afraid Adobe wonøt work or you&#039;ll need the files later - rename the extension to .api_]]></description>
			<content:encoded><![CDATA[<p>Even better solution:</p>
<p>&#8230;Program Files&#8230;AdobeReader 9.0Readerplug_ins<br />
there are 3 files you should delete (or maybe just rar them so you still got them in case something goes wrong)<br />
Accessibility.api, MakeAccessible.api, ReadOutLoud.api<br />
(if that gives troubles, just delete the files with the same name and .xxx where xxx stands for a certain language too)</p>
<p>OR &#8211; if you&#8217;re afraid Adobe wonøt work or you&#8217;ll need the files later &#8211; rename the extension to .api_</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
