GiellaLT Documentation

GiellaLT provides rule-based language technology aimed at minority and indigenous languages

View GiellaLT on GitHub

Page Content

Transducer names

The new infrastructure produces transducers with a different naming scheme than in the old infra. The names are longer and more descriptive.

Regular transducers

The information we want to encode

The strings to represent the value for each class is given first. The order of the info classes represent the order in the filename.








Naming scheme

Based on the above list, we get this:


This should give transducers with names like:

Transcription transducers

These are not lexical transducers, instead they convert between one representational format and another, like between dates written as text and dates written with digits. For this type of transducers there is a separate basic transducertype: transcriptor. The application name specifies what type of transcription is being done by the transducer, and the direction is specified using either digit2text or text2digit.

Possible application names are:

Conversion to IPA is a variant of this type of transducers, and is named:

Since no tags are involved in these types of transducers, the tagset is left out.

The transcriptors are sometimes filtered (i.e. some forms are excluded in one direction or the other) and that is indicated by a suffix .filtered. And because of the issues with Xerox lookup, whether the fst is intended for lookup or composition is also indicated by a suitable suffix.

File name examples