Multi-Dictionary Formatter Code Reference

also known as lemma or headword

\lx tuat

This is the key field or record marker that SHOEBOX uses to keep one entry separate from another. Bound morphemes are listed with a preceding or following hyphen

\lx -oli
\lx nara-

For some languages it may be acceptable to give an inflectable citation form, such as the H-form given in Tetun for inflectable verb roots

\lx holi

representing the paradigm koli, moli, noli, holi, roli, where the linguist would tend to identify the root -oli but the community thinks in terms of holi.

Multiple word or phrasal lexemes are common.

This field is obligatory for each entry.

\hm 1
\hm 2
\hm 3

Different homonyms must be in separate entries. These will sort correctly and format as subscripts using MDF. Use only if needed. Cross-references to one of these entries should include the number, e.g. \cf asw2. When the file is converted to WORD format for printing, MDF will subscript the homonym number, e.g. See: asw². Where they occur, MDF automatically references the homonym number in the reversed finderlists.

\lx nara-
\lc naran

This gives a complete surface form of bound roots that will be printed as the headword in the final printout. The \lc form always replaces the \lx form for the printed dictionary. MDF prompts users to choose whether or not they want entries that use \lc to sort under the \lc form for the printed dictionary. If the entry is not sorted by the \lc form, it will sort under the \lx, but the printed headword will be the \lc form

\lx -angu
\lc (na)-angu

is printed between \lx ane and \lx aok; similarly

\lx -ao
\lc (beke)-ao

is printed between \lx aok and \lx ape.

Use \lc only if the \lx form is inappropriate for the printed dictionary. MDF places the contents of the \lx field as follows:

\lx -hilu
\lc na-hilu

is printed as na-hilu (from: -hilu).

An indication of pronunciation is needed only where phonetic information is underdifferentiated by the practical orthography. MDF will supply square brackets and print the contents of the \ph field as monospace Courier font

\lx enaka
\ph ẽnaka

is printed as [ẽnaka]. The information on how to interpret the phonetic pronunciation of the practical orthography should be explained in the introduction to the dictionary. SHOEBOX v2.0 can handle certain phonetic fonts on screen (see SHOEBOX manual). The \ph fields may also be used following the \se (subentry) field.

This field is used if one is organizing the lexicon primarily around the root morphemes rather than the surface forms. It is also used by some compilers for languages in which phrasal lexemes are common (e.g. put out) where the preference is not to list the phrasal lexemes as separate headwords. Phrasal lexemes can be organized as \se sections under the words that make them up. Polymorphemic forms or phrases are listed under \se, which is like the \lx field except that it occurs within the record (entry), marking the word (or phrase) as a form derived from or associated with the root. Following this field would be all the fields that make up a typical lexical entry. There can be several \se subentries within a record (entry). Subentries can also have multiple senses within them. MDF begins each subentry at the beginning of a new line:

\lx destroy
\se destroyer

For bilingual dictionaries of minority languages, many lexicographers prefer to not use \se, listing everything as main entries to make it easier for the naive user to find information. Upon reversal, both the \se form and the \lx form are referenced for a gloss listed under the \se form e.g.

\lx sima
\ge hand
\se simake klarake
\ge palm

reverses on the subentry as ‘palm —simake klarake, see: sima’).

\ps vt
\ps n
\ps PREP
\ps PRO

This is used to classify the vernacular form, not the English or national language gloss. For example, the quality fat might be an adjective in English, but a verb in the vernacular language. \ps labels should be refined as one’s understanding of the language grows. In other words, don’t believe your early labels. Consistency in labeling is important. The RANGE SETS in SHOEBOX can help with this. There should be no final punctuation. MDF prints the \ps contents as italics (case is printed as entered in the original file) and adds a period

\ps vt

vt.

See chapter 9 for a variety of relevant issues and Appendix E for a starter list of abbreviations. If more than one \ps is used in an entry (e.g. one sense as a noun and another as a verb), then MDF starts each new \ps within an entry or subentry at the beginning of a new line, dividing the entry into sections on the basis of the \ps.

\pn kkt
\pn kb
\ps ks

This is used to classify vernacular parts of speech, labeling them with terms common to national language dictionaries. Keep in mind that part of speech categories in the national language may not match part of speech categories in the vernacular (see chapter 9). Consistent labeling is important. Use SHOEBOX’s RANGE SET feature for this field. MDF requires that the \pn field follow the \ps field:

\ps n (noun)
\pn kb (the national abbreviation for ‘noun’)

This field is used to distinguish multiple sense of meaning, or minor senses

\sn 1
\sn 2
\sn 3

1), 2), 3) Where an entry (or subentry) has more than one sense, this code gives the number and marks the beginning of each sense. There should be no closing parentheses or final punctuation in this field.

This field is primarily for a monolingual dictionary. It can be used as a temporary place to record succinct glosses provided by native speakers. For bilingual dictionaries the \gv information is best moved to the lexical functions fields \lf as Syn(onym), Ant(onym), Gen(eric), etc. (See chapter 7.)

Vernacular explanations or definitions of the headword generally should not be worded by the non-native speaker lexicographer. This field is for a monolingual dictionary and for retaining the integrity of native speaker explanations before they are repackaged in terms that make sense to the lexicographer.

\ge 3s
\ge house; hut ; building

This field is used for

1. interlinearizing
2. printing the dictionary (if there is no \de field or the \de field is empty)
3. reversal (if there is no \re field or the \re field is empty)

Where the user is distinguishing morpheme-level from word-level glosses, the \ge field is used for morpheme-level glosses. Multiple word glosses should be connected with an underline to maintain spacing integrity and force SHOEBOX to treat the whole gloss as a unit when interlinearizing

\ge put_out
\ge kin_group

MDF will convert this to a plain space when printing. There are two options for organizing multiple glosses:

\ge house
\ge hut
\ge building

OR

\ge house ; hut ; building [space-semicolon-space]

The SHOEBOX INTERLINEAR function can recognize either of these formats. For multiple glosses in either format MDF will separate them with commaspace. MDF also places a period after the final gloss. Thus,

\ge house ; hut ; building

is printed as: house, hut, building. The \ge field substitutes for a definition in printing a dictionary if no \de field is used. For speed in interlinearizing, the first gloss given should be the most common, broadest or most technical. It is not a definition! This field should be in all entries.

\re jaw ; chin;

\re exchange ; get ; take ; give

This gives the English word(s) or phrase(s) desired for a reversed English-vernacular finderlist. It is used for reversal only if the form in the \ge field is not suitable. The contents of the \re field are not printed in the dictionary, but only in the reversed finderlist. This is not a definition. Since this field is not used for interlinearizing, the joining underline

\ge put_out

is not used. If an asterisk is placed in this field

\re *

then the relevant entry, subentry, or sense will be discarded or ignored for reversal (i.e. it will not be included in the reversed finderlist).

\we throw_out If interlinearizing is desired at the word-level (surface form), rather than at the morpheme-level, then this field is used.

This field is used for a technical definition, expansion, or explanation of the meaning of the headword. It is more precise and complete than the gloss, aiming to capture meaning and aspects of range and usage. If there are \de field contents, then MDF will print them in the formatted dictionary and ignore the contents of the \ge field. In the \de field the compiler can reword or expand information in the \ge or \re fields using natural English worded for clarity for the broadest target audience.

For additional overflow, use the encyclopedic fields \ee and usage fields \ue.

This is like the English \ge field, but is for Indonesian, Spanish, French, Portuguese, etc. If interlinearizing is not to be done in the national language, then all material for a reversed finderlist is also put in this field and \rn is not used.

This is like the \re field, but is designed for forms that are appropriate for reversal in the national language. For example, mempersilahkan may be an appropriate gloss for the \gn field, but inappropriate for reversal— \rn silahkan is preferred. This field would also be used if interlinearizing is done in the national language and the contents of the \gn field are inappropriate for reversal.

This is like the \we field.

This is like \de field. If triglot printing is selected, national language fields are printed in italics.

These are activated by MDF when National language audience or triglot options are selected.

This is like \ge field, but for the regional language or lingua franca that might be different from the national language, such as Ambonese Malay, Swahili, or regional creoles. These are often the languages in which explanations are given, particularly early in the researcher’s contact, and they may provide more insight into the range of meaning of the headword than the national language.

Like \re field. It is not likely to be needed.

Like the \we field. It is not likely to be needed.

This is like the \de field. If triglot printing is selected, MDF prints the regional language fields in italics within square brackets [ ] preceded by ‘Regnl:’ as in [Regnl: parlente]. Fields clarifying the identity of the headword:

This is used where the literal parts of an idiom or lexeme do not obviously yield the gloss or definition given. MDF adds Lit: before the contents of this field and puts the contents in single quotes, followed by a period.

\sc Phalanger spp

Used where the information is known. Consult the best regional sources on flora, fauna, avifauna, and fish, or get expert advice. Be careful about guessing as a lay person. Educate yourself about principles of identification and taxonomy in botany and zoology. MDF prints the contents of this field as underlined italic, e.g. Phalanger spp. Do not use final punctuation as MDF will add this.

MDF can handle up to five different example sentence bundles for each sense and subentry in a main entry. Within such a unit, multiple examples are printed one after the other.

This refers to the source of the example sentences from data notebooks, the name of the source text and sentence number, etc.

\rf C–89–2:34
\rf Manukama 164.

This housekeeping field does not have to be printed, but the information is useful to record. MDF adds Ref: before the contents of this field. The information is bundled with the following example sentence fields. Punctuation should be used as needed.

Illustrative sentences in the vernacular legitimate and exemplify each separate sense. They should be short and natural. Examples extracted from texts may need to be adjusted to rebuild the information lost by removing them from their context. Punctuation and capitalization should be used as needed. Bartholomew and Schoenhals (1983: ch.9) have a helpful discussion of what makes good example sentences. The contents of this field are printed in the vernacular font (i.e. bold).

This is the English rendering of the example in \xv. Punctuation and capitalization should be used as needed. This field prints as regular font.

This is the national language rendering of the example in \xv. Punctuation and capitalization should be used as needed. In a diglot vernacular-national language dictionary the contents of this field print in italics.

This is the regional language rendering of the example in \xv. Punctuation and capitalization should be used as needed. This prints only if the national language is requested.

This field is for those who wish to include interlinear glossing of \xv in their lexicon.

\ue archaic
\ue ritual
\ue Used by same-sex siblings not opposite-sex siblings.
\ue taboo
\ue vulgar
\ue Rana dialect
\ue H(igh register)

This is for comments on social usage, region, register, or dialect. It is also a place to note pragmatic connotations such as negative overtones if not clear from \de field. May overlap with lexical functions \lf such as SynT(aboo), SynD(ialect), or SynR(egister). Punctuation and capitalization should be used as needed. When printing, MDF places Usage: before the contents of this field.

Like the \ue field.

Like the \ue field.

Like the \ue field.

This expands descriptive or ethnographic information in the \de field for outsiders who do not share the knowledge bank of the local community. The contents of this field are intended for printing (in contrast with the notes fields, such as \nt, which are not intended for final printing). Use normal punctuation and capitalization as needed.

Like the \ee field.

Like the \ee field.

Like the \ee field.

\oe human

\oe female
\oe not said for siblings of opposite sex
\oe collocates with non-active verbs only

This is for semantic or grammatical restrictions pertinent to the use of the headword. Capitalization should be used as needed. MDF places Restrict: before the contents of this field.

Like the \oe field.

Like the \oe field.

Like the \oe field.

This bundle of fields \lf \le \ln \lr should be kept together since each example of a lexical function has its own distinct glosses. There can be as many of these bundles as needed. MDF separates multiple bundles of lexical functions within an entry, subentry or sense with a semicolon [;], and places a period [.] after the final lexical function in the entry, subentry or sense.

\lf Part = sufen

\lf Whole = huma

These are for mapping lexical networks, in effect, cross-referencing the lexeme with entries related to it, including various types of synonyms, antonyms, part-whole, generic-specific, typical actors, undergoers, instruments, material used, etc. The \lf system of cross-referencing links words in specific ways, in contrast to the use of \cf, where the link is vague and undefined. See the discussion of lexical functions in chapter 7 for a listing with examples of relations most commonly used in the \lf field. When printing, MDF converts the space-equals sign [ =] to a colon [:], printing the label of the semantic relationship in italics, and what comes after the equals sign [=] as vernacular font. Thus, \lf Syn = peni prints through MDF as Syn: peni. MDF is set to ignore \lf fields that have nothing after the equals sign, for empty \lf fields that include certain labels in their template. Thus,

\lf Syn = (blank)

will not print as Syn: unless something is filled in after the equals sign.

\le merchant

\le wave

For most lexical functions, the contents of \le are simply the gloss of the contents of the \lf field. But for SynD(ialect), the dialect name is put in this field

\le Rana dialect

For SynR(egister), the speech register name is put in this field

\le

Low MDF places single quotes around the contents of this \le field. Thus, \lf Nact [Actor noun] = gebkaleli, \le merchant prints through MDF as Nact: gebkaleli ‘merchant’.

Like the \le field.

Like the \le field. Additional fields relating the headword with its lexicocultural network:

Available for those who do not want to use the \lf bundles. This field does not provide the advantage of giving a gloss as with the \le field. MDF adds Syn: before the contents of this field and prints the contents in vernacular font, followed by a period.

Available for those who do not want to use the \lf bundles. This field does not provide the advantage of giving a gloss as with the \le field. MDF adds Ant: before the contents of this field and prints the contents in vernacular font, followed by a period.

\lx inaat

\mr ii-en-kaa-t

This field is for indicating morpheme representation, or the underlying forms where morphophonemic processes occur. MDF adds Morph: before the contents of this field and prints the contents in vernacular font, followed by a period.

MDF converts this code to “See” for the final printing, and the prints contents as vernacular font. Thus,

\cf anat

is printed as See: anat.

This is a general purpose cross-reference that may, for example, be used in compounds to cross-reference the underlying roots

\lx anrepun
\ge adopted_child
\cf repu

Complex instruments can be crossreferenced, e.g. bow with arrow, mortar with pestle, and vice versa. These can also be handled in the \lf field with the Counterpart [Cpart] relation. The \cf field is also used to cross-reference a minor variant to a main entry where fuller information is found (but see also \mn below). Cross-references to one of several homonyms should include the number (e.g. \cf asw2). When the file is converted to WORD format for printing, MDF will subscript the homonym number (e.g. See: asw2). MDF allows multiple \cf bundles, separating each with a semicolon [;] and placing a period after the final \cf bundle.

Where the connection is not obvious it is helpful to have the gloss of the cross-reference in the entry at hand rather than have to chase it down

\lx anrepun
\ge adopted_child
\cf repu
\ce retrieve

The contents of this field are printed in single quotes as in, See: repu ‘retrieve’.

Like the \ce field.

Like the \ce field.

This field is used to cross-reference a minor variant to a main entry where fuller information is found. It can also be used for a headword that reflects an unusual or irregular construction or inflection under which the user might look to refer to an entry where fuller information can be found. MDF adds See main entry: before the contents of this field and prints the contents in vernacular font, followed by a period

\lx can’t
\mn cannot

See \va below for a related field.

\lx yako
\va ya, yak
\lx anat
\va an
\lx lidak
\va lidek
\lx cannot
\va can’t

This can be the inverse of \mn. Cliticized forms, alternate pronunciations or alternate spellings are listed here. These variant forms generally refer to minor entries found elsewhere in the dictionary. Some lexicographers handle incomplete inflections or reduplication here as well, but those should be handled under the field(s) for paradigms \pd or reduplication \rd. Use the \ve, \vn, and \vr fields only if there are relevant comments, such as distinguishing usage restrictions between the \lx form and the \va form. MDF adds Variant: before the contents of this field and prints the contents in vernacular font. Multiple \va field bundles are separated by a semicolon and the final bundle is closed with a period. The \va bundle can also be used to record dialect variants.

We are aware that a compiler may use the \va bundle for more than one function (i.e. for morphological variants, and for dialectal variants), and that this sets up limitations for analysis or if one chooses to print one type but not the other. We intend future enhancements of MDF to have fields dedicated to dialectal information, but at present the programming limitations do not allow us any more field bundles. For the present, use \va and \lf SynD =.

Comments regarding the contents of the \va field such as usage restrictions of the contents of \va, or dialect names identifying the source of the forms in \va. The contents of this field are enclosed in parentheses: \lx hahy, \va fafy \ve older speakers, prints as Variant: fafy (older speakers).

Like the \ve field.

Like the \ve field. Origins of the headword:

\bw Sanskrit

\bw Swahili
\bw Spanish
\bw Malay

This identifies the ultimate source language, where known, with the understanding that it may have been introduced through an intermediate language. The form of the original language may also be given

\lx emrimo
\bw Portuguese fi:meirinho.

For the final printing MDF adds From and places a period following the contents of the field, e.g. From: Sanskrit.

\et *biCuka
\et *maRuqanay

Reconstructed proto forms are given in this field. Cite attested published reconstructions only. Use \nt or \ec field if you want to posit your own guess at a reconstruction. MDF adds Etym: for the final printing.

\eg bowels

This field is for the gloss of the reconstructed form so one can see semantic consistency or shift. Reconstructed meanings for most language families are given in English. Give the original published gloss—do not translate the published reconstructed gloss into the national language. MDF prints the contents of this field in single quotes, e.g. Etym: *biCuka ‘bowels’.

\es Blust 1993:46
\es PANDYMPL

This is for the source of the reconstructed form in \et. It is a housekeeping field for data management and is not intended for printing. Abbreviations for works on Austronesian languages can be found in Wurm and Wilson (1975).

\ec metathesis
\ec Expect fv:lesun rather than fv:resun - possible loan

Relevant comments where the connection between the headword and the reconstructed form is not straightforward may be placed in this field. It may also be used to posit tentative unattested reconstructions and supporting data. Not intended for printing. Grammatical paradigm fields:

This is a general field identifying the noun class, verb class, gender, or other paradigm set to which the headword belongs (as explained in the introduction to the dictionary). It can be used to identify incomplete or irregular paradigms. MDF places Prdm: before the contents of this field and adds a period at the end. For those users or languages that require more specific paradigm-related fields, MDF recognizes the following:

singular form [Sg: ]

plural form [Pl: ]

reduplication form(s) [Redup: ]

1st singular form [1s: ]

2nd singular form [2s: ]

3rd singular form [3s: ]

non-human or non-animate singular [3sn: ]

1st dual [1d: ]

2nd dual [2d: ]

3rd dual [3d: ]

non-human or non-animate dual [3dn: ]

1st plural [1p: ]

1st plural inclusive [1pi: ]

1st plural exclusive [1px: ]

2nd plural [2p: ]

3rd plural [3p: ]

non-human or non-animate plural [3pn: ]

This marks the text as unformatted. Line breaks and tabs entered by the user are retained. It may be used for such things as folk taxonomies of plants and animals, clarifying grammatical paradigms, or listing specific terms under a generic term (the latter better done in the \lf field). Punctuation and capitalization should be used as needed. The following example is from Selaru:

\tb Listing of all types of cutting verbs:
fv:akrina: split in two lengthwise
fv:boras: cut s.t. in small pieces with a knife
fv:dow: chop s.t. into smaller pieces while standing it on end
fv:het: chop or hack with a machete
fv:kety: slice open and clean an animal
fv:lary: slice (like chiles, etc.)
fv:lilit: shave or carve
fv:mair: to adze wood
fv:simat: pop out or cut out coconut meat

MDF prints this out as:

Alternatively these could be listed under a generic cutting verb in the \lf field as

\lf Spec = akrina
\le split in two lengthwise, etc.

Tables may require some “tweaking” to fine-tune the formatting when the time comes to print the dictionary after MDF has ported the lexical file into MSWORD. Fields relating the headword to others of similar categories: These are helpful for analysis.

\sd Nkin
\sd Nplant
\sd Vcut
\sd Vspeak

The use and placement of this field marker within the SHOEBOX database is up to the user. Some who use it regularly tend to put it near the front of the entry. Some users place \sd directly following \ps, using \ps to indicate strict subcategorization (e.g. \ps vt), and using \sd to indicate selectional restrictions (e.g. \sd Vcarry). Here one tries to catalog the semantic categories relevant to the language, being careful not to let the English force or mask the vernacular categories. The use of this field greatly assists specialized analysis or extracting topical subsets of the whole lexicon (e.g. publishing a special fascicle on plant terms). Several domains can be listed in the one field, if relevant, or one can use a separate \sd field for each sense. The contents of this field are not ordinarily printed, as it is primarily for analysis. But if one chooses to print the \sd fields, MDF places them toward the end of the entry, preceding the contents of the field with SD: and follows the contents with a period. See Appendix C for a suggested starter list of semantic domains and optional renderings.

Some MDF users have requested this field for correlating vernacular terms with Louw and Nida’s (1988) Greek-English 93 semantic domain categories (many with additional subdomains). While useful for some purposes (like translation of Greek-based materials), the compiler is cautioned to remember that these categories are an etic checklist that may have no relation to emic categories in the vernacular. This field could also be used for the Human Relations Area Files [HRAF] categories from the Outline of cultural materials (Murdock, et. al. 1982). A third system that could be used is that of Hashimoto (1977) which provides an etic list of semantic domains that is more compact than HRAF and less language specific than Louw and Nida. Reversing on this field would yield semantically related entries grouped under the various Louw and Nida, HRAF, or Hashimoto semantic domains. MDF precedes the contents of this field with Semantics: and places of period following the contents of the field.

\th utan

This field is for the vernacular generic term under which the headword is emically categorized by the people themselves. For example, in Selaru, masy ‘fish’ has a broader semantic range than English fish because it also includes sea mammals and crustaceans. Similarly, the Buru generic term manut, whose Austronesian reconstructed form is glossed as ‘bird’, in Buru includes bats and other flying creatures like butterflies whose wings are large enough and slow enough to see in flight, but does not include most other insects.

This field is useful for later analysis or extraction (using SHOEBOX FILTERS) for separate publications of fish-type terms, flying creatures, etc. The contents of this field may or may not correlate with a western taxonomy or with the \sd field. It overlaps with \lf Gen(eric) =. MDF precedes the contents of this field with Thes: and places of period following the contents of the field.

\bb BDG 1991:328
\bb Schut 1917

This field references literature expanding on this lexeme. It is generally for grammatical particles or lexemes of ethnographic significance. MDF places Read: before the contents of this field and places period after.

This may refer to a sketch in a notebook, a photograph or slide in the lexicographer’s collection, a picture or photograph in a published book, or a link to a computerized graphic file (e.g. file.PCX). If the field begins with .G., then MDF will set it up in WORD to print as a graphics image in that entry.

\pc .G.\pcx\eagle.pcx;1.5”;1”;PCX

The .G. marks this as a graphics link. Next follows the path and filename:\pcx\eagle.pcx. Then the width of the picture desired for printing (here 1.5 inches), then the height (1”), and finally the graphics format type (PCX). Each bit of information is separate by a semicolon [;]. When the dictionary is formatted, the graphics information is moved to the beginning of the entry, subentry or sense in which the \pc field is found. This will cause the text to flow around the picture, which will be in a box. Sizes much larger than 1.5” x 1.5” are not recommended. In double column format the picture is placed flush right in the column; in single column format the picture is flush right to the right margin. If no .G. is found, then MDF assumes the contents of the field are a reference to a book or notebook and simply prints the contents of the field enclosed in parentheses.

This is a general note field that can accommodate comments related to any field. It may be placed anywhere within an entry, subentry, or sense. Punctuation and capitalization should be used as needed. If selected to print, the contents of this field will be placed at the end of the entry or sense within square brackets [Note: …]. These fields are intended for the compiler’s use and are not intended for printing, except for drafts. If the lexicographer wants to distinguish different classes of notes, MDF recognizes the following fields:

\so informant’s name/initials
\so researcher’s name/initials
\so village name/code

This is important where a range of sources or several researchers or a team of compilers are involved in producing a dictionary. Normally not printed. When selected for printing, MDF places Source: before the contents of this field and a period after.

\st no print
\st done
\st check

This field can be used to later exclude entries that the informants have specifically requested not appear (e.g. in the national language dictionary they may fear abuse if certain sexual terms in the vernacular are known by immigrants or officials from other ethnic groups). It can also be used to flag entries that are considered fully edited or that need further editing prior to final printing. Not normally printed. When selected for printing, MDF places Status: before the contents of this field and a period after.

This housekeeping matter can be automated with the SHOEBOX DATESTAMP feature. It is not normally printed.

Fields entered by the user that are not recognized by MDF are placed within square brackets at the end of the entry and preceded by a double question mark [?? …]. These can be toggled to print or not print through the Change Settings menu option (where they are called the ‘(huh)’ fields).