Difference between revisions of "Starting a new language with lttoolbox"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
==Preliminaries== |
==Preliminaries== |
||
A morphological transducer in lttoolbox has typically one file, a <code>.dix</code> file. This defines both how morphemes in the language are joined together, ''morphotactics'', and how changes happen when these morphemes are joined together, ''morphographemics'' (or ''morphophonology''). For example, |
|||
* Morphotactics: wolf<n><pl> → wolf + s |
|||
* Morphographemics: wolf + s → wolves |
|||
These two phenomena are treated in the same file. |
|||
==The language== |
==The language== |
||
Revision as of 08:15, 20 December 2011
- For information on how to install lttoolbox, see lttoolbox and minimal installation from SVN
This page is going to describe how to start a new language with lttoolbox. As lttoolbox is not really suited to agglutinative languages, or languages with complex and regular morphophonology (see starting a new language with HFST), we're going to work on one with simpler and less regular morphology.
Preliminaries
A morphological transducer in lttoolbox has typically one file, a .dix file. This defines both how morphemes in the language are joined together, morphotactics, and how changes happen when these morphemes are joined together, morphographemics (or morphophonology). For example,
- Morphotactics: wolf<n><pl> → wolf + s
- Morphographemics: wolf + s → wolves
These two phenomena are treated in the same file.
The language
Lexicon
The basics
Compiling
Paradigms
Analysis and generation
Troubleshooting
Notes
