RE: Writing conventions/translation

Subject: RE: Writing conventions/translation
From: jcredland -at- avaya -dot- com
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Mon, 1 Oct 2001 09:15:10 -0700

From: Jim Shaeffer [mailto:jims -at- spsi -dot- com]

> When our sentences get complex, we should stop thinking
> about sentences. We should try to think in terms of:
> Diagrams
> Illustrations
> Tables
> Lists.

Unless your documents are going to be translated, the first two (diagrams
and illustrations) may also need to be kept to a minimum.

We're specifically enjoined to reduce the number of diagrams and
illustrations in our end user documents, because it makes translation and
localisation more expensive, more time-consuming and more difficult.

We're currently arguing over the need for call-outs. The localisation group
wants us to stop using them. Our user surveys all say "more please".

Has anyone else run into this kind of issue?

jcredland -at- avaya -dot- com


Planning to attend IPCC 01, October 24-27 in Santa Fe? Sign up by
October 3 and get a substantial discount! Program information,
online registration, and more on

+++ Miramo -- Database/XML publishing automation. See us at +++
+++ Seybold SFO, Sept. 25-27, in the Adobe Partners Pavilion +++
+++ More info: +++

You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit for more resources and info.

Previous by Author: RE: Technial Writing Unions
Next by Author: Re: Indexing of reference manual?
Previous by Thread: [techwr-l-daily-announce] TECHWR-L Daily Update Posting
Next by Thread: Robohelp french translation

What this post helpful? Share it with friends and colleagues:

Sponsored Ads