View
2.844
Download
3
Category
Tags:
Preview:
DESCRIPTION
This presentation has been given at FOSDEM 2009, Brussels, on 8 February, by Stany van Gelder, Marketing Director of Connexion Corporate Communications. It explains how you can optimise the translation process of websites built with Drupal, by automating all the technical part of the job, while still calling upon professional human translators.
Citation preview
Automated Web Translation Workflow (AWTW)Automated Web Translation Workflow (AWTW)
Fosdem 2009
February 8, 2009 - Brussels
Automated Website Translation:: Agenda
• Who is Connexion?• Machine translation > < CAT tools• Why not English only?• Traditional > < Automated Website
translation workflow• Which tools?• Demo• Technical approach• Conclusion• Q&A
AWTW:: Machine Translation > < CAT tools
• Machine Translation• Substitution of words in one natural language
for words in another • Rough translation of web page or message• Google is the best
(NIST 2006 – National Institute of Standards and Technology: Machine Translation Evaluation)
Drupal google translate moduleWhy maintain a multi-lingual site while Google Translate can do that for you?
• Try out Babel Fish, Systran and Worldlingo• Sample
AWTW:: Machine Translation:: sample
AWTW:: Machine Translation:: sample
AWTW :: Machine Translation:: sample
Client 2007 premier
Livre maintenant votre table!
Plus de 60 ateliers à commande manuelle…
Customer First 2007
Book now your table!
More than 60 hands-on workshops…
AWTW :: Machine Translation > < CAT tools
• Computer Assisted Translation tools• Human translator remains key• Faster and more reliable with CAT tools• Translation memories (TM’s)
text segments in a source language validated translations in one or more target languages
• Trados/SDL, DéjàVu, WordFast,…
AWTW :: Current Trends
• Globalization >> Localization
• Do you speak (web) English?
• Why not communicating in the language of your target group ?• Time-to-publish• Cost
• Drupal 6 roadmap: integration of i18n• Dries also finds i18n key
AWTW:: Trends :: the issues
• Translation process = not very efficient.
• Time waste:• manually and repetitively
cutting and pasting, emailing, FTPing and project managing
the same translation tasks over and over
• 2 types of web site translations• Full mirror• Partly localised information
AWTW:: Trends :: the issues
• Gap between • people and processes that create and manage
content, using content management systems, • people who use translation software to
translate that content.
• The technologies don't talk to each other very easily, if at all.
AWTW:: Trends :: the issues
• Another process gap:• when translators send content back for
uploading into the CMS• time consuming, • technically challenging • the risk of additional errors.
AWTW:: the solution
Workflow for a 50 page web site in 1 + 5 languages
AWTW:: Auto Workflow:: Xtra Benefits
Next to time and cost savings…• SEO
– Page headers, titles,… also translated– Good for search in local languages by Googlers
• User-friendliness / usability– No technical people needed to do the job !
• Integration with WCMS– Workflow unchanged– Any editing
• Also in (creative) print– Time-to-publish considerably reduced
AWTW:: Autom. Workflow:: Which Tools?
• WCMS– Open Source – Award-winning – Any other valuable WCMS
• TMS (Translation Memory System)– DéjàVu– Trados / SDL– Wordfast– Other xml compatible TMS’s
Our Customers
Website Translations:: Automated Workflow:: Demo
Open your eyes…
WCMS TMS
AWTW:: technical steps :: EXPORT
1. Load all selected nodes
2. For each node:1. Create an <item> in the XML
2. Add the node id to <nid>
3. Add the title to <title>
4. Add the body to <body>
5. Add each CCK text fields to <cck_fieldname>
AWTW:: technical steps :: EXPORT
<?xml version="1.0" encoding="UTF-8" ?>
<export>
<elements>
<item>
<nid>10</nid>
<title>Hello world</title>
<body>
<![CDATA[<p>Hello world!</p>]]>
</body>
<textfield_1>
<![CDATA[<p>Drupal is the best CMS.</p>]]>
</textfield_1>
<textfield_2>
<![CDATA[<p>Forget the rest!</p>]]>
</textfield_1>
</item>
</elements>
</export>
AWTW:: technical steps :: IMPORT
1. Parse the uploaded XML
2. For each <item>:1. Load the original node
2. Reset the node id
3. Update the created and author fields
4. Set the language of the new node
5. Replace all translated values
6. Update all links to other nodes• Nodereference
• Book outline
7. Save the new node
8. Link the translation to the original node
AWTW:: technical steps :: IMPORT
<?xml version="1.0" encoding="UTF-8" ?>
<export>
<elements>
<item>
<nid>10</nid>
<title>Hallo wereld</title>
<body>
<![CDATA[<p>Hallo wereld!</p>]]>
</body>
<textfield_1>
<![CDATA[<p>Drupal is het beste CMS.</p>]]>
</textfield_1>
<textfield_2>
<![CDATA[<p>Vergeet de rest!</p>]]>
</textfield_1>
</item>
</elements>
</export>
node_load
Hallo wereldHallo wereld
Hallo wereld!Hallo wereld!
Drupal is het ...Drupal is het ...
Vergeet de rest!Vergeet de rest!
now()now()
current usercurrent user
import languageimport language
AWTW:: technical steps :: IMPORT
Hallo wereldHallo wereld
Hallo wereld!Hallo wereld!
Drupal is het ...Drupal is het ...
Vergeet de rest!Vergeet de rest!
now()now()
current usercurrent user
import languageimport language
translation of nodetranslation of node
Search translation of the referenced node
AWTW:: included content
• Content that can be translated: – Title– Body– CCK Text fields
• Content that is updated automatically:– CCK Node reference fields– Book outline– Taxonomy
AWTW:: content updates
• The AWTW module can also be used if the translation of the node already exists– In that case the existing translation is
loaded in the import step– The updated translation is saved as a
revision
AWTW:: roadmap
• Drupal 6 version– Make AWTW available for Drupal 6
• Automatic mapping of internal links– All links to internal pages should be
redirected to the translation of these pages
• CCK Filefield and Imagefield– Allow translation of all text fields
(description, title, alt tag) linked to CCK uploads
AWTW:: roadmap
• Translation of meta tags– Integration with Meta Tags module to
translate the meta tags
• Translation of menus– More difficult because there are
several alternatives for managing multilingual menus
• On demand
AWTW:: and what about XLIFF?
Gabor Hojtsy
AWTW:: Benefits
• Easy• Faster• Lower cost• No IT expert needed• Search Engine Friendly
Thank you!
Questions ?General
Stany van Geldersvg@connexion.eu
Drupal.org name = svg
TechnicalKoen Van Isterdael Rachid
Tarsimikvi@connexion.eu rta@connexion.eu Drupal.org = koenvi rashendi
More information?www.connexion.eu
Recommended