<?xml version="1.0" standalone="yes"?>
<Paper uid="W91-0109">
  <Title>REVERSIBLE MACHINE TRANSLATION: WHAT TO DO WHEN THE LANGUAGES DON'T LINE UP</Title>
  <Section position="12" start_page="68" end_page="68" type="concl">
    <SectionTitle>
7 Conclusion
</SectionTitle>
    <Paragraph position="0"> In this paper, we have described an approach to machine translation that has three important properties: * It treats many problems of translation ntismatch and divergence as primarily problems of generation from a flexible semantic representation lahguage rather than as translation problems per se.</Paragraph>
    <Paragraph position="1"> * It relies exclusively on reversible, monolingual descriptions of all of the languages it treats. Although some comparisons of the source and target lexicons are required, they can be done;automatically (and cached if desired). No language-pair information must be explicitly provided.</Paragraph>
    <Paragraph position="2"> * It is stated in a way that enables its performance to in'crease steadily with the performance of the underlying knowledge base and reasoning system.</Paragraph>
    <Paragraph position="3"> This approach does, however, require some additional information that is not normally present either in monolingual NL systems or MT systems. Some of this information must be provided as part of the definition of each language. This includes: The labeling of syntactic assertions as forced or unforced. This information is only useful for MT, but it is very easy to provide.</Paragraph>
    <Paragraph position="4"> The labeling of marked/unmarked distinctions along various dimensions. This requires more work, but it is also useful even in purely monolingual generation systems, since they may be given sets of assertions for which there is no exact match.</Paragraph>
    <Paragraph position="5"> Some additional information must also be passed along during the understanding process. In particular, the grouping together of assertions that came from the same lexical item must be preserved. null</Paragraph>
  </Section>
class="xml-element"></Paper>