Курсы машинного перевода для языков России/Session 4 - Revision history

Trondtr: moved Машинный перевод для языков России/Session 4 to Курсы машинного перевода для языков России/Session 4: ... to get a better structure.

2012-01-31T12:00:28Z

moved Машинный перевод для языков России/Session 4 to Курсы машинного перевода для языков России/Session 4: ... to get a better structure.

Hectoralos: /* Many to one */

2012-01-19T16:54:44Z

Many to one

Hectoralos: /* Translation equivalences */

2012-01-19T16:13:33Z

Translation equivalences

Hectoralos: /* Translation equivalences */

2012-01-19T16:10:13Z

Translation equivalences

Francis Tyers: Reverted edits by Enjo (Talk) to last revision by Francis Tyers

2012-01-11T14:12:49Z

Reverted edits by Enjo (Talk) to last revision by Francis Tyers

Enjo at 12:47, 11 January 2012

2012-01-11T12:47:58Z

Francis Tyers: /* One to many */

2012-01-09T15:43:12Z

One to many

Hectoralos: /* Dialect forms */

2012-01-09T15:34:50Z

Dialect forms

Francis Tyers: /* Dialect forms */

2012-01-09T15:31:31Z

Dialect forms

Francis Tyers: /* One to many */

2012-01-09T15:12:50Z

One to many

@@ Line 102: / Line 102: @@
 </pre>
-For the importance of direction restrictions, see [[/Session 7|Session 7]]. Now compile the dictionary and test the new entry:
+For the importance of direction restrictions, see [[Машинный_перевод_для_языков_России/Session_7|Session 7]]. Now compile the dictionary and test the new entry:
 <pre>

@@ Line 27: / Line 27: @@
 This is an example of a more-or-less one-to-one correspondence, the meanings for ''жаз'' in Kyrgyz and ''весна'' in Russian match up. However this is not always the case. Another possibility is that more than one word in the source language translates to a single word in the target language. For example, both of the Russian words ''вершина'' and ''небо'' can translate to ''тӳпе'' in Chuvash. In fact, the relationship between the words is many-to-many.
-For machine translation, to say that ''вершина'', ''небо'' and ''крыша'' all translate to ''тӳпе'' is not problematic. That ''saison'' can also translate to ''temporada'' and that ''тӳпе'' has three (or more) translations in Russian is problematic.
+For machine translation, to say that ''вершина'', ''небо'' and ''крыша'' all translate to ''тӳпе'' is not problematic. That ''тӳпе'' has three (or more) translations in Russian is problematic.
 Using part-of-speech information to disambiguate lexical relationships can reduce the problem, but not eliminate it entirely. Even after the part-of-speech has been disambiguated, one word may have many translations, as in the ''тӳпе'' example. So, how can this one-to-many translation problem be solved. The most obvious way is to choose the most frequent, or general translation &mdash; in this case ''тӳпе''.

@@ Line 29: / Line 29: @@
 For machine translation, to say that ''вершина'', ''небо'' and ''крыша'' all translate to ''тӳпе'' is not problematic. That ''saison'' can also translate to ''temporada'' and that ''тӳпе'' has three (or more) translations in Russian is problematic.
-Using part-of-speech information to disambiguate lexical relationships can reduce the problem, but not eliminate it entirely. Even after the part-of-speech has been disambiguated, one word may have many translations, as in the ''тӳпе'' example. So, how can this one-to-many translation problem be solved. The most obvious way is to choose the most frequent, or general translation &mdash; in this case ''xxx''.
+Using part-of-speech information to disambiguate lexical relationships can reduce the problem, but not eliminate it entirely. Even after the part-of-speech has been disambiguated, one word may have many translations, as in the ''тӳпе'' example. So, how can this one-to-many translation problem be solved. The most obvious way is to choose the most frequent, or general translation &mdash; in this case ''тӳпе''.
 Apertium currently has an experimental module to treat the problem of ''lexical selection'', that is choosing the most appropriate translation of a source language lexical form given its context, but the use of multiwords can also offer a partial solution, for example in the cases where there are frequent collocations which are exceptions to the general translation (for example, Spanish to French: ''estación del año'' → ''saison de l'année'').

@@ Line 1: / Line 1: @@
 {{TOCD}}
-Цель данного раздела - описать процесс лексической передачи и лексического выбора. В теоретической части будет более подробно рассказано почему передаваемый словарь (или двуязычный словарь) не всегда представляют собой просто соответствия между леммы/части речи одного языка и леммы/части речи другого языка. В практической части мы добавим три вида записи (введения данных), cannot always be just correspondences between lemmas/parts-of-speech in one language and lemmas/parts-of-speech in another. In the practice section, we will add three entries, a simple one-to-one entry, a many-to-one entry and a one-to-many entry.
+The objective of this session is to describe the process of lexical transfer and lexical selection. The theory section will cover some details of why a transfer lexicon (or bilingual dictionary) cannot always be just correspondences between lemmas/parts-of-speech in one language and lemmas/parts-of-speech in another. In the practice section, we will add three entries, a simple one-to-one entry, a many-to-one entry and a one-to-many entry.
-==Теория==
+==Theory==
-Существует два аспекта в лексической передаче, первый - выбор наиболее подходящего перевода, второй - выделение в записях особых характеристик, которые нужно the second is marking in the entries features which need to be inferred by transfer rules. Например, при выборе наиболее часто встречающегося перевода чувашского слова ''тӳпе'' на русский, когда есть несколько возможных вариантов, включая ''вершина'', ''крыша'' и ''небо'' мы выбираем первый. А при выборе единственного или множественного числа в переводе русского слова ''брюки'' на татарский (например, ''чалбар'', ''чалбарлар'') выбираем второй.
+There are two aspects to lexical transfer, the first is choosing the most adequate translation, the second is marking in the entries features which need to be inferred by transfer rules. For example, choosing the most frequent translation of the Chuvash word ''тӳпе'' into Russian, when there are several possible translations including ''вершина'', ''крыша'' and ''небо'' comes under the first. And deciding the number of the Russian word ''брюки'' when translating to Tatar (e.g. ''чалбар'', ''чалбарлар'') comes into the second.
 ===Translation equivalences===

@@ Line 1: / Line 1: @@
 {{TOCD}}
-The objective of this session is to describe the process of lexical transfer and lexical selection. The theory section will cover some details of why a transfer lexicon (or bilingual dictionary) cannot always be just correspondences between lemmas/parts-of-speech in one language and lemmas/parts-of-speech in another. In the practice section, we will add three entries, a simple one-to-one entry, a many-to-one entry and a one-to-many entry.
+Цель данного раздела - описать процесс лексической передачи и лексического выбора. В теоретической части будет более подробно рассказано почему передаваемый словарь (или двуязычный словарь) не всегда представляют собой просто соответствия между леммы/части речи одного языка и леммы/части речи другого языка. В практической части мы добавим три вида записи (введения данных), cannot always be just correspondences between lemmas/parts-of-speech in one language and lemmas/parts-of-speech in another. In the practice section, we will add three entries, a simple one-to-one entry, a many-to-one entry and a one-to-many entry.
-==Theory==
+==Теория==
-There are two aspects to lexical transfer, the first is choosing the most adequate translation, the second is marking in the entries features which need to be inferred by transfer rules. For example, choosing the most frequent translation of the Chuvash word ''тӳпе'' into Russian, when there are several possible translations including ''вершина'', ''крыша'' and ''небо'' comes under the first. And deciding the number of the Russian word ''брюки'' when translating to Tatar (e.g. ''чалбар'', ''чалбарлар'') comes into the second.
+Существует два аспекта в лексической передаче, первый - выбор наиболее подходящего перевода, второй - выделение в записях особых характеристик, которые нужно the second is marking in the entries features which need to be inferred by transfer rules. Например, при выборе наиболее часто встречающегося перевода чувашского слова ''тӳпе'' на русский, когда есть несколько возможных вариантов, включая ''вершина'', ''крыша'' и ''небо'' мы выбираем первый. А при выборе единственного или множественного числа в переводе русского слова ''брюки'' на татарский (например, ''чалбар'', ''чалбарлар'') выбираем второй.
 ===Translation equivalences===

← Older revision	Revision as of 12:00, 31 January 2012
(No difference)

@@ Line 127: / Line 127: @@
 ===One to many===
-For this section of the practical, you need to be in the <code>apertium-sme-fin</code> directory. The bilingual dictionary is <code>apertium-sme-fin.sme-fin.dix</code>
 <div style="float: right">
 {|class=wikitable
@@ Line 145: / Line 143: @@
 |}
 </div>
+For this section of the practical, you need to be in the <code>apertium-sme-fin</code> directory. The bilingual dictionary is <code>apertium-sme-fin.sme-fin.dix</code>
 In this subsection we will add some entries for lexical forms with more than one translation, and write lexical selection rules to select the non-default translations.

@@ Line 35: / Line 35: @@
 ===Dialect forms===
-Often it can be desirable to be able to translate dialect forms from one language into standard forms in another. For example, in Russian, the word ''мясо'' "meat" can be translated into Chuvash as ''аш'', ''какай'', оr ''аш-какай''. The first two translations are dialectal and used in the spoken language. The third is more standard and used in the written language.
+Often it can be desirable to be able to translate dialect forms from one language into standard forms in another. For example, in Russian, the word ''мясо'' "meat" can be translated into Chuvash as ''аш'', ''какай'', оr ''аш-какай''. The first two translations are considered more dialectal and mostly used in the spoken language. The third is more standard and preferred in the written language.
 ===Grammatical divergence===

@@ Line 155: / Line 155: @@
   <e c="ought to"><p><l>berret<s n="V"/><s n="IV"/></l><r>pitää<s n="V"/></r></p><par n="V_V"/></e>
   <e c="like (ela)"><p><l>liikot<s n="V"/><s n="IV"/></l><r>pitää<s n="V"/></r></p><par n="V_V"/></e>
-  <e c="get a foothold/grip"><p><l>coakcut<s n="V"/><s n="IV"/></l><r>pitää<s n="V"/></r></p><par n="V_V"/></e>
+  <e c="get a foothold"><p><l>coakcut<s n="V"/><s n="IV"/></l><r>pitää<s n="V"/></r></p><par n="V_V"/></e>
 </pre>
@@ Line 161: / Line 161: @@
 <pre>
-    <e r="LR"><p><l>galgat<s n="V"/><s n="IV"/></l><r>pitää<s n="V"/></r></p><par n="V_V"/></e>--><!-- skulle, should -->
+  <e r="LR"><p><l>galgat<s n="V"/><s n="IV"/></l><r>pitää<s n="V"/></r></p><par n="V_V"/></e>--><!-- skulle, should -->
 </pre>