Difference between revisions of "Assimilation and Dissemination"

From Apertium
Jump to navigation Jump to search
(wops!)
Line 17: Line 17:




One way of making MT systems more useful is to make their applications/use-cases more restricted<ref>Church and Hovy (1993), "[http://www.isi.edu/natural-language/people/hovy/papers/93churchhovy.pdf Good Applications for Crummy Machine Translation]"</ref>. The "ideal" MT system would do Fully Automatic High Quality MT of Unrestricted text between any language pair. No such system exists :-) The systems that are considered successful are the ones that have removed part of the ideal requirements. For example, [https://en.wikipedia.org/wiki/METEO_System Meteo] was successful already in the early 80's by translating only a restricted domain (weather reports). Some systems are successful because they focus on gisting, where the demand for quality is a lot lower (a reader won't mind much if you always leave out the word "the" when translating from Russian, whereas a post-editor would find it a chore). Apertium's focus has typically been on closely-related languages, here it's a lot easier to get post-editable-quality results.
One way of making MT systems more useful is to make their applications/use-cases more restricted<ref>Church and Hovy (1993), "[http://www.isi.edu/natural-language/people/hovy/papers/93churchhovy.pdf Good Applications for Crummy Machine Translation]"</ref>. The "ideal" MT system would do Fully Automatic High Quality MT of Unrestricted text between any language pair. No such system exists :-) The systems that are considered successful are the ones that have removed part of the ideal requirements. For example, [https://en.wikipedia.org/wiki/METEO_System Meteo] was successful already in the early 80's by translating only a restricted domain (weather reports). Some systems are successful because they focus on gisting, where the demand for quality is a lot lower (a reader won't mind much if you always leave out the word "the" when translating from Russian, whereas a post-editor would find it a chore). If we don't require translating between distant languages, the task of getting post-editable-quality results can be easier due to more overlap in vocabulary and syntax etc. (this has typically been Apertium's niche).





Revision as of 09:31, 13 June 2014

This buffer is for notes you don't want to save, and for Lisp evaluation.
If you want to create a file, visit that file with C-x C-f,
then enter the text in that file's own buffer.

MT systems are useful for mainly two tasks:[1]

  • creating almost-translated text that needs post-editing before being publishable, and
  • creating an understandable translation of a foreign text for getting the gist of some text.

In the gisting task the user does not know the foreign language, while in the post-editing task, the user is a translator who does know the foreign/source language (and will often be reading both the source text and the translation).


MT of post-editing quality into a lesser-resourced language can help with creating more text in that language. We call this dissemination.

MT of gisting quality from a lesser-resourced language can help with letting people who don't speak that language understand text (e.g. blogs, news articles) written in that language (thus removing an argument against writing in the lesser-resourced language). We call this assimilation.


One way of making MT systems more useful is to make their applications/use-cases more restricted[2]. The "ideal" MT system would do Fully Automatic High Quality MT of Unrestricted text between any language pair. No such system exists :-) The systems that are considered successful are the ones that have removed part of the ideal requirements. For example, Meteo was successful already in the early 80's by translating only a restricted domain (weather reports). Some systems are successful because they focus on gisting, where the demand for quality is a lot lower (a reader won't mind much if you always leave out the word "the" when translating from Russian, whereas a post-editor would find it a chore). If we don't require translating between distant languages, the task of getting post-editable-quality results can be easier due to more overlap in vocabulary and syntax etc. (this has typically been Apertium's niche).


Notes

  1. There are of course other practical uses, e.g. MT-supported language learning (see Geriouaeg).
  2. Church and Hovy (1993), "Good Applications for Crummy Machine Translation"