TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Re: Your typographic conventions and justification for
Subject:Re: Your typographic conventions and justification for From:quills -at- airmail -dot- net To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Thu, 04 Feb 2010 18:18:11 -0600
Ooooo! A sensible approach to templates! Unlike how a lot of them are
created.
Scott
On 2/4/10 5:32 PM, Gene Kim-Eng wrote:
> I don't think there's any such thing as a "Gene Kim-Eng typographic convention"
> that you can use as breadcrumbs to track my movement from company to company
> over the years.
>
> If I'm coming into a new place with established templates and styles, I stick to
> whatever's already in use that hasn't been exploding in peoples' systems or
> causing other problems and devote most of my template time to fixing stuff under
> the hood to make things run smoothly.
>
> If I'm starting with a blank screen in a really new place, the operative rule is
> to keep things simple. One serif font, one non-serif font, one fixed font for
> code strings, with varying sizes, boldness, italics and colors for same. I try
> to sync the look and feel of user docs with whatever marketing materials the
> company has successfully used to advance itself to the point where it could
> afford to hire someone to do its technical documentation.
>
> Gene Kim-Eng
>
>
> ----- Original Message -----
> From: "Nancy Allison"<maker -at- verizon -dot- net>
>> I am preparing for a discussion of this issue and wondered what other tech
>> writers do. What do you do, and what reference books or standards do you rely
>> on? Can you recommend any other books or standards for me to take a look at?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
