1 of 29

1
IGNITELinguistic Infrastructure for
Localisation Language Data, Tools and Standards
LRC - XI European Foundation - 25-26 October
2006
Managing multilingual information

• Reinhard Schäler Kevin Bargary Michael Bourke
• Localisation Research Centre (University of
  Limerick)
• LRC_at_ul.ie

2
Overview

• The questions
• Searching for the answer
• Developing solutions
• Snapshot where we are today
• Outlook

3
The questions

• How to localise more digital content within an
  ever decreasing time scale, without a decrease in
  quality and without an increase in your budget?
• How can process automation help to achieve this
  target?
• Are the required technologies interoperable?
• Have relevant standards been implemented by tools
  and technology suppliers?
• In house
• Third party

4
IGNITE Searching for answers

• Develop agreed procedures to validate standards,
  certify their implementation, ensure
  interoperability, and most importantly
  demonstrate their usefulness in an automated
  localisation environment
• Establish independent organisation (not a direct
  stakeholder), with the support of developers,
  users, standard bodies
• Demonstrate successful use and implementation of
  standard in localisation environment
• Strategy
• Prepare the ground for the establishment of an
  independent operation
• Gather linguistic resources, including authentic
  source material, tools and technologies, and
  standards, and use these to build an automated
  localisation environment, the Localisation
  Factory, that will be used to both demonstrate
  and measure the effectiveness of the use of
  standards in the localisation process.

5
From bespoke to standard solutionsThe
Localisation Factory

• Similar developments
• Translation memory systems
• Visual localisation platforms
• Standards
• Bespoke solutions exist
• Large publishers
• Large development teams
• Full control
• Standard solutions are needed
• Medium to small size operations
• Limited access to development teams
• Little control over content production

Automated Localisation Environments have been
built and operate highly successfully in very
large corporations.
6
Genesis towards the use of standards

• Individual effort
• Deal with issues as they occur fire fighting
• In-house tools support
• Automate individual tasks, e.g. string extraction
• Third party tools
• Mainstream, individual tasks
• Best of breed
• Combine tools, e.g. terminology tools,
  translation memories
• Adhoc standards
• Translation Xchange (TMX), Terminology Xchange
  (TBX)
• Open standards
• XLIFF, Trans-WS

7
Developing solutions

• IGNITE Content Repository Language data, tools
  and standards
• Certification framework and infrastructure
• Localisation Factory

8
IGNITE
Performance analysis Standard verification and
enhancement
Performance analysis
Phase III
Phase III
Localisation Process Environment State-of-the-art
technologies and process environent
Phase II
Phase II
L i n g u i s t i c R e s o u r
c e s S u p p o r t N e t w o
r k
IGNITE
IGNITE
IGNITE
IGNITE
Linguistic Resources
Linguistic Resources
Consortium
Contact Group
Consortium
Contact Group
Phase I
Phase I
Language data
Tools
Standard
Language data
Tools
Standards
Digital content source/target
Terminology DBs
Digital content source/target
Terminology DBs
OASIS
OASIS
Terminologies
TM systems
Terminologies
TM systems
ISO
ISO
Examples
Examples
Translation memories
UI editors
Translation memories
UI editors
Unicode
Unicode W3C
9
Partners and Investors

• Coordinator
• University of Limerick, Localisation Research
  Centre (Ireland) contact Reinhard Schäler
• Contractors
• PASS GmbH (Germany) contact Florian Sachse
• Lionbridge VeriTest (Ireland) contact Deirdre
  Farrell
• Vivendi Universal Games (Ireland) contact
  Annette Lee
• Archetypon (Greece) contact George Boukis

10
The Localisation Factory

• Where we are today

11
Measure efficiency
Adding meta-data? Re-use? Archive Knowledge?
Why not use existing tools?
IGNITE
Localisation Factory Reference implementation
Middleware
UDDI host Connectivity (TransWS) Leverage XLIFF,
XLIFF repository XLIFF Editor Workflow control,
version management
I. If input not XLIFF Case 1 Convert material to
be translated Case 2 Convert material to be
referenced
Client
LSP
II. If input XLIFF
Translation or For reference
Control, Connectivity Reusability,
Interoperability
ALWAYS XLIFF Verification (input/output) by
IGNITE at entry/touch points
If NOT XLIFF Conversion (into/out of) IGNITE
certified valid XLIFF, valid representation,
localisable content check
Currently not considered
Complex
Simple
Tools
12
Introduction to IGNITE Factory

• Demonstrates IGNITE localisation process
• Intended to show the usefulness of standards in a
  localisation process
• In particular, shows the benefits of using XLIFF
  to both publishers and LSPs
• Demonstrates the application of automation to a
  localisation process
• Web application written in Java with MySQL and
  eXist database systems
• Presentation will comprise video clips and screen
  captures of the Factory in action

13
Clips Overview

• Clip One
• Log in as publisher
• Create project
• Clip Two
• View project list
• View project details
• Upload files
• Translatable
• Resource
• Screen capture one
• Close up of publisher file list
• Clip Three
• Annotation editor
• Clip Four
• Leverage XLIFF

• Screen captures LSP selection
• Clip Five
• Log in as LSP
• View LSP project details
• Screen captures LSP File Upload
• Clip Six
• Log in as publisher
• Go to project details page
• View translated file uploaded

14
Clip One Creating a new localisation project

• Logging on as a publisher and creating a new
  project
• Two types of user
• Publisher
• Localisation Service Provider (LSP)
• Project
• Collection of translatable, resource and
  translated files
• Project specific localisation requirements

15
Clip Two Project Details File Uploads

• Viewing new project details
• Information we specified during creation
• Uploading files
• From desktop to Factory
• Translatable, Resource and Translated
• Conversion
• From original file type to XLIFF
• Supported file types
• Original and XLIFF are stored
• Skeleton file
• Validation
• File details stored

16
Translatable File List

• Original file
• XLIFF conversion
• Leverage
• Annotation
• Deletion
• Translation

17
Clip Three Annotation of XLIFF files

• Annotation adding extra information to
  converted XLIFF documents
• Usefulness
• Safe editing XLIFF is kept consistent and valid
• Trans-units and groups
• What is a Note?

18
Clip Four Content Leveraging

• Automated leveraging of content
• Translatable files are leveraged against Resource
  files
• Leveraging technology fast and accurate
• Clip before and after leveraging
• New content added to XLIFF file

19
Assigning an LSP to the project

• Project is begun by assigning it to LSP
• LSP list generated on basis of languages
  required, other requirements
• LSP is selected
• This LSP now has access to the project

20
(No Transcript)
21
(No Transcript)
22
Clip Five LSP View

• Clip shows LSP view of project details
• LSP limited and additional functionality
• Downloads XLIFF
• Carries out localisation
• Uploads localised XLIFF file

23
Translated File Upload

• LSP can now upload translated XLIFF file
• Translation will become available to the
  Publisher
• Only LSP can upload translated XLIFF files

24
(No Transcript)
25
(No Transcript)
26
Clip Six Translated File

• LSP has uploaded translation
• Translated version of original file now available
• Reintegration of translation and skeleton file
• Process is complete

27
Future Plans

• Currently proof of concept
• Add more file converters for key localisation
  resource formats
• Expand annotation editor functionality
• Provide leveraging interface with improved
  leveraging algorithms
• Translation Web Services integration

28
Outlook

• Performance testing
• Implementation at partner sites
• Dissemination
• Exploitation
• Commercialisation

29
www.igniteweb.org

• LRC XI The Localisation Factory
• 25-26 October 2006
• European Foundation - Dublin