2.3. Double defining markers
Document Actions
A final step in making sure you get the most out of your .typ file when importing it into LEXUS is to be aware of the possibility of double-defining markers. In Toolbox every marker can be defined only under one other marker. What happens often however is that a certain data category seems to appear consistently in more than one place in the data file. Most often this is the case for . In the MDF file, it is defined under subentry. However, except for appearing under subentry marker, it will be found throughout many lexica also under . The structure is actually in each case the same: appears under which is under . However, in those cases, where it is found under in the data file, the marker - which is in the structure between and , is simply not expressed explicitly. For Toolbox, as we already know this is not a problem.
LEXUS however will have to create an empty group between every and in this case. Importantly however 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 in the .typ file and changing in the copy of that definition the node under which it is defined from to . In that way in the structure file we have two definitions of the marker - under and under . This double definition will not be recognized by Toolbox, but LEXUS can cope with it perfectly. The only limitation is that there should be no more than three double-defined elements in your .typ file, and the general rule is the fewer the better.
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 and for instance.
Third party update, regular expressions
