23.11.2013 Aufrufe

tekom-Jahrestagung 2012 - ActiveDoc

tekom-Jahrestagung 2012 - ActiveDoc

tekom-Jahrestagung 2012 - ActiveDoc

MEHR ANZEIGEN
WENIGER ANZEIGEN

Erfolgreiche ePaper selbst erstellen

Machen Sie aus Ihren PDF Publikationen ein blätterbares Flipbook mit unserer einzigartigen Google optimierten e-Paper Software.

Lokalisierung und Übersetzung / Localization<br />

LOC 17<br />

Presentation<br />

Automated monolingual term extraction<br />

through spelling check: a case study<br />

Uta Kreimeier, Olympus Soft Imaging Solutions GmbH, Münster<br />

Olympus Soft Imaging Solutions GmbH is a global supply unit for microscope<br />

image processing products within the Olympus group. It is<br />

based in Münster, Germany. The software solutions are produced in<br />

English and localized into several European and Asian languages.<br />

Regarding software localization, the company faces the following challenges:<br />

first, as the software solutions are used in science and research,<br />

e.g. life sciences and material sciences, a high percentage of specialized<br />

terminology from different areas has to be translated. In addition, each<br />

software product is highly customizable and many dialogs are created at<br />

run-time. As a result, many strings are difficult to translate because the<br />

localization tool cannot display sufficient context information (e.g. dialog<br />

preview). This leads to specialized terminology which is displayed<br />

in string lists in the localization tool.<br />

Second, the software is developed by an international and interdisciplinary<br />

development team. This can lead to language problems in the<br />

source language, which in turn can cause translation problems. The<br />

situation could be mitigated by using an adapted source language. In<br />

the localization tool, the English strings could be edited, and the resulting<br />

adapted source language could then be translated. However, this<br />

approach is not possible. Due to the number of people involved in each<br />

project, every string change has to be reflected in the software, the specification<br />

and the test plan. Furthermore, simship requires that software<br />

localization starts early, and source strings are still being changed during<br />

the localization stage. Consequently, language problems have to be<br />

reported with a bug tracking tool, even if there is just a simple spelling<br />

mistake.<br />

This situation is very inconvenient for both, software development and<br />

software localization. The specialized terminology without context leads<br />

to translators’ questions and translation problems. Spelling mistakes are<br />

often fixed at the end of the development phase and generate additional<br />

late string changes.<br />

A solution for the above challenges, the specialized terminology without<br />

context information and the spelling mistakes, is an automated spelling<br />

check with term extraction.<br />

A prerequisite for this approach is a localization tool that offers a functionality<br />

to mark whether a string is translatable or technical. The process<br />

of marking strings is automated through rules such as keywords<br />

that software developers supply in technical strings. These rules are the<br />

base of a nightly string build process, which separates translatable and<br />

technical strings and sends the results of a spelling check on translatable<br />

strings to the software developers.<br />

An automated spelling check is not acceptable unless it hardly returns<br />

any false positives. It is therefore of paramount importance to create<br />

and maintain a custom dictionary for the spelling check. The custom<br />

dictionary is generated from the terminology database. This results in<br />

a terminology database which contains entries that do not represent<br />

<strong>tekom</strong>-<strong>Jahrestagung</strong> <strong>2012</strong><br />

207

Hurra! Ihre Datei wurde hochgeladen und ist bereit für die Veröffentlichung.

Erfolgreich gespeichert!

Leider ist etwas schief gelaufen!