12.07.2015 Views

Topics in Language Resources for Translation ... - ymerleksi - home

Topics in Language Resources for Translation ... - ymerleksi - home

Topics in Language Resources for Translation ... - ymerleksi - home

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

212 Re<strong>in</strong>hard Schälerheavily <strong>in</strong> bespoke automated and web-based localisation solutions. We have describedone such model <strong>in</strong> our case study.Today’s challenge is twofold:1. The <strong>in</strong>dustry, supported by targeted publicly funded research must cont<strong>in</strong>ue tobuild an adequate l<strong>in</strong>guistic <strong>in</strong>frastructure <strong>for</strong> localisation, cover<strong>in</strong>g languagedata, tools and standards;2. Bespoke solutions must be moved <strong>in</strong>to a space where they become usable, accessibleand af<strong>for</strong>dable <strong>for</strong> the 75% of localisers made up of entrepreneurs andsmall and medium sised enterprise (SMEs) (Boucau 2006).The IGNITE project, co-funded by the European Union and its five consortiummembers, went some way <strong>in</strong> demonstrat<strong>in</strong>g what an adequate response to thechallenges of Localisation 2.0 could look like. Follow<strong>in</strong>g the development of theIGNITE Localisation Factory and Repository, a laboratory-based localisation environmentwas set up to evaluate their impact and per<strong>for</strong>mance on typical localisationprojects. The bus<strong>in</strong>ess process and the requirements of a “real-life” LocalisationService Provider (LSP), Archetypon S.A., provided an ideal test case tomeasure the per<strong>for</strong>mance and the impact of the IGNITE approach. Archetypon’sper<strong>for</strong>mance evaluation demonstrated that the IGNITE Factory and the supportof XLIFF and Trans-WS offered by it has the potential to supply real and comprehensivesolutions to a series of localisation challenges encountered today bylocalisers, among them: <strong>in</strong>teroperability between tools, support <strong>for</strong> the overall localisationworkflow and the necessity of localisation tool developers to support agrow<strong>in</strong>g number of different <strong>for</strong>mats <strong>in</strong> addition to a large number of proprietary<strong>in</strong>termediate <strong>for</strong>mats.The current IGNITE framework will be further developed follow<strong>in</strong>g the adviceof lead<strong>in</strong>g <strong>in</strong>ternational experts and <strong>in</strong> cooperation with support<strong>in</strong>g projects, suchas the “Localization4all” project at the University of Limerick (Localization4all2008). We have already embarked on a dual approach which <strong>in</strong>cludes universitybasedresearch and development as well as commercial exploitation <strong>for</strong> some ofIGNITE’s core components. There has been significant <strong>in</strong>terest <strong>in</strong> IGNITE’s potentialto provide an adequate response to the challenges of Localisation 2.0. One ofour <strong>in</strong>tentions is to <strong>in</strong>tegrate the IGNITE components with additional open sourcelocalisation technologies <strong>in</strong> an IGNITE Open Source Localisation Distribution thatwill not just become available to large mult<strong>in</strong>ationals but also to thousands of localisers<strong>in</strong> so-called “emerg<strong>in</strong>g markets”. This distribution will allow them to ga<strong>in</strong>access to state-of-the-art localisation technology and will, there<strong>for</strong>e, significantly<strong>in</strong>crease their capacity to not just offer cut-price localisation services to mult<strong>in</strong>ationalclients, but – much more significantly – also to start produc<strong>in</strong>g localisedversions of their native content.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!