2.3. Double defining markers

A final step in making sure that the import into LEXUS will cause problems is to be aware of the possibility of double-defining markers. As in Toolbox markers are defined under other markers, it happens often that certain data categories seem to appear consistently in more than one place in the data file. Most often this is the case for part of speech, ps. In the MDF file, it is defined under subentry. However, except for appearing under the subentry marker, it will also be found throughout your lexicon also under lexeme. The structure is actually in each case the same: part of speech appears under subentry which is under lexeme. In those cases, where it is found under lexeme in the data file, the subentry marker (which is in the structure between lexeme and part of speech) is simply not expressed explicitly. For Toolbox, as we already know, this is not a problem.

In this case, however, LEXUS will have to create an empty subentry group between every lexeme and part of speech. Importantly, part of speech in this place is very consistent throughout lexica and it is desirable to have it there. To solve this problem, LEXUS allows to double define markers manually by simply copying the definition of ps in the .typ file and changing in the copy of that definition the node under which it is defined from subentry to lexeme. In that way, in the structure file we have two definitions of the marker ps: one under lexeme and another under subentry. This double definition will not be recognized by Toolbox, but LEXUS will be able to cope with it. There is no limitation as to the number of double-defined elements in your .typ file but the general rule is: the fewer the better.

Double defined markers in the .typ file.

Figure 2.3. Double defined markers in the .typ file.

Often, there are more than three markers that you would like to double-define. The only solution here is to first order them in a hierarchy and to double define only the very top marker of that hierarchy. The markers that are defined under it will automatically appear under the double-defined markers, both under lexeme and subentry for instance.