<?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: Comparing office file formats</title>
	<atom:link href="http://heliologue.com/2008/02/12/comparing-office-file-formats/feed/" rel="self" type="application/rss+xml" />
	<link>http://heliologue.com/2008/02/12/comparing-office-file-formats/</link>
	<description></description>
	<lastBuildDate>Sat, 04 Feb 2012 03:16:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Ben</title>
		<link>http://heliologue.com/2008/02/12/comparing-office-file-formats/#comment-153450</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Tue, 19 Feb 2008 15:07:56 +0000</pubDate>
		<guid isPermaLink="false">http://heliologue.com/2008/02/12/comparing-office-file-formats/#comment-153450</guid>
		<description>Hunh.  I purposely didn&#039;t include it in the table itself, but I could&#039;ve sworn I mentioned it in the preceding text.  Well, I guess I&#039;ll make the change.

To address Andrew Z&#039;s question:  naturally, the idea of squabbling over kilobytes is silly.  But I&#039;m not marketing ODF as a way to squeeze a bit of extra space out of your documents&#8212;though for large corpuses, the difference will be substantial.

What I&#039;m really trying to highlight is two things:  one, the stronger or weaker overhead, but also the size (and complexity) of generated markup.  Clearly, OOXML has a lot of cruft.</description>
		<content:encoded><![CDATA[<p>Hunh.  I purposely didn&#8217;t include it in the table itself, but I could&#8217;ve sworn I mentioned it in the preceding text.  Well, I guess I&#8217;ll make the change.</p>
<p>To address Andrew Z&#8217;s question:  naturally, the idea of squabbling over kilobytes is silly.  But I&#8217;m not marketing ODF as a way to squeeze a bit of extra space out of your documents&mdash;though for large corpuses, the difference will be substantial.</p>
<p>What I&#8217;m really trying to highlight is two things:  one, the stronger or weaker overhead, but also the size (and complexity) of generated markup.  Clearly, OOXML has a lot of cruft.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Conor</title>
		<link>http://heliologue.com/2008/02/12/comparing-office-file-formats/#comment-153445</link>
		<dc:creator>Conor</dc:creator>
		<pubDate>Tue, 19 Feb 2008 13:08:11 +0000</pubDate>
		<guid isPermaLink="false">http://heliologue.com/2008/02/12/comparing-office-file-formats/#comment-153445</guid>
		<description>While I agree with Andrew that it&#039;s kind of silly to be fussing over kilobytes, I do think there&#039;s a lot of merit to the stance that one should always choose the best tool for the job. If one compression algorithm is better than the other, you should use it—after having also taken into account possible restrictions on its use, of course.

It&#039;s like saying you could bump the RAM in your system up by one percent. Would you? Why the hell not? And comparing OOXML (how I hate that sneaky name) and ODF, the change is more like 25%. Ultimately we&#039;re still talking kilobytes here, but it&#039;s the principle of the thing.

And Ben, shame on you for not including your units in that table!</description>
		<content:encoded><![CDATA[<p>While I agree with Andrew that it&#8217;s kind of silly to be fussing over kilobytes, I do think there&#8217;s a lot of merit to the stance that one should always choose the best tool for the job. If one compression algorithm is better than the other, you should use it—after having also taken into account possible restrictions on its use, of course.</p>
<p>It&#8217;s like saying you could bump the RAM in your system up by one percent. Would you? Why the hell not? And comparing OOXML (how I hate that sneaky name) and ODF, the change is more like 25%. Ultimately we&#8217;re still talking kilobytes here, but it&#8217;s the principle of the thing.</p>
<p>And Ben, shame on you for not including your units in that table!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Z</title>
		<link>http://heliologue.com/2008/02/12/comparing-office-file-formats/#comment-153150</link>
		<dc:creator>Andrew Z</dc:creator>
		<pubDate>Wed, 13 Feb 2008 02:06:37 +0000</pubDate>
		<guid isPermaLink="false">http://heliologue.com/2008/02/12/comparing-office-file-formats/#comment-153150</guid>
		<description>How to get data into Base:
http://searchenterpriselinux.techtarget.com/tip/0,289483,sid39_gci1222186,00.html

Just for discussion, what&#039;s the &quot;big deal&quot; (no pun intended) about large file sizes?  Bandwidth and storage capacity are increasing quickly.</description>
		<content:encoded><![CDATA[<p>How to get data into Base:<br />
<a href="http://searchenterpriselinux.techtarget.com/tip/0,289483,sid39_gci1222186,00.html" rel="nofollow">http://searchenterpriselinux.techtarget.com/tip/0,289483,sid39_gci1222186,00.html</a></p>
<p>Just for discussion, what&#8217;s the &quot;big deal&quot; (no pun intended) about large file sizes?  Bandwidth and storage capacity are increasing quickly.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

