<?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: E-books as the new large &#8216;print&#8217;: An eye doctor speaks out</title>
	<atom:link href="http://www.teleread.com/2008/04/01/e-books-as-the-new-large-print-an-eye-doctor-speaks-out/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.teleread.com/ebooks/e-books-as-the-new-large-print-an-eye-doctor-speaks-out/</link>
	<description>News &#38; views on e-books, libraries, publishing and related topics</description>
	<lastBuildDate>Wed, 15 Feb 2012 08:05:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Rob Preece</title>
		<link>http://www.teleread.com/ebooks/e-books-as-the-new-large-print-an-eye-doctor-speaks-out/comment-page-1/#comment-749014</link>
		<dc:creator>Rob Preece</dc:creator>
		<pubDate>Tue, 01 Apr 2008 22:43:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/2008/04/01/e-books-as-the-new-large-print-an-eye-doctor-speaks-out/#comment-749014</guid>
		<description>I had the opportunity to play with a Kindle last weekend. I was impressed by the number of font sizes. Sadly, my much-loved eBookWise offers fewer options. Not a problem for books available in HTML or RTF as I can re-size them first and then convert but something of a problem for books where the source files are not easily accessible. (This is one reason all of our books are available in HTML format).

Rob Preece
Publisher, www.BooksForABuck.com</description>
		<content:encoded><![CDATA[<p>I had the opportunity to play with a Kindle last weekend. I was impressed by the number of font sizes. Sadly, my much-loved eBookWise offers fewer options. Not a problem for books available in HTML or RTF as I can re-size them first and then convert but something of a problem for books where the source files are not easily accessible. (This is one reason all of our books are available in HTML format).</p>
<p>Rob Preece<br />
Publisher, <a href="http://www.BooksForABuck.com" rel="nofollow">http://www.BooksForABuck.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Lester</title>
		<link>http://www.teleread.com/ebooks/e-books-as-the-new-large-print-an-eye-doctor-speaks-out/comment-page-1/#comment-748858</link>
		<dc:creator>Jim Lester</dc:creator>
		<pubDate>Tue, 01 Apr 2008 19:59:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/2008/04/01/e-books-as-the-new-large-print-an-eye-doctor-speaks-out/#comment-748858</guid>
		<description>I would think that large font reading on any current generation eInk device would become annoying rather quickly because of the refresh rate of the screens.  

In the thread post by Alan on mobileread, the medium large size, 36pt, was fitting about 10 words (5 lines ~10 characters/2 words per line) on the screen.  So you weren&#039;t even seeing a full sentence on the screen, and to get to the next part of the sentence you would have a 1-3 sec delay  while the screen refreshed.  That much of a delay that often would bug the heck out of me.

As much as I like the eInk devices, I would think that the better responsiveness rates and size of LCD screens would make them more suitable to reading at large font sizes.

Does anybody here have experience with this that they would like to share?</description>
		<content:encoded><![CDATA[<p>I would think that large font reading on any current generation eInk device would become annoying rather quickly because of the refresh rate of the screens.  </p>
<p>In the thread post by Alan on mobileread, the medium large size, 36pt, was fitting about 10 words (5 lines ~10 characters/2 words per line) on the screen.  So you weren&#8217;t even seeing a full sentence on the screen, and to get to the next part of the sentence you would have a 1-3 sec delay  while the screen refreshed.  That much of a delay that often would bug the heck out of me.</p>
<p>As much as I like the eInk devices, I would think that the better responsiveness rates and size of LCD screens would make them more suitable to reading at large font sizes.</p>
<p>Does anybody here have experience with this that they would like to share?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Wallcraft</title>
		<link>http://www.teleread.com/ebooks/e-books-as-the-new-large-print-an-eye-doctor-speaks-out/comment-page-1/#comment-748782</link>
		<dc:creator>Alan Wallcraft</dc:creator>
		<pubDate>Tue, 01 Apr 2008 17:27:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/2008/04/01/e-books-as-the-new-large-print-an-eye-doctor-speaks-out/#comment-748782</guid>
		<description>See the recent discussion at http://www.mobileread.com/forums/showthread.php?t=22376

Using 72pts per inch, the Kindle&#039;s maximum font size is about 18pt, the Cybook&#039;s is about 24pt and the iLiad&#039;s is about 30pt.  The above MobileRead thread links to screenshots (bitmaps) of the Kindle and iLiad largest sizes and to photos of the Cybook largest size font.  The default (non-adjustable) line spacing on all three devices is much too large for large fonts.

Note that is is not a font issue, all the devices use scalable fonts.  FBReader on the iLiad can use larger font sizes, but it also has automatic hyphenation and fine control over line spacing (both of which may be essential at really large font sizes).</description>
		<content:encoded><![CDATA[<p>See the recent discussion at <a href="http://www.mobileread.com/forums/showthread.php?t=22376" rel="nofollow">http://www.mobileread.com/forums/showthread.php?t=22376</a></p>
<p>Using 72pts per inch, the Kindle&#8217;s maximum font size is about 18pt, the Cybook&#8217;s is about 24pt and the iLiad&#8217;s is about 30pt.  The above MobileRead thread links to screenshots (bitmaps) of the Kindle and iLiad largest sizes and to photos of the Cybook largest size font.  The default (non-adjustable) line spacing on all three devices is much too large for large fonts.</p>
<p>Note that is is not a font issue, all the devices use scalable fonts.  FBReader on the iLiad can use larger font sizes, but it also has automatic hyphenation and fine control over line spacing (both of which may be essential at really large font sizes).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Darvell</title>
		<link>http://www.teleread.com/ebooks/e-books-as-the-new-large-print-an-eye-doctor-speaks-out/comment-page-1/#comment-748773</link>
		<dc:creator>Brian Darvell</dc:creator>
		<pubDate>Tue, 01 Apr 2008 17:10:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/2008/04/01/e-books-as-the-new-large-print-an-eye-doctor-speaks-out/#comment-748773</guid>
		<description>I think i-devices is a pun for both &#039;ipod&#039; and &#039;i&#039; as in &#039;eye&#039;.  ;)</description>
		<content:encoded><![CDATA[<p>I think i-devices is a pun for both &#8216;ipod&#8217; and &#8216;i&#8217; as in &#8216;eye&#8217;.  <img src='http://www.teleread.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Database Caching using disk: basic
Object Caching 343/370 objects using disk: basic

Served from: www.teleread.com @ 2012-02-15 06:03:39 -->
