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.
The doc is only too long if it contains unnecessary material customers
have to wade through to get to the necessary information. Splitting
such a doc into two parts would make even more work for the customer.
If the content is all necessary, the person complaining that the doc
is too long doesn't understand the audience or is in some other way
unqualified to comment on the matter.
On Thu, Oct 2, 2014 at 12:59 PM, Hannah L. Drake
<hannah -dot- drake -at- formulatrix -dot- com> wrote:
> Would it? Perhaps then you'd only need one of them.
>
> -----Original Message-----
> From: techwr-l-bounces+hannah -dot- drake=formulatrix -dot- com -at- lists -dot- techwr-l -dot- com
> [mailto:techwr-l-bounces+hannah -dot- drake=formulatrix -dot- com -at- lists -dot- techwr-l -dot- com] On
> Behalf Of Robert Lauriston
> Sent: Thursday, October 02, 2014 3:59 PM
> To: TECHWR-L Writing
> Subject: Re: keeping the page count down?
>
> If the doc is really too long, splitting it in two would just make things
> worse.
>
> On Thu, Oct 2, 2014 at 11:40 AM, Hannah L. Drake
> <hannah -dot- drake -at- formulatrix -dot- com> wrote:
>> Maybe you should split it into two documents. ...
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l
