<?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: Kindle Page Layout and Typography</title>
	<atom:link href="http://www.teleread.org/2009/05/05/kindle-page-layout-and-typography/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.teleread.org/2009/05/05/kindle-page-layout-and-typography/</link>
	<description>News &#38; views on e-books, libraries, publishing and related topics</description>
	<lastBuildDate>Mon, 22 Mar 2010 13:23:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Robert Nagle</title>
		<link>http://www.teleread.org/2009/05/05/kindle-page-layout-and-typography/comment-page-1/#comment-1052275</link>
		<dc:creator>Robert Nagle</dc:creator>
		<pubDate>Wed, 06 May 2009 16:56:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/?p=21445#comment-1052275</guid>
		<description>See the  &lt;a href=&quot;http://webtypography.net/toc/&quot; rel=&quot;nofollow&quot;&gt;web version of Elements of Typographic Style  &lt;/a&gt;. Tries to implement Bringhurst&#039;s principles in CSS. Not sure which of these css rules apply to the css subset allowed by epub. For example, &lt;a href=&quot;http://webtypography.net/Rhythm_and_Proportion/Etiquette_of_Hyphenation_and_Pagination/2.4.8/&quot; rel=&quot;nofollow&quot;&gt;pagination and page breaks &lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>See the  <a href="http://webtypography.net/toc/" rel="nofollow">web version of Elements of Typographic Style  </a>. Tries to implement Bringhurst&#8217;s principles in CSS. Not sure which of these css rules apply to the css subset allowed by epub. For example, <a href="http://webtypography.net/Rhythm_and_Proportion/Etiquette_of_Hyphenation_and_Pagination/2.4.8/" rel="nofollow">pagination and page breaks </a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hadrien Gardeur</title>
		<link>http://www.teleread.org/2009/05/05/kindle-page-layout-and-typography/comment-page-1/#comment-1051960</link>
		<dc:creator>Hadrien Gardeur</dc:creator>
		<pubDate>Wed, 06 May 2009 10:01:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/?p=21445#comment-1051960</guid>
		<description>Christo: Well for a start, programmers could read &lt;i&gt;The Elements of Typographic Style&lt;/i&gt; from Robert Bringhurst.</description>
		<content:encoded><![CDATA[<p>Christo: Well for a start, programmers could read <i>The Elements of Typographic Style</i> from Robert Bringhurst.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christo</title>
		<link>http://www.teleread.org/2009/05/05/kindle-page-layout-and-typography/comment-page-1/#comment-1051892</link>
		<dc:creator>Christo</dc:creator>
		<pubDate>Wed, 06 May 2009 07:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/?p=21445#comment-1051892</guid>
		<description>Laying out a page for a book is not solely a technical issue, but is usually addressed by techies, so few book readers have the smarts to do it on the fly, probably because not much attention has been paid to the finer details. On the surface it seems simple, but there are almost infinite layers of complexity if you dare to delve deeper into kerning, line spacing, proper hyphenation, ligatures etc. It isn&#039;t easy to distill several centuries of typographical best practice into rules that a programmer can apply.

Hopefully it will get better over time!</description>
		<content:encoded><![CDATA[<p>Laying out a page for a book is not solely a technical issue, but is usually addressed by techies, so few book readers have the smarts to do it on the fly, probably because not much attention has been paid to the finer details. On the surface it seems simple, but there are almost infinite layers of complexity if you dare to delve deeper into kerning, line spacing, proper hyphenation, ligatures etc. It isn&#8217;t easy to distill several centuries of typographical best practice into rules that a programmer can apply.</p>
<p>Hopefully it will get better over time!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hadrien Gardeur</title>
		<link>http://www.teleread.org/2009/05/05/kindle-page-layout-and-typography/comment-page-1/#comment-1051724</link>
		<dc:creator>Hadrien Gardeur</dc:creator>
		<pubDate>Wed, 06 May 2009 00:10:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/?p=21445#comment-1051724</guid>
		<description>Hyphenation is another very important issue from my point of view. I hate justified text without proper hyphenation.</description>
		<content:encoded><![CDATA[<p>Hyphenation is another very important issue from my point of view. I hate justified text without proper hyphenation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Logan Kennelly</title>
		<link>http://www.teleread.org/2009/05/05/kindle-page-layout-and-typography/comment-page-1/#comment-1051702</link>
		<dc:creator>Logan Kennelly</dc:creator>
		<pubDate>Tue, 05 May 2009 23:38:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/?p=21445#comment-1051702</guid>
		<description>Based on the Sony Reader ePub rendering, I&#039;d say Adobe Digital Editions handles Widows and Orphans properly (although I haven&#039;t attempted to override the default values with CSS). One item that may be worth noting: when not using a margin around the page, the gap generated at the bottom when avoiding Orphans and Widows looks pretty bad.

And, as Dhamu indicates, the &quot;bolding&quot; of text wouldn&#039;t be an issue if we could easily install our own fonts to the device and/or override the document font.

Arghh, people are going to think I&#039;m an Adobe shill...</description>
		<content:encoded><![CDATA[<p>Based on the Sony Reader ePub rendering, I&#8217;d say Adobe Digital Editions handles Widows and Orphans properly (although I haven&#8217;t attempted to override the default values with CSS). One item that may be worth noting: when not using a margin around the page, the gap generated at the bottom when avoiding Orphans and Widows looks pretty bad.</p>
<p>And, as Dhamu indicates, the &#8220;bolding&#8221; of text wouldn&#8217;t be an issue if we could easily install our own fonts to the device and/or override the document font.</p>
<p>Arghh, people are going to think I&#8217;m an Adobe shill&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dhamu</title>
		<link>http://www.teleread.org/2009/05/05/kindle-page-layout-and-typography/comment-page-1/#comment-1051665</link>
		<dc:creator>Dhamu</dc:creator>
		<pubDate>Tue, 05 May 2009 22:45:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/?p=21445#comment-1051665</guid>
		<description>There are semi-bold fonts that are heavier than normal fonts but can still show a difference between bold and not-bold.  Widows and orphans shouldn&#039;t really be too hard to handle.  The eleven-year-old tech in my eBookwise handles them fine with a CSS line.</description>
		<content:encoded><![CDATA[<p>There are semi-bold fonts that are heavier than normal fonts but can still show a difference between bold and not-bold.  Widows and orphans shouldn&#8217;t really be too hard to handle.  The eleven-year-old tech in my eBookwise handles them fine with a CSS line.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
