| { |
| "paper_id": "1984", |
| "header": { |
| "generated_with": "S2ORC 1.0.0", |
| "date_generated": "2023-01-19T01:11:19.681674Z" |
| }, |
| "title": "Machine Translation with Post Editing versus A Three-Level Integrated Translator Aid System", |
| "authors": [ |
| { |
| "first": "Alan", |
| "middle": [ |
| "K" |
| ], |
| "last": "Melby", |
| "suffix": "", |
| "affiliation": { |
| "laboratory": "", |
| "institution": "Brigham Young University Provo", |
| "location": { |
| "postCode": "84602", |
| "settlement": "Utah", |
| "country": "USA" |
| } |
| }, |
| "email": "" |
| } |
| ], |
| "year": "", |
| "venue": null, |
| "identifiers": {}, |
| "abstract": "The standard design for a computer-assisted translation system consists of data entry of source text, machine translation, and post editing (i.e. revision) of raw machine translation. This paper discusses this standard design and presents an alternative three-level design consisting of word processing integrated with terminology aids, simple source text processing, and a link to an off-line machine translation system. Advantages of the new design are discussed. THE STANDARD DESIGN FOR A COMPUTER-ASSISTED TRANSLATION SYSTEM.", |
| "pdf_parse": { |
| "paper_id": "1984", |
| "_pdf_hash": "", |
| "abstract": [ |
| { |
| "text": "The standard design for a computer-assisted translation system consists of data entry of source text, machine translation, and post editing (i.e. revision) of raw machine translation. This paper discusses this standard design and presents an alternative three-level design consisting of word processing integrated with terminology aids, simple source text processing, and a link to an off-line machine translation system. Advantages of the new design are discussed. THE STANDARD DESIGN FOR A COMPUTER-ASSISTED TRANSLATION SYSTEM.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Abstract", |
| "sec_num": null |
| } |
| ], |
| "body_text": [ |
| { |
| "text": "The standard design for a computer-assisted translation system consists of three phases: (A) data entry of the source text, (B) machine translation of the text, and (C) human post editing of the raw machine translation. Most machine translation projects of the past thirty years have used this design without questioning its validity, yet it may not be optimal. This section will discuss this design and some possible objections to it.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "The data entry phase may be trivial if the source text is available in machine-readable form already or can be optically scanned, or it may involve considerable overhead if the text must be entered on a keyboard and proofread.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "The actual machine translation is usually of the whole text. That is, the system is generally designed to produce some output for each sentence of the source text. Given current analysis systems, some sentences will not receive a full syntactic and semantic analysis, and so there will be a considerable variation in the quality of the output from sentence to sentence.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "Also, there may be several possible translations for a given word, even within the same grammatical category and subject matter, which may result in the system choosing one of the translations arbitrarily. That choice will, of course, sometimes be inappropriate. It is well-known that for these and other reasons, a machine translation of a whole text is usually of rather uneven quality. There is an alternative to translating the whole text -namely, \"selective translation\", a notion which will be discussed further later on.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "Revision of the raw machine translation by a human translator seems at first to be an attractive way to compensate for whatever errors may occur in the raw machine translation. However, revision is effective only if the raw translation is already nearly acceptable. Brinkmann (1980) concluded that even if only 20% of the text needs revision, it is better to translate from scratch instead of revising.", |
| "cite_spans": [ |
| { |
| "start": 266, |
| "end": 282, |
| "text": "Brinkmann (1980)", |
| "ref_id": "BIBREF2" |
| } |
| ], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "The author worked on a system with this standard design for a whole decade (from 1970 to 1980) . This design can, of course, work very well. The author's major objection is that the machine translation must be almost perfect or the system is nearly useless. In other words, the system does not become progressively \u2022 more useful as the output improves from being 50% correct to 60% to 70% to 80% to 90%. Instead, the system is nearly useless as the output improves and passes some threshold of quality. Then, all of a sudden, it becomes very useful. It would, of course, be preferable to work with a design which allows the system to become progressively more useful.", |
| "cite_spans": [ |
| { |
| "start": 75, |
| "end": 94, |
| "text": "(from 1970 to 1980)", |
| "ref_id": null |
| } |
| ], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "Here is a summary of objections to the standard design:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "Because even if the algorithms start out \"clean\", they must be \"kludged\" to make sure that something comes out for every sentence that goes in.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "WHY COMPUTATIONAL LINGUISTS DO NOT LIKE IT:", |
| "sec_num": null |
| }, |
| { |
| "text": "Because they feel that they are tools of the system instead of artists using tools.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "WHY TRANSLATORS DO NOT LIKE IT:", |
| "sec_num": null |
| }, |
| { |
| "text": "Because the system has to be worked on for a long time and be almost perfect before it can be determined whether or not any useful result will be obtained.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "WHY SPONSORS DO NOT LIKE IT:", |
| "sec_num": null |
| }, |
| { |
| "text": "There has been for some time a real alternative to the standard design -namely, translator aids. These translator aids have been principally terminology aids of various kinds and some use of standard word processing. These aids have been found to be clearly useful. However, they have not attracted the attention of computational linguists because they do not involve any really interesting or challenging linguistic processing. This is not to say that they are trivial. It is, in fact, quite difficult to perfect a reliable, user-friendly word processor or a robust, easy to use automated dictionary, especially if they must both be simultaneously visible on the same screen. But the challenge is more in the area of computer science and engineering than in computational linguistics.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "II AN ALTERNATIVE DESIGN", |
| "sec_num": null |
| }, |
| { |
| "text": "Until now, there has not been much real integration of work in machine translation and translator aids. This paper is a proposal for a system design which allows just such an integration. The proposed system consists of two pieces of hardware: (1) a translator work station (probably a single-user microcomputer) and (2) a \"selective\" machine translation system (probably running on a more powerful computer and serving multiple users). The translator work station is a three-level system of aids. All three levels look much the same to the translator. At each level, the translator works at the same keyboard and screen. The display is divided into two major windows. One window (which we will call the output window) contains a portion of the translated text. It is a human work area, and nothing goes in it except what the translator puts there. The other window (which we will call the input window) contains various helps such as dictionary entries, segments of source text, or suggested translations.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "II AN ALTERNATIVE DESIGN", |
| "sec_num": null |
| }, |
| { |
| "text": "To the translator, the difference between the various levels is simply the nature of the helps that appear in the input window; and the translator in all cases produces the translation a segment at a time in the output window. Internally, however, the three levels are vastly different. Level 1 is the lowest level of aid to the translator. At this level, there is no need for data entry of the source text. The translator can sit down with a source text on paper and begin translating immediately. The system at this level includes word processing of the target text, access to a local terminology file, and communications either with remote data bases of documents and terminology or with other translators. Level 2 is an intermediate level at which the source text must be available in machine readable form. It can be entered remotely and supplied to the translator (e.g. on a diskette) or it can be entered at the translator work station by a clerk. Level 2 provides all the aids available at level 1 and two additional helps -(a) preprocessing of the source text to search for unusual or misspelled terms, etc., and (b) dynamic processing of the source text as it is translated. The translator sees in the input window the current segment of text to be translated and suggested translations of selected words and phrases found by automatically identifying the words of the current segment of source text and looking them up in the bilingual dictionary that can be accessed manually in level 1.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "II AN ALTERNATIVE DESIGN", |
| "sec_num": null |
| }, |
| { |
| "text": "Level 3 requires a separate machine translation system and an interface to it. Instead of supplying just the source text to the translator work station, the work station receives (on diskette or through a network) the source text and (for each segment of source text) either a machine translation of the segment or an indication of the reason for failure of the machine translation system on that segment. This explains the notion of \"selective\" machine translation referred to previously. A selective machine translation system does not attempt to translate every segment of text. It contains a formal model of language which may or may not accept a given segment of source text. If a given segment fails in analysis, transfer, or generation, a reason is given. If no failure occurs, a machine translation of that segment is produced and a problem record is attached to the segment indicating difficulties encountered, such as words missing from the dictionaries and arbitrary syntactic and lexical choices made by the system.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "II AN ALTERNATIVE DESIGN", |
| "sec_num": null |
| }, |
| { |
| "text": "Level 3 provides to the translator all the aids of levels 1 and 2. In addition, the translator has the option of specifying a maximum acceptable problem level, called a tolerance level. When a segment of source text is displayed, if the machine translation of that segment has a problem level which is low enough, the machine translation of that segment will be displayed along with the source text, instead of the level 2 suggestions. The translator can examine the machine translation of a given segment and, if it is judged to be good enough by the translator, pull it into the output window with a keystroke or two and revise it as needed. If, on the other hand, a segment of machine translation slips through the problem check and yet is not worth revising, the translator can simply ignore it or request a level 2 display.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "II AN ALTERNATIVE DESIGN", |
| "sec_num": null |
| }, |
| { |
| "text": "Note that writing a selective machine translation system need not mean starting from scratch. It should be possible to take any existing machine translation system and modify it to be a selective translation system. And translator work stations can provide valuable feedback to the machine translation * development team by recording which segments of machine translation were seen by the translator and whether they were used and if so how revised. The standard design for a machine translation system and the alternative multi-level design just described use essentially the same components. They both involve data entry of the source text (although the data entry is needed only at levels 2 and 3 in the multi-level design). They both involve machine translation (although the machine translation is needed only at level 3 in the multi-level design) . And they both involve interaction with a human translator. In the standard design, this interaction consists of human revision of the raw machine translation. In the multilevel design, this interaction consists of both revision and human translation in which the human uses word processing, terminology lookup, and suggested translations from the computer. At one extreme (level 1), the multi-level system involves no machine translation at all, and the system is little more than an integrated word processor and terminology file. At the other extreme (level 3), the multi-level system could act much the same as the standard design. If every sentence of the source text received a machine translation with a low problem count and high quality, then the translation could conceivably be produced by the translator choosing to pull each segment of translated text into the output window and revise it as needed. The difference between the two designs becomes apparent only when the raw machine translation is not almost perfect. In that case, which is of course common, the multi-level system continues to produce translations with the human translator translating more segments using level 1 and level 2 aids instead of level 3 aids; the translation process continues with some loss of speed but no major difficulty. When the same raw machine translation is placed in a standard design context, the translator is expected to revise if in spite of the problems, and according to the author's experience, the translators tend to become frustrated and unhappy with their work. Both designs use the same components but put them together differently. See Figure 1 .", |
| "cite_spans": [], |
| "ref_spans": [ |
| { |
| "start": 2506, |
| "end": 2514, |
| "text": "Figure 1", |
| "ref_id": null |
| } |
| ], |
| "eq_spans": [], |
| "section": "II AN ALTERNATIVE DESIGN", |
| "sec_num": null |
| }, |
| { |
| "text": "Here is a summary of the arguments for a multi-level design:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "II AN ALTERNATIVE DESIGN", |
| "sec_num": null |
| }, |
| { |
| "text": "Because they can set up a \"clean\" formal model and keep it clean, because there is no undue pressure to produce a translation for every sentence that goes in.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "WHY COMPUTATIONAL LINGUISTS LIKE IT:", |
| "sec_num": null |
| }, |
| { |
| "text": "Because the system is truly a tool for the translator. The translator is never pressured to revise the machine output. Of course, if the raw machine translation of a sentence is very good and needs only a minor change or two, the translator will naturally pull it into the output window and revise it because that is so much faster and easier than translating from scratch.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "WHY TRANSLATORS LIKE IT:", |
| "sec_num": null |
| }, |
| { |
| "text": "Because the system is useful after a modest investment in level 1. Then level 2 is added and the system becomes more useful. While the system is being used at levels 1 and 2, level 3 is developed and the machine translation system can become a useful component of the multi-level system when only a small fraction of the source sentences receive a good machine translation. Thus, there is a measurable result obtained from each increment of investment.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "WHY SPONSORS LIKE IT:", |
| "sec_num": null |
| }, |
| { |
| "text": "The multi-level design grew out of a Naval Research Laboratory workshop the summer of 1981, a paper on translator aids by Martin Kay (1980) , and user reaction to a translator aid system (called a \"Suggestion Box\" aid) was tested on a seminar of translators fall 1981. A demonstration prototype including all three levels, with simulated machine translation being used at level 3, was completed and tested by another seminar of translators fall 1982. A commercial version is currently under development on an 8086/8088 microcomputer, written in C under the PC-DOS operating system.", |
| "cite_spans": [ |
| { |
| "start": 129, |
| "end": 139, |
| "text": "Kay (1980)", |
| "ref_id": "BIBREF4" |
| } |
| ], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "III IMPLEMENTATION EXPERIENCE AND PLANS", |
| "sec_num": null |
| }, |
| { |
| "text": "A project has recently been approved by the US NSF and the French CNRS to use ARIANE-78.4 as the level 3 machine translation component for a multi-level translator work station (See Boitet 1982) . Further papers will discuss the successes and disappointments of a multi-level translation system.", |
| "cite_spans": [ |
| { |
| "start": 182, |
| "end": 194, |
| "text": "Boitet 1982)", |
| "ref_id": "BIBREF1" |
| } |
| ], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "III IMPLEMENTATION EXPERIENCE AND PLANS", |
| "sec_num": null |
| } |
| ], |
| "back_matter": [], |
| "bib_entries": { |
| "BIBREF0": { |
| "ref_id": "b0", |
| "title": "Translation: Aids, Robots, and Automation", |
| "authors": [ |
| { |
| "first": "Alexander", |
| "middle": [], |
| "last": "Andreyewski", |
| "suffix": "" |
| } |
| ], |
| "year": 1981, |
| "venue": "META Translator's Journal", |
| "volume": "26", |
| "issue": "", |
| "pages": "1--57", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "ANDREYEWSKI, Alexander. 1981. Translation: Aids, Robots, and Automation. META Translator's Journal 26:1.57-66.", |
| "links": null |
| }, |
| "BIBREF1": { |
| "ref_id": "b1", |
| "title": "Implementation and Conversational Environment", |
| "authors": [ |
| { |
| "first": "Ch", |
| "middle": [], |
| "last": "Boitet", |
| "suffix": "" |
| }, |
| { |
| "first": "M", |
| "middle": [], |
| "last": "Guillaume", |
| "suffix": "" |
| }, |
| { |
| "first": "", |
| "middle": [], |
| "last": "Quezel-Ambrunaz", |
| "suffix": "" |
| } |
| ], |
| "year": 1982, |
| "venue": "", |
| "volume": "", |
| "issue": "", |
| "pages": "19--28", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "BOITET, Ch., Guillaume, and M. Quezel-Ambrunaz. 1982. Implementation and Conversational Environment, of ARIANE 78.4. COLING82, ed. by Jan Horecky, 19-28. Amsterdam: North Holland.", |
| "links": null |
| }, |
| "BIBREF2": { |
| "ref_id": "b2", |
| "title": "Terminology Data Banks as a Basis for High-Quality Translation. COLING80, Proceedings. Tokyo", |
| "authors": [ |
| { |
| "first": "Karl-Heinz", |
| "middle": [], |
| "last": "Brinkmann", |
| "suffix": "" |
| } |
| ], |
| "year": 1980, |
| "venue": "", |
| "volume": "", |
| "issue": "", |
| "pages": "", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "BRINKMANN, Karl-Heinz. 1980. Terminology Data Banks as a Basis for High-Quality Translation. COLING80, Proceedings. Tokyo.", |
| "links": null |
| }, |
| "BIBREF4": { |
| "ref_id": "b4", |
| "title": "The Proper Place of Men and Machines in Language Translation", |
| "authors": [ |
| { |
| "first": "Martin", |
| "middle": [], |
| "last": "Kay", |
| "suffix": "" |
| } |
| ], |
| "year": 1980, |
| "venue": "", |
| "volume": "", |
| "issue": "", |
| "pages": "", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "KAY, Martin. 1980. The Proper Place of Men and Machines in Language Translation, Palo Alto Research Center: Xerox Corporation.", |
| "links": null |
| }, |
| "BIBREF5": { |
| "ref_id": "b5", |
| "title": "Multi-level Translation aids in a Distributed System", |
| "authors": [ |
| { |
| "first": "Alan", |
| "middle": [ |
| "K" |
| ], |
| "last": "Melby", |
| "suffix": "" |
| } |
| ], |
| "year": 1982, |
| "venue": "", |
| "volume": "82", |
| "issue": "", |
| "pages": "215--220", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "MELBY, Alan K. 1982. Multi-level Translation aids in a Distributed System, COLING82, ed. by Jan Horecky, 215- 220. Amsterdam: North Holland.", |
| "links": null |
| }, |
| "BIBREF6": { |
| "ref_id": "b6", |
| "title": "Computer-Assisted Translation Systems: The Standard Design and a Multi-level Design", |
| "authors": [], |
| "year": 1983, |
| "venue": "Proceedings of the Conference on Applied Natural Language Processing", |
| "volume": "", |
| "issue": "", |
| "pages": "", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "_______ 1983. Computer-Assisted Translation Systems: The Standard Design and a Multi-level Design. Proceedings of the Conference on Applied Natural Language Processing (Santa Monica, February 1983). [The current paper is based on the Santa Monica paper, with permission.]", |
| "links": null |
| } |
| }, |
| "ref_entries": {} |
| } |
| } |
