Apertium New Language Pair HOWTO - Revision history

TommiPirinen: /* Monolingual dictionaries */

2021-02-22T16:14:28Z

Monolingual dictionaries

Khannatanmai: /* Transfer rules */ probably more intuitive than the earlier way of representing the patterns

2020-05-10T13:12:10Z

Transfer rules: probably more intuitive than the earlier way of representing the patterns

Beboppinbobby: /* Monolingual dictionaries */

2020-01-09T19:48:49Z

Monolingual dictionaries

Beboppinbobby: Undo revision 71028 by Beboppinbobby (talk)

2020-01-09T19:34:13Z

Undo revision 71028 by Beboppinbobby (talk)

Beboppinbobby: /* Monolingual dictionaries */

2020-01-09T19:32:29Z

Monolingual dictionaries

Ashwaths: /* A brief note on terms */

2019-03-03T09:11:32Z

A brief note on terms

Ashwaths: /* What does a language pair consist of? */

2019-03-03T09:09:06Z

What does a language pair consist of?

Sushain: /* You will need */

2018-04-09T23:45:09Z

You will need

Putti: /* See also */

2017-05-28T16:34:48Z

Rcrowther: Better generality referencing

2017-04-27T16:08:20Z

Better generality referencing

@@ Line 184: / Line 184: @@
 At this stage, the command should produce the same output.
-We can now test these. Run lt-proc on the analyser.
+We can now test these. Run lt-proc on the analyser; echo "gramofoni" (gramophones) at it, and see the output:
-<pre>
-$ lt-proc hbs-eng.automorf.bin
-</pre>
-Now try it out, type in "gramofoni" (gramophones), and see the output:
 <pre>
+$ echo gramofoni | lt-proc hbs-eng.automorf.bin
 ^gramofoni/gramofon<n><pl>$
 </pre>

@@ Line 324: / Line 324: @@
 </pre>
-The first tag is obvious, it defines a rule. The second tag, pattern basically says: "apply this rule, if this pattern is found". In this example the pattern consists of a single noun (defined by the category item nom). Note that patterns are matched in a longest-match first. So, say you have three rules, the first catches "<prn><vblex><n>", the second catches "<prn><vblex>" and the third catches "<n>". The pattern matched, and rule executed would be the first one.
+The first tag is obvious, it defines a rule. The second tag, pattern basically says: "apply this rule, if this pattern is found". In this example the pattern consists of a single noun (defined by the category item nom). Note that patterns are matched in a longest-match first. So, say you have three rules, the first catches the pattern: <code><prn> <vblex> <n></code>, the second catches <code><prn> <vblex></code> and the third catches <code><n></code>. The pattern matched, and rule executed would be the first one.
 For each pattern, there is an associated action, which produces an associated output, out. The output, is a lexical unit (lu).

@@ Line 116: / Line 116: @@
 <?xml version="1.0" encoding="UTF-8"?>
 <dictionary>
+   <alphabet>ABCČĆDDžĐEFGHIJKLLjMNNjOPRSŠTUVZŽabcčćddžđefghijklljmnnjoprsštuvzž</alphabet>
    <sdefs>
      <sdef n="n"/>
@@ Line 131: / Line 132: @@
 Now we've got the skeleton in place, we can start by adding a noun. The noun in question will be 'gramofon' (which means 'gramophone' or 'record player').
-The first thing we need to do, as we have no prior paradigms, is to define a paradigm.
+The first thing we need to do, as we have no prior paradigms, is to define a paradigm inside the <pardefs> tag.
 Remember, we're assuming masculine gender and nominative case. The singular form of the noun is 'gramofon', and the plural is 'gramofoni'. So:

@@ Line 187: / Line 187: @@
 $ lt-proc hbs-eng.automorf.bin
 </pre>
-Now try it out, type in <pre>gramofoni</pre> (gramophones), and see the output:
+Now try it out, type in "gramofoni" (gramophones), and see the output:
 <pre>
 ^gramofoni/gramofon<n><pl>$

@@ Line 187: / Line 187: @@
 $ lt-proc hbs-eng.automorf.bin
 </pre>
-Now try it out, type in gramofoni (gramophones), and see the output:
+Now try it out, type in <pre>gramofoni</pre> (gramophones), and see the output:
 <pre>
 ^gramofoni/gramofon<n><pl>$

@@ Line 49: / Line 49: @@
 There are number of terms that will need to be understood before we continue.
-The first is ''[[lemma]]''. A lemma is the citation form of a word. It is the word stripped of any grammatical information. For example, the lemma of the word cats is ''cat''. In English nouns this will typically be the singular form of the word in question. For verbs, the lemma is the infinitive stripped of to, e.g. the lemma of ''was'' would be ''be''.
+The first is ''[[lemma]]''. A lemma is the citation form of a word. It is the word stripped of any grammatical information. For example, the lemma of the word cats is ''cat''. In English nouns, this will typically be the singular form of the word in question. For verbs, the lemma is the infinitive stripped of to, e.g., the lemma of ''was'' would be ''be''.
 The second is ''symbol''. In the context of the Apertium system, symbol refers to a grammatical label. The word cats is a plural noun, therefore it will have the noun symbol and the plural symbol. In the input and output of Apertium modules these are typically given between angle brackets, as follows:
@@ Line 58: / Line 58: @@
 Other examples of symbols are <sg>; singular, <p1> first person, <pri> present indicative, etc (see also: [[list of symbols]]). When written in angle brackets, the symbols may also be referred to as tags. It is worth noting that in many of the currently [[List of language pairs|available language pairs]] the symbol definitions are acronyms or contractions of words in Catalan. For example, vbhaver — from vb (verb) and haver ("to have" in Catalan). Symbols are defined in <sdef> tags and used in <nowiki><s></nowiki> tags.
-The third word is ''paradigm''. In the context of the Apertium system, paradigm refers to an example of how a particular group of words inflect. In the morphological dictionary, lemmas (see above) are linked to paradigms that allow us to describe how a given lemma inflects without having to write out all of the endings.
+The third word is ''paradigm''. In the context of the Apertium system, paradigm refers to an example of how a particular group of words inflects. In the morphological dictionary, lemmas (see above) are linked to paradigms that allow us to describe how a given lemma inflects without having to write out all of the endings.
 An example of the utility of this is, if we wanted to store the two adjectives ''happy'' and ''lazy'', instead of storing two lots of the same thing:

@@ Line 31: / Line 31: @@
 # [[Bilingual dictionary]]: contains correspondences between words and symbols in the two languages. In our example this will be called: <code>apertium-hbs-eng.hbs-eng.dix</code>
-In a translation pair, both languages can be either source or target for translation, these are relative terms.
+In a translation pair, both languages can be either source or target for translation; these are relative terms.
-There are also files for transfer rules in either direction. These are the rules that govern how words are re-ordered in sentences, e.g. ''chat noir'' → ''cat black'' → ''black cat''. It also governs agreement of gender, number etc. The rules can also be used to insert or delete lexical items, as will be described later. These files are:
+There are also files for transfer rules in either direction. These are the rules that govern how words are re-ordered in sentences, e.g. ''chat noir'' → ''cat black'' → ''black cat''. It also governs agreement of gender, number, etc. The rules can also be used to insert or delete lexical items, as will be described later. These files are:
 * language xxx to language yyy transfer rules: this file contains rules for how language xxx will be changed into language yyy. In our example this will be: <code>apertium-hbs-eng.hbs-eng.t1x</code>

@@ Line 18: / Line 18: @@
 * to install Apertium core, usually [[Install Apertium core using packaging]]
 * install a new, empty, language pair [[How to bootstrap a new pair]]
-* a text editor (or a specia1ised [[XML editors|XML editor]] if you prefer)
+* a text editor (or a specalised [[XML editors|XML editor]] if you prefer)
 This document will not describe how to install these packages, nor the new language framework. For general information please see also [[Installation]].

@@ Line 726: / Line 726: @@
 *[[Building dictionaries]]
-*[[Finding_errors_in_dictionaries]]
+*[[Finding_errors_in_dictionaries|Finding errors in dictionaries]]
 *[[Cookbook]]
 *[[Chunking]]

@@ Line 38: / Line 38: @@
 * language yyy to xxx language transfer rules: this file contains rules for how language yyy will be changed into language xxx. In our example this will be: <code>apertium-hbs-eng.eng-hbs.t1x</code>
-Many of the language pairs currently available have other files, but we won't cover them here. If you want to know more about the other files, or the overall process, see [[[Documentation]], especially the [Workflow diagram]]
+Many of the language pairs currently available have other files, but we won't cover them here. If you want to know more about the other files, or the overall process, see [[Documentation]], especially the [[Workflow diagram]]
-and [[Workflow reference]]. These '.dix' and '.t1x'/'.t2x' files are the only ones required to generate a functional system.
+and [[Workflow reference]]. But the '.dix' and '.t1x'/'.t2x' files are the only ones required to generate a functional system.
 ==Language pair==