RE: General writing question

["Wright, Lynne" <Lynne -dot- Wright -at- Kronos -dot- com>]

Speaking from the perspective of an ex-typesetter, using serif for text and sans serif for headings was never a standard for the publications we produced.  

If anything, over the 30 years since I was in the typography/publication production biz, the trend has been away from serif fonts. Sans serif is definitely the standard now; its considered more modern and easier to red, and the fine strokes in serif fonts used to be an issue in terms of display and readability on computer monitors. 

Look at pretty much any company's website or on-line documentation; I bet you'll be hard-pressed to find one that doesn't use a Helvetica-like sans serif. 

When I see a doc that uses Times or similar font, I actually get a bit annoyed. It seems so old-fashioned.  

Everyone is entitled to their preference, but I wouldn't say that fighting for Times is worth the effort. If your client wants sans serif, why on earth wouldn't you give them what they want?

-----Original Message-----
From: techwr-l-bounces+lynne -dot- wright=kronos -dot- com -at- lists -dot- techwr-l -dot- com [mailto:techwr-l-bounces+lynne -dot- wright=kronos -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf Of Tammy Van Boening
Sent: January-26-17 9:59 AM
To: lonewriter-discuss -at- mailer -dot- stc -dot- org; techwr-l -at- lists -dot- techwr-l -dot- com
Subject: General writing question

All,

Since the cows have come home, I have always, and I mean always, used Times or another serif font for body text and san serif for headings and I know that this is considered the "norm" or "standard" for tech. docs. That said, a new client is insistent on using sans serif fonts for both headings and text and it isn't pretty when you're trying to read this manual.

Does anyone have any hard references/links to sites that you could point me to that stipulate why this is the norm/standard for writing manuals?  Right now, my client considers everything that I offered as an explanation as simply anecdotal and not worthy of consideration.

Yea, I am about to punt. . . .

Thanks,

TVB


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as Lynne -dot- Wright -at- kronos -dot- com -dot- 

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications?  Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions?  Search our public email archives @ http://techwr-l.com/archives
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications?  Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions?  Search our public email archives @ http://techwr-l.com/archives