<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>blog &#187; tech</title>
	<atom:link href="http://steelplatesahead.com/matt/blog/category/tech/feed/" rel="self" type="application/rss+xml" />
	<link>http://steelplatesahead.com/matt/blog</link>
	<description></description>
	<lastBuildDate>Sun, 31 Jan 2010 22:49:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Don&#8217;t Bother Replacing Office</title>
		<link>http://steelplatesahead.com/matt/blog/2009/10/dont-bother-replacing-office/</link>
		<comments>http://steelplatesahead.com/matt/blog/2009/10/dont-bother-replacing-office/#comments</comments>
		<pubDate>Thu, 01 Oct 2009 16:00:14 +0000</pubDate>
		<dc:creator>Matt</dc:creator>
				<category><![CDATA[free software]]></category>
		<category><![CDATA[tech]]></category>

		<guid isPermaLink="false">http://steelplatesahead.com/matt/blog/?p=49</guid>
		<description><![CDATA[Recently <a href="http://www.thebigmoney.com/articles/money-trail/2009/09/28/office-rules">Mark Gimein wrote in his blog</a> that Microsoft Office doesn't have any real competition because its closest competitor, <a href="http://openoffice.org">OpenOffice.org</a> (OO), is free, but mediocre.]]></description>
			<content:encoded><![CDATA[<p>Recently <a href="http://www.thebigmoney.com/articles/money-trail/2009/09/28/office-rules">Mark Gimein wrote in his blog</a> that Microsoft Office doesn&#8217;t have any real competition because its closest competitor, <a href="http://openoffice.org">OpenOffice.org</a> (OO), is free, but mediocre. According to him, because the latter suite is mediocre, few would use it to replace the Old MS Standby, and because it is free, no one can be expected  to develop and subsequently <em>sell</em> an alternative office suite for anything more than nothing. </p>
<p>He makes some excellent points. For one, I think he&#8217;s right in saying that OpenOffice.org is in many ways a clone of MS Office pre-2007. Of course, this isn&#8217;t entirely true, but it appears that the purpose of OO and its predecessor, StarOffice, was to duplicate Office functionality for a lower price. Unfortunately, while Office underwent a pretty significant and, in my opinion, positive overhaul with its 2007 version, OO seems mired in the past, particularly in terms of its interface &mdash; functionality buried behind a dizzying array of menus, submenus, dialog boxes and property sheets. Gimein believes that the OO community has settled for &#8220;good enough&#8221; software since its price tag is $0. Furthermore, we shouldn&#8217;t expect anyone else in the open source community to produce anything superior in the non-sexy realm of office productivity software. I hope, to a degree, he&#8217;s right.</p>
<p>I don&#8217;t think anyone <em>should bother</em> replacing Microsoft Office <em>in its current form</em>. That is, a large office software suite with a plethora of features, most of them of acceptable quality, but none of them particularly amazing. Instead, I&#8217;d rather see the <a href="http://www.gnu.org/philosophy/free-sw.html">free software</a> community develop modular, more specific tools that work together happily via open standards. The idea is old. Individual software programs should fulfill a particular niche within a larger procedural pipeline, not consist of the entire pipeline in themselves. People in the Linux/Unix world seem to get this. Why use Word for everything including word processing, HTML and image editing, desktop publishing, writing theses and dissertations (with references!), creating forms for users to fill-in, and sharing documents <em>for viewing</em> when each of these tasks really needs its own, dedicated system to do the job well? </p>
<p>I&#8217;m guessing my argument is moot anyway. The future of office software is not primarily on the desktop, but likely <em>in the cloud</em> (a whole other topic altogether). Like <a href="http:docs.google.com">Google Docs</a>, they&#8217;re likely to be a bit more streamlined than the Office we&#8217;re used to. In the meantime, do yourself a favor and learn about more focused systems that replace bits of Office functionality &mdash; text editors (other than Notepad), image editors, desktop publishing systems (even for academic posters!), HTML editors, database systems, diagramming tools, and so on. (Take note, there are free systems [other than OO] in all of these categories.)</p>
<hr />
For my own sake, I can&#8217;t go without griping about a couple of Gimein&#8217;s assertions: </p>
<ol>
<li>Don&#8217;t confuse the so-called <em>open source</em> movement with the <em><a href="http://www.gnu.org/philosophy/free-sw.html">free software</a></em> movement. Richard Stallman is more concerned with ethical issues regarding our liberty and freedom with software than about production processes and quality; those latter issues are promoted more by the <a href="http://www.opensource.org/">Open Source Initiative</a>, which is trying to appeal to the business world.</li>
<li>OO&#8217;s benefits go beyond the free price; the author neglected to mention that it natively supports the OpenDocument format, preventing users from <a href="http://en.wikipedia.org/wiki/Vendor_lock-in">vendor lock-in</a>.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://steelplatesahead.com/matt/blog/2009/10/dont-bother-replacing-office/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Bemoaning the Decline of Print</title>
		<link>http://steelplatesahead.com/matt/blog/2009/09/bemoaning-the-decline-of-print/</link>
		<comments>http://steelplatesahead.com/matt/blog/2009/09/bemoaning-the-decline-of-print/#comments</comments>
		<pubDate>Sat, 26 Sep 2009 14:34:44 +0000</pubDate>
		<dc:creator>Matt</dc:creator>
				<category><![CDATA[tech]]></category>
		<category><![CDATA[drm]]></category>
		<category><![CDATA[e-books]]></category>
		<category><![CDATA[media]]></category>

		<guid isPermaLink="false">http://steelplatesahead.com/matt/blog/?p=37</guid>
		<description><![CDATA[This morning I stumbled upon a blog entry titled <a href="http://radar.oreilly.com/2009/09/rebooting-the-book-one-apple-i.html">Rebooting the Book (One Apple iPad Tablet at a Time)</a> by <a href="http://radar.oreilly.com/msigal">Mark Sigal</a>. In the article, Sigal dreams of the new possibilities of when digital readers…]]></description>
			<content:encoded><![CDATA[<p>This morning I stumbled upon a blog entry titled <a href="http://radar.oreilly.com/2009/09/rebooting-the-book-one-apple-i.html">Rebooting the Book (One Apple iPad Tablet at a Time)</a> by <a href="http://radar.oreilly.com/msigal">Mark Sigal</a>. In the article, Sigal dreams of the new possibilities of when digital readers and other multimedia devices completely replace the printed book, in particular when Apple gets involved in the e-book reader business. (I personally don&#8217;t know anything about Apple&#8217;s e-book projects, but it&#8217;s really beside the point.) </p>
<p>This article is another example of dramatic, high-tech speculation in which possibilities in the future world astound us, and those who hold on to present or past ways are cast aside in irrelevance. In this case, it&#8217;s the bibliophiles who are desperately (and apparently, naively) holding on to the printed word; if only they would open their eyes to the <em>inevitable</em> developments &mdash; &#8220;books&#8221; with internet connections, interactive features, simulations, video immersion, and built-in social networking &mdash; they would see the light too! So the other author pleads. </p>
<p>For better or worse, I don&#8217;t quite consider myself a bibliophile. I like reading, but I tend to get distracted and forget about the two or three books I&#8217;m trying to engage. However, I, like some bibliophiles, am really hesitant to fully embrace the e-book reader trend, or the multi-media remaking of the book. My primary concerns are in the form of questions. First, there are the copyright issues. How will future e-books be distributed, who will have the rights to read them, and will I be able to give a copy to my friend when I am done (something I can do now with physical books, at no risk to my legal self)? Will e-books make me more or less dependent on energy companies, telecoms, and technology companies? Will they help the small publisher, or more greatly benefit the large media outlets (e.g., Amazon, Apple, etc)? </p>
<p>These last concerns are particularly directed at Sigal&#8217;s speculations about the new possibilities for multimedia in learning. Will future forms of what are now printed genres help me better reason about the world? Will simulations and immersive digital environments help me to better develop, communicate, and defend my ideas? Will they help me think and speak coherently? I for one have a really hard time reading a long <a href="http://wikipedia.org">wikipedia</a> article without getting completely distracted with links redirecting me and my thought processes to other articles or other places on the web.</p>
<p>I like new things. They&#8217;re fun and exciting. I also understand that communication media change and will continue to change. (Personal case in point: I&#8217;m writing a blog.) However, don&#8217;t give up on print just yet. Don&#8217;t give up on that which is non-interactive. Don&#8217;t give up on the linear construction of ideas. And please, don&#8217;t just assume that if Apple is coming out with a new technology that the best thing to do with it is to push it into our schools. </p>
<p><em>Update</em> (1 October 2009): I just read <a href="http://www.nytimes.com/2009/10/01/books/01book.html">an article regarding these new kinds of media</a> and some and those who are suspicious. </p>
]]></content:encoded>
			<wfw:commentRss>http://steelplatesahead.com/matt/blog/2009/09/bemoaning-the-decline-of-print/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Review: Web Style Guide</title>
		<link>http://steelplatesahead.com/matt/blog/2009/09/review-web-style-guide/</link>
		<comments>http://steelplatesahead.com/matt/blog/2009/09/review-web-style-guide/#comments</comments>
		<pubDate>Fri, 11 Sep 2009 14:54:56 +0000</pubDate>
		<dc:creator>Matt</dc:creator>
				<category><![CDATA[books]]></category>
		<category><![CDATA[tech]]></category>
		<category><![CDATA[style]]></category>
		<category><![CDATA[typography]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://steelplatesahead.com/matt/blog/?p=24</guid>
		<description><![CDATA[I recently read the Web Style Guide (3rd ed.) by Patrick J. Lynch and Sarah Horton. This book struck me as a mature, down-to-earth, and useful guide to designing for the web. The authors intelligently address the web development process, information design, page structure, layout and typography. They avoid gimmicky trends and focus on approach [...]]]></description>
			<content:encoded><![CDATA[<p>I recently read the <cite title="Web Style Guide (3rd. ed.)"><a href="http://webstyleguide.com/">Web Style Guide (3rd ed.)</a></cite> by Patrick J. Lynch and Sarah Horton. This book struck me as a mature, down-to-earth, and useful guide to designing for the web. The authors intelligently address the web development process, information design, page structure, layout and typography. They avoid gimmicky trends and focus on approach as opposed to rushing into new technologies; it&#8217;s not a how-to guide or a book about any particular web system or language. Instead, the authors elaborate on emerging standards and conventions the web community has developed over the past two decades.</p>
<p>I was particularly impressed by Lynch and Horton&#8217;s commitment to <a href="http://en.wikipedia.org/wiki/Universal_usability">universal usability</a>, that is, designing to support all users, including those not typically supported such as the visually-impaired. As a result, they rightly emphasize the semantic nature of <acronym title="Hyper Text Markup Language">HTML</acronym>. For example, instead of creating your headings with a styled <code>&lt;div&gt;</code> tag, use the appropriate <code>&lt;h*&gt;</code> tag and style as necessary. (This prompted me to re-familiarize myself with some of the underused features of <acronym title="Hyper Text Markup Language">HTML</acronym>, including <code>&lt;abbr&gt;</code> for abbreviations, <code>&lt;cite&gt;</code> for in-document citations, <code>&lt;address&gt;</code> for addresses, and <code>&lt;dl&gt;</code>, <code>&lt;dt&gt;</code>, <code>&lt;dd&gt;</code> for lists of terms and definitions.) By using these tags instead of styled <code>&lt;p&gt;</code> or  <code>&lt;div&gt;</code> tags, you can provide hints to screen readers and search engines about how to render or interpret your web content.</p>
<p>The <cite title="Web Style Guide">Web Style Guide</cite> is generally helpful, easy to read, and well-written. (I recommend it if you plan to re-design your own website.) If you don&#8217;t feel like purchasing the text or simply want to sample some of the content, you can access the <a href="http://webstyleguide.com/wsg3/index.html">full text online</a>.</p>
<p>m</p>
<p>ps: unfortunately, reading this book made me realize that I have a lot of work to do to improve this site. Don&#8217;t judge me by the authors&#8217; standards just yet!</p>
]]></content:encoded>
			<wfw:commentRss>http://steelplatesahead.com/matt/blog/2009/09/review-web-style-guide/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Improving the MS Word Experience</title>
		<link>http://steelplatesahead.com/matt/blog/2009/06/improving-the-ms-word-experience/</link>
		<comments>http://steelplatesahead.com/matt/blog/2009/06/improving-the-ms-word-experience/#comments</comments>
		<pubDate>Wed, 17 Jun 2009 19:38:22 +0000</pubDate>
		<dc:creator>Matt</dc:creator>
				<category><![CDATA[tech]]></category>
		<category><![CDATA[typesetting]]></category>

		<guid isPermaLink="false">http://steelplatesahead.com/matt/blog/?p=17</guid>
		<description><![CDATA[During the process of writing my master&#8217;s thesis, I learned how to use LaTeX. Prior to this experience, I certainly wasn&#8217;t fond of using Word, particularly for creating large documents with figures and bibliographies, but now I know I&#8217;ll never go back, if I can help it. Word is, however, what most academics I&#8217;ve encountered [...]]]></description>
			<content:encoded><![CDATA[<p>During the process of writing my master&#8217;s thesis, I learned how to use <a href="http://en.wikipedia.org/wiki/LaTeX">LaTeX</a>. Prior to this experience, I certainly wasn&#8217;t fond of using Word, particularly for creating large documents with figures and bibliographies, but now I know I&#8217;ll never go back, if I can help it. Word is, however, what most academics I&#8217;ve encountered use for writing papers (perhaps in a slightly better world they&#8217;d be using <a href="http://openoffice.org">OpenOffice</a> instead). Thus, if you&#8217;re going to collaborate with other Word users, sometimes you just have to buckle down and use it.</p>
<p>Fortunately, while recently working on a paper in Word, I came across a few bits of information that made using Word just a <em>bit</em> more tolerable, and led to the production of a slightly more attractive document, in my opinion. These tips are particularly relevant to authors using a document template for, say, a conference submission. (In my case it was the ACM CHI template for CSCW.)</p>
<ol>
<li>Enable auto-hyphenation. With this setting enabled, Word will try to hyphenate long words at the end of justified paragraphs to minimize unsightly lines of text with far too much space between words. For some reason, the auto-hyphenate option is disabled by default. When using a two-column, justified paragraph layout as in the ACM template, using auto-hyphenate can really make your documents look better, and may even allow you to squeeze in a bit of extra content. See <a href="http://office.microsoft.com/en-us/word/HA100963951033.aspx">this MS support page</a> to learn how to enable auto-hyphenation. (Fortunately, LaTeX already does this quite nicely.)</li>
<li>Manually insert hyphenation suggestions when necessary. In some cases Word is unable to hyphenate a word at the right edge of a column (particularly words it doesn&#8217;t recognize). For these occasions you can manually insert an invisible hyphen suggestion. If it needs to, Word will hyphenate the word at the point you suggest. Again, see <a href="http://office.microsoft.com/en-us/word/HA100963951033.aspx">this MS support page</a> to learn how to insert hyphenation suggestions. It&#8217;s easy. If you enable the option to view all formatting marks, you can see all of the manual hyphenation suggestions you insert (and delete them as well).</li>
<li>Insert the proper dash manually. Dashes are long versions of the hyphen (see the <a href="http://en.wikipedia.org/wiki/Dash">wikipedia page on dashes</a> for an overview). I used to rely on AutoCorrect to adjust multiple hyphens into a dash, but no longer. With num-lock on, insert an en dash using <code>Ctrl + -</code> and an em dash with <code>Ctrl + Alt + -</code>.</li>
<li>Insert ellipses manually. Use <code>Ctrl + Alt + &lt;period&gt;</code>.</li>
<li>Use relative positioning for your figures. Instead of trying to manually position your figures, anchor them to a place within your text that makes sense (e.g., where you first reference it). By doing this you can position figures <em>relative</em> to the top or bottom of page margins, and they will automatically move with the anchor point as you edit the text. See <a href="http://office.microsoft.com/en-us/word/HP051899251033.aspx">this MS support page</a> to see how to enable relative positioning. (Once on this page, expand the option &#8220;Position a drawing object in relation to page, text, or other anchor.&#8221;) Find out how to set an anchor point for your figures in one of the responses <a href="http://en.allexperts.com/q/Microsoft-Word-1058/moving-text-boxes-1.htm">on this page</a>. (Incidentally, this person advocates not placing figures in a text box, but I find that placing figures/graphs/tables in text boxes makes it easier to maintain the relative caption position. If you have a better way of handling it, please let me know!)<br />
Once I adopted relative positioning with in-text anchors, I no longer had to wait until the end of the writing process to position my figures.</li>
</ol>
<p>I hope some of these tips make your Word experience more bearable. In the mean time, take a look at LaTeX.</p>
<p>m</p>
]]></content:encoded>
			<wfw:commentRss>http://steelplatesahead.com/matt/blog/2009/06/improving-the-ms-word-experience/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

