SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez nos Conditions d’utilisation et notre Politique de confidentialité.
SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez notre Politique de confidentialité et nos Conditions d’utilisation pour en savoir plus.
CHALLENGES: 1. CAT EXPENSES.Localization Process Complicationand Rise in PriceAlmost every CAT now has its Term Management System.Investment in CAT:• purchasing,• examination,• resources training (and forcing to use a new CAT),• implementation into the workflow,• your translation price indirectly includes the client’s expenditures on theparticular CAT.
Benefits & cost reduction Independence from CAT-tools No need to train resources for each new TM tool No need to convert glossaries between CATs Easy involvement of smart customers in localization processes More contacts and relationships with customer Prompt understanding and approving => less terminology corrections => save time &money Product community involvement if required It’s hardly possible to integrate product users into the CAT tools, but it’s easy in unifiedterminology storageSOLUTIONS: 1.Unified TerminologyStorage & Management
CHALLENGES: 2. Term miningGood glossary looks like But usual glossary is more like…
USUAL ILLUSIONS ON TERMINOLOGYNo glossary => No pain?No glossary => More pain:Without a terminology management system Terminology is hardly controlled Translation is inconsistent Errors are easily propagated and hardly foundIn localization projects each term should be: Additional support point Low cost checkpoint
CHALLENGES: 2. Term miningUsual ways: Term extraction utilities, based on statistical methods Manual gathering from bilingual contentUsual problem:Reducing costs on terminology gathering.
Features Integration with: web dictionaries encyclopedias terminology portals Minimization of user manual activityBenefits Fast finding of the term value: Convenient Reply-on-Click operability No need to learn ways of glossaries connectionSOLUTIONS: 2. Special UtilitiesTime savingsEconomy
USUAL ILLUSIONS ON TERMINOLOGYTerminology is already in TM, no need to create a separate glossary?Without a derived glossaryyou face a severe problem of choice at the very first occurrence of any term:Which translation of the term to pick from the TM? More recent?And if there’s no history for the term and no adding time specified?And what about the context? Is it the same in the TM or different?And what about the meaning of the term? Its concept? “Ask Google”?…To make your localization life easier, store the glossary separately.
The Glossary you gathered and saved in the Unified Storageis your Intellectual Assetthat may be successfully reused again and again.because it is stored independently from CAT-tools.SOLUTIONS: 2. Terminology mining.Results
CHALLENGES: 3. Overweight glossariesIf the client sends you 10 000 “terminologically relevant” strings, how canyou treat them properly? Will you ask you translator and editor to remember all those stringswhile processing the translatable text? Are you sure they will keep such amounts of terms in mind? Do you think they are able to successfully apply them? How much of your budget are you going to spend on this pseudo-control?
SOLUTIONS: 3. Proper attitudeIncludes: Term concepts (UI, product-specific, DNT, etc.) and definitions Confidence levels for terms: which translation you should trust? History: tracking of term changes in the unified storage. You need to know,who changed the term and when to understand, which one to apply and whyto avoid corporate risks Smooth synchronization of glossary changes: spreading the info amonglocalization team (for example, you need to urgently notify the translators ofclient’s latest term changes. Will you send Excel sheets? What will you do, ifthey store the glossaries offline in CAT project files on their PCs?) Comments: for example, if you don’t protocol reviewer’s approved termchanges, you would be hardly able to prove to client that your version hadbeen initially correct and changed to incorrect by other team afterwards Discussion: reading the team’s discussion on terms helps you (and customer!)solve the problem of choice
CHALLENGES: 4. Which attitude to choose?The most frequently used terminology (management) tools as perJoanna Gough from the University of Surrey, 2012• SDL Multiterm (14,7%)• ApSIC Xbench (4,5%)• TermStar (3,8%)Other popular solutions• Kilgray qTerm• ITI multiQA.com• Interverbum Termweb• MultiCorpora MultiTrans Prism• CSOFT Termwiki• INTERPLEX• etc.0246810121416SDLMultitermApSIC Xbench TermStarTool
SOLUTIONS: 4.Formulate and Prioritize your needsLearning the glossary byeditors andterminologistsEveryday notificationson changesTerminological plug-ins(Financial) incentivesfor users properlyenhancing the glossaryMay excludeGeneralitiesDifferent language pairsand projectsRollback to particulardateUser Management(notifications, subscriptions, etc.)Amount of termsadded by particularuserInclude on demandSource and TargetContextConceptTerm ConfidenceLevelHistory of changesGlossaries’ hierarchy:branches, clonesIncludeTerm Mining(crowd source)Integration with QA
SOLUTIONS: 4. ExamplesHistoryof changesExample. Was the term the client’s reviewer claims youwrongly used already in the provided glossary?At the moment of review the term was there.But at the moment of translation it wasn’t. How will you proveyour position to save your reputation? Search through e-mails?And if you occasionally don’t have those in your inbox?In such case you obviously needlogs from your TMS with info onwho, when and why hasimported the “harmful” term.Rollback toparticular date
SOLUTIONS: 4. ExamplesExample. No terminology on significant project. No time and/or budget for terminologists or additional term mining stage.Will you ‘blindly’ proceed with localization-without-terminology finding yourself at the minefield?Translators and editors of any team always investigateterminology while doing their job. If they have an option ofon-click adding of the term into glossary, why not give thema chance?(Financial)incentives for usersproperly enhancingthe glossaryIn such case you may consider token payment for valid termaddition to user who inserted it.Amount of termsadded by userKey PerformanceIndicators
SOLUTIONS: 4. ExamplesExample. You have got the brilliant glossary on the projectand your client has kindly approved the terminology.How can you check that the terms are translated properlythroughout the translation?In such case you need your unified terminology system toeasily interact with QA-tool to build a terminology checkreport on the selected glossary.Integrationwith QA-tool
SOLUTIONS: 4. ExamplesExample. Multilingual project. Lack of termsin one of the languages in TMS (new teaminvolved). Give the team a chance to see theexamples of other languages.In such case you would need multilingualglossary with concepts for users to considerthe meanings of the terms.Example. Good release of English version ofthe product. Reduce time spent onachieving same results in other languages.Thus you need unified multilingual “multi-user” tool.Different languagepairs and projectsConcept
SOLUTIONS: 4. ExamplesExample. In particular automotive project, let’s sayBentley, appears the general important term which needs tobe used in other automotive projects. Will you copy andpaste it to another glossary? And waste time onpropagation?In such case you need to have the clear hierarchy ofglossaries and cloning option of a term or the wholeglossary into another.Glossaries’hierarchy:branches,clonesExample. Managing a set of glossaries at oneproject. If your client has sophisticatedrequirements to control, forinstance, terminology of 4 glossaries stages (oreven different glossaries), will you have andtrack 4 different copies and thus complicate theQA process?In such case it’s better own 1 growing copywith an option to perform QA on selectedbranch (1 or more of 4).
USUAL ILLUSIONS ON TERMINOLOGYMy Terminology Management Tool already supports all languages.Enough for proper terminology control.?Choose the tool with minimum level of false positives interminology QA procedures.In languages with flexions Linguistic Support in TMS must not meanonly storage,but associated Quality Assurance procedures.
SummaryThe most effective way to make your terminology fit isthe right choice of the Tool or TMS, which covers all ofyour terminological requirements.Terms live their own life, from birth (meaning offeredterm status) to death (meaning obsolete), and youneed to know how to treat them properly to makethem fit and working.But regardless the tool the thingyou can’t exclude fromterminology management is thework of the person, who makesterminological decisions.
P.S.Taking into consideration the growing variety ofTerminology Management tools and systems, the bestsolution could be using required term managementoptions and facilities through API.Then all the tools could successfully interact, combiningtheir functions to better the localization world. But that’s a kind of utopia, isn’t it?..