Translating Database Content with

Who We Are… CMS – Cross Media Solutions  is an independent software vendor from Würzburg, Germany.  Founded in 2006 from elements of the printing company Stürtz GmbH,  CMS has decades of experience in providing database solutions for publishers of technical and scientific documentation and industrial catalogs  Technology partners  My name is Steven Calkins.

What will be discussed… Translating Database Content with KITE  Introduction 1. Why is standardized database translation important? 2. Definition of terms  KITE: 1. Features 2. Advantages of XLIFF and KITE 3. Integration in workflow  Conclusion 1. Why is this issue urgent? 2. Decisions to be made

Why is standardized database translation important? Estimates put all the content stored in databases on the world wide web at more than 500 times the information available on the pages which can be found by popular search engines: Database “Dynamic Searchable Databases represent the Deep Web. The Deep Web is made up of hundreds of thousands of publicly accessible databases and is approximately 500 times bigger than the surface Web. At each Deep Web database, you enter a query and get back a Web page created dynamically (on-the-spot) specific to your search. These dynamic Web pages are not linked since they didn’t exist before your query and cease to exist after being sent to you — the search engines can't see nor find them.” * Using the Deep Web as a model of knowledge distribution we can infer that the vast majority of available knowledge is found in databases. Company information is generally stored in a database, typically an electronic resource planning (ERP) software. So if something needs localization, most likely the original source is found somewhere in a database. Search engines index only the surface web Database Surface Web Deep Web Database queries are not indexed * CMS – Cross Media Solutions GmbH is not responsible for the content of any links external to its own website.

Why is standardized database translation important?  Regulations have been increasing in recent years:  USA: Sarbanes-Oxley Act (finance documents).  EU: EU Directive 2006/42/EG (manuals, in 2009).  The people served by translations have greatly varying needs:  Designers & technicians need more “technical” documentation than normal product users do.

Can translation be accomplished with standard procedures?  For low-complexity, small volumes it can be done  With increasing volume and complexity, automated procedures become necessary  Human translators are absolutely necessary, but Translation Memory systems can help translators 1.translate consistently with proper vocabulary, 2.avoid translating the same terms twice.

Definition of terms TermMeaning TMSTranslation Memory Systems They work by looking up seg- ments in a database containing large numbers of previously translated segments with their translation. They provide matches that fit exactly or are similar to the term being trans- lated and display them as suggestions to the translator. SegmentsUnits of sensible translation, usually sentences. Database contents are well-suited for processing with TMS because the segmentation process can be virtually eliminated. * TMXTranslation Memory eXchange Format OSCAR standard (Open Standards for Container/Content Allowing Reuse, a committee of LISA -- the Localization Industry Standards Association) XLIFFXML Localization Interchange File Format OASIS standard KITEThe TMS of Cross Media Solutions implementing the TMX and XLIFF standards. Fully XLIFF compliant. * Still, the segmentation must not be lost in the database–XLIFF–database roundtrip process.

Features of  Localization of database contents  Translation memory functionality  Termbase functionality (TBX)  Scalable, suitable for very large XLIFF files  XLIFF 1.2 and TMX 1.4 support  for Mac OS X and Windows  Single-user and site licenses  Can be integrated in an outsourced workflow

 Translation memory functionality  Faster, more consistent and non-redundant translation  Vocabulary is project-oriented  It is not proprietary, it is open to all  Permits independent developments  Enables tight integration with extant systems Advantages of XLIFF and TMS

All the advantages of XLIFF and TMS, plus:  Preserves database content assignment  Contextual information available  Scalable, suitable for very large XLIFF files  XLIFF 1.2 and TMX 1.4 support  for Mac OS X and Windows  Low cost: Single-user and site licenses Advantages of

Views of

Start by opening a translation memory

Lucene-indexed folder containing translation memory. Details here.

Information about the translation memory may be inspected below

The translation memory may be manipulated in the TM menu:  Open a TM  Save the segments in the TM  Close the TM  Create a new TM  Import a TM from a TMX file  Export the TM to a TMX file

Once the proper TM is open, an XLIFF file may be edited.

Various meta-information is displayed about the selected XLIFF file before opening it. Note the language pair: German -> English

On the left side a tree view is displayed. This shows the content structure of the XLIFF file. Important: properly handles groups. Not every XLIFF system does this recursively. To our knowledge, only KITE is fully XLIFF compliant.

Other features: Approved translation pairs are colored green for easy identification Other features: Context information is displayed, notes can be inserted

Segments: Segments (translation pairs) can be edited in the Segment menu:  Approved  Not approved  Accept only 100% TM matches  Accept best match  Accept source (for terms not to be translated like proper names, technical terms, etc)

Explorer-like tree view can show group hierarchy to any depth

Matches for the translation units are suggested by the Translation Memory. Double-click transfers the suggestion to the target unit(s).

The button “Accept source text” transfers, e.g., technical terms from the source text without translating them. The button “Accept 100% match” transfers only 100% matches to any selected segments The button “Accept best match” also transfers the best TM suggestion to the segments

The translation memory is searchable: The search text is typed here. The quality here. The results are given here.

For a live demonstration, please visit CMS at Stand E10

How can be integrated into a workflow? The catalog data is found in a Product Information Management (PIM) system and an Electronic Resource Planning (ERP) system. Typically, the PIM system can extract information from the ERP and publish this data enriched with marketing texts online and in print. Where does KITE fit in?

How can be integrated into a workflow? Let assume the following task: a large online and print catalog is to be translated from German into English. The work is to be shared among outside translators and an internal translation department. 1.The internal department first exports the Translation Memory (TM) and XLIFF segments from the database. 2.All 100% matches are found in KITE so that no redundant translation is done. All available terms are now correctly assigned. 3.The XLIFF is re-imported into the database. 4.Now the XLIFF and TM are sent to an external translator, who receives only those segments that need translation.

How can save money? ERP Product Information Management XLIFF + TM export XLIFF + TMX XLIFF import Localized online and printed documentation generation, user manuals, catalogs XLIFF + TMX External translation service Internal translation dept.

Why is this issue urgent? The following cites the new EU directive 2006/42/EG. This directive will become effective : Instructions All machinery must be accompanied by instructions in the official Community language or languages of the Member State in which it is placed on the market and/or put into service… General principles for the drafting of instructions (b) Where no "Original instructions" exist in the official language(s) of the country where the machinery is to be used, a translation into that/those language(s) must be provided by the manufacturer or his authorised representative or by the person bringing the machinery into the language area in question. … (d) In the case of machinery intended for use by non-professional operators, the wording and layout of the instructions for use must take into account the level of general education and acumen that can reasonably be expected from such operators.

What decisions are necessary?  Does my company have large quantities of database information?  Will we be required to translate large sections of the database for technical documentation?  Should we use document-based translation?  What is the source of our company documentation?  Could automation help us? We would be glad to speak with you further on these issues at our stand (E10) or contact:

Thank you for your attention