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: Capitalization in lists From:Janice Gelb <Janice -dot- Gelb -at- Sun -dot- COM> To:TECHWR-L <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Thu, 28 Jan 2010 08:11:18 +1100
On Jan 28, 2010 8:02AM, Combs, Richard wrote:
> Janice Gelb wrote:
>
>> As others have said, this is largely a matter
>> of style. However, I do want to mention in case
>> your docs are translated that our localization
>> people have told us not to break infinitives
>> across a list introduction because many languages
>> do not use that construct and it can therefore
>> cause difficulties.Therefore, they prefer
>> something like:
>>
>> Use this feature for the following actions:
>> * Eating cats
>> * Killing mice
>> * Riding horses
>
> Sounds reasonable. OTOH, I've been told to avoid gerunds because
> _they're_ hard to translate. :-)
>
> I suspect Peter is correct. Competent translators should be able to
> handle such common constructions in their sleep, just as they do
> countless common idioms that don't translate literally into one or
> another language (and non-idiomatic expressions that _should_ be
> translated into an idiomatic one in some language).
>
Yes, probably translators can deal with this
construction, just as they can think of idioms
to replace English-centric ones, or a myriad
of other challenges often encountered in English-
language docs. But why pose them a challenge
when using a different structure in the English
base document means a more seamless translation?
We were glad for their feedback in general as it
meant that the English docs we submitted for
translation could be translated more quickly.
Agree completely with your advice for starting
all items in a bulleted list with a capital letter.
That's our in-house style as well.
-- Janice
***********************************************************
Janice Gelb | The only connection Sun has with
janice -dot- gelb -at- sun -dot- com | this message is the return address
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-