qui - Tekom

This new localisation model, which is characterised by small "chunks"
of translatable information, has called the need for more automation.
Sending each small change or update to a page on a web site to a project
manager, who then coordinates the translation in all required languages is
just too time-consuming and inefficient. This is the reason many translation
tool developers are now working on workflow systems which enable
companies to automate the transfer of files between all people involved in a
translation project, i.e. client, project manager, translator, editor,
proofreader, client validator, etc. Examples of such tools are Lionbridge's
LionTrack and SDL's SDLX WebFlow. Apart from workflow automation
some of these tools also contain online project tracking features, so clients
can see any time of the day how far translation of their material has
progressed.
Implementation of these systems requires a thorough analysis of the
client's and vendor's processes and information flows, so the tool can be
customised. Moving to this new, automated localisation project model also
means that many clients are looking for long-term partnerships with
localisation vendors, in order to better integrate them in their development
and business processes, and to build up expertise and product knowledge in
one central location.
In a few years from now, it is not unlikely that translators will be part
of "virtual teams" working for one or more clients. These teams will consist
of translators who, regardless of their location, have all qualified or
received training to do translations for a particular client. If new
information is added to the client's web site, the text is transferred to the
first translator in the team, who then indicates if he or she is available to do
the work. If rejected, the job is automatically passed to the next translator
in the team until someone can do it. After translation, the translated
material is automatically transferred to a reviewer working for the client,
114