“As the saying goes, type is a beautiful group of letters, not a group of beautiful letters.” – Matthew Carter. I agree with Carter because we don’t select one font for each letter, we select one font for all letters. Selecting the font is the most important part of formatting and designing your white paper. In my opinion, fonts show your understanding and sense of the document you are presenting to readers. For technical documents, fonts should display your understated personality, fit and tidy. Fonts like Bradley, Ravie, Harrington, etc. they show your fun side, which is not suitable for technical documents.

Recommended fonts:

The most suitable fonts for technical documents are the SANS SERIF and SERIF groups. SANS SERIF fonts include Arial, Helvetica, Tahoma, and Verdana. And SERIF fonts include Times Roman, Times New Roman, Georgia, and Bookman.

Definitions:

The technical definition of the term SERIF is “a typeface that has small strokes at the end of the main strokes of each character.” In plain language, SERIF fonts have feet at the end of each letter. According to some research, it makes content much easier to read.

As in SANS SERIF, SANS means NO or NON in French. Because feet are an acknowledgment of SERIF font, therefore SANS SERIF stands for font without feet. It is technically defined as “typeface that does not have serifs (small strokes at the end of the main strokes of each character)”.

Why use SERIFS and SANS SERIFS:

The most important benefit of using these fonts is that they are readable. SERIFS are believed to improve the reading experience and readability for readers (Arditi, Cho 2005). Readers can distinguish the ends of the letters in this group by their feet. The industry uses SERIFS for user manuals and online helps because, even at small sizes, they are legible. While it was felt a few years ago that NON SERIFS should be used for online content and publishing, it is now accepted that both are perfect for reading online and in print. Bernard (2003), in his research compared SERIFS and SANS SERIFS with Times New Roman and Arial. The results varied in font size, but both were readable.

It is also a common practice for writers who format and design their documents, in which we keep the font Arial 12 and Times New Roman 10 and both are legible. Technical documents have codes, definitions, descriptions, diagrams, etc. so writing the text in SERIFS and SANS SERIFS increases the speed of reading and following the text. According to www.unc.edu, in a recent study, Arditi and Cho evaluated the use of SERIFS and SANS SERIFS with respect to speed, letter recognition, and continuous reading. And both had negligible difference from these aspects.

A large percentage of users use Microsoft Windows as their operating system. The fonts available with Microsoft Office are those that are automatically installed with the operating system. So while you write on Microsoft Office documents or even use Adobe printer for PDF conversion; use SERIFS and SANS SERIFS. When we write technical documents, it is very likely that they will be converted to PDF or published as a web page/document.

Recommended styles for SERIFS and SANS SERIFS

1. Use SANS SERIFS for headings and chapters
2. Use SERIFS for content, subtitles, and text
3. Select fonts with spacing between letters
4. Chicago Manual Style
5. MLA-style
6. APA style
7. They work best in italics because they keep their salient features and remain legible. We need to italicize some terms in technical documents, such as functions, features, tabs, or web pages.
8. Use 2-3 fonts in a document, i.e. my favorite is Times New Roman, Arial and Verdana