Sans-Sucky - Part 1: Text Readability and Optimization
The text readability discussion is one that every person is readily willing to give their opinions on. Do you like white on black? Black on white? Serif? Sans-serif? Italic? Bold? Color? Textured backgrounds? Whitespace? Full-justify?
Well, if you're looking to please any sized audience, then throw your preferences out the window! What you prefer doesn't matter, because, presumably, what you'd really prefer is for someone to read your shit, yes? Right. So is there a standard?
There's a standard for anything, and text readability is no different. I actually attended a few seminars on typography and text-readability back in the day, just for fun. Yes, this makes me incredibly geeky. No, I don't mind it at all. Yes, the seminars were a blast. Yes, I made charts and came home and researched and never stopped. I won't call myself the Goddess of Fonts or anything, but I will admit that, if the title existed, I'd work exceptionally hard to obtain it.
Please Note: These are simply facts and opinions coming from the technical spectrum. I don't claim to know what's best for fiction-writing, nor am I trying to pee on anyone's artistic license. XD
I Shot the Serif
For print, serif fonts (ie. Times New Roman) are best for blocks of text, because the serifs (the little tails on the letters) help our eyes easily distinguish the lines and guide us to the next word. However, operating systems have options and settings which smooth and slightly alter serifs (alias and kerning), and combined with the light source of the screen, this makes the text look overwhelming to our eyes. We distinguish all of this stuff happening and we are compelled to jump around and find our places.
Also consider this:
Tip: Readers can change font styles on FFn.
Look at majorly trafficked websites like Twitter and Google. Note their constant use of sans-serif fonts. They have billions of dollars and plenty of statistical analysis at their disposal. If there were more evidence that serif fonts on-screen weren't difficult to read, then they'd be using them, as their top priority is mass appeal.
Sure, there a certainly valid arguments that sans-serif fonts can create distracting optical illusions on screens, and a few studies even show that the type of font used doesn't much matter, but I don't personally or professionally subscribe to this theory, as there are far more studies proving that, not only does font type matter, but it is essential to eye comfort.
The exception for serifs would be headers and titles, and any other text which is generally larger in size and one line or less. In these cases, serifs are perfect, which is another anomaly compared to print, wherein sans-serif fonts would be used for such a thing.
TL;DR - Serifs are eyefuckers.
Excerpt taken from Chapter 1 of
Now that we've deduced which types of fonts are optimum for readability, lets break this down once more and explore different font families!
So long as you're going sans-serif for large blocks of text, you can exercise some level of preference and favoritism. It is important to remember that, though you personally might have 200 fonts installed on your PC, that many people won't. Therefore, you must stay within a certain spectrum of commonly installed fonts. What are these fonts?
Below is a list of commonly used fonts, and the operating systems they come bundled with. (from upsdell)
|Times New Roman|
|Microsoft Sans Serif|
|cursive||Comic Sans MS|
My own personal faves for block text are Tahoma and Trebuchet MS, though many websites, like fanfiction.net and default Google Docs, use Verdana. This is all personal preference, of course. For titles and headers, you can get a little more creative, and I much enjoy the use of Cambria and Impact (which is a sans-serif, but not suitable for block text).
Keep in mind that those optical illusion issues mentioned above are caused by the Arial typeface. It is widely avoided because of this.
In the evnt that you're setting fonts geek-style, it's always an excellent idea to make font "stacks" when setting families in HTML or CSS. This means that, instead of choosing one, we give the browser a back-up option that is most like our original. We do this because font style is important to design and readability, and sometimes, whatever the browser defaults to when your first choice isn't installed on the browsing machine may be far from what you intended.
Font stacks will look like this:
So the first font the browser is going to look for is Tahoma, and if it's not present, it'll look for Verdana, and if that's not present, it will default to your operating system's sans-serif.
The biggest factor in the previous two sections is going to be text-size. Smaller text is best in sans-serif, and larger text is best in serif. The optimum font size for large blocks of text is 12px (or 9pt), though you have +/-1px breathing room. Headers and titles require anything above 16px.
Tip: Readers can change line-height on FFn.
How to set line-height?
Fanfiction.net, like font faces, sizes, and colors, allows you to set your preferred line-height. Try playing with this some time! Test it out, get a feel for the differences, and see if you enjoy it more.
<font style="line-height: 20px">
<font style="line-height: 1.5pt">
These are good, comfy amounts of line-height for 12px text.
As late as 1941, the practice of using double spaces to separate sentences was still alive in the U.S., as seen in this extract from Damon Runyon. Within the following few years, the practice became all but extinct in commercial publishing on American shores. Source.
Well, some people do this, and the "proper" term is an "em-space." You know, kinda like how the "em-dash" is a long version of the plain-dash. Basically, it's this totally archaic deal in which some old mofos started this trend, be it for commerical printing profit conerns or whatever else, and it was apparently "all the rage" back in the 1770's. There was no real discernable purpose for it back then, but then with the eventual invention of the typewriter, em-spacing was actually proper, typographically speaking. This was due to the fact that typewriters use monospace (every letter and space is the same width) characters, and allowing the extra space made it so the carriage moved a fixed amount after every keystroke. Its benefit was strictly mechanical.
But we aren't working on a typewriter, and we aren't a bunch of penny-pinching old dudes, so there's no real purpose to em-spacing. I won't say there are any adverse effects to using it, however, aside from that of the reader stopping to wonder, "Wait, why are there two spaces after every sentence?" And anyone out there who thinks their use of em-spacing equates to their shit not stinking can just gtfo.
Justify My Love
Okay, so it would seem as though I commonly break the rules here, but I can explain why.
Justify is the perfect spacing of text that is flush to both side margins.
Why is it bad? Well, depending on the content of the text, it can cause major readability issues, such as something called "rivers of text." It also takes away important visual line cues---kind of like seeing a staggered line and knowing when you jump back to the other margin where your place is.
There are different levels of justification, however, and used in the proper way, many issues regarding justification can be avoided.
Full-force-justify will make the text margins a perfect square. This is the worst of all justify options, as the white-space it forces can be dramatic and jarring.
Simple justify will simply move text around to accommodate the justification, leaving the final line of text shorter or equal to the rest, however necessary. This lessens the problems with dramatic white-space and still allows you the perfect margins, in the event that you're doing an article like this, or wishing to show images with your text wrapped around it.
I like the look of the straight flowing lines justification offers, but consider what you're using it for. Large blocks of story text probably aren't an ideal place to play with it.
Excerpt taken from Chapter 12 of
Swanky Italics, Bolds!
Sarcastic Strikethroughs, and Ultra Uber Underlines.
Aldus Manutius, famous printer, inventor of italics, and EPOV mindreading pioneer.
But with great power comes great responsibility.
Italics, like all wonderful things, should be used in moderation. After so long reading italics, you eyes go all crossed and itchy. How much italicized text is okay?
Well, in the case of italics, sans-serif fonts are actually more difficult to read on-screen. IKR? All of these fucking conditions, so annoying. But keep in mind that the purpose of italics is to emphasize words or short phrases (cwidt?). It was never meant to emphasize enormous blocks of text.
As a personal rule, I always prefer to italicize when the sentence is two lines or less. I know, this can't always be followed, like in instances where Carlisle is thinking a particularly lengthy medical explanation to Edward, etc., but we should aim for brevity! I mean, we've all gotten to that point in a story (I've done this before myself, so no hate) where an entire scene will be in italics. We see this daunting page full of slanty text and involuntarily groan. We kind of wanna skip it, yeah?
Full journals, diaries, letters, flashbacks, and anything else more than a couple paragraph is definitely too long to be italicized comfortably. In these cases, I suggest (no hate mail, please) use of a horizontal line (<HR>) or one of your very own fancy scene markers to separate it from the main text. Our eyes will thank you.
chapter 47, I jump from ENORMOUS blocks of italicized text to non-italicized text several times. Obviously, I could have used a horizontal line or my signature scene marker (---) to split these up, and it would have been more comfortable. Instead, we're adjusting our eyes like a gabillion times. ~slaps own hand~
Addicted to Edward Cullen, the author of
Music of My Soulhas two flashbacks in
chapter 4, but as you can see, she made such a flawless transition from present to past that italics weren't necessary.
A small smile formed on my lips.
I'd been walking by the narrow aisle of Classic Literature books in library at Forks High School when I'd noticed a girl with long brown hair stretching to reach a book on the very top shelf. She was standing on her tiptoes on a small step stool, apparently not realizing her feet were off-center and causing the stool to begin to tip.
How to Save a Lifeouttake,
Miss Mad Worldshows various journal entries, along with the thoughts of Bella, who is reading it. Instead of using italics to make us distinguish journal entry from internal dialog, UO uses scene markers, and this, coupled with the inherent context of what's being read, is more than enough to help us distinguish.
It is 2:30 PM. I did not go to school today. I still haven't slept. But I've been busy. I've been so very, very busy and you want to know the best part? My mind is quiet. My mind is finally, finally, finally blessedly quiet and I have some peace of mind.
TL;DR - Step away from the CTRL+I.
Boldshould be used in even greater moderation. Its purpose is to draw attention, and if you've ever seen a chapter/flyer/article/etc with many words or phrases bolded, you know what I mean when I call such things, "The bold that cried wolf." When so many items are being flagged as important, then are they really important anymore? Not really. And then, there will come a time in the text when something really is important, and no one will believe you.
Bold causes a big readability issue, since items are competing for attention, but it also causes extra noise issues that we just don't want.
When you're about to press the big "CTRL+B," consider if the same effect could be achieved by italicizing the text instead. Then, apply the above rules for italics to consider if the same effect could be achieved by using horizontal lines or scene breaks.
TL;DR - Bold is last resort.
I rarely see
strikethroughsused for anything other than sarcasm, visual scribbles (like in journal entries), beta editing, or, if we're being proper, to depict the crossing out of an item from a list. Fanfiction.net doesn't allow you to use strikethrough, however, so keep this in mind when writing, so as to avoid any embarrassing "was meant to be crossed out, but now it's not" situations.
Sarcasm:No, I didn't eat dinner,
especially not Cocoa Puffs.
Visual Scribbles in Fiction:[Study Hall Note to Alice]
I guess you can come over after school.Is that a curling iron in your backpack?
Beta Editing:"This is dumb," Edward said
Crossing Out from List:
Bacon, eggs, bread, muffins, Cocoa Puffs, hot dogs, grapes.
ALL CAPS: THE VIRTUAL YELLLLLL
STOP SCREAMING AT ME. I DON'T CARE THAT BELLA IS LITERALLY SCREAMING AT EDWARD IN CHAPTER FIVE OF YOUR FIC. THIS IS NOT COOL. AN EXCLAMATION MARK AND A DRAMATIC DIALOG MARKER DOES THE JOB SO CAPS-LOCK DOESN'T HAVE TO, KNOW WHAT I MEAN? I HAVE NO FANCY STATISTICAL EVIDENCE TO PROVE WHY ALL CAPS IS SO FULL OF SUCK.
IT JUST IS.
The Color and the Shape
Tip: Readers can change color schemes on FFn.
Again, take a gander at majorly trafficked websites such as Google and Twitter. They use dark text with a light background, and I've never seen anyone complain over Google's totally annoying white background and black text.
If you're playing it safe, go black on white.
If you're looking to be a little adventurous, then consider the brightness of font colors versus backgrounds. Stark white on black is harder to read than stark white on dark grey, or light grey on stark black.
neat little toolthat will allow you to experiment with variations. As you can see, it'll alert you whenever the readability alogrithm catches a combination that's difficult or impossible to read.
Excerpt taken from Chapter 8 of
Fun with Titles!
Super Awesome Title
The title above was created using the CSS tags, font-variant and letter-spacing.
Other than my use of serif for a title, I have no fancy statistical or scientific evidence to prove why this is cool.
It just is.
Block Text Width
Tip: Readers can change page widths on FFn.
Well, our screens are really wide. I remember back in the old days when it made sense to optimize all designs to 800x600. Now, the notion is almost laughable. Who the fuck still sets their screen resolution to 800X600? (My mother doesn't count.)
Now, the laughably small screen resolution is 1024x768. We usually go larger than this, what with the advancement in graphic card technology over the years. This means that our screens are wiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiide.
Tip: Authors can change page widths in Google Docs.
Therefore, it's a pretty good idea to make block text a fixed-width. In FFn, we, as authors, have no control over this, but as readers, we do. I always read on 1/2 screen (and I use the dark scheme with high line-height, but you dgaf about this).
Fortunately, we can control our block widths in other places, such a Google Docs and any posting location that allows HTML.
Important:Never use pixels to define width in HTML. There are too many screen-size possibilities within your audience. Instead, always use percentages..
The nature of screen-based text is more important than many realize. Consider how many hours per day we spend reading text from a screen. This shit can get painful. Whether you're doing a blog, making an archive, posting a story to LiveJournal, or just creating a PDF or Word document, you definitely want to make your audience as comfortable as possible.
As I stated ^^^ up there, this is all coming from a technical web spectrum. Thus far, I've found no reliable resources that are specific to on-screen text readability with literature in mind. I think it's a credit to the advance in times that it's probably becoming common enough to consider it, though.
hgrebdes.com's Color Theory,
Skills for Access,
The History of Linear, Sans Serif Typefaces
Next time, the real fun begins!
Big thanks to