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: translation From:"Simon North" <sintac -at- home -dot- nl> To:obair81 -at- comcast -dot- net, techwr-l -at- lists -dot- techwr-l -dot- com (techwr-l -at- lists -dot- techwr-l -dot- c) Date:Thu, 01 Jun 2006 02:39:18 +0200
Four weeks sounds optimistic. It is quite normal to send out translations in
Any half-decent translation bureau or freelancer, should be using a
translation package that includes a translation memory (Trados, SDLX,
STAR Transit, just to name the ones I use). Using one of these packages,
a translation can be made once and the results kept. The second time the
document comes by, assuming it has been changed, it can be automatically
pre-translated to filter out the parts that have not changed. The remaining
are categorised as fuzzy matches or new text and treated accordingly (and
charged at a lower rate accordingly).
As for Peter's idea of Systran ... no offense meant, but ha ha ha. I
occasionally use Prompt, especially for a language I am not too familiar
with such as Russian, but these packages have very limited language
support and still suck big time. Machine translation has not come very far in
more than 20 years. A pre-scan will pick out the obvious phrases and save
some time in trivial sentences, but anything above elementary school level
requires either a disproportionate amount of preparation or a massive
amount of post-scan clean up that it simply isn't worth the effort on anything
but really large, standard projects (defense documentation, where it's pretty
constant and BIG ... the Leopard main battle tank maintenance docs were
more than 500,000 words).
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!. http://www.webworks.com/techwr-l