<?xml version="1.0" standalone="yes"?>
<Paper uid="A94-1006">
  <Title>Termight: Identifying and Translating Technical Terminology</Title>
  <Section position="7" start_page="37" end_page="38" type="concl">
    <SectionTitle>
4 Conclusions
</SectionTitle>
    <Paragraph position="0"> We have shown that terminology research provides a good application for robust natural language technology, in particular for part-of-speech tagging and word-alignment algorithms. Although the output of these algorithms is far from perfect, it is possible to extract from it useful information that is later corrected and augmented by a user. Our extraction algorithms emphasize completeness, and identify also infrequent candidates that may not meet some of the statistical significance criteria proposed in the literature. To make the entire process efficient, however, it is necessary to analyze the user's work process and provide interfaces that support it. In many cases, improving the way information is presented to the user may have a larger effect on productivity than improvements in the underlying natural language technology. In particular, we have found the following to be very effective: * Grouping linguistically related terms, making it easier to judge their validity.</Paragraph>
    <Paragraph position="1"> * Sorting candidates such that the better ones are found near the top of the list. With this sorting one's time is efficiently spent by simply going down the list as far as time limitations permit.</Paragraph>
    <Paragraph position="2"> * Providing quick access to relevant concordance lines to help identify incorrect candidates as well as terms or translations that are missing from the candidate list.</Paragraph>
    <Paragraph position="3">  bilingual concordance for each candidate. Typos are due to OCR errors. * Minimizing the number of required key-strokes.</Paragraph>
    <Paragraph position="4"> As the need for efficient knowledge acquisition tools becomes widely recognized, we hope that this experience with termight will be found useful for other text-related systems as well.</Paragraph>
  </Section>
class="xml-element"></Paper>