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: localizing gerunds? (was: Writing English for Translation)
Subject:Re: localizing gerunds? (was: Writing English for Translation) From:Bill Swallow <techcommdood -at- gmail -dot- com> To:Monique Semp <monique -dot- semp -at- earthlink -dot- net> Date:Tue, 14 Jun 2011 11:20:43 -0400
See my comment earlier about conventions for specific markets. ;-)
Gerunds work well for English user documentation. A good translator
will not just focus on the words but will understand the intent and
will focus on using a similar tone and engagement style that works for
their target language and market. And of course, this needs to go back
into the localization style guide.
Translation is only part of localization.
On Tue, Jun 14, 2011 at 10:54 AM, Monique Semp
<monique -dot- semp -at- earthlink -dot- net> wrote:
> So this thread is reminding me of a topic that seemingly confronts me every
> time I write things that are to be localized: whether to use gerunds.
> So I'd welcome a general discussion: do you strongly advocate using gerunds,
> avoiding gerunds, it depends (on what?), or it just doesn't matter?
> Procedure writing advice seems pretty unanimous in recommending that gerunds
> be used, but localization advice seems to come out strongly against them.
> Well, mostly. In Leah Guren's presentation in the recent User Assistance
> conference, we discussed this and her experience has been that localization
> vendors haven't had any problems with properly translating her procedure's
> gerunds into the target languages.
> So, I’m wondering, is it that there are different best practices depending
> on what the original authoring language and the target localization
> languages are, or is there any way to meld the different best practices (for
> English authoring vs. localization requirements)?
> I recently read a rather old blog post about this:
> The blog post itself is quite short, but there are a lot of interesting
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-