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.
Jane Credland reports that if <<...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.>>
If the job were easy, localisation contractors couldn't charge enough to
make such a good living. "Difficult" strikes me as a spurious objection; if
the graphic is truly useful, including it should actually facilitate the
task of translation because it communicates more clearly, in fewer words,
than the comparable text. "Time-consuming" also strikes me as unlikely,
except insofar as someone has to produce a screenshot or other image. Since
the localizers will have to translate the interface anyway, "time-consuming"
shouldn't be an issue. Perhaps the problem is that they're using inadequate
tools or don't have any easy way to annotate the graphics? Perhaps they're
trying to avoid manual translations using some form of translation memory or
machine translation system, and can't run graphics through the filters?
Perhaps they're using incompatible writing or graphics software that makes
it difficult to look at or edit callouts and other illustration text?
<<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".>>
Tell the localisation group to "suck it up". <g> If the users want more
graphics, they should get more graphics. It's never a good idea to
compromise the documentation simply because it's inconvenient to do it
right; about the only exception to that sweeping generalization is when
"doing it right" means you'll run out of time or other resources and not be
able to do it at all.
--Geoff Hart, FERIC, Pointe-Claire, Quebec
geoff-h -at- mtl -dot- feric -dot- ca
"User's advocate" online monthly at
www.raycomm.com/techwhirl/usersadvocate.html
"I vowed [that] if I complained about things more than three times, I had to
do something about it."--Jon Shear
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 http://ieeepcs.org/2001/
+++ Miramo -- Database/XML publishing automation. See us at +++
+++ Seybold SFO, Sept. 25-27, in the Adobe Partners Pavilion +++
+++ More info: http://www.axialinfo.comhttp://www.miramo.com +++
---
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 http://www.raycomm.com/techwhirl/ for more resources and info.
