Writing for Translation?

Subject: Writing for Translation?
From: Geoff Hart <ghart -at- videotron -dot- ca>
To: TECHWR-L Writing <techwr-l -at- lists -dot- techwr-l -dot- com>, Nancy Allison <maker -at- verizon -dot- net>
Date: Thu, 06 Aug 2009 09:11:20 -0400

Nancy Allison wondered about writing for translation: <<1. I once knew
of a PDF prepared by, I dunno, a translation company maybe, that was
all about how to write with translation in mind. It was book-length
and was highly recommended (at an STC meeting, Boston chapter, a few
years ago). Does anyone know of it, and, if so, can you send me a link
to it, assuming it is still available?>>

Probably one of the books published by the Localization Industry
Standards Association (http://www.lisa.org/Industry-Data.512.0.html)?

<<2. Specific, immediate concern: Callouts in figures. My client still
has callouts (in Framemaker text boxes, if it matters) in the figure
itself. What is the preferred format of callouts for translation? Put
only numbers and arrows in the figure, and then have the key separate,
in the main body text? Or have the key in a separate text frame, but
within the anchored frame (that would be for Framemaker)?>>

This is generally a question you should ask your translation vendor,
since I'm sure that practices vary and your real goal is to work
efficiently with whoever does your translation. Anything that makes
the text easy to extract and run through machine-assisted translation
will make the translator's work easier (thus, less expensive); text is
difficult or impossible to extract from graphics (this is definitely
true for bitmaps, but I'm way out of date on this issue, so don't take
that as authoritative for vector art). A good translator will work
with you to find efficient ways to localize everything (e.g., your
software interface), not just your graphics.

------------------------------------------------------------------------
Geoff Hart (www.geoff-hart.com)
ghart -at- videotron -dot- ca / geoffhart -at- mac -dot- com
------------------------------------------------------------------------
Effective Onscreen Editing:
http://www.geoff-hart.com/books/eoe/onscreen-book.htm
------------------------------------------------------------------------

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Free Software Documentation Project Web Cast: Covers developing Table of
Contents, Context IDs, and Index, as well as Doc-To-Help
2009 tips, tricks, and best practices.
http://www.doctohelp.com/SuperPages/Webcasts/

Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/

---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/ for more resources and info.

Please move off-topic discussions to the Chat list, at:
http://lists.techwr-l.com/mailman/listinfo/techwr-l-chat


Follow-Ups:

References:
Writing for Translation: From: Nancy Allison

Previous by Author: Re: Are tech writers inherently snobby?
Next by Author: Standards for warning icons?
Previous by Thread: Re: Writing for Translation
Next by Thread: Re: Writing for Translation?


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

Sponsored Ads


Sponsored Ads