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: Dropping the you? The Asian response to imperative voice. (was: Re: you or he/it)
Subject:Re: Dropping the you? The Asian response to imperative voice. (was: Re: you or he/it) From:Monica Cellio <cellio -at- pobox -dot- com> To:TECHWR-L <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Thu, 22 Jun 2006 22:12:51 -0400 (EDT)
> Sean Hower noted: <<no one has suggested that you could simply adopt a
> style that uses neither you nor the user. That would eliminate this
> entire discussion. For example: You can use the color picker to set the
> background of your pages. can be rewritten as Use the color picker to
> set the background color for pages.>>
The imperative can work well for direct, procedural material. I'm
having trouble imagining how it would work when writing more open-ended
documentation, such as when giving advice about the alternatives available
to the reader. How would you rewrite something like this (in a
sys-admin or programming manual)? "If most of your users are located
in one facility, we recommend using the standard client-server
configuration. If most of your users are in remote locations, or if
any have slow or unreliable network connections, we instead recommend
using the multi-server configuration with the following modifications
[...]."
I generally find the second person to be the least-awkward approach,
even when writing for translation. But I also take to heart the
comments about negative feedback being hard to get; thanks for the
tip.
Monica Cellio
Senior SDK Developer
I don't represent my company (which is why I don't name it).
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!. http://www.webworks.com/techwr-l