<?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>MacWhiz Blog &#187; iPad</title>
	<atom:link href="http://macwhiz.com/blog/tag/ipad/feed/" rel="self" type="application/rss+xml" />
	<link>http://macwhiz.com/blog</link>
	<description>Macs, customer service, and other musings</description>
	<lastBuildDate>Thu, 26 Apr 2012 03:20:39 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Reading Books on the iPad</title>
		<link>http://macwhiz.com/blog/2010/06/11/reading-books-on-the-ipad/</link>
		<comments>http://macwhiz.com/blog/2010/06/11/reading-books-on-the-ipad/#comments</comments>
		<pubDate>Sat, 12 Jun 2010 01:58:07 +0000</pubDate>
		<dc:creator>Rob Levandowski</dc:creator>
				<category><![CDATA[Recommendations]]></category>
		<category><![CDATA[Amazon]]></category>
		<category><![CDATA[B&N]]></category>
		<category><![CDATA[ePub]]></category>
		<category><![CDATA[iBooks]]></category>
		<category><![CDATA[iPad]]></category>
		<category><![CDATA[Kindle]]></category>

		<guid isPermaLink="false">http://macwhiz.com/blog/?p=247</guid>
		<description><![CDATA[I'm more sold on reading books on my iPad than I thought I'd be. However, the experience is marred by some publishers' poor quality control on their electronic texts. Of the reader applications, all have flaws, but iBooks has the best experience. The Kindle app is feature-poor but okay, and the B&#038;N app wounds itself fatally by inexcusably poor typography.]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fmacwhiz.com%2Fblog%2F2010%2F06%2F11%2Freading-books-on-the-ipad%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fmacwhiz.com%2Fblog%2F2010%2F06%2F11%2Freading-books-on-the-ipad%2F&amp;source=macwhiz&amp;style=normal&amp;service=ow.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>Before I got my iPad, I didn&#8217;t think I&#8217;d use it much for reading books.  I love books.  The house is full of books. I&#8217;m proud that I am perennially short of bookshelves.</p>
<p>Now, I find myself leaning toward buying books via the iPad more than going to the bookstore.</p>
<p>The thing is, I usually have my iPad with me.  It&#8217;s easy to carry. That means I can read nearly anywhere, and as a result I can read more often. I&#8217;m already a devout reader, so this just feeds the addiction.</p>
<p>Of the available readers, Apple&#8217;s iBooks is my favorite.  By no means is it perfect, but it&#8217;s good enough.  With the right font, and the right type size, I don&#8217;t find the iPad&#8217;s LCD objectionable.  It certainly gets dim enough to read comfortably in bed. (It lights up the room considerably less than the LED miner&#8217;s lamp I use for reading physical books in bed.)</p>
<p>Where iBooks falls down is in the texts themselves.<span id="more-247"></span></p>
<h2>Texts</h2>
<p>Some publishers are doing right by the electronic reader, and are releasing books that match the formatting and copy-editing of the paper version.  Others are taking various shortcuts.  Browsing the iBookstore, you&#8217;ll find many bestsellers getting poor reviews because of editing and typographical errors.  I suspect some publishers are sending off their uncorrected galley proofs for digital conversion in the name of speed, hoping that the electronic buyer won&#8217;t notice or won&#8217;t care. I suspect those publishers are wrong. I certainly avoid those electronic texts, and as a result those publishers have to wait until I&#8217;m done reading eBooks and get to the store&#8230; or sometimes, they don&#8217;t get my money at all.</p>
<p>Note to publishers: An impulse purchase is a potential sale only so long as the impulse exists.</p>
<p>Even otherwise well-done books have odd flaws.  For example, <a href="http://www.amazon.com/gp/product/0446554960?ie=UTF8&amp;tag=macwhiztechnolog&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=0446554960">Preston and Child&#8217;s <em>Fever Dream</em></a> on iBooks looks very close to the print layout, except that the word &#8220;fixing&#8221; is set as &#8220;fi xing&#8221; throughout.</p>
<p>Some of the texts from established e-book vendors are highly uneven. <a href="http://www.baen.com">Baen Books</a> has embraced <a href="http://www.baen.com/library/">free e-book versions</a> of their authors&#8217; back catalogues for some time. They even bind CD-ROMs of their e-book library to new hardcovers for some titles.  Some of these versions are well formatted. Some are okay, but are missing niceties like “curly quotes”—something forgivable on a blog site, but uncomfortable in a book.  A few have obviously taken a detour through plain-text-file-ville at some point in their life, making them awkward to utterly unreadable.  (Imagine reading a book where all the extra line breaks signifying a change in scene or point-of-view have been elided.)</p>
<p>Okay, but those are free e-books, so you have to make allowances, right? Unfortunately, I&#8217;ve found the same flaws in Baen&#8217;s paid DRM-free ePub e-books as well. If I&#8217;m paying for the book, I expect a well-edited text that is properly &#8220;typeset.&#8221;</p>
<p>If e-Books are going to take off, publishers have to make them as close to the print version as possible, especially in terms of layout and editing.</p>
<h2>Readers</h2>
<p>I&#8217;ve tried the big three iPad e-book readers: Apple&#8217;s <a href="http://itunes.apple.com/us/app/ibooks/id364709193?mt=8">iBooks</a>, the <a href="http://itunes.apple.com/app/bn-ereader-for-ipad/id373582546?mt=8">Barnes &amp; Noble eReader</a>, and Amazon&#8217;s <a href="http://itunes.apple.com/us/app/kindle/id302584613?mt=8">Kindle app</a>.</p>
<p>All have flaws.</p>
<p>iBooks limits you to a small handful of fonts. Only one of them resembles anything you&#8217;re likely to find in a well-designed mass-market book: Baskerville. I suppose Palatino and Times New Roman aren&#8217;t horrible, but they aren&#8217;t typical book faces. Cochin is too ornate to be comfortable as a text font, and Verdana… well… it&#8217;s Verdana. It&#8217;s an ugly Microsoft sans-serif typeface designed for reading on Windows 95-era CRTs.  I suppose it has its fans, but then, the same could be said for velvet paintings of dogs playing poker.</p>
<p>On the plus side, iBooks does a very good job rendering those fonts. Apple&#8217;s Type Services are used to full effect; you get <a href="http://en.wikipedia.org/wiki/Typographic_ligature">ligatures</a> (&#64257; and &#64258; instead of fi and fl, for example) automatically. The letters are well-kerned, and the line-spacing generally matches what you&#8217;d expect in a real book.  The result is comfortable to read, especially in Baskerville.</p>
<p>The B&amp;N eReader gives you more font choices: Amasis, Century Schoolbook, Georgia, Joanna, Times New Roman, Ascender Sans, Gill Sans, and Trebuchet MS. With the exception of Trebuchet, all are reasonable fonts. The serif fonts wouldn&#8217;t be out of place in a real book. However, the font rendering is fatally flawed. The lack of ligatures is bad enough.  However, except for Century Schoolbook, none of the fonts provided will display italics. Any italicized text gets rendered as plain text.  This can render a book utterly incomprehensible.</p>
<p>Even Century Schoolbook is flawed. While you can make out italic text in Century Schoolbook, it isn&#8217;t set in a true italic face. Instead, the font is mathematically slanted (&#8220;oblique&#8221;) to make a pseudo-italic appearance. The result is ugly, and very reminiscent of early Mac typography circa 1984. The poor typography of B&amp;N eReader is indefensible in a book-reading application.</p>
<p>I also find the line spacing and page width options uncomfortable.</p>
<p>I quickly ruled out the B&amp;N app.</p>
<p>The Kindle app gives you one typeface, reminiscent of paperbacks from the 1950s and 1960s. It&#8217;s not bad for reading, but it is what it is. It also comes with relatively unimaginative page design as a result. However, it does scale to small sizes very well, and is very legible on the iPad&#8217;s screen.</p>
<p>Like the B&amp;N app, the Kindle app fails to take advantage of iOS&#8217;s built-in support for advanced typography, such as ligatures.</p>
<p>The B&amp;N and Kindle apps both lack an in-app bookstore, forcing you to jump out to Safari and use the vendor&#8217;s web site to purchase new books.  On the other hand, both the B&amp;N and Amazon web sites are far easier to browse than Apple&#8217;s iBookstore.  Trying to &#8220;browse the shelves&#8221; in iBookstore can be infuriating, as you see only a fraction of the content unless you perform a search.</p>
<p>All three apps have a common failing: None of them implement proper hyphenation. This leads to some ugly typography, especially for certain texts at certain font sizes. I don&#8217;t find it as objectionable as some, but many book snobs find it painful. The B&amp;N app offers an option to display ragged-right text, which reduces the need for hyphenation; the other two only offer full justification.</p>
<p style="text-align: center;">* * *</p>
<p>So far, all three readers are flawed, but I find iBooks&#8217; flaws the least objectionable. It looks good, it works well, and it feels polished. B&amp;N&#8217;s app is decidedly half-baked, and not up to professional standards—never mind professional <em>book publishing</em> standards. The Kindle app shows more experience with e-Books, but is definitely &#8220;Kindle lite&#8221; and short of the mark.</p>
<p>I look forward to future versions of all three, hopefully combined with a more serious commitment to quality from the publishers.</p>
]]></content:encoded>
			<wfw:commentRss>http://macwhiz.com/blog/2010/06/11/reading-books-on-the-ipad/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Review: Incase Grip Protective Cover for iPad</title>
		<link>http://macwhiz.com/blog/2010/05/17/review-incase-grip/</link>
		<comments>http://macwhiz.com/blog/2010/05/17/review-incase-grip/#comments</comments>
		<pubDate>Tue, 18 May 2010 03:46:59 +0000</pubDate>
		<dc:creator>Rob Levandowski</dc:creator>
				<category><![CDATA[Recommendations]]></category>
		<category><![CDATA[iPad]]></category>

		<guid isPermaLink="false">http://macwhiz.com/blog/?p=238</guid>
		<description><![CDATA[Since I got my iPad, I&#8217;ve been a bit worried about dropping it.  The aluminum back doesn&#8217;t give one a lot of confidence; while I&#8217;ve not dropped it yet, it sometimes feels distressingly like it could slip out of one&#8217;s grasp. It seemed like a silicone slipcover would be just the ticket. I bought the [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fmacwhiz.com%2Fblog%2F2010%2F05%2F17%2Freview-incase-grip%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fmacwhiz.com%2Fblog%2F2010%2F05%2F17%2Freview-incase-grip%2F&amp;source=macwhiz&amp;style=normal&amp;service=ow.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>Since I got my iPad, I&#8217;ve been a bit worried about dropping it.  The aluminum back doesn&#8217;t give one a lot of confidence; while I&#8217;ve not dropped it yet, it sometimes feels distressingly like it could slip out of one&#8217;s grasp.</p>
<p>It seemed like a silicone slipcover would be just the ticket.</p>
<p><span id="more-238"></span></p>
<p>I bought the Incase Grip Protective Cover at an Apple Store. Admittedly, I confused it with the almost identical Incase Protective Cover.  It was the Protective Cover I was really looking to buy.</p>
<p>I have several Incase protective cases, and I&#8217;ve been happy with their design and construction.  But&#8230;</p>
<p>The Grip Protective Cover isn&#8217;t just a straight silicone slipcover.  It adds two humps near the top and bottom of the iPad.  They provide a bit more heft to grip the iPad when it&#8217;s held in landscape orientation.  Some may find they help in the normal portrait orientation, as well; I find them sort of awkward.</p>
<p>There are two major flaws with the Grip Protective Cover:</p>
<ol>
<li>The humps add weight.  A noticeable amount of weight.  With the cover on, my wrists complain more quickly and more loudly about trying to hold the iPad one-handed.</li>
<li>It doesn&#8217;t fit tightly enough.  If you hold the iPad in portrait orientation with your hand about halfway up the screen, your grip will tend to peel the Grip Protective Cover off the side of the iPad.  It could stand to be a good deal tighter.</li>
</ol>
<p>There&#8217;s also the common flaw to silicone slipcovers for any iPod or iPad: although you can use a docking cable, you can&#8217;t use a <em>dock</em> without removing the cover.  This is especially true for the Grip Protective Cover; the humps eliminate any question of docking.</p>
<p>I&#8217;m not impressed with this product.  My objection to the humps are my own mistake, but the loose fit is a problem.  I recommend passing on this product.</p>
]]></content:encoded>
			<wfw:commentRss>http://macwhiz.com/blog/2010/05/17/review-incase-grip/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Some iPad thoughts</title>
		<link>http://macwhiz.com/blog/2010/04/06/some-ipad-thoughts/</link>
		<comments>http://macwhiz.com/blog/2010/04/06/some-ipad-thoughts/#comments</comments>
		<pubDate>Tue, 06 Apr 2010 19:39:33 +0000</pubDate>
		<dc:creator>Rob Levandowski</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[iPad]]></category>

		<guid isPermaLink="false">http://macwhiz.com/blog/2010/04/06/some-ipad-thoughts/</guid>
		<description><![CDATA[My coworker Jack expressed a thought about the iPad that I have had myself a few times over the past few days. While it&#8217;s a great too, and does many things well, it is a bit on the large IDE to be one&#8217;s constant companion. It would be awesome if Apple released something in between [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fmacwhiz.com%2Fblog%2F2010%2F04%2F06%2Fsome-ipad-thoughts%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fmacwhiz.com%2Fblog%2F2010%2F04%2F06%2Fsome-ipad-thoughts%2F&amp;source=macwhiz&amp;style=normal&amp;service=ow.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>My coworker Jack expressed a thought about the iPad that I have had myself a few times over the past few days. While it&#8217;s a great too, and does many things well, it is a bit on the large IDE to be one&#8217;s constant companion. It would be awesome if Apple released something in between the iPad and the iPhone.  Something paperback-sized.  Something that would fit in cargo shorts.</p>
<p>I also have a few gripes about the onscreen keyboard.  Typing on it isn&#8217;t a problem, per se.  The thing is the keys that it&#8217;s missing.</p>
<p>The worst omission is the apostrophe key.  You have to go into a submenu to get that. If you are used to touch-typing, you will find yourself hitting Return a lot when you mean to use an apostrophe. Your alternatives are to learn to type without them (and hope that the autocorreect does the right thing, not always possible with English&#8217;s homophones), or press a button to make the keyboard switch to &#8220;symbol mode.&#8221; That&#8217;s quite annoying.</p>
<p>The other problem is that there are no number keys on the main keypad, even in portrait orientation where there is plenty of room to have them.</p>
<p>I&#8217;d rather have a smaller visible arrea above the keyboard and have number keys and an onscreen apostrophe.</p>
<p>Maybe the idea is to sell more Bluetooth keyboards&#8230;</p>
<p>If someone comes up with a decent iPad case having an integrated Bluetooth keyboard, even if the keyboard is largely rubbish, it will sell like Ames.</p>
]]></content:encoded>
			<wfw:commentRss>http://macwhiz.com/blog/2010/04/06/some-ipad-thoughts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>iPad iPad iPad</title>
		<link>http://macwhiz.com/blog/2010/03/15/ipad-ipad-ipad/</link>
		<comments>http://macwhiz.com/blog/2010/03/15/ipad-ipad-ipad/#comments</comments>
		<pubDate>Tue, 16 Mar 2010 01:44:38 +0000</pubDate>
		<dc:creator>Rob Levandowski</dc:creator>
				<category><![CDATA[Administrative]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[iPad]]></category>

		<guid isPermaLink="false">http://macwhiz.com/blog/?p=54</guid>
		<description><![CDATA[My iPad is on order.  Maybe I&#8217;ll post more often once it arrives&#8230;]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fmacwhiz.com%2Fblog%2F2010%2F03%2F15%2Fipad-ipad-ipad%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fmacwhiz.com%2Fblog%2F2010%2F03%2F15%2Fipad-ipad-ipad%2F&amp;source=macwhiz&amp;style=normal&amp;service=ow.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>My <a href="http://www.apple.com/ipad">iPad</a> is on order.  Maybe I&#8217;ll post more often once it arrives&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://macwhiz.com/blog/2010/03/15/ipad-ipad-ipad/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

