Interlinearization mode is a text oriented mode designed for parsing and glossing annotations to one or more lines of interlinearized text. This can be done manually or with the use of one or more so-called Analyzers. The segmentation and (typically) the transcription of speech events need to be done in one of the other modes before interlinearization can be added in this mode.
Analyzers are software modules that accept an annotation as input and produce suggestions for one or more annotations as output. Examples of the type of processing analyzers can perform are tokenization, morphological parsing and lookup of glosses. The behavior of some analyzers can be configured in a settings panel. Some analyzers need a connection to a lexicon, others can perform their task based on the input alone. Analyzers are implemented as extensions so that others can create and add their own analyzers (eventually, the API still has to be finalized and documented).
Part of the user interface of this mode is a Lexicon panel, the front end of a Lexicon Component module. It allows to create, import and edit a lexicon and its entries. Lexicons are stored separately from annotation data in a new data format. These are the lexicons that analyzers can get access to.
The lexicon and analyzer modules are work-in-progress. A lot is still missing, incomplete and/or under-documented.
To start the Interlinearization mode, clickfrom the main window.
The main screen is split up in 4 panels, the panels on the left side are used for global settings, not tied to any particular transcription. The panels on the right side of the screen contain more specific settings and the transcriptions.
Top-left panel: Analyzer settings. Each analyzer may have a settings panel which can be configured here.
Bottom-left panel: Lexicon editor. Lexicons may be used by an analyzer and are user-defined.
Top-right panel: Analyzer - Tier type configuration. Set the source and target tiers for the analyzers.
Bottom-right panel: View of the annotations in an interlinear text style.
To start working in Interlinearization Mode, you need to have already set up a proper tier structure. This can be done in Annotation mode, please refer to Section 2.3 and Section 2.4 for more information about tier structures.
It is also important that you have set up a Lexicon service (See Section 2.7.1 and that it is associated to the proper tier type. (You can associate a lexicon in the Tier type dialog under 'Lexicon connection').
Currently, you can choose from the following analyzers:
The names are somewhat misleading; both the Parse, Gloss and Lexicon analyzer require access to a lexicon. The Parse analyzer morphologically parses annotations from a word (or token) level tier, based on lexical units (prefixes, stems, suffixes etc.) available in the lexicon. The results are shown as parse suggestions in a suggestion window from which the user can select one. This analyzer requires one source tier and one target tier, where the target is of a subdivision tier type.
The Gloss analyzer looks up the source annotation in the lexicon and lists all glosses found in the matched entries. The results are again presented as suggestions from which the user can select one. This analyzer requires one source tier and one target tier, where the target is of a symbolic association tier type.
The Lexicon analyzer is a combination of the parse and the gloss analyzer. By configuring the lexicon analyzer, the source tier containing the annotations will both be parsed and the glossed in one action. This analyzer requires one source tier and two target tiers (see above).
The Whitespace analyzer splits the selected source annotation at whitespaces and places the result on the target tier. It does not need any user confirmation. This analyzer requires one source tier and one target tier, where the target is of a subdivision tier type.
When configuring analyzers and their source and target tiers, it is possible that the target tier from one analyzer, is the source tier for the next analyzer. The configuration of the tiers is based on tier types rather than on individual tiers.
Configuration on the basis of individual tiers might be added later as an option as well.