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 important thing is to go with your style. Styles will certainly differ
for different language and geographic markets. The translation should have
considered this and the style needs for the target's (in this case, your)
needs. Discuss with your team and management, and correct the content as
necessary but also give stylistic feedback (detailed) to your Chinese
office and to their translators for future work. The translation group can
fix their TM to accommodate your needs (and vice versa). If you are a
global company and do not have a global style and translation guide yet,
now is the best time to start creating that.
On Tue, Jun 25, 2013 at 10:34 AM, Anonymous <anonymous -at- techwhirl -dot- com> wrote:
> Anonymous has a new challenge, and asks for the list's advice on handling.
> Please make your replies directly to the list, as they cannot be
> forwarded.
>
> --------------------
>
> Greetings,
>
> I need some advice.
>
> I've been asked to review and edit some Ops manuals from our Chinese tech
> pubs department for a product we will be selling domestically. It appears
> that the manual was written in Chinese and then translated into English. It
> is in bad shape. I don't have access to their style guide, but I've noticed
> that they use the pronoun "you" in their manuals and we don't in our
> manuals. For example, "Use [Quick Admit] only if you do not have the time
> or information to fully admit a patient. " and "You can transfer a patient
> with an XYZ or ABC to a new location without re-entering the patient
> demographic information or changing the settings. "
>
> They also use "will" throughout the manual and we do not. For example,
> "Select
> a patient and then click [Import]. Then the monitor *will* update the
> information for the corresponding patient." We would write, "Select a
> patient and then click [Import]. The monitor updates the information for
> the corresponding patient."
>
> I'm uncomfortable re-writing this manual based on our style guide even
> though it is for our US clients and not theirs because I don't want them to
> feel snubbed. I'm also not sure if this manual has been translated yet (I
> have asked the project manager to find out), so that will be a factor in
> how much I change as they are VERY cost conscious and likely will not want
> to pay for so many updates.
>
> Gentle opinions are welcome.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> New! Doc-to-Help 2013 features the industry's first HTML5 editor for
> authoring.
>
> Learn more: http://bit.ly/ZeOZeQ
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as techcommdood -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
>
--
Bill Swallow
Writing and Content Strategy Consultant http://www.linkedin.com/in/techcommdood
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.
