In linguistics, the term morphology refers to the study of the internal structure of words. Each word is assumed to consist of one or more morphemes, which can be defined as the smallest linguistic unit having a particular meaning or grammatical function. One can come across morphologically simplex words, i.e. roots, as well as morphologically complex ones, such as compounds or affixed forms.

Bati-li-las-tir-il-ama-yan-lar-dan-mis-iz west-With-Make-Caus-Pass-Neg.Abil-Nom-Pl-Abl-Evid-A3Pl 'It appears that we are among the ones that cannot be westernized.'

The morphemes that constitute a word combine in a (more or less) strict order. Most morphologically complex words are in the "ROOT-SUFFIX1-SUFFIX2-..." structure. Affixes have two types: (i) derivational affixes, which change the meaning and sometimes also the grammatical category of the base they are attached to, and (ii) inflectional affixes serving particular grammatical functions. In general, derivational suffixes precede inflectional ones. The order of derivational suffixes is reflected on the meaning of the derived form. For instance, consider the combination of the noun goz 'eye' with two derivational suffixes -lIK and -CI: Even though the same three morphemes are used, the meaning of a word like gozculuk 'scouting' is clearly different from that of gozlukcu 'optician'.

Here we present a new morphological analyzer, which is (i) open: The latest version of source codes, the lexicon, and the morphotactic rule engine are all available here, (ii) extendible: One of the disadvantages of other morphological analyzers is that their lexicons are fixed or unmodifiable, which prevents to add new bare-forms to the morphological analyzer. In our morphological analyzer, the lexicon is in text form and is easily modifiable, (iii) fast: Morphological analysis is one of the core components of any NLP process. It must be very fast to handle huge corpora. Compared to other morphological analyzers, our analyzer is capable of analyzing hundreds of thousands words per second, which makes it one of the fastest Turkish morphological analyzers available.

The morphological analyzer consists of five main components, namely, a lexicon, a finite state transducer, a rule engine for suffixation, a trie data structure, and a least recently used (LRU) cache.

In this analyzer, we assume all idiosyncratic information to be encoded in the lexicon. While phonologically conditioned allomorphy will be dealt with by the transducer, other types of allomorphy, all exceptional forms to otherwise regular processes, as well as words formed through derivation (except for the few transparently compositional derivational suffixes are considered to be included in the lexicon.

In our morphological analyzer, finite state transducer is encoded in an xml file.

To overcome the irregularities and also to accelerate the search for the bareforms, we use a trie data structure in our morphological analyzer, and store all words in our lexicon in that data structure. For the regular words, we only store that word in our trie, whereas for irregular words we store both the original form and some prefix of that word.

You can also see Python, Cython, C++, C, Swift, Js, or C# repository.

• Java Development Kit 8 or higher, Open JDK or Oracle JDK
• Maven
• Git

To check if you have a compatible version of Java installed, use the following command:

If you don't have a compatible version, you can download either Oracle JDK or OpenJDK

To check if you have Maven installed, use the following command:

To install Maven, you can follow the instructions here.

Install the latest version of Git.

In order to work on code, create a fork from GitHub page. Use Git for cloning the code to your local or below line for Ubuntu:

A directory called MorphologicalAnalysis will be created. Or you can use below link for exploring the code:

Steps for opening the cloned project:

• Start IDE
• Select File | Open from main menu
• Choose MorphologicalAnalysis/pom.xml file
• Select open as project option
• Couple of seconds, dependencies with Maven will be downloaded.

From IDE

After being done with the downloading and Maven indexing, select Build Project option from Build menu. After compilation process, user can run Morphological Analysis.

From Console

Go to MorphologicalAnalysis directory and compile with

From IDE

Use package of 'Lifecycle' from maven window on the right and from MorphologicalAnalysis root module.

From Console

Use below line to generate jar file:

• Creating FsmMorphologicalAnalyzer
• Word level morphological analysis
• Sentence level morphological analysis

FsmMorphologicalAnalyzer provides Turkish morphological analysis. This class can be created as follows:

This generates a new TxtDictionary type dictionary from turkish_dictionary.txt with fixed cache size 100000 and by using turkish_finite_state_machine.xml.

Creating a morphological analyzer with different cache size, dictionary or finite state machine is also possible.

• With different cache size,

  FsmMorphologicalAnalyzer fsm = new FsmMorphologicalAnalyzer(50000);


• Using a different dictionary,

  FsmMorphologicalAnalyzer fsm = new FsmMorphologicalAnalyzer("my_turkish_dictionary.txt");


• Specifying both finite state machine and dictionary,

  FsmMorphologicalAnalyzer fsm = new FsmMorphologicalAnalyzer("fsm.xml", "my_turkish_dictionary.txt") ;


• Giving finite state machine and cache size with creating TxtDictionary object,

  TxtDictionary dictionary = new TxtDictionary("my_turkish_dictionary.txt", new TurkishWordComparator());
FsmMorphologicalAnalyzer fsm = new FsmMorphologicalAnalyzer("fsm.xml", dictionary, 50000) ;


• With different finite state machine and creating TxtDictionary object,

  TxtDictionary dictionary = new TxtDictionary("my_turkish_dictionary.txt", new TurkishWordComparator(), "my_turkish_misspelled.txt");
FsmMorphologicalAnalyzer fsm = new FsmMorphologicalAnalyzer("fsm.xml", dictionary);


For morphological analysis, morphologicalAnalysis(String word) method of FsmMorphologicalAnalyzer is used. This returns FsmParseList object.

Output

From FsmParseList, a single FsmParse can be obtained as follows:

Output

morphologicalAnalysis(Sentence sentence) method of FsmMorphologicalAnalyzer is used. This returns FsmParseList[] object.

Output

1. Standard setup for packaging is similar to:

2. Only top level dependencies should be added. Do not forget junit dependency.

3. Maven compiler, gpg, source, javadoc plugings should be added.

4. Currently publishing plugin is Sonatype.

5. For UI jar files use assembly plugins.

1. Add resources to the resources subdirectory. These will include image files (necessary for UI), data files, etc.

1. Do not forget to comment each function.

2. Function names should follow caml case.

3. Write toString methods, if necessary.
4. Use Junit for writing test classes. Use test setup if necessary.