<?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: Office suites and user interface</title>
	<atom:link href="http://www.arpia.be/2008/12/office-and-interface/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.arpia.be/2008/12/office-and-interface/</link>
	<description>Website of Peter Craddock, novel writer and composer</description>
	<lastBuildDate>Thu, 26 Aug 2010 20:57:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: JacaByte</title>
		<link>http://www.arpia.be/2008/12/office-and-interface/#comment-321</link>
		<dc:creator>JacaByte</dc:creator>
		<pubDate>Mon, 22 Dec 2008 22:30:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.arpia.be/?p=125#comment-321</guid>
		<description>For now, I&#039;ve got Word 2008 on a Windows machine and have to rely on it. It&#039;s frustrating that I still have to use M$ products when I&#039;ve got a Mac of my own. If I ever do decide to buy some office suite software for my Mac, it&#039;ll probably have to be Word 2004/08, since I know it much better than iWork (I&#039;ve never so much as touched it in my life) and it would afford some more peace of mind, since at my school, if the formatting in a document is screwed up, don&#039;t chalk it up to the computer gods, because it&#039;s all your fault, and it&#039;s your grade that will suffer.</description>
		<content:encoded><![CDATA[<p>For now, I&#8217;ve got Word 2008 on a Windows machine and have to rely on it. It&#8217;s frustrating that I still have to use M$ products when I&#8217;ve got a Mac of my own. If I ever do decide to buy some office suite software for my Mac, it&#8217;ll probably have to be Word 2004/08, since I know it much better than iWork (I&#8217;ve never so much as touched it in my life) and it would afford some more peace of mind, since at my school, if the formatting in a document is screwed up, don&#8217;t chalk it up to the computer gods, because it&#8217;s all your fault, and it&#8217;s your grade that will suffer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Craddock</title>
		<link>http://www.arpia.be/2008/12/office-and-interface/#comment-319</link>
		<dc:creator>Peter Craddock</dc:creator>
		<pubDate>Mon, 22 Dec 2008 16:41:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.arpia.be/?p=125#comment-319</guid>
		<description>Actually, Pages has great .doc support.
The main &quot;exporting to .doc&quot; problem I&#039;ve noticed is that sometimes, text can end up being 1 point smaller than it&#039;s supposed to be (I&#039;ve only encountered that with section headings though).
Importing .doc changes the layout more so than when exporting from Pages to .doc, though.
There&#039;s also a slight problem that I encounter for all my lecture notes, because in Pages, I have &quot;Notes of Peter Craddock&quot; in the middle of the footer, and in the right-hand corner of the footer, the page number. The resulting .doc doesn&#039;t copy over that layout, and puts the whole text to the right. Afterwards, you just have to tweak a little.

In my experience, it&#039;s just easier to do the work in Pages (a non-frustrating program, especially when compared to Word), and then export to .doc and check in Word what it looks like. But you could choose to rely solely on iWork.</description>
		<content:encoded><![CDATA[<p>Actually, Pages has great .doc support.<br />
The main &#8220;exporting to .doc&#8221; problem I&#8217;ve noticed is that sometimes, text can end up being 1 point smaller than it&#8217;s supposed to be (I&#8217;ve only encountered that with section headings though).<br />
Importing .doc changes the layout more so than when exporting from Pages to .doc, though.<br />
There&#8217;s also a slight problem that I encounter for all my lecture notes, because in Pages, I have &#8220;Notes of Peter Craddock&#8221; in the middle of the footer, and in the right-hand corner of the footer, the page number. The resulting .doc doesn&#8217;t copy over that layout, and puts the whole text to the right. Afterwards, you just have to tweak a little.</p>
<p>In my experience, it&#8217;s just easier to do the work in Pages (a non-frustrating program, especially when compared to Word), and then export to .doc and check in Word what it looks like. But you could choose to rely solely on iWork.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JacaByte</title>
		<link>http://www.arpia.be/2008/12/office-and-interface/#comment-318</link>
		<dc:creator>JacaByte</dc:creator>
		<pubDate>Mon, 22 Dec 2008 16:19:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.arpia.be/?p=125#comment-318</guid>
		<description>In the short time that I played around with NeoOffice, I was disgusted by its user interface (as you were) and at the abysmal loading times that it presented. Loading the program took ages, the program itself was slow at times, and it was far too easy to launch parts of the suite that I didn&#039;t need, further bogging down the program. Slow, slow, slow.

My machine isn&#039;t slow, by any stretch of the mind, with a 1.25 GHz G4 processor and 1.25 GB of RAM. OS X is meant to give users as broad a range of usable programs as possible, meaning that many modern day programs can still run on 500 MHz G4 computers. Whether or not this was intentional is beside the point, since now we always expect such a high standard from all (or most) of the programs we use on a day to day basis. NeoOffice doesn&#039;t meet this standard. It&#039;s really a shame, because the only program that I do know that meets these standards is iWork, and from what I hear, it doesn&#039;t have full support of the .doc files that Word uses, which I need for assignments at my school. I could be wrong, but it seems that M$ has dominated office suites in all areas of software.</description>
		<content:encoded><![CDATA[<p>In the short time that I played around with NeoOffice, I was disgusted by its user interface (as you were) and at the abysmal loading times that it presented. Loading the program took ages, the program itself was slow at times, and it was far too easy to launch parts of the suite that I didn&#8217;t need, further bogging down the program. Slow, slow, slow.</p>
<p>My machine isn&#8217;t slow, by any stretch of the mind, with a 1.25 GHz G4 processor and 1.25 GB of RAM. OS X is meant to give users as broad a range of usable programs as possible, meaning that many modern day programs can still run on 500 MHz G4 computers. Whether or not this was intentional is beside the point, since now we always expect such a high standard from all (or most) of the programs we use on a day to day basis. NeoOffice doesn&#8217;t meet this standard. It&#8217;s really a shame, because the only program that I do know that meets these standards is iWork, and from what I hear, it doesn&#8217;t have full support of the .doc files that Word uses, which I need for assignments at my school. I could be wrong, but it seems that M$ has dominated office suites in all areas of software.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
