<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments for TeleRead: Bring the E-Books Home</title>
	<link>http://www.teleread.org/blog</link>
	<description>News &#38; views on e-books, libraries, publishing and related topics</description>
	<pubDate>Mon, 12 May 2008 03:21:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>Comment on BooksForABuck owner: The lowdown on our biz model by Rob Preece</title>
		<link>http://www.teleread.org/blog/2008/05/10/bucksforabuck-owner-the-lowdown-on-our-biz-model/#comment-795383</link>
		<dc:creator>Rob Preece</dc:creator>
		<pubDate>Sun, 11 May 2008 19:33:53 +0000</pubDate>
		<guid>http://www.teleread.org/blog/2008/05/10/bucksforabuck-owner-the-lowdown-on-our-biz-model/#comment-795383</guid>
		<description>Hi Al,

A great story about your father. Something to think about--when the Japanese began selling cars in the US, they offered their cars at a discount to what Detroit was selling. They did so, even though their cars were of significantly higher quality. Why did they do it? Because American consumers were unaware of the quality differential and had to be persuaded to try something new.

I think the eBook experience has some aspects in common with that. 

Rob Preece
Publisher, www.BooksForABuck.com</description>
		<content:encoded><![CDATA[<p>Hi Al,</p>
<p>A great story about your father. Something to think about&#8211;when the Japanese began selling cars in the US, they offered their cars at a discount to what Detroit was selling. They did so, even though their cars were of significantly higher quality. Why did they do it? Because American consumers were unaware of the quality differential and had to be persuaded to try something new.</p>
<p>I think the eBook experience has some aspects in common with that. </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>Comment on Sea change in e-book market? Romance beating science fiction at Fictionwise by Marion Gropen</title>
		<link>http://www.teleread.org/blog/2008/05/10/sea-change-in-e-book-market-romance-beating-science-fiction-at-fictionwise/#comment-795237</link>
		<dc:creator>Marion Gropen</dc:creator>
		<pubDate>Sun, 11 May 2008 17:13:02 +0000</pubDate>
		<guid>http://www.teleread.org/blog/2008/05/10/sea-change-in-e-book-market-romance-beating-science-fiction-at-fictionwise/#comment-795237</guid>
		<description>I'd say that it MIGHT mean that women are finally adopting ebooks. And this could be a very significant development. After all, women buy more books than men do, by a fair margin. 

NB: Women avoiding science fiction may not be because women aren't interested in science and speculative fiction. It might be because most science fiction has a notable lack of female characters. After all, romance that leans toward science fiction in tone and setting is a thriving sub-genre.</description>
		<content:encoded><![CDATA[<p>I&#8217;d say that it MIGHT mean that women are finally adopting ebooks. And this could be a very significant development. After all, women buy more books than men do, by a fair margin. </p>
<p>NB: Women avoiding science fiction may not be because women aren&#8217;t interested in science and speculative fiction. It might be because most science fiction has a notable lack of female characters. After all, romance that leans toward science fiction in tone and setting is a thriving sub-genre.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BooksForABuck owner: The lowdown on our biz model by Al</title>
		<link>http://www.teleread.org/blog/2008/05/10/bucksforabuck-owner-the-lowdown-on-our-biz-model/#comment-795181</link>
		<dc:creator>Al</dc:creator>
		<pubDate>Sun, 11 May 2008 16:14:29 +0000</pubDate>
		<guid>http://www.teleread.org/blog/2008/05/10/bucksforabuck-owner-the-lowdown-on-our-biz-model/#comment-795181</guid>
		<description>When my father retired from the USCG he was an expert in his field.  Companies kept asking him to consult.  He kept raising his prices, hoping to ward them off.  The higher his prices went, the more in demand he became.  I suggested he lower his price to the minimum of free plus expenses.  He thought I was crazy, but did it and the consulting dried up immediately.  People value the product by the cost, even though the value does not change with the varying price.  Think of all the people that won't buy things on sale because they don't have the value to them of the full retail priced product.  Books are not immune to this phenomenon.  There are a lot of people out there that do buy on sales, who will try a book for a buck and then go on to paying $4 for more of that author, and I am one of them.</description>
		<content:encoded><![CDATA[<p>When my father retired from the USCG he was an expert in his field.  Companies kept asking him to consult.  He kept raising his prices, hoping to ward them off.  The higher his prices went, the more in demand he became.  I suggested he lower his price to the minimum of free plus expenses.  He thought I was crazy, but did it and the consulting dried up immediately.  People value the product by the cost, even though the value does not change with the varying price.  Think of all the people that won&#8217;t buy things on sale because they don&#8217;t have the value to them of the full retail priced product.  Books are not immune to this phenomenon.  There are a lot of people out there that do buy on sales, who will try a book for a buck and then go on to paying $4 for more of that author, and I am one of them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BooksForABuck owner: The lowdown on our biz model by Blaine Higgy</title>
		<link>http://www.teleread.org/blog/2008/05/10/bucksforabuck-owner-the-lowdown-on-our-biz-model/#comment-795169</link>
		<dc:creator>Blaine Higgy</dc:creator>
		<pubDate>Sun, 11 May 2008 16:04:28 +0000</pubDate>
		<guid>http://www.teleread.org/blog/2008/05/10/bucksforabuck-owner-the-lowdown-on-our-biz-model/#comment-795169</guid>
		<description>&lt;i&gt;"I love e-books and can understand charging more for the portability, adjustable font, and convenience."&lt;/i&gt;

What?????

A move to ebooks eliminates the need/costs of production/printing/binding/warehousing/shipping/returns/remaindering/etc. and you feel that a few byproducts of reading a book via an electronic device (changing a font size is something a publisher feels should bring him more money???)is justification for charging MORE?</description>
		<content:encoded><![CDATA[<p><i>&#8220;I love e-books and can understand charging more for the portability, adjustable font, and convenience.&#8221;</i></p>
<p>What?????</p>
<p>A move to ebooks eliminates the need/costs of production/printing/binding/warehousing/shipping/returns/remaindering/etc. and you feel that a few byproducts of reading a book via an electronic device (changing a font size is something a publisher feels should bring him more money???)is justification for charging MORE?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on E-book-capable laptops with a catch from Microsoft: 80G drive limit and screens no bigger than 10.2 inches by David Rothman</title>
		<link>http://www.teleread.org/blog/2008/05/11/e-book-capable-laptops-with-a-catch-from-microsoft-80g-drive-limit-and-screens-no-bigger-than-102-inches/#comment-795142</link>
		<dc:creator>David Rothman</dc:creator>
		<pubDate>Sun, 11 May 2008 15:40:57 +0000</pubDate>
		<guid>http://www.teleread.org/blog/2008/05/11/e-book-capable-laptops-with-a-catch-from-microsoft-80g-drive-limit-and-screens-no-bigger-than-102-inches/#comment-795142</guid>
		<description>Given &lt;a href="http://en.wikipedia.org/wiki/Moore%27s_law" rel="nofollow"&gt;Moore's Law&lt;/a&gt;, Microsoft may be worried that even lower-end laptops may be Vista capable in the near future. Microsoft in one sense fears low-priced hardware since that hides the cost of the OS. Lots of factors at work here. Some big Microsoft customers like Dell, moreover, accustomed to more expensive laptops, may actually love the restrictions. Thanks. David</description>
		<content:encoded><![CDATA[<p>Given <a href="http://en.wikipedia.org/wiki/Moore%27s_law" rel="nofollow">Moore&#8217;s Law</a>, Microsoft may be worried that even lower-end laptops may be Vista capable in the near future. Microsoft in one sense fears low-priced hardware since that hides the cost of the OS. Lots of factors at work here. Some big Microsoft customers like Dell, moreover, accustomed to more expensive laptops, may actually love the restrictions. Thanks. David</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on E-book-capable laptops with a catch from Microsoft: 80G drive limit and screens no bigger than 10.2 inches by Jon Noring</title>
		<link>http://www.teleread.org/blog/2008/05/11/e-book-capable-laptops-with-a-catch-from-microsoft-80g-drive-limit-and-screens-no-bigger-than-102-inches/#comment-795087</link>
		<dc:creator>Jon Noring</dc:creator>
		<pubDate>Sun, 11 May 2008 14:32:45 +0000</pubDate>
		<guid>http://www.teleread.org/blog/2008/05/11/e-book-capable-laptops-with-a-catch-from-microsoft-80g-drive-limit-and-screens-no-bigger-than-102-inches/#comment-795087</guid>
		<description>Considering that Microsoft wants to wean everyone away from XP to Vista, I suspect that the primary reason MS is offering XP Home for this purpose is because Vista is quite a resource hog (compared to XP). There are no doubt other reasons, though.</description>
		<content:encoded><![CDATA[<p>Considering that Microsoft wants to wean everyone away from XP to Vista, I suspect that the primary reason MS is offering XP Home for this purpose is because Vista is quite a resource hog (compared to XP). There are no doubt other reasons, though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ficbot&#8217;s hairdo and the font size-changing debate by Greg Schofield</title>
		<link>http://www.teleread.org/blog/2008/05/10/ficbots-hairdo-and-the-font-size-changing-debate/#comment-794607</link>
		<dc:creator>Greg Schofield</dc:creator>
		<pubDate>Sun, 11 May 2008 05:37:06 +0000</pubDate>
		<guid>http://www.teleread.org/blog/2008/05/10/ficbots-hairdo-and-the-font-size-changing-debate/#comment-794607</guid>
		<description>ficbot, we could have the best of both worlds with a little imaginative adjustment.

It is still early days in e-book development. It is not going away anytime soon, the whole evolution of digital technology dictates its eventual triumph.

Meanwhile, we are stuck with the problem of how to develop things and which direction they should follow.

EPUB is not only an open format, it is capable of development in practically any direction, including PDF generation, p-paper printing, aural renditions and various levels of reflow. It does not do this at the moment, but as a format it is more envelope than contents, which is a good thing.

I believe the real question is not either/or, but how to have both forms together in the one publication.</description>
		<content:encoded><![CDATA[<p>ficbot, we could have the best of both worlds with a little imaginative adjustment.</p>
<p>It is still early days in e-book development. It is not going away anytime soon, the whole evolution of digital technology dictates its eventual triumph.</p>
<p>Meanwhile, we are stuck with the problem of how to develop things and which direction they should follow.</p>
<p>EPUB is not only an open format, it is capable of development in practically any direction, including PDF generation, p-paper printing, aural renditions and various levels of reflow. It does not do this at the moment, but as a format it is more envelope than contents, which is a good thing.</p>
<p>I believe the real question is not either/or, but how to have both forms together in the one publication.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ficbot&#8217;s hairdo and the font size-changing debate by ficbot</title>
		<link>http://www.teleread.org/blog/2008/05/10/ficbots-hairdo-and-the-font-size-changing-debate/#comment-794592</link>
		<dc:creator>ficbot</dc:creator>
		<pubDate>Sun, 11 May 2008 05:19:10 +0000</pubDate>
		<guid>http://www.teleread.org/blog/2008/05/10/ficbots-hairdo-and-the-font-size-changing-debate/#comment-794592</guid>
		<description>I guess the problem, then, is that what we have here is two separate markets occupying the same product. On the one side, we have the 'art' product, which its creators allege needs to look a certain way. On the other side, we have the 'technology' product, which its users allege needs to function a certain way. Who wins? It's a tough question. But right now, I am voting for the technology needs taking precedence because an un=pretty book is still read-able, but an un-useable tech product isn't. And you are never EVER going to get mass-market adoption of something like an ebook is a person like my mother can't download one in five minutes and use it right away. I can just picture the tech support phone calls I would have gotten about my ebookwise if I had given it to her. We're talking about people who phone me up with twenty-minute stories about their day where the bottom line is, they want to get pictures off the camera but they don't have the technical vocabulary to explain why it isn't working, so they have to tell you about how they went to pick up their grandson, and then they took her for ice cream, and then they went to the park etc. These types of customers aren't going to spend money on a tech item unless it adds value to their lives (e.g. you can carry 100 books around with you on device the size of a paperback), offers tangible benefits over the alternative (you can resize the fonts or access additional content or look up words in the dictionary while you read or whatever the case may be) and is easy enough to use that they can figure it out without needing 20 pages of FAQ's and a tech support call to their genius kid.

As for 'it keeps jobs for designers' I say (and this may sound harsh) that the designers need to suck it up and adapt with the times. The marketplace grows and evolves and changes. I read a novel set in pre-WW1 Poland, and they had people in the village whose actual job it was to carry water or deliver milk or clear the streets of hay every morning. All of those jobs are now obsolete. Or how about the manufacturers of clothes-wringing machines? They had to either learn to build electric ones or go out of business.

I am not anti-book. There are definitely certaint ypes of books I do prefer to buy in paper and always will. That includes not only graphics-heavy things like cookbooks but also plain-vanilla prose fiction (if the book is a cherished favourite, I do enjoy having a print copy). But for fairly disposable mystery/romance/reads of the day bestseller type stuff, I prefer E because I can read it and get rid of it (or keep it should I wish, and not have to worry about storing so many one-off reads in my smallish apartment). And for that kind of thing, it frustrates me when needless barriers are put up. Do you really think Nora Roberts cares what font size I am using? Wouldn't she rather get her newest book in as many hands as possible while the fire is hot?</description>
		<content:encoded><![CDATA[<p>I guess the problem, then, is that what we have here is two separate markets occupying the same product. On the one side, we have the &#8216;art&#8217; product, which its creators allege needs to look a certain way. On the other side, we have the &#8216;technology&#8217; product, which its users allege needs to function a certain way. Who wins? It&#8217;s a tough question. But right now, I am voting for the technology needs taking precedence because an un=pretty book is still read-able, but an un-useable tech product isn&#8217;t. And you are never EVER going to get mass-market adoption of something like an ebook is a person like my mother can&#8217;t download one in five minutes and use it right away. I can just picture the tech support phone calls I would have gotten about my ebookwise if I had given it to her. We&#8217;re talking about people who phone me up with twenty-minute stories about their day where the bottom line is, they want to get pictures off the camera but they don&#8217;t have the technical vocabulary to explain why it isn&#8217;t working, so they have to tell you about how they went to pick up their grandson, and then they took her for ice cream, and then they went to the park etc. These types of customers aren&#8217;t going to spend money on a tech item unless it adds value to their lives (e.g. you can carry 100 books around with you on device the size of a paperback), offers tangible benefits over the alternative (you can resize the fonts or access additional content or look up words in the dictionary while you read or whatever the case may be) and is easy enough to use that they can figure it out without needing 20 pages of FAQ&#8217;s and a tech support call to their genius kid.</p>
<p>As for &#8216;it keeps jobs for designers&#8217; I say (and this may sound harsh) that the designers need to suck it up and adapt with the times. The marketplace grows and evolves and changes. I read a novel set in pre-WW1 Poland, and they had people in the village whose actual job it was to carry water or deliver milk or clear the streets of hay every morning. All of those jobs are now obsolete. Or how about the manufacturers of clothes-wringing machines? They had to either learn to build electric ones or go out of business.</p>
<p>I am not anti-book. There are definitely certaint ypes of books I do prefer to buy in paper and always will. That includes not only graphics-heavy things like cookbooks but also plain-vanilla prose fiction (if the book is a cherished favourite, I do enjoy having a print copy). But for fairly disposable mystery/romance/reads of the day bestseller type stuff, I prefer E because I can read it and get rid of it (or keep it should I wish, and not have to worry about storing so many one-off reads in my smallish apartment). And for that kind of thing, it frustrates me when needless barriers are put up. Do you really think Nora Roberts cares what font size I am using? Wouldn&#8217;t she rather get her newest book in as many hands as possible while the fire is hot?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ficbot&#8217;s hairdo and the font size-changing debate by Greg Schofield</title>
		<link>http://www.teleread.org/blog/2008/05/10/ficbots-hairdo-and-the-font-size-changing-debate/#comment-794590</link>
		<dc:creator>Greg Schofield</dc:creator>
		<pubDate>Sun, 11 May 2008 05:14:41 +0000</pubDate>
		<guid>http://www.teleread.org/blog/2008/05/10/ficbots-hairdo-and-the-font-size-changing-debate/#comment-794590</guid>
		<description>ficbot, the problem is not novels, but works of science and other complex prose. Novels are just narratives and present no real problem, do with them whatever you like it presents no real problem.

Take a history book where indexing, footnotes, illustrations, diagrams, glossaries etc., plus typographical tables in the form of genealogies and coherent typography is critically important and not amendable to ad hoc changes made haphazardly.

Consider Beowulf in Anglo-Saxon, with a glossary and two or three different translations that may be read concurrently, or Chaucer with references etc.,. 

Restrict e-books to novels and light fiction only and it is unnecessarily doomed to trivial entertainment (eg an annotated Jane Austin, is not easily amendable to any form of user preference, if the annotation is to be useful).

PS I am not making any argument for PDF, but rather a fuller and more versatile form of CSS within the EPUB format.

Jon Jermey, unfortunately with more complex publications layout can be an essential part of its readability. Narratives are the simplest form to typeset, unless used for study they are simply read from beginning to end and in a sense every part has the same and equal value. Not so with other non-fiction works (and I am not talking about decorative graphic eye-candy).</description>
		<content:encoded><![CDATA[<p>ficbot, the problem is not novels, but works of science and other complex prose. Novels are just narratives and present no real problem, do with them whatever you like it presents no real problem.</p>
<p>Take a history book where indexing, footnotes, illustrations, diagrams, glossaries etc., plus typographical tables in the form of genealogies and coherent typography is critically important and not amendable to ad hoc changes made haphazardly.</p>
<p>Consider Beowulf in Anglo-Saxon, with a glossary and two or three different translations that may be read concurrently, or Chaucer with references etc.,. </p>
<p>Restrict e-books to novels and light fiction only and it is unnecessarily doomed to trivial entertainment (eg an annotated Jane Austin, is not easily amendable to any form of user preference, if the annotation is to be useful).</p>
<p>PS I am not making any argument for PDF, but rather a fuller and more versatile form of CSS within the EPUB format.</p>
<p>Jon Jermey, unfortunately with more complex publications layout can be an essential part of its readability. Narratives are the simplest form to typeset, unless used for study they are simply read from beginning to end and in a sense every part has the same and equal value. Not so with other non-fiction works (and I am not talking about decorative graphic eye-candy).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ficbot&#8217;s hairdo and the font size-changing debate by gnawingonfoot</title>
		<link>http://www.teleread.org/blog/2008/05/10/ficbots-hairdo-and-the-font-size-changing-debate/#comment-794535</link>
		<dc:creator>gnawingonfoot</dc:creator>
		<pubDate>Sun, 11 May 2008 04:27:44 +0000</pubDate>
		<guid>http://www.teleread.org/blog/2008/05/10/ficbots-hairdo-and-the-font-size-changing-debate/#comment-794535</guid>
		<description>ficbot- I'm far from anywhere related to anything publishing, but I can make a killer green smoothie.  I use a cup of strawberry kefir, two bananas, two handfuls of organic mixed baby greens (some of which are purple), and a cup of water.  After pureeing it, the smoothie looks like baby vomit in both color and consistency, but it tastes great.  I tried to force it on some of my friends, but they rejected it outright because of how it looks.  Even after my guaranteeing that it isn't as gross as it looks, they wouldn't stop pussyfooting around and just drink it.

I later learned that using baby spinach instead of mixed baby greens (with the purple) will give the smoothie a much happier vibrant green color.  Having swapped the ingredients, I find people are much more willing to try it and admit liking it and no longer have the tastes-as-healthy-as-it-looks fear.  

So for my understanding of the argument, the publishers feel they have to make it look pretty because the (majority of potential) customers will otherwise be hesitant to try something new.  It's certainly not true, but there's a mindset that production values reflect the quality of the product.  I'm sure I could dig up some sociology studies that show how people's presumptions about and perceptions of a product's quality are affected by presentation, but I'm too lazy right now, and I think (hope) that the point is kinda clear.</description>
		<content:encoded><![CDATA[<p>ficbot- I&#8217;m far from anywhere related to anything publishing, but I can make a killer green smoothie.  I use a cup of strawberry kefir, two bananas, two handfuls of organic mixed baby greens (some of which are purple), and a cup of water.  After pureeing it, the smoothie looks like baby vomit in both color and consistency, but it tastes great.  I tried to force it on some of my friends, but they rejected it outright because of how it looks.  Even after my guaranteeing that it isn&#8217;t as gross as it looks, they wouldn&#8217;t stop pussyfooting around and just drink it.</p>
<p>I later learned that using baby spinach instead of mixed baby greens (with the purple) will give the smoothie a much happier vibrant green color.  Having swapped the ingredients, I find people are much more willing to try it and admit liking it and no longer have the tastes-as-healthy-as-it-looks fear.  </p>
<p>So for my understanding of the argument, the publishers feel they have to make it look pretty because the (majority of potential) customers will otherwise be hesitant to try something new.  It&#8217;s certainly not true, but there&#8217;s a mindset that production values reflect the quality of the product.  I&#8217;m sure I could dig up some sociology studies that show how people&#8217;s presumptions about and perceptions of a product&#8217;s quality are affected by presentation, but I&#8217;m too lazy right now, and I think (hope) that the point is kinda clear.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ficbot&#8217;s hairdo and the font size-changing debate by Jon Jermey</title>
		<link>http://www.teleread.org/blog/2008/05/10/ficbots-hairdo-and-the-font-size-changing-debate/#comment-794518</link>
		<dc:creator>Jon Jermey</dc:creator>
		<pubDate>Sun, 11 May 2008 04:05:43 +0000</pubDate>
		<guid>http://www.teleread.org/blog/2008/05/10/ficbots-hairdo-and-the-font-size-changing-debate/#comment-794518</guid>
		<description>Unfortunately it's very hard for people to accept that they have spent a good part of their working lives fixated on something that customers regard as of little or no importance. Typesetters and designers spend so much time and effort obsessing about layout and typography that they get very upset when it's demonstrated that the content is what people are interested in. And they have a (reasonable) suspicion that if their employers realise that too, they'll be out of a job. Hence some of the frantic attempts to defend PDF: it provides jobs for designers.</description>
		<content:encoded><![CDATA[<p>Unfortunately it&#8217;s very hard for people to accept that they have spent a good part of their working lives fixated on something that customers regard as of little or no importance. Typesetters and designers spend so much time and effort obsessing about layout and typography that they get very upset when it&#8217;s demonstrated that the content is what people are interested in. And they have a (reasonable) suspicion that if their employers realise that too, they&#8217;ll be out of a job. Hence some of the frantic attempts to defend PDF: it provides jobs for designers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ficbot&#8217;s hairdo and the font size-changing debate by ficbot</title>
		<link>http://www.teleread.org/blog/2008/05/10/ficbots-hairdo-and-the-font-size-changing-debate/#comment-794507</link>
		<dc:creator>ficbot</dc:creator>
		<pubDate>Sun, 11 May 2008 03:51:37 +0000</pubDate>
		<guid>http://www.teleread.org/blog/2008/05/10/ficbots-hairdo-and-the-font-size-changing-debate/#comment-794507</guid>
		<description>"needs to be balanced against the publisher’s need to present the publication typographically coherent and aesthetically pleasing."

See, this is where I am not following the whole "Yay, PDF" argument. I don't understand this 'need' you allege the publishers have. If I am sitting at the hairdresser without my glasses and I can't make the font go bigger, it is not aesthetically pleasing. If I am not able to reflow the text to fit the screen of my reader, it is not typograpically coherent. Why do you say the publisher has this 'need' and what benefit do they derive from it when it so obviously can't be a factor in a digital marketplace? I am just baffled by this whole argument, and I really don't see why JK Rowling or Stephen King or whomever should care if I want my Harry Potter or The Shining in 14 pt or 10 pt---or, sometimes in 14 pt AND sometimes in 10. Unless the book in question is some sort of illustrated art edition where they want us to see the pictures, who cares? Someone explain this to me. This whole 'need' you say the publishers have makes no logical sense to me at all.</description>
		<content:encoded><![CDATA[<p>&#8220;needs to be balanced against the publisher’s need to present the publication typographically coherent and aesthetically pleasing.&#8221;</p>
<p>See, this is where I am not following the whole &#8220;Yay, PDF&#8221; argument. I don&#8217;t understand this &#8216;need&#8217; you allege the publishers have. If I am sitting at the hairdresser without my glasses and I can&#8217;t make the font go bigger, it is not aesthetically pleasing. If I am not able to reflow the text to fit the screen of my reader, it is not typograpically coherent. Why do you say the publisher has this &#8216;need&#8217; and what benefit do they derive from it when it so obviously can&#8217;t be a factor in a digital marketplace? I am just baffled by this whole argument, and I really don&#8217;t see why JK Rowling or Stephen King or whomever should care if I want my Harry Potter or The Shining in 14 pt or 10 pt&#8212;or, sometimes in 14 pt AND sometimes in 10. Unless the book in question is some sort of illustrated art edition where they want us to see the pictures, who cares? Someone explain this to me. This whole &#8216;need&#8217; you say the publishers have makes no logical sense to me at all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ficbot&#8217;s hairdo and the font size-changing debate by Greg Schofield</title>
		<link>http://www.teleread.org/blog/2008/05/10/ficbots-hairdo-and-the-font-size-changing-debate/#comment-794472</link>
		<dc:creator>Greg Schofield</dc:creator>
		<pubDate>Sun, 11 May 2008 03:21:27 +0000</pubDate>
		<guid>http://www.teleread.org/blog/2008/05/10/ficbots-hairdo-and-the-font-size-changing-debate/#comment-794472</guid>
		<description>Mark Coker says:
“Readers should be allowed to buy a book and customize all aspects of their reading experience such as font size, font style, font color, background color, reading device, reading media, whatever. This is the aspect of digital publishing that gets me most excited - to achieve the holy grail of your book, your way.”

As a feature the ability to make a User’s stylesheet is very much welcome, however it needs to be balanced against the publisher’s need to present the publication typographically coherent and aesthetically pleasing. Moreover, that means the publisher  needs a better stylesheet system than those currently available (CSS can suffice, but in a more modular and dynamic way).

The problem with leaving too much to the reader software and the reader, is that some publication may well need to use flexible XML rather than HTML and the tag sets may be extensive and unpredictable. However if we think this one out clearly we could well have the best of both worlds.

Certain elements, no matter what they are called, are common: Fonts families, headers, footers, footnotes, page, margins, paragraphs, macro divisions (chapters, sections, parts).  These need only declare their element sets, to deliver to the user a subset that can be predictable changed, so long as the stylesheets supplied by the publisher are well designed to begin with.

We have a fair way yet to go before reflowing e-books take on a definite and long-lived form.</description>
		<content:encoded><![CDATA[<p>Mark Coker says:<br />
“Readers should be allowed to buy a book and customize all aspects of their reading experience such as font size, font style, font color, background color, reading device, reading media, whatever. This is the aspect of digital publishing that gets me most excited - to achieve the holy grail of your book, your way.”</p>
<p>As a feature the ability to make a User’s stylesheet is very much welcome, however it needs to be balanced against the publisher’s need to present the publication typographically coherent and aesthetically pleasing. Moreover, that means the publisher  needs a better stylesheet system than those currently available (CSS can suffice, but in a more modular and dynamic way).</p>
<p>The problem with leaving too much to the reader software and the reader, is that some publication may well need to use flexible XML rather than HTML and the tag sets may be extensive and unpredictable. However if we think this one out clearly we could well have the best of both worlds.</p>
<p>Certain elements, no matter what they are called, are common: Fonts families, headers, footers, footnotes, page, margins, paragraphs, macro divisions (chapters, sections, parts).  These need only declare their element sets, to deliver to the user a subset that can be predictable changed, so long as the stylesheets supplied by the publisher are well designed to begin with.</p>
<p>We have a fair way yet to go before reflowing e-books take on a definite and long-lived form.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why reflowable formats like ePub are overvalued by Greg Schofield</title>
		<link>http://www.teleread.org/blog/2008/05/10/why-reflowable-formats-like-epub-are-overvalued/#comment-794459</link>
		<dc:creator>Greg Schofield</dc:creator>
		<pubDate>Sun, 11 May 2008 03:04:42 +0000</pubDate>
		<guid>http://www.teleread.org/blog/2008/05/10/why-reflowable-formats-like-epub-are-overvalued/#comment-794459</guid>
		<description>To flow or not to flow is hardly the question. Perfecting stylesheets, and their display, is the point.

Not that many years ago, book publishing, for reasons of paper-costs, included photographs as a separate plates’ section inserted where text-page imposition dictated. In-text illustrations had to be included only as line-illustrations and, for the most part, placed somewhere before or after the text reference to them.

The point being that readers adapted to the new, but technically convoluted, form of publishing which is still practised. It was not replaced, in other words, by glossy-page fully illustrated books. It remains a workable solution if not a perfect one.

To make an analogy to this example, the graphic e-book is best served (though not absolutely) by PDF or something similar – a given page size and fixed text.

On the other hand, the other type of e-book is text, rather than graphically based – that will nor change nor will it be shifted by any other form of communications. Writing, not graphics, remains the supreme means of conveying concepts with accuracy and unambiguously to a reader. Everything is secondary to that, no publishable graphic can replace that basic attribute of the written word and its supremacy in terms of human knowledge.

The question is not whether or not this form of text-centric publishing should be reflowable, countless editions of the same works in p-books have been reflowed into a variety of page and text sizes, much to the endless frustration of those trying to locate page references to different editions.

The question is how should it be reflowed, especially when parts of the publication (tables, formulas, text graphics, diagrams etc.,.) are typographically coherent and should be displayed differently according to how the text in the main is displayed. Here the problem with stylesheets as they have now developed (CSS) has distinct limits and needs to approached differently to how it is now implemented.

Ideally for reading and for justifying text etc., text should aim to be about 72 letters per line. However, display and text size will rarely meet this ideal. At one stage or another of “magnification” justified text needs to revert to left aligned, various typographical elements need to be treated differently, pictures may have to be separated and shown in landscape despite the device being read in portrait. In other words, aside from the more “artistic” concerns, there are mundane typographical concerns that no reader software should be allowed to solve for itself without specific instruction.

That is the problem; creating an interactive relationship between the device, users preference and stylesheets. It presents itself not just as an interface problem (which could be easily solved – ie micro-display + small text, as against micro-display + extra-large text), but also as a reference problem to parts within element tags. I would bring one other useful element into the picture – SVG not just as graphic element, but also as “template”, especially for complex tables, where text can via the particular stylesheet be flowed in some sensible way (ie alternative SVGs for different sizes being employed).

My point here is the debate between fixed and flowing text models is misplaced – graphic publications have to assume some fixed proportion and relative size, that can be compromised by smart readers, but will never be completely satisfactory so long as different needs and devices, now or in the future (with the possible exception of fold-out or other another expandable display technology – it may be some time before an A2 display can be folded up into A6).

Text publications (with or without illustrations) is another question, but it needs a lot of development to be be truly suitable for reading, as against monitor browsing for which it was initially designed.

I repeat, that nothing now or promised by the most vivid imagination is about to supplant the written word for concise, precise and unambiguous publication of knowledge and serious thought. We should not get the graphic magazine mixed up with  the serious tome, they are two very different things.</description>
		<content:encoded><![CDATA[<p>To flow or not to flow is hardly the question. Perfecting stylesheets, and their display, is the point.</p>
<p>Not that many years ago, book publishing, for reasons of paper-costs, included photographs as a separate plates’ section inserted where text-page imposition dictated. In-text illustrations had to be included only as line-illustrations and, for the most part, placed somewhere before or after the text reference to them.</p>
<p>The point being that readers adapted to the new, but technically convoluted, form of publishing which is still practised. It was not replaced, in other words, by glossy-page fully illustrated books. It remains a workable solution if not a perfect one.</p>
<p>To make an analogy to this example, the graphic e-book is best served (though not absolutely) by PDF or something similar – a given page size and fixed text.</p>
<p>On the other hand, the other type of e-book is text, rather than graphically based – that will nor change nor will it be shifted by any other form of communications. Writing, not graphics, remains the supreme means of conveying concepts with accuracy and unambiguously to a reader. Everything is secondary to that, no publishable graphic can replace that basic attribute of the written word and its supremacy in terms of human knowledge.</p>
<p>The question is not whether or not this form of text-centric publishing should be reflowable, countless editions of the same works in p-books have been reflowed into a variety of page and text sizes, much to the endless frustration of those trying to locate page references to different editions.</p>
<p>The question is how should it be reflowed, especially when parts of the publication (tables, formulas, text graphics, diagrams etc.,.) are typographically coherent and should be displayed differently according to how the text in the main is displayed. Here the problem with stylesheets as they have now developed (CSS) has distinct limits and needs to approached differently to how it is now implemented.</p>
<p>Ideally for reading and for justifying text etc., text should aim to be about 72 letters per line. However, display and text size will rarely meet this ideal. At one stage or another of “magnification” justified text needs to revert to left aligned, various typographical elements need to be treated differently, pictures may have to be separated and shown in landscape despite the device being read in portrait. In other words, aside from the more “artistic” concerns, there are mundane typographical concerns that no reader software should be allowed to solve for itself without specific instruction.</p>
<p>That is the problem; creating an interactive relationship between the device, users preference and stylesheets. It presents itself not just as an interface problem (which could be easily solved – ie micro-display + small text, as against micro-display + extra-large text), but also as a reference problem to parts within element tags. I would bring one other useful element into the picture – SVG not just as graphic element, but also as “template”, especially for complex tables, where text can via the particular stylesheet be flowed in some sensible way (ie alternative SVGs for different sizes being employed).</p>
<p>My point here is the debate between fixed and flowing text models is misplaced – graphic publications have to assume some fixed proportion and relative size, that can be compromised by smart readers, but will never be completely satisfactory so long as different needs and devices, now or in the future (with the possible exception of fold-out or other another expandable display technology – it may be some time before an A2 display can be folded up into A6).</p>
<p>Text publications (with or without illustrations) is another question, but it needs a lot of development to be be truly suitable for reading, as against monitor browsing for which it was initially designed.</p>
<p>I repeat, that nothing now or promised by the most vivid imagination is about to supplant the written word for concise, precise and unambiguous publication of knowledge and serious thought. We should not get the graphic magazine mixed up with  the serious tome, they are two very different things.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BookGlutton co-founder: We&#8217;ve released an easy ePub conversion tool by Rob Preece</title>
		<link>http://www.teleread.org/blog/2008/05/08/bookglutton-releases-an-easy-epub-conversion-tool/#comment-794453</link>
		<dc:creator>Rob Preece</dc:creator>
		<pubDate>Sun, 11 May 2008 03:01:48 +0000</pubDate>
		<guid>http://www.teleread.org/blog/2008/05/08/bookglutton-releases-an-easy-epub-conversion-tool/#comment-794453</guid>
		<description>As promised, I've done a bit of experimenting with this program. It appears to work very well with a few formatting quibbles (possibly related to deprecated HTML tags). I was able to convert an entire novel in a matter of seconds, and read that novel on the FBReader with no problem.

With a few tweaks to support graphics and minor formating fixes, this appears to be a usable system--and the price is right.

I'm going to do a bit more experimenting before I add ePub to my assortment of supported formats, but as I offer HTML already, any user wanting to read in ePub could use this as is.

Rob Preece
Publisher, www.BooksForABuck.com</description>
		<content:encoded><![CDATA[<p>As promised, I&#8217;ve done a bit of experimenting with this program. It appears to work very well with a few formatting quibbles (possibly related to deprecated HTML tags). I was able to convert an entire novel in a matter of seconds, and read that novel on the FBReader with no problem.</p>
<p>With a few tweaks to support graphics and minor formating fixes, this appears to be a usable system&#8211;and the price is right.</p>
<p>I&#8217;m going to do a bit more experimenting before I add ePub to my assortment of supported formats, but as I offer HTML already, any user wanting to read in ePub could use this as is.</p>
<p>Rob Preece<br />
Publisher, <a href="http://www.BooksForABuck.com" rel="nofollow">http://www.BooksForABuck.com</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
