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.
Subject:Re: manual vs white paper From:Haim Roman <haim -dot- roman -at- gmail -dot- com> To:"techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Tue, 25 Aug 2015 20:51:39 +0300
If I understood Gina correctly, her client told her to merge 2 documents
that have different styles (writing, not Word) & functions. And she's
trying to avoid that.
_______________________________________________________________
Howard (Haim) Roman -- haim -dot- roman -at- gmail -dot- com -- 052-8-592-599 -- ×××× ××××
On Tue, Aug 25, 2015 at 8:40 PM, Ryan Haber <ryan -dot- haber -at- gmail -dot- com> wrote:
> Why not just send the client only the text as you want it published? Or
> maybe send two versions - one for the user manual, and the other clearly
> labeled as not for the user manual.
>
> I'm not sure I follow. If you are looking for the client to edit the paper
> into a final form, that doesn't seem likely to go well.
>
>
> All the best,
> Ryan
>
> [image: --]
>
> Ryan Haber
> [image: http://]5151 Dudley Ln.
> Bethesda, MD 20814
> 301-908-3049
> about.me/ryan.haber
>
> <http://about.me/ryan.haber?promo=email_sig>
>
>
> On Tue, Aug 25, 2015 at 1:32 PM, Gina Jones <gina -dot- techwriter -at- gmail -dot- com>
> wrote:
>
> > Hi all!
> >
> > I was recently sent a white paper as is, with instructions to insert the
> > content as a new topic within the relevant chapter of a user manual I am
> > working on.
> >
> > To maintain writing consistency and keep out pre-sale narrative, I'm
> going
> > to suggest appending the white paper to the manual or including a
> > cross-reference to the site it's published on. Is there an alternative to
> > these options? Can you think of additional reasons or have any advice on
> > persuading my client to go this route?
> >
> > Thanks,
> >
> > Gina
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > Learn more about Adobe Technical Communication Suite (2015 Release) |
> > http://bit.ly/1FR7zNW
> >
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >
> > You are currently subscribed to TECHWR-L as ryan -dot- haber -at- gmail -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
> >
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Learn more about Adobe Technical Communication Suite (2015 Release) |
>http://bit.ly/1FR7zNW
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as haim -dot- roman -at- gmail -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
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Learn more about Adobe Technical Communication Suite (2015 Release) | http://bit.ly/1FR7zNW
