<?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: Why Shared Reviews?</title>
	<atom:link href="http://blogs.adobe.com/thesamepage/2008/03/why_shared_reviews.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blogs.adobe.com/thesamepage/2008/03/why_shared_reviews.html</link>
	<description>Tips, updates and best practices from Acrobat Product Evangelist Ali Hanyaloglu for using Adobe Acrobat for document-based collaboration, and to ensure everyone is on the same page.</description>
	<lastBuildDate>Tue, 20 Mar 2012 18:37:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Ali Hanyaloglu</title>
		<link>http://blogs.adobe.com/thesamepage/2008/03/why_shared_reviews.html#comment-635</link>
		<dc:creator>Ali Hanyaloglu</dc:creator>
		<pubDate>Mon, 06 Jun 2011 15:33:14 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/thesamepagedev/2008/03/28/why_shared_reviews/#comment-635</guid>
		<description><![CDATA[[Lenny and I had been communicating off-blog on this topic. I meant to share the suggestions with everyone else sooner, so forgive me for the delay here]


I received a couple of options from engineering. They are based on the fact that PDF files under shared review have the original server location URL stored inside them in JavaScript.

1)	Ask IT if they can create a redirect on the DOT’s internal DNS servers to reroute requests for the old server name and IP address over to the new one. This should work best, as the only thing that has changed is the server name – the path to the folder and file for the shared review is the same across the servers. That way, when the PDF file requests access to the old server, it should be redirected to the new one.
2)	Modify the JavaScript in the PDF file under shared review. I suggest trying this with a test file first, should you make a mistake.
a.	Open the file under shared review that is pointing to the older server.
b.	Choose File &gt; Save a copy…  and give the file a new name. What this does is remove the Reader enablement so that you can make changes to the file.
c.	Open the copy. Choose Advanced &gt; Document Processing &gt; Document JavaScripts…
d.	There should be a couple of functions there. One will end in .register. Edit this function.
e.	Look for all occurrences of the old server name and replace with the new one.
f.	Save the PDF file. Close it. Reopen the file. See if it now syncs correctly with the new server.]]></description>
		<content:encoded><![CDATA[<p>[Lenny and I had been communicating off-blog on this topic. I meant to share the suggestions with everyone else sooner, so forgive me for the delay here]</p>
<p>I received a couple of options from engineering. They are based on the fact that PDF files under shared review have the original server location URL stored inside them in JavaScript.</p>
<p>1)	Ask IT if they can create a redirect on the DOT’s internal DNS servers to reroute requests for the old server name and IP address over to the new one. This should work best, as the only thing that has changed is the server name – the path to the folder and file for the shared review is the same across the servers. That way, when the PDF file requests access to the old server, it should be redirected to the new one.<br />
2)	Modify the JavaScript in the PDF file under shared review. I suggest trying this with a test file first, should you make a mistake.<br />
a.	Open the file under shared review that is pointing to the older server.<br />
b.	Choose File &gt; Save a copy…  and give the file a new name. What this does is remove the Reader enablement so that you can make changes to the file.<br />
c.	Open the copy. Choose Advanced &gt; Document Processing &gt; Document JavaScripts…<br />
d.	There should be a couple of functions there. One will end in .register. Edit this function.<br />
e.	Look for all occurrences of the old server name and replace with the new one.<br />
f.	Save the PDF file. Close it. Reopen the file. See if it now syncs correctly with the new server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lenny massotti</title>
		<link>http://blogs.adobe.com/thesamepage/2008/03/why_shared_reviews.html#comment-614</link>
		<dc:creator>lenny massotti</dc:creator>
		<pubDate>Tue, 29 Mar 2011 15:48:08 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/thesamepagedev/2008/03/28/why_shared_reviews/#comment-614</guid>
		<description><![CDATA[Hello,

Have been happily using a shared review approach for PDF comments for about 2 years now, but have run into a server migration glitch this week.  The local &quot;shared&quot; server where all of the archived comment server links were pointed toward was replaced with a new server . . . all the root folders and files were migrated and the XML files look okay to me? (sample included below)

The issue mainfests as a call to work offline since the orginal server named in the Welcome Back screen under &quot;Comment Server: xyz&quot; cannot be located.

Can we apply a system wide fix of some kind to re-direct the comment server associations? I am concerned that we have lost the archive of previous comments and may be unable to complete document reviews that were begun in advance of the Server Migtration, but were not yet consolidated for action.

Thanks in advance for any insight you can share.]]></description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>Have been happily using a shared review approach for PDF comments for about 2 years now, but have run into a server migration glitch this week.  The local &#8220;shared&#8221; server where all of the archived comment server links were pointed toward was replaced with a new server . . . all the root folders and files were migrated and the XML files look okay to me? (sample included below)</p>
<p>The issue mainfests as a call to work offline since the orginal server named in the Welcome Back screen under &#8220;Comment Server: xyz&#8221; cannot be located.</p>
<p>Can we apply a system wide fix of some kind to re-direct the comment server associations? I am concerned that we have lost the archive of previous comments and may be unable to complete document reviews that were begun in advance of the Server Migtration, but were not yet consolidated for action.</p>
<p>Thanks in advance for any insight you can share.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ali Hanyaloglu</title>
		<link>http://blogs.adobe.com/thesamepage/2008/03/why_shared_reviews.html#comment-609</link>
		<dc:creator>Ali Hanyaloglu</dc:creator>
		<pubDate>Mon, 28 Mar 2011 22:05:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/thesamepagedev/2008/03/28/why_shared_reviews/#comment-609</guid>
		<description><![CDATA[Hi Anita, thanks for the comment. I wonder if it&#039;s because users are trying to open the original PDF file from the SharePoint library directly? Also, make sure they have the ability to read and write files to the SharePoint library.]]></description>
		<content:encoded><![CDATA[<p>Hi Anita, thanks for the comment. I wonder if it&#8217;s because users are trying to open the original PDF file from the SharePoint library directly? Also, make sure they have the ability to read and write files to the SharePoint library.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anita Stegeman</title>
		<link>http://blogs.adobe.com/thesamepage/2008/03/why_shared_reviews.html#comment-604</link>
		<dc:creator>Anita Stegeman</dc:creator>
		<pubDate>Fri, 18 Feb 2011 01:14:14 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/thesamepagedev/2008/03/28/why_shared_reviews/#comment-604</guid>
		<description><![CDATA[I keep running into problems using shared reviews.  The latest, like Bill above, is the shared file is opening as a regular pdf for some, but other participate successfully.  I am using Acrobat Professional 9 and Sharepoint to create the shared review.  Users have Adobe Reader 8.0 or 9.0 or Acrobat.  The ones having the problem have Internet Explorer 8.0.  Others successfully using the shared review have Internet Explorer 6.0.  I&#039;m guessing the problem has to do with the version of Internet Explorer.  I think shared review is really nice to use and those who can use it love it, but I need to be able to rely on it consistently across the company.  Any suggestions?  Is there a setting I should have them change in IE 8?]]></description>
		<content:encoded><![CDATA[<p>I keep running into problems using shared reviews.  The latest, like Bill above, is the shared file is opening as a regular pdf for some, but other participate successfully.  I am using Acrobat Professional 9 and Sharepoint to create the shared review.  Users have Adobe Reader 8.0 or 9.0 or Acrobat.  The ones having the problem have Internet Explorer 8.0.  Others successfully using the shared review have Internet Explorer 6.0.  I&#8217;m guessing the problem has to do with the version of Internet Explorer.  I think shared review is really nice to use and those who can use it love it, but I need to be able to rely on it consistently across the company.  Any suggestions?  Is there a setting I should have them change in IE 8?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Farr</title>
		<link>http://blogs.adobe.com/thesamepage/2008/03/why_shared_reviews.html#comment-596</link>
		<dc:creator>David Farr</dc:creator>
		<pubDate>Thu, 13 Jan 2011 00:58:20 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/thesamepagedev/2008/03/28/why_shared_reviews/#comment-596</guid>
		<description><![CDATA[I&#039;ve been sending email and shared reviews the last few years using Pro 8 on a shared Novell server. We can make it work but it&#039;s completey non-intuitive to the poor reviewers themselves. When they publish comments it will tell them the comments couldn&#039;t be published and for the reviewer to close the PDF they need to click NO I don&#039;t want to publish, however the comments DO get published. Is this a Novell server mess-up?]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve been sending email and shared reviews the last few years using Pro 8 on a shared Novell server. We can make it work but it&#8217;s completey non-intuitive to the poor reviewers themselves. When they publish comments it will tell them the comments couldn&#8217;t be published and for the reviewer to close the PDF they need to click NO I don&#8217;t want to publish, however the comments DO get published. Is this a Novell server mess-up?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ali Hanyaloglu</title>
		<link>http://blogs.adobe.com/thesamepage/2008/03/why_shared_reviews.html#comment-9</link>
		<dc:creator>Ali Hanyaloglu</dc:creator>
		<pubDate>Mon, 21 Dec 2009 11:14:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/thesamepagedev/2008/03/28/why_shared_reviews/#comment-9</guid>
		<description><![CDATA[Is it possible that a deadline may have been applied on the PDF file sent for Shared Review? Also, check where the comments are being stored online, and whether the relevant Shared Review folder and comments are still there (if a web server, network share or SharePoint workspace).
]]></description>
		<content:encoded><![CDATA[<p>Is it possible that a deadline may have been applied on the PDF file sent for Shared Review? Also, check where the comments are being stored online, and whether the relevant Shared Review folder and comments are still there (if a web server, network share or SharePoint workspace).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Greeve</title>
		<link>http://blogs.adobe.com/thesamepage/2008/03/why_shared_reviews.html#comment-8</link>
		<dc:creator>Bill Greeve</dc:creator>
		<pubDate>Wed, 28 Oct 2009 13:33:12 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/thesamepagedev/2008/03/28/why_shared_reviews/#comment-8</guid>
		<description><![CDATA[We&#039;ve had excellent results using shared review, but now there&#039;s a problem we can&#039;t solve.

Some users who could open a shared review pdf no longer can. They can open the pdf, but as a normal pdf, not shared. I can&#039;t find any reason why this has stopped working for some users.

thanks.
]]></description>
		<content:encoded><![CDATA[<p>We&#8217;ve had excellent results using shared review, but now there&#8217;s a problem we can&#8217;t solve.</p>
<p>Some users who could open a shared review pdf no longer can. They can open the pdf, but as a normal pdf, not shared. I can&#8217;t find any reason why this has stopped working for some users.</p>
<p>thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Pehrson</title>
		<link>http://blogs.adobe.com/thesamepage/2008/03/why_shared_reviews.html#comment-7</link>
		<dc:creator>Tim Pehrson</dc:creator>
		<pubDate>Tue, 12 May 2009 10:28:30 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/thesamepagedev/2008/03/28/why_shared_reviews/#comment-7</guid>
		<description><![CDATA[How to automatically enable Shared Review?

We are starting to use Adobe Shared Reviews for our workflow.  We write our own in-house tools to do much of our workflow and document management.  We want to start a shared review without going through the normal GUI interface - I.E. we want to automate starting the review from within our own in-house developed tool.  Is there a way to do this?  Are there command line arguments that make it possible?  Are there scripts or other methods to automate starting a Shared Review that can be called from third-party tools (mainly our own)?

[ALI&#039;S REPLY: There is no way to automate the initiation of shared reviews. However, there is a collaboration API to create custom review repositories: check the online collaboration documentation on www.adobe.com/devnet/acrobat - it was created for Acrobat 8, but is still relevant for Acrobat 9]

]]></description>
		<content:encoded><![CDATA[<p>How to automatically enable Shared Review?</p>
<p>We are starting to use Adobe Shared Reviews for our workflow.  We write our own in-house tools to do much of our workflow and document management.  We want to start a shared review without going through the normal GUI interface &#8211; I.E. we want to automate starting the review from within our own in-house developed tool.  Is there a way to do this?  Are there command line arguments that make it possible?  Are there scripts or other methods to automate starting a Shared Review that can be called from third-party tools (mainly our own)?</p>
<p>[ALI'S REPLY: There is no way to automate the initiation of shared reviews. However, there is a collaboration API to create custom review repositories: check the online collaboration documentation on <a href="http://www.adobe.com/devnet/acrobat" rel="nofollow">http://www.adobe.com/devnet/acrobat</a> - it was created for Acrobat 8, but is still relevant for Acrobat 9]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicole</title>
		<link>http://blogs.adobe.com/thesamepage/2008/03/why_shared_reviews.html#comment-6</link>
		<dc:creator>Nicole</dc:creator>
		<pubDate>Fri, 08 May 2009 15:32:58 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/thesamepagedev/2008/03/28/why_shared_reviews/#comment-6</guid>
		<description><![CDATA[Sorry for the late post. I hope you can help me. I am trying to use Acrobat 8 to perform shared reviews using a network folder.

After I click Finish in the wizard, the process freezes. Nothing else happens. The review is not created.

I do have read/write permission on the network folder. I am using Acrobat 3D version 8.1.4.

Do you know how I can fix this?

Thank you,
Nicole

[ALI&#039;S REPLY: Sorry for the delay in posting these comments - Adobe recently updated our blogging system. Anyway, you need to be able to read, write and delete files to the folder. Ensure you have full access to the folder&#039;s contents. Also, try a different folder or new sub folder just as a trouble shooting step to see if that works.]
]]></description>
		<content:encoded><![CDATA[<p>Sorry for the late post. I hope you can help me. I am trying to use Acrobat 8 to perform shared reviews using a network folder.</p>
<p>After I click Finish in the wizard, the process freezes. Nothing else happens. The review is not created.</p>
<p>I do have read/write permission on the network folder. I am using Acrobat 3D version 8.1.4.</p>
<p>Do you know how I can fix this?</p>
<p>Thank you,<br />
Nicole</p>
<p>[ALI'S REPLY: Sorry for the delay in posting these comments - Adobe recently updated our blogging system. Anyway, you need to be able to read, write and delete files to the folder. Ensure you have full access to the folder's contents. Also, try a different folder or new sub folder just as a trouble shooting step to see if that works.]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Ramsay</title>
		<link>http://blogs.adobe.com/thesamepage/2008/03/why_shared_reviews.html#comment-5</link>
		<dc:creator>Jim Ramsay</dc:creator>
		<pubDate>Thu, 19 Mar 2009 18:08:05 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/thesamepagedev/2008/03/28/why_shared_reviews/#comment-5</guid>
		<description><![CDATA[I&#039;ve been using Acrobat for Shared Reviews for years, and I update review comments with the Set Status tool religiously, but I&#039;ve never understood the meaning or purpose of the Migration and Review menu items. I use Review&gt;Completed or Review&gt;Rejected to mark comments I&#039;ve acted on or rejected, and I use Review&gt;Accepted for comments I act on but in a different way from what may have been suggested. I never use Canceled (how is that different from Rejected?) or any of the three Migration options. Are these documented anywhere, or is this a mystery feature only for Adobe insiders?

[ALI&#039;S RESPONSE: Glad to hear you have been using Shared Reviews, Jim. I will be writing an article on these flags and how they are used with the &quot;migrate comments&quot; command soon. But for now, there&#039;s nothing secret about them. In fact, continue to use them as flags to help you track the status of reviewing comments from others. Stay tuned.]
]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve been using Acrobat for Shared Reviews for years, and I update review comments with the Set Status tool religiously, but I&#8217;ve never understood the meaning or purpose of the Migration and Review menu items. I use Review&gt;Completed or Review&gt;Rejected to mark comments I&#8217;ve acted on or rejected, and I use Review&gt;Accepted for comments I act on but in a different way from what may have been suggested. I never use Canceled (how is that different from Rejected?) or any of the three Migration options. Are these documented anywhere, or is this a mystery feature only for Adobe insiders?</p>
<p>[ALI'S RESPONSE: Glad to hear you have been using Shared Reviews, Jim. I will be writing an article on these flags and how they are used with the "migrate comments" command soon. But for now, there's nothing secret about them. In fact, continue to use them as flags to help you track the status of reviewing comments from others. Stay tuned.]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
