150 likes | 366 Views
Integrated Language Checker. Automation of Translation Quality Assurance :. First QA Tool for Languages with Flexions. By Dmitry Karpachev, Lead Project Manager and Quality Manager, Janus, Russia. Agenda. Introduction 1.1 Why automated QA tools are needed?
E N D
Integrated Language Checker Automation of Translation Quality Assurance: First QA Tool for Languages with Flexions By Dmitry Karpachev, Lead Project Manager and Quality Manager, Janus, Russia
Agenda • Introduction 1.1 Why automated QA tools are needed? 1.2 Overview of the current QA tools market • Introducing the first QA tool for languages with flexions - Integrated Language Checker (ILC) 2.1 Idea of developing ILC 2.2 About the tool 2.3 Setting up ILC 2.4 Using ILC 2.5 Analyzing the QA check results • ILC development in the future
Introduction 1.1 Why automated QA tools are needed? • Automated QA tools can help to assure the consistent terminology use which is an important prerequisite for high-quality localization of products • They help to lower the editing and proofreading costs within the localization process. Especially it’s important for MLVs (multi-language vendors) when localizing one product into several languages • Automated QA tools help to meet tight deadlines by identifying low-quality translations on an early project stage and correcting such mistakes without big pressure of time • With the help of these tools, a translation agency can “rate” its vendors and use only best-performing resources in the future
Introduction 1.2 Overview of the current QA tools market • ErrorSpy 3.5 by Dokumentation ohne Grenzen GmbH, Germany Checks: • Terminology • Tags • Numbers • Completeness • Acronyms • Typography • Formatting
Introduction 1.2 Overview of the current QA tools market • QA DistillerTM 5.5 by YAMAGATA EUROPE, Belgium Checks: • Terminology • Numbers • Inconsistencies • Omissions • Formatting
Introducing the first QA tool for languages with flexions - Integrated Language Checker (ILC) 2.1 Idea of developing ILC • As known, it’s very important and useful to make spot checks of a translation handed-back by a translator to ensure that the translation is of appropriate quality before passing it to a reviewer. One of the most important checks is to assure that terminology is translated according to a glossary and is consistent. • We tried to use many good tools that are perfectly suitable for checking tags, numbers, and punctuation. But unfortunately, we cannot find a QA tool that could appropriately check the terminology for a language with flexions (endings) like Russian, Ukrainian and some other European languages and don’t throw a lot of errors due to different endings. • So we decided to develop our own internal QA tool that among many other standard checks performed by another tools should check the terminology correctly. So was the Integrated Language Checker (ILC) born.
Introducing the first QA tool for languages with flexions - Integrated Language Checker (ILC) 2.2 About the tool Supported file formats • Segmented Trados files • TagEditor files • Logoport files Checks being performed • Terminology • Numbers • Inconsistencies • Tags (internal and external) • Punctuation • Hidden text in the translation • Brackets, double spaces and more
Introducing the first QA tool for languages with flexions - Integrated Language Checker (ILC) 2.3 Setting up ILC 3 easy steps to set-up: • Select the checks to be performed • Load a glossary file • Load a file with flexions
Introducing the first QA tool for languages with flexions - Integrated Language Checker (ILC) 2.4 Using ILC • Open one or multiple files to be checked: File -> Open file(s) • View the results in the left pane or in Microsoft Word and uncheck false errors • Save log file only with real errors and send it to the translator for analysis and correction
Introducing the first QA tool for languages with flexions - Integrated Language Checker (ILC) 2.5 Analyzing the QA check results • Analyzing the log file and correcting the errors on spot
ILC development in the future New features are planned: • Translation memory check • Support of other Translation Memory Software, like Transit. English version of GUI is being prepared
Contact Us • Do you have questions or suggestions? • Is my language supported? • Do you need additional information about the ILC? • Any feedback? • A very useful feature is missing… Can you add it in a future release? Please feel free to contact us: • by email management@janus.ru • by phone 007 (495) 913-6653 • by fax 007 (495) 913-6653 (ext. 299)