<?xml version="1.0" encoding="UTF-8"?>
<modsCollection xmlns="http://www.loc.gov/mods/v3">
<mods ID="group-koch-1993-machine">
    <titleInfo>
        <title>Machine translation and terminology database - uneasy bedfellows?</title>
    </titleInfo>
    <name type="personal">
        <namePart type="given">Machine</namePart>
        <namePart type="given">Translation</namePart>
        <namePart type="family">Group</namePart>
        <role>
            <roleTerm authority="marcrelator" type="text">author</roleTerm>
        </role>
    </name>
    <name type="personal">
        <namePart type="given">Katharina</namePart>
        <namePart type="family">Koch</namePart>
        <role>
            <roleTerm authority="marcrelator" type="text">author</roleTerm>
        </role>
    </name>
    <originInfo>
        <dateIssued>1993-apr&quot; 26–28&quot;</dateIssued>
    </originInfo>
    <typeOfResource>text</typeOfResource>
    <relatedItem type="host">
        <titleInfo>
            <title>Third International EAMT Workshop: Machine Translation and the Lexicon</title>
        </titleInfo>
        <originInfo>
            <publisher>Springer Berlin Heidelberg</publisher>
            <place>
                <placeTerm type="text">Heidelberg, Germany</placeTerm>
            </place>
        </originInfo>
        <genre authority="marcgt">conference publication</genre>
        <identifier type="isbn">3-540-59040-4</identifier>
    </relatedItem>
    <abstract>The software company SAP translates its documentation into more than 12 languages. To support the translation department, SAPterm is used as a traditional terminology database for all languages, and the machine translation system METAL for German-to-English translation. The maintenance of the two terminology databases in parallel, SAPterm and the METAL lexicons, requires a comparison of the entries in order to ensure terminological consistency. However, due to the differences in the structure of the entries in SAPterm and METAL, an automatic comparison has not yet been implemented. The search for a solution has led to the consideration of using another existing SAP tool, called Proposal Pool.</abstract>
    <identifier type="citekey">group-koch-1993-machine</identifier>
    <location>
        <url>https://aclanthology.org/1993.eamt-1.9</url>
    </location>
    <part>
        <date>1993-apr&quot; 26–28&quot;</date>
        <extent unit="page">
            <start>131</start>
            <end>140</end>
        </extent>
    </part>
</mods>
</modsCollection>

%0 Conference Proceedings
%T Machine translation and terminology database - uneasy bedfellows?
%A Group, Machine Translation
%A Koch, Katharina
%S Third International EAMT Workshop: Machine Translation and the Lexicon
%D 1993
%8 apr" 26–28"
%I Springer Berlin Heidelberg
%C Heidelberg, Germany
%@ 3-540-59040-4
%F group-koch-1993-machine
%X The software company SAP translates its documentation into more than 12 languages. To support the translation department, SAPterm is used as a traditional terminology database for all languages, and the machine translation system METAL for German-to-English translation. The maintenance of the two terminology databases in parallel, SAPterm and the METAL lexicons, requires a comparison of the entries in order to ensure terminological consistency. However, due to the differences in the structure of the entries in SAPterm and METAL, an automatic comparison has not yet been implemented. The search for a solution has led to the consideration of using another existing SAP tool, called Proposal Pool.
%U https://aclanthology.org/1993.eamt-1.9
%P 131-140

Markdown (Informal)

[Machine translation and terminology database - uneasy bedfellows?](https://aclanthology.org/1993.eamt-1.9) (Group & Koch, EAMT 1993)

• Machine translation and terminology database - uneasy bedfellows? (Group & Koch, EAMT 1993)

ACL

• Machine Translation Group and Katharina Koch. 1993. Machine translation and terminology database - uneasy bedfellows?. In Third International EAMT Workshop: Machine Translation and the Lexicon, pages 131–140, Heidelberg, Germany. Springer Berlin Heidelberg.