Apertium has moved from SourceForge to GitHub.
If you have any questions, please come and talk to us on #apertium on irc.freenode.net or contact the GitHub migration team.

Starting a new language with HFST

From Apertium
Jump to: navigation, search

Contents

For information on how to install HFST, see HFST

This page is going to describe how to start a new language with HFST. There are some great references out there to the lexc and twol formalisms, for example the FSMBook, but a lot of them deal with the proprietary Xerox implementations, not the free HFST implementation.

While the actual formalisms are more or less identical, the commands used to compile them are not necessarily the same. HFST has a much more Unix-compatible philosophy. So we're going to take advantage of this. As most Indo-European languages, and isolating languages can be dealt with fairly easily in lttoolbox, we're going to deal with a language that is not from this family, and one that has more complex morphology that isn't easily dealt with in lttoolbox.

[edit] Preliminaries

A morphological transducer in HFST has two principle files, one is a lexc file. This defines how morphemes in the language are joined together, morphotactics. The other file can be a twol (two-level rules) or xfst (sequential rewrite rules) file. These describe what changes happen when these morphemes are joined together, morphographemics (or morphophonology). For example,

Morphotactics: wolf<n><pl>wolf + s
Morphographemics: wolf + swolves

Here we're going to deal with twol, the two-level rules. If you're interested in xfst, there is a nice tutorial on the Foma site.

In the next sections we're going to start with the lexicon (lexc file) then progress onto the morphographemics (twol file).

Make sure you have HFST3 compiled. You may also want to use apertium-init to start an minimal language module that will compile (python3 apertium-init.py foo --analyser=hfst where foo is the ISO 639-3 code for the language).

[edit] The language

The language we're going to model today — well, start to model — is Turkmen, a Turkic language spoken in Turkmenistan. The language pair we will supposedly be working on is Turkish--Turkmen. We're going to try and model the basic inflection (number, case) of the category of nouns. The basic inflection for Turkmen nouns is: Six cases, two numbers, and possessive. Suffixes can have different forms depending on if they are attached to a vowel ending stem, or a consonant ending stem.

[edit] Vowel harmony

Simplifying a lot,[1] we can say that stems in Turkmen can be one of two types, back-vowel stems, or front-vowel stems. Back-vowel stems, such as mugallym "teacher" only have back vowels, and front-vowel stems, such as kädi "pumpkin" have only front vowels. The back vowels in Turkmen are: a, y, o, and u. The front vowels are: ä, e, i, ö, and ü.

So, when adding a suffix to a stem, we need to know what vowels are in the stem in order to choose the right vowel to put in the suffix.

[edit] Number

Number in Turkmen can either be undefined (where there is no suffix) or plural, where the suffix is -lar or -ler. The first is used with back vowels, and the second with front vowels.

[edit] Case

We use a more compact representation below to show the suffixes for case. In between { and } are vowel alternations in the suffixes, and in between ( and ) are epentheses.

Case Suffix Usage Example
V C V C
Nominative Indicates the subject of the sentence pagta gazan
Genitive -n{y,i,u,ü}ň -{y,i,u,ü}ň Indicates possession pagtanyň gazanyň
Dative -{a,ä} , -n{a,e} -{a,e} Indirect object (directed action) pagta gazana
Accusative -n{y,i} -{y,i} Direct object pagtany gazany
Locative -(n)d{a,e} -d{a,e} Time/place pagtada gazanda
Ablative -(n)d{a,e}n -d{a,e}n Origin pagtadan gazandan

[edit] Full paradigm

Note: This does not include the possessive.

maşgala "family"
Case Singular Plural
Nominative maşgala maşgalalar
Genitive maşgalanyň maşgalalaryň
Dative maşgala maşgalalara
Accusative maşgalany maşgalalary
Locative maşgalada maşgalalarda
Ablative maşgaladan maşgalalardan
esger "soldier"
Case Singular Plural
Nominative esger esgerler
Genitive esgeriň esgerleriň
Dative esgere esgerlere
Accusative esgeri esgerleri
Locative esgerde esgerlerde
Ablative esgerden esgerlerden

[edit] Lexicon

So, after going through the little description above, let's start with the lexicon. The file we're going to make is called apertium-tuk.tuk.lexc, and it will contain the lexicon of the transducer. So open up your text editor.

[edit] The basics

The first thing we need to define are the tags that we want to produce. In lttoolbox, this is done through the <sdefs> section of the .dix file.

Multichar_Symbols

%<n%>   ! Noun
%<nom%> ! Nominative
%<pl%>  ! Plural

The symbols < and > are reserved in lexc, so we need to escape them with %

We also need to define a Root lexicon, which is going to point to a list of stems in the lexicon NounStems. The Root lexicon is analagous to the <section id="main" type="standard"> in lttoolbox:


LEXICON Root

NounStems ;

Now let's add our two words:

LEXICON NounStems

maşgala Ninfl ; ! "family"
esger Ninfl ;   ! "soldier"

First we put the stem, then we put the paradigm (or continuation class) that it belongs to, in this case Ninfl, and finally, in a comment (the comment symbol is !) we put the translation.

And define the most basic of inflection, that is, tagging the bare stem with <n> to indicate a noun:

LEXICON Ninfl

%<n%>: # ;

This LEXICON should go before the NounStems lexicon. The # symbol is the end-of-word boundary. It is very important to have this, as it tells the transducer where to stop.

[edit] Compiling

So, now we've got our basic lexicon, let's compile it and test it. We compile with hfst-lexc:

$ hfst-lexc apertium-tuk.tuk.lexc -o tuk.lexc.hfst

(If you do not have hfst-lexc installed, you have a problem -- probably you need to compile hfst with --enable-lexc, but in the meantime you can use hfst-lexc2fst in place of hfst-lexc.)

And we can test it both with hfst-fst2strings:

$ hfst-fst2strings tuk.lexc.hfst 
maşgala<n>:maşgala
esger<n>:esger

If you bootstrapped a language pair with apertium-init, then you can just run make to compile.

[edit] Continuation lexica

So, we've managed to describe that maşgala and esger are nouns, but what about the inflection. This is where continuation lexica come in. These are like paradigms in lttoolbox.

The basic morphotactics of the Turkmen noun is:

stem plural? possessive? case copula?

Where ? denotes optionality. We're just working with number and case here, so let's describe the inflection, first we can start with number. In the section of the file LEXICON Ninfl, add the following line:

%<n%>%<pl%>:%>l%{A%}r # ;

Phew, that looks pretty complicated!! Well, perhaps, but each part has it's reason, let's describe them:

Part Description
%<n%>%<pl%> The part on the left side defines the analysis, in this case noun, plural. Note, this is in contrast to lttoolbox, where the analysis is usually on the right side.
: The symbol : delimits the left and right sides (or surface side, and lexical side)
%>l%{A%}r This is the surface form, which is split into:
    %> The morpheme boundary delimiter (we'll talk about this later, but you put it in between morphemes where changes might happen.
    l%{A%}r The surface morpheme, in this case -lar or -ler
    %{A%} An "archivowel"... a placeholder for a vowel that can be either a or e
# The end of word boundary
; End of line

Part of the reason it looks complicated is all of the % symbols. If we remove them it looks far more readable:

<n><pl>:>l{A}r # ;

(You need to have them though)

For comparison, in lttoolbox (using · for morpheme boundary and <s n="A"/> for the {A}) for , this would look something like:

<e><p><l>·l<s n="A"/>r</l><r><s n="n"/><s n="pl"/></e>

So, we've added the first of our inflections, the plural. We need to do two things before we can test it. First we need to add %{A%} to the Multichar_Symbols section of the file, so scroll to the top and add it, you should get something like:

Multichar_Symbols

%<n%>   ! Noun
%<nom%> ! Nominative
%<pl%>  ! Plural

%{A%}   ! Archivowel 'a' or 'e'

Now save the file. The next thing we need to do is compile again:

$ hfst-lexc apertium-tuk.tuk.lexc -o tuk.lexc.hfst

And then we can test:

$ hfst-fst2strings tuk.lexc.hfst 
maşgala<n><pl>:maşgala>l{A}r
maşgala<n>:maşgala
esger<n><pl>:esger>l{A}r
esger<n>:esger

Ok, so this is cool, but it also kind of sucks, these aren't real surface forms. We'll never see esger>l{A}r in any text. The surface form we're looking for is esgerler. So how do we get that ?

[edit] Enter twol

The idea of twol is to take the surface forms produced by lexc and apply rules to them to change them into real surface forms. So, this is where we change -l{A}r into -lar or -ler.

What we basically want to say is "if the stem contains front vowels, then we want the front vowel alternation, if it contains back vowels then we want the back vowel alternation". And at the same time, remove the morpheme boundary. So let's give it a shot.

We're going to make a new file apertium-tuk.tuk.twol.

First we need to define the alphabet:

Alphabet
 A B Ç D E Ä F G H I J Ž K L M N Ň O Ö P R S Ş T U Ü W Y Ý Z
 a b ç d e ä f g h i j ž k l m n ň o ö p r s ş t u ü w y ý z
 %{A%}:a ;

You don't have to define the upper and lower case on separate lines, but it can help make it clearer.

We also want to define at this point, that whatever happens, we want to remove the morpheme boundaries %> from the surface forms, so add the following line just below the last line of lower case letters, and before the ;:

 %>:0 

Here, the left side is the morphotactic form, and the right side is the surface form. Doing %>:0 changes %> into 0, which is the same as deleting it. The 0 symbol is not output.

So, the final alphabet section will look like this:

Alphabet
 A B Ç D E Ä F G H I J Ž K L M N Ň O Ö P R S Ş T U Ü W Y Ý Z
 a b ç d e ä f g h i j ž k l m n ň o ö p r s ş t u ü w y ý z
 %{A%}:a %>:0  ;

Next we need to define some "sets" to work with, these are basically for giving mnemonics to features, like "front vowel" and "back vowel" which we want to refer to later in the rules:

Sets

Consonant = B Ç D F G H J Ž K L M N Ň P R S Ş T W Z
            b ç d f g h j ž k l m n ň p r s ş t w z ; 
Vowel =     A E Ä I O Ö U Ü Y Ý 
            a e ä i o ö u ü y ý ;
FrontVowel = Ä E I Ö Ü ä e i ö ü ;  
BackVowel = A Y O U a y o u ;
NonBack = Consonant FrontVowel %> ;
NonFront = Consonant BackVowel %> ; 

So now we've got everything set up, to add the rule, there is a new section, Rules:

Rules
  
"Front harmony in suffixes"
%{A%}:e <=> FrontVowel: NonBack:* %>: NonBack:* _ ;

The rule is basically saying: "A {A} is e if the previous letters are anything except back vowels, then there is a morpheme boundary, then there are no back vowels, and at some point there is a front vowel"

Next up, to compile the rule and test it:

$ hfst-twolc -R -i apertium-tuk.tuk.twol -o tuk.twol.hfst
Reading input from tuk.twol.
Writing output to tuk.twol.hfst.
Reading alphabet.
Reading sets.
Reading rules and compiling their contexts and centers.
Compiling and storing rules.
Compiling rules.
Storing rules.

[edit] With the power of intersecting composition!

In order to get the final transducer, what we need to do is combine the morphotactic model (lexc) with the morphographemic model (twol). There is a way of doing this called "intersecting composition" which is fairly efficient. There is also a tool in HFST called hfst-compose-intersect which is what we'll be using.

$ hfst-compose-intersect -1 tuk.lexc.hfst -2 tuk.twol.hfst -o tuk.autogen.hfst

Now we can test the final transducer:

$ hfst-fst2strings tuk.autogen.hfst
maşgala<n>:maşgala
maşgala<n><pl>:maşgalalar
esger<n>:esger
esger<n><pl>:esgerler

Great!! We have the desired forms.

[edit] Analysis and generation

The transducer we made above was for generation, but we can't yet use it with hfst-proc because of the format. If we want to use it with hfst-proc, all we need to do is change the format, with the following command:

$ hfst-fst2fst -O -i tuk.autogen.hfst -o tuk.autogen.hfst.ol

Now we should be able to generate both of our plurals:

$ echo "^maşgala<n><pl>$" | hfst-proc -g tuk.autogen.hfst.ol
maşgalalar

and

$ echo "^esger<n><pl>$" | hfst-proc -g tuk.autogen.hfst.ol
esgerler

But what if we want to analyse some words ? Well, then we need to invert the transducer. This is changing the left side to the right side, and the right side to the left side, let's do it in two stages so we can see the results:

$ hfst-invert -i tuk.autogen.hfst -o tuk.automorf.hfst

$ hfst-fst2strings tuk.automorf.hfst
maşgala:maşgala<n>
maşgalalar:maşgala<n><pl>
esger:esger<n>
esgerler:esger<n><pl>

As we can see, now the left side is the surface form, and the right side the analysis. Now just to convert the analyser to optimised lookup format:

$ hfst-fst2fst -O -i tuk.automorf.hfst -o tuk.automorf.hfst.ol

And do some analysis:

$ echo "maşgalalar" | hfst-proc tuk.automorf.hfst.ol
^maşgalalar/maşgala<n><pl>$

$ echo "esgerler" | hfst-proc tuk.automorf.hfst.ol
^esgerler/esger<n><pl>$

[edit] Troubleshooting

Here is a brief troubleshooting checklist for when you do something, but it isn't working:

  • Are all your multicharacter symbols defined ? Including archivowels/consonants. If you think you added them, triple check. This goes for problems in twol as well as in lexc.

[edit] Notes

  1. This is actually supercomplicated, but for this didactic example, it'll do

[edit] See also

Personal tools