elf: Quote: She is too fond of books, and it has turned her brain (Fond of Books)
elf ([personal profile] elf) wrote in [community profile] ebooks2010-02-20 01:46 pm
Entry tags:

Ebook typography

Inspired by a discussion at the Mobileread forums; decided it really should go here. In a thread about ebook formats, typography was mentioned. (It always is, in the PDF-vs-epub filetype wars.) And while a lot of us who read onscreen are prone to saying, "who needs fancy typography? Just gimme text!" ... typography doesn't have to be "fancy" to be useful and important. It was brought up that typography was developed over hundreds of years, to be what's easiest for the human eye to read, and that ebooks, being fed to those same eyes, are going to need to use a lot of those standards. So I started thinking:

Conventions of typography & layout were designed for the limitations of paper. While a lot of them apply to ebooks, some don't.

Margins, for example. I don't need a half-inch of white space around my ebook text, because I have an ebook reader--my fingers won't cover the text while I'm holding it. I don't need page numbers built into the book, so margins aren't necessary for that, either. Don't need chapter headers at the tops of the pages (I gather this is a printer's convention, rather than one designed for readers); it might be nice, but also might be done very differently from the print methods.

The cover's not going to be torn off to return the book; I don't need a picture cover *and* a text-based title page. Don't need text to give me information that's in the book's metadata, or at least, don't need it at the same level of prominence that's provided for print.

Ebooks being read on light-emitting devices are going to need different typography standards than print books. And we're not seeing any signs that light-emitting screens are going to go away. Sans-serif is often easier to read, especially at lower DPI, on a light-emitting screen. DPI is going to drastically change what fonts are most readable, and DPI isn't going to stop being a concern anytime soon.

Print typography has always had problems with large text, both because it just costs a lot more to print extra pages, and because fonts & layouts don't scale upwards precisely. Ebook typography is going to need to deal with both tiny-text and huge-text options, and we'll need new standards for both of those.

Reflow. Print doesn't deal with reflow options; ebooks will have to. Most of 'em do okay--but features like "images with captions" will need standards that haven't been established yet. So far, only a few ebook reading programs cope with this, and they all do it badly. (Except for PDF viewers that are entirely page-view based. Which is still "badly;" zooming in and scrolling around a page sucks.)

For the most part--almost anything will work for novels. It's when you get into nonfic with diagrams or charts, news stories with photos-and-captions, non-linear text (plays, quizzes, schedules), or heavily-artistic layouts (like many magazines, or gaming books) that typography starts to really matter. And the lack of ebook typographical standards is part of why none of those types of content have taken off in ebook forms, while novels are selling very well.
amalthia: (Default)

[personal profile] amalthia 2010-02-20 11:19 pm (UTC)(link)
This was an interesting post because with all the formatting I do I have had to make decisions such as margins, default margin sizes, whether or not the ebook needed a header (I went with no header) I also feel as long as the data is correctly listed in the metadata then it's all good. I've even moved away from including the TOC inside the ebook and instead people have to access the TOC from the menu options of the ebook. (I'm still debating on this one, maybe with future readers the user will be able to immediately select chapter 14 without having to click through 13 chapters to reach it) My main concern with the TOC is do people know it's there if it's not on a page in the ebook?

amalthia: (Default)

[personal profile] amalthia 2010-02-21 03:11 am (UTC)(link)
That's kind of interesting. I actually use TOC because it helps me find where I want to be in an ebook to re-read favorite sections. :) I had thought everyone else used them the same way. I do agree for reference type stuff a TOC is a must.
cyprinella: broken neon sign that reads "lies & fish" (Default)

[personal profile] cyprinella 2010-02-21 12:35 am (UTC)(link)
I actually like to have the cover and blurb in my ebook files. I often have multiple books by an author on my reader and I may not always remember which book is which. Having the cover and blurb is very helpful and I always add it with Calibre.
finch: (Default)

[personal profile] finch 2010-02-21 07:05 am (UTC)(link)
I don't like the way a lot of PDFs end up laid out on my reader. I usually have to size them up one to read, since otherwise it's the entire PDF page squished onto my Sony Pocket screen. If I have the option, I go for an e-type format.
finch: (Default)

[personal profile] finch 2010-02-21 07:56 pm (UTC)(link)
I tend to have that problem in particular with books from Lulu, since the PDF is designed for printing and not really for downloading.

I have access to Acrobat Pro at work, though, so I might try playing around with that and seeing what I can get out of it. Thanks.
havocthecat: the lady of shalott (Default)

[personal profile] havocthecat 2010-02-22 02:26 pm (UTC)(link)
Don't need chapter headers at the tops of the pages (I gather this is a printer's convention, rather than one designed for readers); it might be nice, but also might be done very differently from the print methods.

I need some kind of a chapter break, though. It's very disconcerting to discover, from one line to the next, that the action has shifted, or the POV has changed, and to have to make the mental shift. I'm used to chapter breaks.
babaca: (Default)

[personal profile] babaca 2010-02-23 04:35 pm (UTC)(link)
I know what you mean. PDFs are the worst because you do have to resize in the reader. Headers are a touch annoying. And page numbers are ok... if they are actually the same page numbers you have while reading. If in epub that won't be the case. I do convert stuff in Calibre (mostly converting pdfs into lrf or epub), but even then you will get typography errors like "smartquotes" looking like ??. That annoys me because I've yet to figure out a way to make it behave.

There really should be an ebook stylebook created for publishers.