<?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: OpenSolaris Governing Board, Acrobatics</title>
	<atom:link href="http://blogs.gnome.org/calum/2009/03/24/opensolaris-governing-board-acrobatics/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/calum/2009/03/24/opensolaris-governing-board-acrobatics/</link>
	<description>Usability an' that</description>
	<lastBuildDate>Thu, 22 Oct 2009 17:46:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Matěj Cepl</title>
		<link>http://blogs.gnome.org/calum/2009/03/24/opensolaris-governing-board-acrobatics/comment-page-1/#comment-593</link>
		<dc:creator>Matěj Cepl</dc:creator>
		<pubDate>Wed, 25 Mar 2009 16:10:52 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/calum/?p=406#comment-593</guid>
		<description>... respecitvely, my point was that Adobe Acrobat Reader should be used only sparringly and when necessary (yes, comments are problem).

Otherwise, in situations when evince is sufficient (which is 100% cases for me, and apparently a little less for you), evince tends to work much better (simple menu, fitting into Gnome better, uncluttered interface, etc.)</description>
		<content:encoded><![CDATA[<p>&#8230; respecitvely, my point was that Adobe Acrobat Reader should be used only sparringly and when necessary (yes, comments are problem).</p>
<p>Otherwise, in situations when evince is sufficient (which is 100% cases for me, and apparently a little less for you), evince tends to work much better (simple menu, fitting into Gnome better, uncluttered interface, etc.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matěj Cepl</title>
		<link>http://blogs.gnome.org/calum/2009/03/24/opensolaris-governing-board-acrobatics/comment-page-1/#comment-592</link>
		<dc:creator>Matěj Cepl</dc:creator>
		<pubDate>Wed, 25 Mar 2009 16:08:49 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/calum/?p=406#comment-592</guid>
		<description>Sure, I am not arguing against that (we have it in RHEL as well), just wanted to make sure we are on the same page, which apparently we are.</description>
		<content:encoded><![CDATA[<p>Sure, I am not arguing against that (we have it in RHEL as well), just wanted to make sure we are on the same page, which apparently we are.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: calum</title>
		<link>http://blogs.gnome.org/calum/2009/03/24/opensolaris-governing-board-acrobatics/comment-page-1/#comment-591</link>
		<dc:creator>calum</dc:creator>
		<pubDate>Wed, 25 Mar 2009 11:52:02 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/calum/?p=406#comment-591</guid>
		<description>@Matěj:  I&#039;m not really talking about rendering bugs, just missing features.  

E.g. right now I&#039;m collaborating on a PDF document where we&#039;re making heavy use of comments and annotations, but Evince doesn&#039;t let me read existing comments, or add new comments or annotations.  So I can&#039;t use Evince for this, I have to use Adobe Reader, or something like Preview on OS X.  (Bug numbers: 515243, 568052.)

Last I heard, Reader still had better accessibility support than Evince too, although I haven&#039;t looked into that for a while.

I know there are people working hard on all these things for Evince, but in the meantime, from a business perspective, Adobe Reader is still a necessary evil, IMHO&#8212;bottom line is, Sun will sell support for more Solaris desktops because Adobe Reader is available natively.  (And you might be surprised how many support contracts Red Hat would lose if there was no Linux version!)</description>
		<content:encoded><![CDATA[<p>@Matěj:  I&#8217;m not really talking about rendering bugs, just missing features.  </p>
<p>E.g. right now I&#8217;m collaborating on a PDF document where we&#8217;re making heavy use of comments and annotations, but Evince doesn&#8217;t let me read existing comments, or add new comments or annotations.  So I can&#8217;t use Evince for this, I have to use Adobe Reader, or something like Preview on OS X.  (Bug numbers: 515243, 568052.)</p>
<p>Last I heard, Reader still had better accessibility support than Evince too, although I haven&#8217;t looked into that for a while.</p>
<p>I know there are people working hard on all these things for Evince, but in the meantime, from a business perspective, Adobe Reader is still a necessary evil, IMHO&mdash;bottom line is, Sun will sell support for more Solaris desktops because Adobe Reader is available natively.  (And you might be surprised how many support contracts Red Hat would lose if there was no Linux version!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matěj Cepl</title>
		<link>http://blogs.gnome.org/calum/2009/03/24/opensolaris-governing-board-acrobatics/comment-page-1/#comment-590</link>
		<dc:creator>Matěj Cepl</dc:creator>
		<pubDate>Wed, 25 Mar 2009 08:17:35 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/calum/?p=406#comment-590</guid>
		<description>&gt; Very fine though Evince is at handling the majority of PDF-reading
&gt; tasks, some jobs still just require the proprietary Real Thing…

and bug numbers at b.g.o are? I am a big fan of elimination of Adobe goo from Linux distros, and I haven&#039;t met for a long time PDF which wouldn&#039;t be processed with Evince correctly (sans Javascript in Reader, which I am really happy that Evince cannot do; apparently Adobe themselves are not eager to fix exploited bug in it).</description>
		<content:encoded><![CDATA[<p>&gt; Very fine though Evince is at handling the majority of PDF-reading<br />
&gt; tasks, some jobs still just require the proprietary Real Thing…</p>
<p>and bug numbers at b.g.o are? I am a big fan of elimination of Adobe goo from Linux distros, and I haven&#8217;t met for a long time PDF which wouldn&#8217;t be processed with Evince correctly (sans Javascript in Reader, which I am really happy that Evince cannot do; apparently Adobe themselves are not eager to fix exploited bug in it).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
