<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://typophile.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Typophile - Seeking Resources for Page-Spread Design - Comments</title>
 <link>http://typophile.com/node/40359</link>
 <description>Comments for &quot;Seeking Resources for Page-Spread Design&quot;</description>
 <language>en</language>
<item>
 <title>With all the kind words</title>
 <link>http://typophile.com/node/40359#comment-253287</link>
 <description>&lt;p&gt;With all the kind words about the &lt;cite&gt;Glossary of Typesetting Terms&lt;/cite&gt; I got out my copy &amp;amp; reread a little.&lt;/p&gt;
&lt;p&gt;I really can’t recommend anyone spending hard-earned dollars on this, at least, if their view is to find something as instructive as the books by Bringhurst, Hendel, etc.&lt;/p&gt;
&lt;p&gt;The &lt;cite&gt;Glossary&lt;/cite&gt; came out of an AAUP panel in 1990 about why typesetting seemed to have fallen off in quality in “recent” times. As you may remember, 1990 was just at the beginning of the PostScript era, and most all composition was still done with photocomp machines, some of them “professional” (Linotron 202), some of them less so (the lesser offerings from Compugraphic, A/M, etc.). Part of the problem was the fonts, but the largest problem was the use of the equipment. &lt;/p&gt;
&lt;p&gt;So, there were multiple answers to why typesetting quality was diminishing: (1) good shops still turned out excellent comp, but (2) the cost of getting into setting type was much lower with photocomp, so anybody with $30,000 could get into the business, and (3) the unions were at an end, which mean the apprenticeship programs too were gone.&lt;/p&gt;
&lt;p&gt;There was a forth factor. Just as apprenticeship had fallen off for compositors, apprenticeship had also fallen off for designers, and to some extent, editors. Some newer designers had trouble expressing what they wanted, and a number of editors had little understanding of the compromises involved in setting type. This lead to an increase of proscriptive rules (don’t do this). As the number of things one couldn’t do increased, the choices a comp had in resolving an awkward situation diminished.&lt;/p&gt;
&lt;p&gt;In any case, the &lt;cite&gt;Glossary&lt;/cite&gt; was aimed only at the fourth problem. But the world has changed again. By now (2008), many of the technical terms and procedures of the photocomp era seem out of date. The fonts are different (PostScript, OpenType), the layout programs are different (PageMaker, Quark, InDesign, etc.). In many ways, what is considered good design has changed as well.&lt;/p&gt;
&lt;p&gt;The &lt;cite&gt;Glossary&lt;/cite&gt; covered a period of history and the problems of that time. I do think there is still something one can learn from it, but things have changed enough so anyone desiring a quick understanding of what constitutes “good design and composition” would be better served by works either more basic, or more specific to present times.&lt;/p&gt;
&lt;p&gt;FWIW&lt;/p&gt;
&lt;p&gt;Charles Ellertson&lt;/p&gt;
</description>
 <pubDate>Tue, 22 Jan 2008 06:58:18 -0800</pubDate>
 <dc:creator>charles_e</dc:creator>
 <guid isPermaLink="false">comment 253287 at http://typophile.com</guid>
</item>
<item>
 <title>I spoke to soon. It’s a</title>
 <link>http://typophile.com/node/40359#comment-253189</link>
 <description>&lt;p&gt;I spoke to soon. It&amp;#8217;s a &amp;#8220;book preview&amp;#8221;, which means some pages are omitted. But you can get a good idea of the contents. Thanks for introducing me to this book, Will and Kent. It&amp;#8217;s never seen on the lists of typographer&amp;#8217;s must-haves.&lt;/p&gt;
</description>
 <pubDate>Mon, 21 Jan 2008 15:12:12 -0800</pubDate>
 <dc:creator>Stephen Coles</dc:creator>
 <guid isPermaLink="false">comment 253189 at http://typophile.com</guid>
</item>
<item>
 <title>Just a note to inform you</title>
 <link>http://typophile.com/node/40359#comment-253188</link>
 <description>&lt;p&gt;Just a note to inform you all that &amp;#8220;Glossary of Typesetting Terms&amp;#8221; is now available for online reading at &lt;a href=&quot;http://books.google.com/books?id=ewSglB2f7qYC&quot;&gt;Google&lt;/a&gt;.&lt;/p&gt;
</description>
 <pubDate>Mon, 21 Jan 2008 15:10:13 -0800</pubDate>
 <dc:creator>Stephen Coles</dc:creator>
 <guid isPermaLink="false">comment 253188 at http://typophile.com</guid>
</item>
<item>
 <title>&amp;emsp;When I saw a thread</title>
 <link>http://typophile.com/node/40359#comment-253114</link>
 <description>&lt;p&gt;&amp;emsp;When I saw a thread entitled &lt;a class=&quot;freelinking-external&quot; href=&quot;http://typophile.com/node/18382&quot;&gt;8½&amp;times;11&amp;Prime;&lt;/a&gt;, I thought I&amp;#8217;d add a link to this thread&amp;mdash;but it&amp;#8217;s two years old, so I&amp;#8217;m linking the other way &amp;#8217;round.&lt;br /&gt;
—Joel&lt;/p&gt;
</description>
 <pubDate>Mon, 21 Jan 2008 09:44:18 -0800</pubDate>
 <dc:creator>JCSalomon</dc:creator>
 <guid isPermaLink="false">comment 253114 at http://typophile.com</guid>
</item>
<item>
 <title>I want to second Will’s</title>
 <link>http://typophile.com/node/40359#comment-251331</link>
 <description>&lt;p&gt;I want to second Will&amp;#8217;s enthusiastic review of the &lt;cite&gt;Glossary of Typesetting Terms&lt;/cite&gt;. The prosaic title may belie its value to a designer. (&amp;#8220;A &lt;em&gt;glossary&lt;/em&gt;? &amp;#8212; What, are you kidding me?!&amp;#8221;) Really, it is surprisingly readable. I, too, went pretty much straight through &amp;#8212; albeit not in a single sitting, not in a hammock, and not with summer refreshment. I continue to refer to it now and again, and it&amp;#8217;s a good resource to have, right alongside Bringhurst.&lt;/p&gt;
&lt;p&gt;When learning a craft, I think it&amp;#8217;s important to try to get inside the &amp;#8220;rules&amp;#8221; and understand the principles behind them. Charles is right to caution against using them as a crutch. One needs to educate one&amp;#8217;s eyes and one&amp;#8217;s mind. Part of this may come initially from following such guidelines, but only by then looking, contemplating, comparing, and understanding. &lt;/p&gt;
&lt;p&gt;But over time, rules should recede, and experience will take over.&lt;/p&gt;
&lt;p&gt;&amp;#8212; K.&lt;/p&gt;
</description>
 <pubDate>Sat, 12 Jan 2008 06:56:05 -0800</pubDate>
 <dc:creator>kentlew</dc:creator>
 <guid isPermaLink="false">comment 251331 at http://typophile.com</guid>
</item>
<item>
 <title>Will,
I wasn’t being</title>
 <link>http://typophile.com/node/40359#comment-251207</link>
 <description>&lt;p&gt;Will,&lt;/p&gt;
&lt;p&gt;I wasn&amp;#8217;t being personal &amp;#8212; I&amp;#8217;m well aware you don&amp;#8217;t need crutches. But book design is more akin to set design for the theater, or perhaps as often said, architecture (I&amp;#8217;m less happy with the architecture analogy). I&amp;#8217;m sure there are other possibilities as well. But whatever your favorite analogy, it shouldn&amp;#8217;t be engineering. A volt is a volt, and it shows up as such on a calibrated meter. &lt;/p&gt;
&lt;p&gt;The remark was aimed generally. I am puzzled that so many of the people who frequent Typophile feel Bringhurst&amp;#8217;s book is a kind of bible &amp;#8212; it is, after all, basically mid-20th century British typography &amp;#8212; and yet the same people feel the fonts of the period are dated &amp;amp; should not be used.&lt;/p&gt;
&lt;p&gt;For J. C. Salmon, I believe the point to consider is that, at least historically, the proper element of a book is not a single page, but a spread; two pages. The relationship of the type block to the spread is such that the gutter (between the two pages) should be visually smaller that the outer margins.&lt;/p&gt;
&lt;p&gt;Now first of all, you may not agree that the *open* book is the proper thing to view. Certainly other means of presenting text give a different relationship. But even if you accept that traditional perspective, judging that gutter gets pretty difficult given the various binding techniques today. And remember too that most book design today is for a what is called &amp;#8220;split production.&amp;#8221; That means that, say, 2,500 copies will be printed, and 1,000 will be Smythe-sewn with a hard case, and 1,500 will be bound paperback &amp;#8212; either perfect bound, or notch bound. That means compromise. Do you penalize the more expensive Smythe-sewn copies so the cheap paperbacks have a nice gutter, or do you suffer a tight paperback gutter for a pleasant cloth bound book? Or compromise both just a little?&lt;/p&gt;
</description>
 <pubDate>Fri, 11 Jan 2008 13:21:20 -0800</pubDate>
 <dc:creator>charles_e</dc:creator>
 <guid isPermaLink="false">comment 251207 at http://typophile.com</guid>
</item>
<item>
 <title>I did not speak of</title>
 <link>http://typophile.com/node/40359#comment-251179</link>
 <description>&lt;p&gt;I did not speak of &amp;#8220;rules.&amp;#8221; I did speak of what I&amp;#8217;d call &amp;#8220;good practice.&amp;#8221; And I have violated my own ideas of good practice quite often. Most of the time with intention. Sometimes by mistake that went un-caught. I have done all the things Charles notes that Richard did.&lt;/p&gt;
&lt;p&gt;One has to start out somewhere, especially when someone new to this sort of work asks opinions. I see that Mr Salomon is an engineer, and he has taken an interest in typography, asking advice from those of us who read this forum. So I suggested to him some good practices. I do not know how much leeway is allowed from good practice among engineers, people who deal with very precise specifications. I bet really good engineers know where they can introduce variations safely.&lt;/p&gt;
&lt;p&gt;I do not use crutches, and I trust my many years of experience. I also trust my skills and my understanding of the page to tell me when I may deviate from good practice. I also encourage myself to try new things, regardless of how they may vary from my training.&lt;/p&gt;
&lt;p&gt;I do regard Richard as an extraordinarily good book designer, and I&amp;#8217;m sorry I did not have many occasions to talk about the craft with him. Saying that, I will suggest to anyone who wants to know how to put pages together that they read a very good book on which Richard &amp;amp; Charles collaborated with 4 other skilled typographers.&lt;/p&gt;
&lt;p&gt;That book is &amp;#8220;Glossary of Typesetting Terms&amp;#8221;, published in 1994 by U of Chicago Press. This is an essential text. When my copy arrived on a summer day, I took it to the hammock for a quick first look. What happened was that I did not get out of the hammock except once, to pour a good gin-and-tonic. I read the whole damn book through in one sitting, as thrilled as if it were a fine novel. And wrote comments all over the pages. For several years Chicago was selling it in their annual sale for 6 bucks a copy. I would buy ten or twelve copies and on the last day of typography class I&amp;#8217;d give them to the students. This is as important a book as Bringhurst (which I have students work with during the semester).&lt;/p&gt;
&lt;p&gt;cheers.&lt;/p&gt;
&lt;p&gt;powers&lt;/p&gt;
</description>
 <pubDate>Fri, 11 Jan 2008 11:29:18 -0800</pubDate>
 <dc:creator>will powers</dc:creator>
 <guid isPermaLink="false">comment 251179 at http://typophile.com</guid>
</item>
<item>
 <title>I find all these *rules*</title>
 <link>http://typophile.com/node/40359#comment-250876</link>
 <description>&lt;p&gt;I find all these *rules* more like *crutches.* I think Will would allow that Richard Eckersley was one of the better book designers of the last half of the twentieth century. Much of Richard&amp;#8217;s attention was the look of the page. A few things he tried, and over time, accepted:&lt;/p&gt;
&lt;p&gt;1. Carding (feathering, vertical justification) was required in setting his books. He usually used about 13.5 points of lead, and around 38 lines (so 37 line spaces) per page. With carding, the variance would be 37 or 39 lines per page &amp;#8212; with 37, leading would be 13.875, with 39, leading would be 3.145. A &amp;#8220;plus&amp;#8221; carded page could not face a &amp;#8220;minus&amp;#8221; carded page.&lt;/p&gt;
&lt;p&gt;2. Avoid the first line of a paragraph ending a page. &amp;#8220;Avoid&amp;#8221; meant just that. If doing so caused a worse problem, go ahead &amp;amp; end the page with a 1st line.&lt;/p&gt;
&lt;p&gt;3. No widows, but if a line ran 75% or more of full measure, and you were in a real bad situation, it was allowed. Of course, in a work having a lot of dialog, a single short line was allowed.&lt;/p&gt;
&lt;p&gt;When Richard was setting a book himself (always PageMaker), he would vary the measure a bit (for the whole page or spread) to see if he got a better page (well, chapter). Most of us use applications programs where this isn&amp;#8217;t practical. But I do remember from the days of the Linotron 202 that output could vary as much as 3 points over a 26-pica measure, day to day. If you were making patch corrections (2nd, 3rd proof) and that happened, you centered that long/short correction over the existing type, and it wasn&amp;#8217;t really noticeable. If the horizontal amplifier go so far off you could notice the different line lengths, you had to reset the correction, using a smaller (larger) specified measure. BTW, the older Linotype VIP was worse than the 202 at holding a constant measure across days.&lt;/p&gt;
&lt;p&gt;Anyway, the point is that from Richrd&amp;#8217;s perspective, the look of the page was paramount, and all his composition rules were keyed to how he wanted the page to look. Others may have a different idea of what constitutes a good page, or even feel that there is something more basic. To say the *rules* require this or that is only to show you don&amp;#8217;t have much experience and/or don&amp;#8217;t trust what your experience has shown you.&lt;/p&gt;
</description>
 <pubDate>Thu, 10 Jan 2008 07:06:17 -0800</pubDate>
 <dc:creator>charles_e</dc:creator>
 <guid isPermaLink="false">comment 250876 at http://typophile.com</guid>
</item>
<item>
 <title>&gt; A single first line of a</title>
 <link>http://typophile.com/node/40359#comment-250626</link>
 <description>&lt;p&gt;&amp;gt; A single first line of a paragraph standing alone at the bottom of a page or column&lt;/p&gt;
&lt;p&gt;The one area where this does not work, and probably why it is bundled in with widows as a no-no, is in technical documentation, or other work where there is a blank line before a paragraph. In this situation a lone (orphaned) line looks odd, rather like an additional footer.&lt;/p&gt;
&lt;p&gt;In bookwork, with no paragraph spacing, the orphan is completely acceptable (until you get an editor who knows a bit less than they think they know).&lt;/p&gt;
</description>
 <pubDate>Wed,  9 Jan 2008 06:25:23 -0800</pubDate>
 <dc:creator>Don McCahill</dc:creator>
 <guid isPermaLink="false">comment 250626 at http://typophile.com</guid>
</item>
<item>
 <title>I have encountered so much</title>
 <link>http://typophile.com/node/40359#comment-250510</link>
 <description>&lt;p&gt;I have encountered so much contention, disagreement, and confusion about the definitions of &lt;em&gt;widow&lt;/em&gt; and &lt;em&gt;orphan&lt;/em&gt; that I now try to avoid using the terms altogether. The important thing, as Will outlined, is to understand the three questionable situations and to establish guidelines for what is and what is not acceptable and under what circumstances.&lt;/p&gt;
&lt;p&gt;Echoing some of what Will covered (with which I mostly concur):&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;A) A single last line separated from its paragraph by either page turn, or across the spread, or a jump to the top of the next column.&lt;/strong&gt; All of these circumstances are almost universally considered &lt;em&gt;persona non grata&lt;/em&gt;. I differ from Will in that I generally won&amp;#8217;t accept any of these even if the last line is nearly full measure. If the last line is truly full measure and will justify as such, then I might conceivably let it pass as a last resort. I will look more leniently on a full line separated across the spread than one across a page turn. In unjustified text, I might let a shorter line pass, but I reserve the right to judge such in context, and I would still try to avoid it.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;B) A short final line in a paragraph.&lt;/strong&gt; There are varying definitions/guidelines regarding what constitutes an unacceptable last line. The one I hear most commonly is &amp;#8220;must have at least &lt;em&gt;x&lt;/em&gt; letters,&amp;#8221; where &lt;em&gt;x&lt;/em&gt; can vary usually from 5 to 7. I don&amp;#8217;t subscribe to such a fixed standard. To me, it is relative to the design. My general rule of thumb is that the last line should be at least twice the indent &amp;#8212; the point being that it should provide enough visual weight to the end of the paragraph that the indent of the next not combine to create a queer isthmus. &lt;/p&gt;
&lt;p&gt;Longer measures or more elegant designs are less tolerant of shorter last lines, in which case my rule might adjust to require a last line to be at least 1/3 the measure. Narrower columns or more prosaic matter, on the other hand, may admit of looser standards.&lt;/p&gt;
&lt;p&gt;A paragraph should never end with the tail of a hyphenated word break, regardless of its length.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;C) A single first line of a paragraph standing alone at the bottom of a page or column.&lt;/strong&gt; I agree that this is acceptable and I will generally let it stand. I do feel that it is not entirely desirable, and if there is an opportunity to avoid it immediately available, I will prefer to eliminate this situation.&lt;/p&gt;
&lt;p&gt;&amp;#8212; K.&lt;/p&gt;
</description>
 <pubDate>Tue,  8 Jan 2008 14:44:41 -0800</pubDate>
 <dc:creator>kentlew</dc:creator>
 <guid isPermaLink="false">comment 250510 at http://typophile.com</guid>
</item>
<item>
 <title>ORPHANS are acceptable.
I</title>
 <link>http://typophile.com/node/40359#comment-250484</link>
 <description>&lt;p&gt;&lt;cite&gt;ORPHANS are acceptable.&lt;/cite&gt;&lt;/p&gt;
&lt;p&gt;I agree. And we don’t call them ‘&lt;a href=&quot;/wiki/orphan&quot; class=&quot;wiki&quot;&gt;orphans&lt;/a&gt;’ anymore, that’s so pathetic. Now they’re &lt;em&gt;‘cliffhangers’ &lt;/em&gt;. Officially pimped!&lt;/p&gt;
</description>
 <pubDate>Tue,  8 Jan 2008 13:13:13 -0800</pubDate>
 <dc:creator>Florian Hardwig</dc:creator>
 <guid isPermaLink="false">comment 250484 at http://typophile.com</guid>
</item>
<item>
 <title>What you DON’T want is to</title>
 <link>http://typophile.com/node/40359#comment-250462</link>
 <description>&lt;p&gt;What you DON&amp;#8217;T want is to have one of those little buggers turn the page and be the only word at the top of a block of text. That is so tacky and ugly. Or even worse, the second half of a hyphenated word. Yuck.&lt;/p&gt;
</description>
 <pubDate>Tue,  8 Jan 2008 11:35:39 -0800</pubDate>
 <dc:creator>DanGayle</dc:creator>
 <guid isPermaLink="false">comment 250462 at http://typophile.com</guid>
</item>
<item>
 <title>Will have you written a</title>
 <link>http://typophile.com/node/40359#comment-250446</link>
 <description>&lt;p&gt;Will have you written a book? This is great stuff. I will start to use your rules as Widows and Orphans have always bothered me but some of your rules eliminate some of my heartache.&lt;/p&gt;
&lt;p&gt;. . . And Kent. Kent your stuff is great too. I need to re-read this entire thread.&lt;/p&gt;
</description>
 <pubDate>Tue,  8 Jan 2008 10:58:30 -0800</pubDate>
 <dc:creator>Miss Tiffany</dc:creator>
 <guid isPermaLink="false">comment 250446 at http://typophile.com</guid>
</item>
<item>
 <title>I fully agree with Kent’s</title>
 <link>http://typophile.com/node/40359#comment-250443</link>
 <description>&lt;p&gt;I fully agree with Kent&amp;#8217;s &amp;amp; Don&amp;#8217;s comments about feathering or adding space between paras. I recently did allow 1/4 point feathering of one page, for there really was no other way round it in a very complex ms and the facing page was so odd that no one would notice [except those fanatics who hold pages to the light to check back-up].&lt;/p&gt;
&lt;p&gt;But you also need to decide what you will call a widow and what you will call an orphan, and what is unacceptable. There is much difference of opinion among typographers concerning the correct definitions of these words, as well as difference about the acceptability of widows &amp;amp; orphans.&lt;/p&gt;
&lt;p&gt;Here are my opinions, for book work.&lt;/p&gt;
&lt;p&gt;WIDOWS are not acceptable. A widow is defined as a paragraph exit line that is the first line of a text page &amp;amp; that is less than full measure. A full-measure exit line in such position is not a widow, &amp;amp; may be permitted to stand. A short single-line text paragraph is not a widow, wherever it falls. A single-line subhead of any length is not a widow. Widows approximately 75% of measure can be accepted in ragged right settings.&lt;/p&gt;
&lt;p&gt;ORPHANS are acceptable. An orphan is the first line of a paragraph falling as the last line of a page or column.&lt;/p&gt;
&lt;p&gt;Designers trained for advertising work often have harsher rules about widows and orphans than designers trained for bookwork, for their concerns are often more &amp;#8220;aesthetic&amp;#8221; than &amp;#8220;text-serving.&amp;#8221;&lt;/p&gt;
&lt;p&gt;During my tenure as an advertising type director I was often asked by art directors to kill a short line—a &amp;#8220;widow&amp;#8221;—that fell in the middle of a column. The only thing I could do was haul in the writer and get text added or killed. For some reason these &amp;#8220;widows&amp;#8221; were not OK. I never could see that.&lt;/p&gt;
&lt;p&gt;Nor would they allow orphans (as described above). I was more willing to accept this than the overly-heated fear of short lines mid-text. But there&amp;#8217;s absolutely nothing wrong in book work with starting a para on the last line of a page. The indent is not unsightly.&lt;/p&gt;
&lt;p&gt;powers&lt;/p&gt;
</description>
 <pubDate>Tue,  8 Jan 2008 10:56:08 -0800</pubDate>
 <dc:creator>will powers</dc:creator>
 <guid isPermaLink="false">comment 250443 at http://typophile.com</guid>
</item>
<item>
 <title>&gt; (For example, adjusting</title>
 <link>http://typophile.com/node/40359#comment-250372</link>
 <description>&lt;p&gt;&amp;gt; (For example, adjusting the inter-paragraph spacing to avoid widows &amp;amp; orphans, which I think looks better than changing all the leading on the page.)&lt;/p&gt;
&lt;p&gt;I also object to feathering of this type. If there are only 3 paragraphs on a page, you are adding 4 or more points between them, which would look like a blank line to the average eye. (You can safely save or lose a line around a subhead by varying the spacing around these, in many cases).&lt;/p&gt;
&lt;p&gt;The traditional way of avoiding widows (when editing is not allowed) is to run pages a line short/long. Both pages on a spread are run either one line longer or shorter than the text block. You occasionally have to go back two or more spreads to avoid the problem. Normally you would never go directly from a long spread to a short spread, or vice versa.&lt;/p&gt;
</description>
 <pubDate>Tue,  8 Jan 2008 07:39:42 -0800</pubDate>
 <dc:creator>Don McCahill</dc:creator>
 <guid isPermaLink="false">comment 250372 at http://typophile.com</guid>
</item>
<item>
 <title>Seeking Resources for Page-Spread Design</title>
 <link>http://typophile.com/node/40359</link>
 <description>&lt;p&gt;&amp;emsp;I&amp;#8217;ve been trying to design a page spread for a fiction book but I&amp;#8217;m not finding many examples worth emulating.&amp;ensp;Just about every recent book in the library uses equal spacing on all four sides, some pushing the text into the spine or crowding the outside of the page.&amp;ensp;Sometimes both.&lt;br /&gt;
&amp;emsp;I&amp;#8217;ve read up on the subject and found references to &amp;#8216;canons&amp;#8217; and various uses of the golden section, and that modern usage (for good or ill) doesn&amp;#8217;t much make use of them&amp;mdash;but all the reputable sources (&lt;em&gt;e.g.&lt;/em&gt;, Bringhurst, or &lt;a class=&quot;freelinking-external&quot; href=&quot;http://www.ctan.org/tex-archive/macros/latex/contrib/memoir/memman.pdf&quot;&gt;the LᴬTᴇX Memoir Class documentation&lt;/a&gt;) suggest learning from examples.&amp;ensp;Of which I can&amp;#8217;t find any!&lt;br /&gt;
&amp;emsp;Can folks suggest publishers whose books tend to exemplify good design?&amp;ensp;I&amp;#8217;m looking at hard-cover formats at sizes close to 6&amp;times;9&amp;Prime;.&amp;ensp;(Jason Dewinetz &lt;a class=&quot;freelinking-external&quot; href=&quot;http://typophile.com/node/40250#comment-247981&quot;&gt;suggested&lt;/a&gt; 5&amp;frac34;&amp;times;9&amp;Prime; instead.)&lt;br /&gt;
&amp;emsp;Also, what hints are there in a book that some care was taken with typography?&amp;ensp;The American edition of the Harry Potter books, for instance, are very proud of their layout and include a colophon describing the font, but the type block is set unusually low on the page and the text&amp;mdash;especially in the thicker books&amp;mdash;tends toward the spine.&amp;ensp;The &amp;#8217;98 HarperCollins edition of &lt;em&gt;The Silmarillion&lt;/em&gt; is comfortably placed on the page, but the text is set and leaded poorly.&amp;ensp;In cases like these, is the &amp;#8216;good&amp;#8217; layout more likely deliberate-but-incomplete or accidental?&amp;ensp;Can I learn from these?&lt;br /&gt;
&amp;emsp;Thanks,&lt;br /&gt;
&amp;mdash;Joel&lt;/p&gt;
</description>
 <comments>http://typophile.com/node/40359#comments</comments>
 <category domain="http://typophile.com/taxonomy/term/5">Design</category>
 <pubDate>Thu, 27 Dec 2007 15:02:04 -0800</pubDate>
 <dc:creator>JCSalomon</dc:creator>
 <guid isPermaLink="false">40359 at http://typophile.com</guid>
</item>
</channel>
</rss>
