{"id":32128,"date":"2024-07-02T18:49:39","date_gmt":"2024-07-02T22:49:39","guid":{"rendered":"https:\/\/ianchadwick.com\/blog\/?p=32128"},"modified":"2024-07-02T18:49:55","modified_gmt":"2024-07-02T22:49:55","slug":"review-the-design-of-books","status":"publish","type":"post","link":"https:\/\/ianchadwick.com\/blog\/review-the-design-of-books\/","title":{"rendered":"Review: The Design of Books"},"content":{"rendered":"
<\/div>\n

<\/g><\/svg><\/i> \"Loading\"<\/p>\n

<\/div>\n

\"The<\/a>L<\/span>ike with so many other technologies<\/strong> in our lives \u2014 computers, cars, bread machines, flushing toilets, DVD players, convection ovens \u2014 most consumers don’t know or appreciate how books are made, or why they are made in such familiar shapes and structure. In more than four millennia since humans invented writing, the way that writing has been recorded and shared has evolved from clay tablets to the modern paperback and hardcover. Because we are so used to seeing and reading books, few of us stop to consider how that evolution happened and why. Debbie Berne’s The Design of Books<\/em> (University of Chicago Press, 2024) will help explain it. But not, as I’ll comment on, entirely.<\/p>\n

The subtitle of her book is An Explainer for Authors, Editors, Agents, and Other Curious Readers<\/em>. Having been three of those four, and always an avid consumer of books on related topics \u2014 grammar, typography, graphic design, alphabets, style, usage, writing, the science of reading, and etymology \u2014 plus having worked in the book trade, I believed I fit snugly in her target audiences. And on top of that, I am currently tinkering with a book design myself, using Affinity Publisher software (Berne only mentions Adobe’s InDesign but Affinity Publisher<\/a><\/em> is an excellent and much-less-expensive alternative), with the eventual goal of having it self-published. Any advice I can get on doing so in the most aesthetically pleasing manner is welcome.<\/p>\n

Berne writes for the intellectually curious reader who likely has little-to-no background in her craft, but I suspect that authors (would-be and actual) \u2014 particularly those considering self-publishing \u2014 will benefit most from her book. The information Berne provides could help the new author when dealing with the multitude of choices offered by book publishers. It’s chock full of general information about book structure, layout, formatting, type, and construction without being overly detailled or prescriptive about anything.<\/p>\n

But that’s where I find she lets me down. Perhaps I am too focused on the practical aspects to benefit fully from the high-level overview approach, but I wanted more<\/em> detail. Berne’s presents a general book about many more aspects of book design than, say Robert Bringhurst’s The Elements of Typographic Style<\/em><\/a>, Mark Argetsinger’s A Grammar of Typography<\/a>, or Sophie Beier’s Reading Letters<\/a> <\/em>\u2014 all of which are in my library, along with books on style and usage. However, while Berne covers a lot of areas all three leave out, particularly in the business of printing and ebooks, I kept wanting more about the intimate stuff.<\/p>\n

For example, margins. Berne says margins are “buffers, separating the text, visually, from the world. Bigger margins offer more protection. Practically, the size of the margins is a negotiation between beauty and efficiency.” Yes, but how should a designer calculate the best margin size? Is there a formula? Or is it done by sight with every book different? She adds the gutter “keeps words from sliding into the crease of the binding. But if the gutter is too wide, the text block starts to feel disconnected.” Why is that a bad<\/em> thing? Is there an optimal gutter width? Does it depend on the number of pages? Do font size or line width affect margins and gutters? Is there a preferred ratio of text block to margin width for different types of books or book sizes? Can the Golden Ratio be used anywhere at all? How do margins differ with genres or publication format?<\/p>\n

Okay, what about paragraph indentation? Berne writes that indentation is a better choice for making text feel connected, and more economical than using a line space in terms of space used. True, but what is an ideal indent? What’s too little and too much? She says it’s a “judgment call” and “the longer the line, the more indent is needed to make an impression.” That’s rather too vague for me, and I’d like to see some examples of what she thinks are good and bad indentations.*<\/strong><\/span><\/p>\n

And then typefaces\/fonts. Berne gives us many excellent pages explaining the basics of typography, but when she gets to discussing font size and readability, she equivocates and doesn’t get into detail about how or why font decisions matter in those areas.<\/p>\n

She also says, “Point size is useful notation, but not all that meaningful… Designers use their eyes, not the drop-down menu, to make judgements around size and all other questions of style.” That’s a bit like saying brakes are meaningless, car drivers use their clutch and shift to slow down. Design software requires a full understanding and appreciation of the point system. Text is set in styles that affect the entire body, and most software can make very subtle adjustments. Yes, the designer’s eye is the final judge, but tweaking those numbers is a crucial part of the process.**<\/strong><\/span><\/p>\n

Designers use different typefaces, different font styles, sizes, and weights to set parts of a book apart. Chapter titles, running heads, body text, foot- or endnotes for example, are often set in different fonts or colours. Berne herself uses three typefaces, as well as colour, to identify such components. I would also have liked to see some graphic examples of good and bad pairings, as well as examples of body text set in some common serif and sans-serif faces. Yes, these are readily available in other books and online, but I felt they should be included, at least briefly, here, too.<\/p>\n

Paper is a big issue in publishing: what type, size, texture, weight, colour, and coating is appropriate? Admittedly, that’s a choice that editors and authors seldom get to make if a publishing house is doing it. But for self-publishing, it can be daunting to decide what is best. Berne gives the reader some things to consider about the choices, but leaves us with a comment on paper shortages and a challenge to “reimagine lower-grade or brown papers for use in certain kinds of books…” What<\/em> kinds? What does this paper look like or feel? Even a photo showing the difference in contrast on such paper would have helped.<\/p>\n

In my limited experience buying perhaps a dozen such books, the print-on-demand (POD) and self-published books on services like Amazon and Abebooks, seem to use standard 80-lb, white printer paper (and are too often atrociously formatted, so could benefit from Berne’s advice). Are there better, more economical choices? Is there a reason to choose letter-sized or 6″x 9″ or 8.5″ x 5.5″ size for self-publishing? I’ve seen them all in use. Berne doesn’t get into it.<\/p>\n

When designing a cover, how does the artist or creator determine how thick a spine should be? That matters when designing a spine. Some book covers are one-piece graphics, incorporating front, flaps, spine, and back, sometimes with wrap-around graphics. Others have three or more separate elements. The front, back, and flap cover sizes are easy to determine, but the spine width depends on the number of pages, type of cover, and paper weight (thickness). She doesn’t give us any suggestions (there are formulae you can download and adapt for your own use but they are not always exact).<\/p>\n

Berne has a good chapter on ebooks, with considerable practical advice, but does not say what software is required to create such titles. Popular software like Microsoft Word or Apple Pages won’t do it, and not all DTP software exports to ebook format. Users need to purchase or download a program that turns those files into ebook formats (and there are two distinct formats), then test the resulting files for consistency and errors (either in an app or device). Berne points out several basic formatting errors, but in this chapter doesn’t reiterate her comments about screen fonts vs print fonts (p53-54) or comment on whether serif or sans-serif are best for ebooks (there are arguments for sans-serif as body text in small screens, using serif for headlines; the opposite of what is commonly used in print).<\/p>\n

Overall, Berne’s book is a good, albeit basic introduction to book design, aimed I suggest, at those who are not already involved in printing or typography. She writes well and clearly. But it lacks some of the detail I had hoped to find, as well as needing some practical advice as noted above. I’d give it 3.5 out of 5 stars (perhaps 4 out of 5 if you have no experience in publishing), but suggest would-be publishers and authors also add the books mentioned above to their reading list.***<\/strong><\/span><\/p>\n

Notes:<\/h5>\n

I’d also like to point out a small mistake in the book. On page 180, she shows an example of tagged XML text, However, while she prints the opening tags, she does not include closing tags. XML and CSS are similar in their usage. According to the W3schools<\/a>, “All elements must have a closing tag.” So her example:<\/p>\n

<h1>Summer Pies<\/code><\/p>\n

should really be:<\/p>\n

<h1>Summer Pies<\/h1><\/code><\/p>\n

Otherwise the entire block will be treated as a headline. Ditto with the rest of her example: closing tags (case sensitive, unlike CSS) are required after each opening tag.<\/p>\n

(I did not see any reference to having to embed fonts when creating PDFs which can also be read on ebook platforms… some of the PDF creators, including some non-Adobe printer drivers do not embed fonts in the subsequent files, which can create a poorly-formatted PDF.)<\/p>\n

*<\/strong><\/span> Both Bringhurst and Argetsinger recommend a one-em indentation<\/a>, which can be rather tight (this dash is one em wide: \u2014). They point out that the first paragraph in a chapter or under a section head is never indented (Berne does not mention this, although she uses the convention). Bringhurst also suggests the indentation could be the leading size, so if the type is 11pts on 13pt leading, the indentation would be 13pt. Depending on the font, this could be wider than an em, but also narrower. The Chicago Manual of Styl<\/em>e (17th edn.; CMOS is another recommended title) suggests a tab space (0.5 in) can be used (this seems to be Berne’s choice), but while acceptable in office documents or manuscripts, may be too wide for published books, although it again depends on the typeface, line spacing, and contrast.<\/p>\n

**<\/strong> <\/span>Good desktop publishing software can adjust font sizes, leading (line spacing), indentation, and other features in fractional increments, not simple whole points: 13.5pt, or 12.1pt. Depending on the typefaces used, adjusting such small increments can change the look and feel of the text, but you need to properly appreciate points as a unit of measurement.<\/p>\n

***<\/strong><\/span> I also recommend, among others, that you read or consult Thinking With Type<\/em> by Ellen Lupton (2nd or 3rd edition); Why Fonts Matter<\/em> by Sarah Hyndman; Letter Fountain<\/a><\/em> by Joep Pohlen; Type Tricks: Layout Design<\/em>, by Sophie Beier; Layout Essentials: 100- Design Principles for Using Grids<\/em>, by Beth Tondreau; The Non-Designer’s Design Book<\/em> by Robin Williams; Typography Essentials: 100 Design Principles for Working With Type<\/em>, by Ina Saltz; Designing With Type: The Essential Guide to Typography,<\/em> by James Craig; Making and Breaking the Gri<\/em>d, by Timothy Samara;\u00a0 and Getting It Right With Type: The Dos and Don’ts of Typography<\/em>, by Victoria Squire. Of course, writers will need usage, style, and grammar guides<\/a> as well.<\/p>\n

Words: 1,848<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

<\/div>\n

<\/g><\/svg><\/i> \"Loading\"<\/p>\n

<\/div>\n

Like with so many other technologies in our lives \u2014 computers, cars, bread machines, flushing toilets, DVD players, convection ovens \u2014 most consumers don’t know or appreciate how books are made, or why they are made in such familiar shapes and structure. In more than four millennia since humans invented writing, the way that writing has been recorded and shared has evolved from clay tablets to the modern paperback and hardcover. Because we are so used to seeing and reading books, few of us stop to consider how that evolution happened and why. Debbie Berne’s The Design of Books (University \u2026…… click below for more \u2193<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_hide_featured_image":false,"_jetpack_featured_image_duplicate_dismissed":0,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[8,1181,72],"tags":[1975,437,990,340],"class_list":["post-32128","post","type-post","status-publish","format-standard","hentry","category-books","category-books-about-books","category-books-by-the-bedside","tag-book-design","tag-publishing","tag-review","tag-typography"],"a3_pvc":{"activated":true,"total_views":526,"today_views":1},"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"jetpack-related-posts":[],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/ianchadwick.com\/blog\/wp-json\/wp\/v2\/posts\/32128","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ianchadwick.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ianchadwick.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ianchadwick.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ianchadwick.com\/blog\/wp-json\/wp\/v2\/comments?post=32128"}],"version-history":[{"count":13,"href":"https:\/\/ianchadwick.com\/blog\/wp-json\/wp\/v2\/posts\/32128\/revisions"}],"predecessor-version":[{"id":32141,"href":"https:\/\/ianchadwick.com\/blog\/wp-json\/wp\/v2\/posts\/32128\/revisions\/32141"}],"wp:attachment":[{"href":"https:\/\/ianchadwick.com\/blog\/wp-json\/wp\/v2\/media?parent=32128"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ianchadwick.com\/blog\/wp-json\/wp\/v2\/categories?post=32128"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ianchadwick.com\/blog\/wp-json\/wp\/v2\/tags?post=32128"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}