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: Government Contracts, Standards, and Online Help
Subject:Re: Government Contracts, Standards, and Online Help From:Robert Lauriston <robert -at- lauriston -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Fri, 12 Jun 2009 12:17:37 -0700
Yeah, it's fairly trivial to use different fonts in the print version.
The main reasons I haven't done that are:
1. I've had a lot of character mapping problems over the years and in
response try to keep things as simple as possible.
2. Using the same fonts makes one less thing to do and maintain. Maybe
more than one, depending.
3. So long as it's readable, personally I don't care about fonts (been
trained not to by art directors), so I'm not going to make extra work
for myself, and to date nobody has complained.
4. The companies I was working for didn't own any better fonts.
On Fri, Jun 12, 2009 at 11:15 AM, Combs,
Richard<richard -dot- combs -at- polycom -dot- com> wrote:
>
> But there's no reason why the fonts for the user manual and online help
> outputs have to be the same -- and good reasons why they shouldn't be.
>
> With the tool sets for single sourcing that I'm familiar with, it's
> relatively trivial to use one set of fonts for print/PDF and others for
> the online help. What tool set are you using that forces you to use the
> same fonts for both?
>
> Robert Lauriston wrote:
>
>> To me, generating the user manual and online help from the same source
>> is standard practice, or at least best practice. I've been doing that
>> for years.
>>
>> The fonts have to be chosen to work in both situations, which in
>> practice, in my experience, means Arial, Times New Roman, and Courier
>> New. The only significant issue I have with that is that Courier New
>> is not an optimal monofont for code listings.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing
solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or
HTML and publish to the Web, Help systems or printed manuals. http://www.doctohelp.com
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-