Wim, sage advice on all fronts! I learned a long time ago to know what
translators need to do their job and focus on creating and preparing
content for that phase of the development; they are a part of my content
development team.

When working with Frame files, I deliver mif files with all the images and
fonts. The translators massage these files to work with their translation
tools. Talk with your translators and they'll tell you about their
conversions, tools and processes. If I ask them to deliver a PDF of the
final product, they save the files as as fm and do the DTP. (I recommend
this approach; translation firms provide invaluable quality checks for
every language. They catch even the small things the inexperienced eye
might miss--characters, hyphens, wraps, keep-together and more.) If I
deliver XML files, I must be sure to deliver everything the translator
needs to work with those XML files. And while automated publishing is my
preferred method, the first few cycles must be closely monitored. The
smallest publishing wrinkle can cause unexpected errors!

Doing my part of the work well is no small accomplishment. Building a team
that works with translation well is a bonus. I work to my strength and
enable others to work to theirs.

Like writing, translation is not mechanical. It is all about the content!

 Mollye Barrett | ClearPath, LLC
414-331-1378  | [email protected]  |  www.clearpath.cc
http://www.linkedin.com/in/mollyebarrett | http://www.twitter.com/mollye
Skype: mollyebarrett
_______________________________________________


You are currently subscribed to framers as [email protected].

Send list messages to [email protected].

To unsubscribe send a blank email to
[email protected]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [email protected]. Visit
http://www.frameusers.com/ for more resources and info.

Reply via email to