Glossing Rules: Difference between revisions

From Glossing Ancient Languages

Jump to: navigation, search
(Cross check with Lehmann (2004))
m (varia, lapsus, Verbesserungsvorschläge: W.Sommerfeld)
 
(12 intermediate revisions by 4 users not shown)
Line 5: Line 5:
=== Alignment ===
=== Alignment ===
; (1) Alignment Rule
; (1) Alignment Rule
: An object language word and its gloss need to be ''' arranged vertically left-aligned'''. <ref>''LGR'' (2008): rule 1; cf. Lehmann (2004: R27).</ref>  
: An object language word and its gloss need to be '''arranged vertically left-aligned'''. <ref>''LGR'' (2008): rule 1; cf. Lehmann (2004: R27).</ref>  


; Example:
; Example:
Line 32: Line 32:
=== One-to-Many Correspondences ===
=== One-to-Many Correspondences ===
==== One object language word = many gloss elements ====
==== One object language word = many gloss elements ====
<div id="Punctuation_period">
; (2a) Standard Joining Rule (for the gloss)
; (2a) Standard Joining Rule (for the gloss)
: Within a pair of an object language word and gloss, neither the word nor the gloss may contain any whitespaces (blanks, tabs).  
: Within a pair of an object language word and gloss, neither the word nor the gloss may contain any whitespaces (blanks, tabs).  
: If one object language word corresponds to two or more elements in the gloss, these elements have to be joined by a punctuation mark.  
: If one object language word corresponds to two or more elements in the gloss, these elements have to be joined by a punctuation mark.  
:The standard punctuation mark for '''joining elements in the gloss''' is the '''period “.”'''. <ref>Cf. ''LGR'' (2008): rule 4.</ref>
:The standard punctuation mark for '''joining elements in the gloss''' is the '''period “.”'''. <ref>Cf. ''LGR'' (2008): rule 4.</ref>
</div>


; Example:
; Example:
Line 56: Line 58:
</small>
</small>


<div id="Punctuation_person_number">
; Standard exception to the Standard Joining Rule
; Standard exception to the Standard Joining Rule
: The sequence PERSON – NUMBER is usually spelled simply without a period “.”, i.e. [[Glossing Abbreviations|abbreviated]] as e.g. “3PL” (instead of “3'''.'''PL”). <ref>Cf. ''LGR'' (2008): rule 5.</ref>
: The sequence PERSON – NUMBER is usually spelled simply without a period “.”, i.e. [[Glossing Abbreviations|abbreviated]] as e.g. “3PL” (instead of “3'''.'''PL”). <ref>''LGR'' (2008): rule 5.</ref>
</div>


For another meaning of the period “.” in cases in which other punctuation marks like colons “:”, hyphens “-” or else are also used, see [[#The period in the expert mode|The Period in the Expert Mode section]] below.  
For another meaning of the period “.” in cases in which other punctuation marks like colons “:”, hyphens “-” or else are also used, see [[#Punctuation_period_expert|The Period in Expert Mode section]] below.  


{{Separating bar}}
{{Separating bar}}


===== Compact translation phrases in the gloss =====
===== Compact translation phrases in the gloss =====
<div id="Punctuation_underscore_gloss">
; (2b) Compact phrase joining recommendation
; (2b) Compact phrase joining recommendation
: If one object language word corresponds to a compact '''multi-word phrase translation in the gloss''', these elements should rather be joined by an '''underscore “_”''' than by a period “.”. <ref>''LGR'' (2008): rule 4a; Lehmann (2004: R23).</ref>
: If one object language word corresponds to a compact '''multi-word phrase translation in the gloss''', these elements should rather be joined by an '''underscore “_”''' than by a period “.”. <ref>''LGR'' (2008): rule 4a; Lehmann (2004: R23).</ref>
</div>


; Example:
; Example:
Line 72: Line 78:
| ''Vorgestern'' || ''bin'' || ''ich'' || ''aus'' || ''einem'' || ''Kurzurlaub'' || ''zurückgekommen''.
| ''Vorgestern'' || ''bin'' || ''ich'' || ''aus'' || ''einem'' || ''Kurzurlaub'' || ''zurückgekommen''.
|-
|-
| th'''e_d'''a'''y_b'''efor'''e_y'''esterday || am || I || out || a.SG.M.DAT || short.vacation.M.SG.DAT || back.come.PTCP.PRF
| th'''e_d'''a'''y_b'''efor'''e_y'''esterday || am || I || out || a || short.vacation || back.come
|}
|}


Line 81: Line 87:
| ''Vorgestern'' || ''bin'' || ''ich'' || ''aus'' || ''einem'' || ''Kurzurlaub'' || ''zurückgekommen''.
| ''Vorgestern'' || ''bin'' || ''ich'' || ''aus'' || ''einem'' || ''Kurzurlaub'' || ''zurückgekommen''.
|-
|-
| th'''e.d'''a'''y.b'''efor'''e.y'''esterday || am || I || out || a.M.DAT || short.vacation.M.SG.DAT || back.come.PTCP.PRF
| th'''e.d'''a'''y.b'''efor'''e.y'''esterday || am || I || out || a || short.vacation || back.come
|}
|}
</small>
</small>
Line 95: Line 101:


==== Many object language words = one gloss element ====
==== Many object language words = one gloss element ====
<div id="Punctuation_underscore_object_language">
; (2c) Standard Joining Rule for object language words
; (2c) Standard Joining Rule for object language words
: If two or more object language words corresponds to one elements in the gloss, these elements have to be joined by a punctuation mark. The standard punctuation mark for '''joining object language words''' that correspond to one single gloss is the '''underscore “_”''' (rather than the period “.”). <ref>Lehmann (2004: R11).</ref>
: If two or more object language words corresponds to one element in the gloss, these elements have to be joined by a punctuation mark. The standard punctuation mark for '''joining object language words''' that correspond to one single gloss is the '''underscore “_”''' (rather than the period “.”). <ref>Lehmann (2004: R11).</ref>
</div>


; Example:
; Example:
Line 120: Line 128:


=== Analyzing grammatical categories ===
=== Analyzing grammatical categories ===
; (3) Categories Markup Rule
==== Grammatical morphemes ====
<div id="Categories_style">
; (3) Grammatical categories markup rule
: Grammatical categories marked on or inherent to the object language word may be analyzed in the gloss. These '''grammatical categories''' have to be typeset in '''small caps''' (small capital letters), or else – but less elegant – in normal capital letters.  
: Grammatical categories marked on or inherent to the object language word may be analyzed in the gloss. These '''grammatical categories''' have to be typeset in '''small caps''' (small capital letters), or else – but less elegant – in normal capital letters.  
: For the sake of space, frequent grammatical categories are usually abbreviated. <ref>Cf. ''LGR'' (2008): rule 3; Lehmann (2004: R29).</ref>
: For the sake of space, frequent grammatical categories are usually abbreviated. <ref>Cf. ''LGR'' (2008): rule 3; Lehmann (2004: R29).</ref>
</div>


For common glossing abbreviations, see the [[Glossing Abbreviations|Glossing Abbreviations section]].
For common glossing abbreviations, see the [[Glossing Abbreviations|Glossing Abbreviations section]].
Line 141: Line 152:
|-
|-
| the_day_before_yesterday || '''am''' || '''I''' || out || '''a'''.SG.M.DAT || short.vacation.M.SG.DAT || back.come.PTCP.PRF
| the_day_before_yesterday || '''am''' || '''I''' || out || '''a'''.SG.M.DAT || short.vacation.M.SG.DAT || back.come.PTCP.PRF
|}
{{Separating bar}}
==== Ambiguous morphemes ====
<div id="Punctuation_slash">
; (4) Ambiguous polysemous morphemes recommendation
: If a morpheme has two or more different meanings, i.e. if it is '''polysemous''', the encoder might optionally want to give two or more of the meanings separated by a '''slash “/”'''. <ref>Lehmann (2004: §3.5, tab. 6.2).</ref>
</div>
Cf. the following paradigm:
{| class="wikitable"
|-
! Number, case !! Word !! Gloss
|-
| SG, NOM || ''Urlaub'' || vacation.SG.NOM ''or'' vacation.SG.'''NOM/ACC/DAT''' ''or'' vacation.SG.NGEN
|-
| SG, GEN || ''Urlaubs'' || vacation.SG.GEN
|-
| SG, ACC || ''Urlaub'' || vacation.SG.ACC ''or'' vacation.SG.'''NOM/ACC/DAT''' ''or'' vacation.SG.NGEN
|-
| SG, DAT || ''Urlaub'' || vacation.SG.DAT ''or'' vacation.SG.'''NOM/ACC/DAT''' ''or'' vacation.SG.NGEN
|-
| PL, NOM || ''Urlaube'' || vacation.PL.NOM ''or'' vacation.PL.'''NOM/GEN'''
|-
| PL, GEN || ''Urlaube'' || vacation.PL.GEN ''or'' vacation.PL.'''NOM/GEN'''
|-
| PL, ACC || ''Urlauben'' || vacation.PL.ACC ''or'' vacation.PL.'''ACC/DAT'''
|-
| PL, DAT ||''Urlauben'' || vacation.PL.DAT ''or'' vacation.PL.'''ACC/DAT'''
|}
|}


Line 150: Line 191:


=== General marking of separable inflection ===
=== General marking of separable inflection ===
; (9) Unspecified inflection markup
<div id="Punctuation_colon">
; (5) Unspecified inflection markup
: If one object language word corresponds to two or more elements in the gloss that '''can be distinguished between, theoretically''', but the encoder is not able to or does not want to specify the type of inflection or the morpheme boundary, these elements may be joined (or rather separated) in the gloss by a '''colon “:”''' (rather than by a period “.”). <ref>''LGR'' (2008): rule 4c; cf. Lehmann (2004: R13).</ref>
: If one object language word corresponds to two or more elements in the gloss that '''can be distinguished between, theoretically''', but the encoder is not able to or does not want to specify the type of inflection or the morpheme boundary, these elements may be joined (or rather separated) in the gloss by a '''colon “:”''' (rather than by a period “.”). <ref>''LGR'' (2008): rule 4c; cf. Lehmann (2004: R13).</ref>
</div>


; Example:
; Example:
{| {{Glossing table}}
{| {{Glossing table}}
|-
|-
| ''Vorgestern'' || ''bin'' || ''ich'' || ''aus'' || ''einem'' || ''Kurzurlaub'' || ''zurückgekommen''.
| ''Vorgestern'' || ''bin'' || ''ich'' || ''aus'' || ''ei'''ne'''m'' || ''Kur'''zu'''rlaub'' || ''zurüc'''kgek'''om'''me'''n''.
|-
|-
| the_day_before_yesterday || be.PRS.1SG || 1SG.NOM || out || ART.INDF.S'''G:M'''.DAT || shor'''t:v'''acation.'''M:S'''G.DAT || bac'''k:c'''om'''e:P'''TCP.PRF
| the_day_before_yesterday || be.PRS.1SG || 1SG.NOM || out || ART.INDF.S'''G:M'''.DAT || shor'''t:v'''acation.'''M:S'''G.DAT || bac'''k:c'''om'''e:P'''TCP.PRF
Line 172: Line 215:
</small>
</small>


Note that, consequently, the period (“.”) has a more precise meaning then in the advanced mode (see [[#Punctuation period advanced|below]]).
Note that, consequently, the period (“.”) has a more precise meaning than in the advanced mode (see [[#Punctuation_period_advanced|below]]).


{{Separating bar}}
{{Separating bar}}


=== The period in advanced mode ===
=== The period in advanced mode ===
<div name="Punctuation period advanced">
<div id="Punctuation_period_advanced">
; (4') The period in advanced mode
; (2a') The period in advanced mode
: If one chooses to mark separable morphemes by a colon “:”, elements in a gloss should only be joined by a period “.”, if these are inseparably fused in the object language word, i.e. if they are part of a ''Portmanteau'' morpheme. <ref>Cf. Lehmann (2004: R21).</ref>
: If one chooses to mark separable morphemes by a colon “:”, elements in a gloss should only be joined by a period “.”, if these are inseparably fused in the object language word, i.e. if they are part of a ''Portmanteau'' morpheme. <ref>Cf. Lehmann (2004: R21). ''LGR'' (2008: rule 4B) suggest the semi-colon “;” as an alternative.</ref>
</div>
</div>


Line 196: Line 239:
== Optional rules: expert mode ==
== Optional rules: expert mode ==
=== An extra Glossing line ===
=== An extra Glossing line ===
<div id="Glossing_line">
In the expert mode, inflections are marked more specifically as to its type and degree of attachment. Additionally, morpheme boundaries are not only indicated in the gloss but also in the object language. Consequently, the encoder needs to add an '''extra glossing transliteration line''' between the original object language line and the glossing line.
In the expert mode, inflections are marked more specifically as to its type and degree of attachment. Additionally, morpheme boundaries are not only indicated in the gloss but also in the object language. Consequently, the encoder needs to add an '''extra glossing transliteration line''' between the original object language line and the glossing line.
</div>


; Example (to be explained below):
; Example (to be explained below):
Line 205: Line 250:
| '''Glossing <br/>transliteration''' || vorgestern <ref>For the lower case, cf. Lehmann (2004: R31).</ref> || bin || ich || aus || ei'''n-e'''m || Kur'''z=u'''rlaub || zurüc'''k=ge-k'''om'''m-e'''n.
| '''Glossing <br/>transliteration''' || vorgestern <ref>For the lower case, cf. Lehmann (2004: R31).</ref> || bin || ich || aus || ei'''n-e'''m || Kur'''z=u'''rlaub || zurüc'''k=ge-k'''om'''m-e'''n.
|-
|-
| '''Glossing <br/>line''' || the_day_<br/>before_yesterday || be.PRS.1SG || 1SG.NOM || out || '''a-M'''.DAT || shor'''t=v'''acation(M)[ SG.DAT] || bac'''k=P'''TCP.PR'''F<sub>1</sub>-c'''om'''e-P'''TCP.PRF<sub>1</sub>
| '''Glossing <br/>line''' || the_day_<br/>before_yesterday || be.PRS.1SG || 1SG.NOM || out || '''a-M'''.DAT || shor'''t=v'''acation(M)[SG.DAT] || bac'''k=P'''TCP.PR'''F<sub>1</sub>-c'''om'''e-P'''TCP.PRF<sub>1</sub>
|}
|}
{{Translation|‘I came back from a short vacation the day before yesterday.’}}
{{Translation|‘I came back from a short vacation the day before yesterday.’}}
Line 225: Line 270:
=== Inflection markup rules ===
=== Inflection markup rules ===
==== Affixes and clitics ====
==== Affixes and clitics ====
; (4a) Affix markup rules
<div id="Punctuation_hyphen">
; (6) Affix markup rules
: If one object language word contains a clearly and neatly separable '''affix''' (suffix or prefix), this affix should be attached to its stem '''in both, in the transcription and in the gloss''', by a '''hyphen “-”''' (rather than by a period “.” or colon “:”). <ref>''LGR'' (2008): rule 2; Lehmann (2004: R12).</ref>
: If one object language word contains a clearly and neatly separable '''affix''' (suffix or prefix), this affix should be attached to its stem '''in both, in the transcription and in the gloss''', by a '''hyphen “-”''' (rather than by a period “.” or colon “:”). <ref>''LGR'' (2008): rule 2; Lehmann (2004: R12).</ref>
</div>


; (4b) Clitic morpheme markup rules
<div id="Punctuation_equal_sign">
; (7) Clitic morpheme markup rules
: If an object language morpheme attaches to another word as a '''clitic''' (enclitic or proclitic), this clitic should be attached to its base '''in both, in the transcription and in the gloss''', by an '''equal sign “=”''' (rather than by a hyphen “-”). <ref>''LGR'' (2008): rule 2; Lehmann (2004: R15).</ref>
: If an object language morpheme attaches to another word as a '''clitic''' (enclitic or proclitic), this clitic should be attached to its base '''in both, in the transcription and in the gloss''', by an '''equal sign “=”''' (rather than by a hyphen “-”). <ref>''LGR'' (2008): rule 2; Lehmann (2004: R15).</ref>
</div>


; Example:
; Example:
Line 257: Line 306:
! Gender, case !! Word !! Glossing transcription !! Gloss
! Gender, case !! Word !! Glossing transcription !! Gloss
|-  
|-  
| M, NOM || ''ein'' || ein || ART.INDF.SG.M.NOM (''or rather'' ART.INDF.SG[M.NOM], ''see [[#Missing inflection|below]]'')
| M, NOM || ''ein'' || ein || ART.INDF.SG.M.NOM (''or rather'' ART.INDF.SG[M.NOM], ''see [[#Punctuation_square_brackets|below]]'')
|-
|-
| M, GEN || ''eines'' || ei'''n-e'''s || ART.INDF.S'''G-M'''.GEN
| M, GEN || ''eines'' || ei'''n-e'''s || ART.INDF.S'''G-M'''.GEN
Line 275: Line 324:


==== Circumfixes and other circum-morphemes ====
==== Circumfixes and other circum-morphemes ====
; (4c) Circum-morpheme markup recommendation
<div id="Punctuation_circumfix">
: If a split object language morpheme encircles another word from both sides as a '''circumfix''' or ‘circum-clitic’, or if two object language words encircle other words, we recommend to simply '''repeat the same gloss''' for both elements identically and mark both glosses with the '''same superscript index'''. <ref>Cf. ''LGR'' (2008): rule 8 (there without index) and Lehmann (2004: R17) with alternative suggestions.</ref>
; (8) Circum-morpheme markup recommendation
: If a split object language morpheme encircles another word from both sides as a '''circumfix''' or ‘circum-clitic’, or if two object language words encircle other words, we recommend to simply '''repeat the same gloss''' for both elements identically and mark both glosses with the '''same subscript index'''. <ref>Cf. ''LGR'' (2008): rule 8 (there without index) and Lehmann (2004: R17) with alternative suggestions.</ref>
</div>


; Examples:
; Examples:
Line 285: Line 336:
| šipr-am || '''ta-'''štapr'''-ī'''  
| šipr-am || '''ta-'''štapr'''-ī'''  
|-
|-
| writing(M)-ACC.SG || '''2SG.F<sub>1</sub>'''-write.PRF-'''2SG.F<sub>1</sub>'''
| writing(M)-ACC.SG || '''2SG.F<sub>1</sub>'''-write.PST-'''2SG.F<sub>1</sub>'''
|}
|}
{{Translation| ‘You have sent a letter.’}}
{{Translation| ‘You have sent a letter.’}}
Line 312: Line 363:


==== Infixes ====
==== Infixes ====
; (4d) Infix markup recommendation
<div id="Punctuation_angle_brackets">
; (9) Infix markup recommendation
: If one object language word contains a clearly and neatly separable '''infix''', this infix may optionally be marked '''in both, in the transcription and in the gloss''', by '''angle brackets “&lt;&nbsp;&gt;”''' (rather than by periods “.”, colons “:”, or hyphens “-”). In the gloss, the brackets might either follow or precede the gloss of the element with the infix.<ref>''LGR'' (2008): rule 9; Lehmann (2004: R18).</ref>
: If one object language word contains a clearly and neatly separable '''infix''', this infix may optionally be marked '''in both, in the transcription and in the gloss''', by '''angle brackets “&lt;&nbsp;&gt;”''' (rather than by periods “.”, colons “:”, or hyphens “-”). In the gloss, the brackets might either follow or precede the gloss of the element with the infix.<ref>''LGR'' (2008): rule 9; Lehmann (2004: R18).</ref>
</div>


; Example:
; Example:
Line 322: Line 375:
| šipr-am || ta-š'''&lt;ta&gt;'''pr-ī  
| šipr-am || ta-š'''&lt;ta&gt;'''pr-ī  
|-
|-
| letter(M)-ACC.SG || 2SG.F<sub>1</sub>-write'''&lt;PRF&gt;'''-2SG.F<sub>1</sub>
| letter(M)-ACC.SG || 2SG.F<sub>1</sub>-write'''&lt;PST&gt;'''-2SG.F<sub>1</sub>
|}
|}
{{Translation|‘You have sent a letter.’}}
{{Translation|‘You have sent a letter.’}}
Line 329: Line 382:


==== Reduplication phenomena ====
==== Reduplication phenomena ====
; (4e) Reduplication markup recommendation
<div id="Punctuation_tilde">
; (10) Reduplication markup recommendation
: Categories that are expressed by a regular '''reduplication''' phenomenon in a paradigm may optionally be marked '''in both, in the transcription and in the gloss''', with a '''tilde “~”''' (rather than with a period “.”, colon “:”, or hyphen “-”). <ref>''LGR'' (2008): rule 10; Lehmann (2004: R19).</ref>
: Categories that are expressed by a regular '''reduplication''' phenomenon in a paradigm may optionally be marked '''in both, in the transcription and in the gloss''', with a '''tilde “~”''' (rather than with a period “.”, colon “:”, or hyphen “-”). <ref>''LGR'' (2008): rule 10; Lehmann (2004: R19).</ref>
</div>


Cf. the following Egyptian paradigm:
Cf. the following Egyptian paradigm:
Line 347: Line 402:
If affixes, clitics, reduplications and/or infixes are marked by “-”, “=”, “~”, and “&lt;&nbsp;&gt;”, respectively, it is mandatory to obey the following rule:
If affixes, clitics, reduplications and/or infixes are marked by “-”, “=”, “~”, and “&lt;&nbsp;&gt;”, respectively, it is mandatory to obey the following rule:


; Correct sequential alignment rule
<div id="Correct_sequential_alignment">
; (11) Correct sequential alignment rule
: The number and sequence of hyphens “-”, equal signs “=”, tildes “~”, and angle brackets “&lt;&nbsp;&gt;” must always be exactly the same in the object language transliteration and the gloss. <ref>Lehmann (2004: R9, R10).</ref>
: The number and sequence of hyphens “-”, equal signs “=”, tildes “~”, and angle brackets “&lt;&nbsp;&gt;” must always be exactly the same in the object language transliteration and the gloss. <ref>Lehmann (2004: R9, R10).</ref>
</div>


Cf. for example:
Cf. for example:
Line 367: Line 424:


==== Missing inflection ====
==== Missing inflection ====
; (5) Missing inflection markup recommendation
<div id="Punctuation_square_brackets">
; (12) Missing inflection markup recommendation
: If one can determine a grammatical category of a word only by the fact that '''a morpheme (ending, affix, infix, ...) is missing''', this category should be attached to the gloss in '''square brackets “[&nbsp;]”''' (rather than by a period “.” or colon “:”). <ref>''LGR'' (2008): rule 6. Lehmann (2004: R24, R16) used “[&nbsp;]” and “(&nbsp;)” differently.</ref>
: If one can determine a grammatical category of a word only by the fact that '''a morpheme (ending, affix, infix, ...) is missing''', this category should be attached to the gloss in '''square brackets “[&nbsp;]”''' (rather than by a period “.” or colon “:”). <ref>''LGR'' (2008): rule 6. Lehmann (2004: R24, R16) used “[&nbsp;]” and “(&nbsp;)” differently.</ref>
</div>


Cf. the following paradigm:
Cf. the following paradigm:
Line 383: Line 442:
| SG, DAT || ''Urlaub'' || Urlaub || vacation'''['''SG.DAT''']''' (''or'' vacation'''['''SG.NGEN''']''')
| SG, DAT || ''Urlaub'' || Urlaub || vacation'''['''SG.DAT''']''' (''or'' vacation'''['''SG.NGEN''']''')
|-  
|-  
| PL, NOM || ''Urlaube'' || Urlau'''b-e''' || vacation-PL.NOM (''or'' vacation-PL.NOM;GEN)
| PL, NOM || ''Urlaube'' || Urlau'''b-e''' || vacation-PL.NOM (''or'' vacation-PL.NOM/GEN)
|-
|-
| PL, GEN || ''Urlaube'' || Urlau'''b-e''' || vacation-PL.GEN  (''or'' vacation-PL.NOM;GEN)
| PL, GEN || ''Urlaube'' || Urlau'''b-e''' || vacation-PL.GEN  (''or'' vacation-PL.NOM/GEN)
|-
|-
| PL, ACC || ''Urlauben'' || Urlau'''b-e''' || vacation-PL.ACC  (''or'' vacation-PL.ACC;DAT)
| PL, ACC || ''Urlauben'' || Urlau'''b-e''' || vacation-PL.ACC  (''or'' vacation-PL.ACC/DAT)
|-
|-
| PL, DAT ||''Urlauben'' || Urlau'''b-e''' || vacation-PL.DAT  (''or'' vacation-SG.ACC;DAT)
| PL, DAT ||''Urlauben'' || Urlau'''b-e''' || vacation-PL.DAT  (''or'' vacation-SG.ACC/DAT)
|}
|}


Line 415: Line 474:
</small>
</small>


Alternatively, one might want to explicitly mark the paradigmatic missing of a morpheme (ending, affix, infix, ...) in the transcription by the means of a '''‘zero-morpheme’ affix “-ø”'''. (Cf. the [[#Affix markup recommendation|Affix Markup Recommendation]] above.)
<div id="Punctuation_zero_morpheme">
Alternatively, one might want to explicitly mark the paradigmatic missing of a morpheme (ending, affix, infix, ...) in the transcription by the means of a '''‘zero-morpheme’ affix “-ø”'''. (Cf. the [[#Punctuation_hyphen|Affix Markup Recommendation]] above.)
</div>


; Example:
; Example:
Line 431: Line 492:


==== Covert, inherent categories ====
==== Covert, inherent categories ====
; (6) Inherent categories markup recommendation
<div id="Punctuation_parentheses">
; (13) Inherent categories markup recommendation
: Categories that are never expressed by a morpheme in a paradigm, i.e. categories that are rather inherent to a lexeme, may optionally be attached to the respective gloss in '''parentheses “(&nbsp;)”''' (rather than by a period “.” or square brackets “[&nbsp;]”). <ref>''LGR'' (2008): rule 7.</ref>
: Categories that are never expressed by a morpheme in a paradigm, i.e. categories that are rather inherent to a lexeme, may optionally be attached to the respective gloss in '''parentheses “(&nbsp;)”''' (rather than by a period “.” or square brackets “[&nbsp;]”). <ref>''LGR'' (2008): rule 7.</ref>
</div>


; Example:
; Example:
Line 462: Line 525:


==== ''Ablaut'' phenomena ====
==== ''Ablaut'' phenomena ====
; (7) ''Ablaut'' markup recommendation
<div id="Punctuation_backslash">
; (14) ''Ablaut'' markup recommendation
: Categories that are expressed by a regular '''''ablaut''''' phenomenon in a paradigm may optionally be attached to the gloss with a '''back slash “\”''' (rather than with a period “.” or colon “:”). <ref>''LGR'' (2008): rule 4d; cf. Lehmann (2004: R20).</ref>
: Categories that are expressed by a regular '''''ablaut''''' phenomenon in a paradigm may optionally be attached to the gloss with a '''back slash “\”''' (rather than with a period “.” or colon “:”). <ref>''LGR'' (2008): rule 4d; cf. Lehmann (2004: R20).</ref>
</div>


Cf. the following paradigm:
Cf. the following paradigm:
Line 478: Line 543:


==== Transfix (root-and-pattern morphology) ====
==== Transfix (root-and-pattern morphology) ====
In some languages, like many Afro-Asiatic languages, one can neatly separate (a) a word root and (b) a vowel pattern, although they are intertwined like two cogwheels. This phenomenon is known under as ‘root-and-pattern morphology’ or ‘transfixation’.
In some languages, like many Afro-Asiatic languages, one can neatly separate (a) a word root and (b) a vowel pattern, although they are intertwined like two cogwheels. This phenomenon is known as ‘root-and-pattern morphology’ or ‘transfixation’.


; (8) Transfix markup recommendation
<div id="Punctuation_transfix">
: Categories that are expressed by a transfix, i.e. a complex regular vocalic pattern applied to a (consonantal) root in a paradigm, may be marked as unspecified inflection (“:”, see [[#Punctuation colon|above]]).
; (15) Transfix markup recommendation
: Categories that are expressed by a transfix, i.e. a complex regular vocalic pattern applied to a (consonantal) root in a paradigm, may be marked as unspecified inflection (“:”, see [[#Punctuation_colon|above]]).
: Some scholars suggest to use the ''ablaut'' backslash “\” (see [[#Punctuation_backslash|above]]) also for transfixation. <ref>Cf. Lehmann (2004: R20).</ref>.
</div>


; Discussion:
; Discussion:
: Some scholars suggest to use the backslash (“\”; see [[#Punctuation backslash|above]]) also for transfixation. <ref>Cf. Lehmann (2004: R20).</ref>.
: Alternatively, Daniel Werning suggests to use a ‘new’ punctuation mark, e.g. “^”, to mark transfixation.
: Alternatively, we suggest to use a ‘new’ punctuation, e.g. '''“#”''', to mark transfixation.
 
; Current recommendation:
: Currently this Wiki uses '''“{{tf}}”''' as a mark.


Cf. the following examples from Akkadian:
Cf. the following examples from Akkadian:
{| class="wikitable"
{| class="wikitable"
|-  
|-  
| ''šapārum'' || š'''a'''p'''ā'''r-um || writ'''e:I'''NF-NOM.SG || ‘(to) write; (to) send’
| ''šapārum'' || š'''a'''p'''ā'''r-um || writ'''e:I'''NF-NOM.SG ''or'' writ'''e{{tf}}I'''NF-NOM.SG || ‘(to) write; (to) send’
|-  
|-  
| ''ašpur'' || a-šp'''u'''r || 1SG-writ'''e:P'''ST || ‘I sent’
| ''ašpur'' || a-šp'''u'''r || 1SG-writ'''e:P'''ST ''or'' 1SG-writ'''e{{tf}}P'''ST || ‘I sent’
|-  
|-  
| ''ašappar''  || a-š'''a'''p'''pa'''r  || 1SG-writ'''e:I'''PFV || ‘I send, I will send’
| ''ašappar''  || a-š'''a'''p'''pa'''r  || 1SG-writ'''e:I'''PFV ''or'' 1SG-writ'''e{{tf}}I'''PFV || ‘I send, I will send’
|-  
|-  
| ''aštapar'' || a-š'''&lt;ta&gt;'''p'''a'''r || 1SG-write'''&lt;PRF&gt;''' || ‘I have sent’
| ''aštapar'' || a-š'''&lt;ta&gt;'''p'''a'''r || 1SG-write'''&lt;PST&gt;''' ''or'' 1SG-writ'''e{{tf}}P'''ST || ‘I have sent’
|-  
|-  
| ''šiprum''  || š'''i'''pr-um  || '''writing(M)'''-NOM.SG || ‘message, writing; work’
| ''šiprum''  || š'''i'''pr-um  || '''writing(M)'''-NOM.SG || ‘message, writing; work’
Line 504: Line 574:


=== The period and the colon in expert mode ===
=== The period and the colon in expert mode ===
<div name="Punctuation period expert">
<div id="Punctuation_period_expert">
; (10) The period and the colon in expert mode
; (2a") The period and the colon in expert mode
: If one chooses to mark affixes, clitics, reduplications and/or infixes by “-”,“=”, “~”, and “&lt;&nbsp;&gt;”, respectively,  
: If one chooses to mark affixes, clitics, reduplications and/or infixes by “-”,“=”, “~”, and “&lt;&nbsp;&gt;”, respectively,  
: – elements in a gloss should only be joined by a colon “:” as a last resort for difficult cases like e.g. transfixation, and  
: – elements in a gloss should only be joined by a colon “:” as a last resort for difficult cases like e.g. transfixation, and  
Line 522: Line 592:
{{Translation|‘I came back from a short vacation the day before yesterday.’}}
{{Translation|‘I came back from a short vacation the day before yesterday.’}}


However, the encoder may of course choose to use the colon “:” instead of any of the other indications of separable morphemes (“-”, “=”, “&lt;&nbsp;&rt;”, “~”, “\”) – but not for ''Portmanteau'' morphemes. But remember that that, differently to the cases of “-”, “=”, “&lt;&nbsp;&rt;”, and “~”, the colon “:” in the gloss is not supposed to match with a colon “:” in the Glossing transliteration line.  
However, the encoder may of course choose to use the colon “:” instead of any of the other indications of separable morphemes (“-”, “=”, “&lt;&nbsp;&gt;”, “~”, “\”) – but not for ''Portmanteau'' morphemes. But remember that, differently to the cases of “-”, “=”, “&lt;&nbsp;&gt;”, and “~”, the colon “:” in the gloss is not supposed to match with a colon “:” in the Glossing transliteration line.  


Note that a separate glossing transcription line is not necessary if the encoder uses only periods “.”, colons “:”, backslashes “\”, parentheses “(&nbsp;)”, and square brackets “[&nbsp;]”.
Note that a separate glossing transcription line is not necessary if the encoder uses only periods “.”, colons “:”, backslashes “\”, parentheses “(&nbsp;)”, and square brackets “[&nbsp;]”.
Line 534: Line 604:
== Bibliography ==
== Bibliography ==
* Di Biase Dyson, Camilla, Frank Kammerzell &amp; Daniel A. Werning (2009). [http://wwwuser.gwdg.de/%7Edwernin/published/DiBiase_Kammerzell_Werning-2009-Glossing_Ancient_Egyptian.pdf Glossing Ancient Egyptian. Suggestions for Adapting the Leipzig Glossing Rules]. In: ''Lingua Aegyptia. Journal of Egyptian Language Studies'' 17: 243–266.
* Di Biase Dyson, Camilla, Frank Kammerzell &amp; Daniel A. Werning (2009). [http://wwwuser.gwdg.de/%7Edwernin/published/DiBiase_Kammerzell_Werning-2009-Glossing_Ancient_Egyptian.pdf Glossing Ancient Egyptian. Suggestions for Adapting the Leipzig Glossing Rules]. In: ''Lingua Aegyptia. Journal of Egyptian Language Studies'' 17: 243–266.
* Kutscher, Silvia &amp; Daniel A. Werning (eds.) (forthc.). [http://www.degruyter.com/view/product/204910 ''On Ancient Grammars of Space: Linguistic Research on the Expression of Spatial Relations and Motion in Ancient Languages''], Topoi. Berlin Studies of the Ancient World, Berlin: de Gruyter, ISBN 978-3110311358.
* Kutscher, Silvia &amp; Daniel A. Werning (eds.) (2014). [http://www.degruyter.com/view/books/9783110311358/9783110311358.xxv/9783110311358.xxv.xml?format=EBOK ''On Ancient Grammars of Space: Linguistic Research on the Expression of Spatial Relations and Motion in Ancient Languages''], Topoi. Berlin Studies of the Ancient World, Berlin: de Gruyter, ISBN 978-3110311358.
* Lehmann, Christian (2004). Interlinear Morphemic Glossing. In: Booij, Geert, Christian Lehmann, Joachim Mugdan & Stavros Skopeteas (eds.), ''Morphologie. Ein internationales Handbuch zur Flexion und Wortbildung. 2. Halbband'', Handbücher der Sprach- und Kommunikationswissenschaft 17/2, Berlin: De Gruyter, 1834–1857 (online manuscript: http://www.folialinguistica.com/documents/Interlinearmorphemicglossing.pdf)
* Lehmann, Christian (2004). Interlinear Morphemic Glossing. In: Booij, Geert, Christian Lehmann, Joachim Mugdan & Stavros Skopeteas (eds.), ''Morphologie. Ein internationales Handbuch zur Flexion und Wortbildung. 2. Halbband'', Handbücher der Sprach- und Kommunikationswissenschaft 17/2, Berlin: De Gruyter, 1834–1857 (online manuscript: http://www.folialinguistica.com/documents/Interlinearmorphemicglossing.pdf)
* ''LGR'' (2008) = ''The Leipzig Glossing Rules: Conventions for Interlinear Morpheme-by-Morpheme Glosses'', ed. by the Department of Linguistics of the Max Planck Institute for Evolutionary Anthropology (Bernard Comrie, Martin Haspelmath) and by the Department of Linguistics of the University of Leipzig (Balthasar Bickel), http://www.eva.mpg.de/lingua/resources/glossing-rules.php, Leipzig, 12. Sept. 2008.
* ''LGR'' (2008) = ''The Leipzig Glossing Rules: Conventions for Interlinear Morpheme-by-Morpheme Glosses'', ed. by the Department of Linguistics of the Max Planck Institute for Evolutionary Anthropology (Bernard Comrie, Martin Haspelmath) and by the Department of Linguistics of the University of Leipzig (Balthasar Bickel), http://www.eva.mpg.de/lingua/resources/glossing-rules.php, Leipzig, 12. Sept. 2008.

Latest revision as of 11:12, 13 February 2019

Core rules[edit | edit source]

Alignment[edit | edit source]

(1) Alignment Rule
An object language word and its gloss need to be arranged vertically left-aligned. [1]
Example
Vorgestern bin ich aus einem Kurzurlaub zurückgekommen.
the.day.before.yesterday am I out a short.vacation back.come
‘I came back from a short vacation the day before yesterday.’
 

But not:

Vorgestern bin ich von einem Kurzurlaub zurückgekommen.
the.day.before.yesterday am I out a short.vacation back.come

The best way to edit this in text editing programs is by the means of invisible tables, i.e. tables without border lines. (Whitespaces like blanks or tabs are not very helpful for this purpose.)


One-to-Many Correspondences[edit | edit source]

One object language word = many gloss elements[edit | edit source]

(2a) Standard Joining Rule (for the gloss)
Within a pair of an object language word and gloss, neither the word nor the gloss may contain any whitespaces (blanks, tabs).
If one object language word corresponds to two or more elements in the gloss, these elements have to be joined by a punctuation mark.
The standard punctuation mark for joining elements in the gloss is the period “.”. [2]
Example
Vorgestern bin ich aus einem Kurzurlaub zurückgekommen.
the.day.before.yesterday am I out a short.vacation back.come
‘I came back from a short vacation the day before yesterday.’
 

But not:

Vorgestern bin ich aus einem Kurzurlaub zurückgekommen.
the day before yesterday am I out a short vacation back come

Standard exception to the Standard Joining Rule
The sequence PERSON – NUMBER is usually spelled simply without a period “.”, i.e. abbreviated as e.g. “3PL” (instead of “3.PL”). [3]

For another meaning of the period “.” in cases in which other punctuation marks like colons “:”, hyphens “-” or else are also used, see The Period in Expert Mode section below.


Compact translation phrases in the gloss[edit | edit source]
(2b) Compact phrase joining recommendation
If one object language word corresponds to a compact multi-word phrase translation in the gloss, these elements should rather be joined by an underscore “_” than by a period “.”. [4]
Example
Vorgestern bin ich aus einem Kurzurlaub zurückgekommen.
the_day_before_yesterday am I out a short.vacation back.come

Rather than

Vorgestern bin ich aus einem Kurzurlaub zurückgekommen.
the.day.before.yesterday am I out a short.vacation back.come

FAQ
What is the difference between the case of “vorgestern – the_day_before_yesterday” and “Kurzurlaub – short.vacation”?
In the case of “Kurzurlaub – short.vacation”, the object language word “Kurzurlaub” actually contains the separate elements “short” (“kurz”) and “vacation” (“Urlaub”) – and only these elements. In the case of “vorgestern – the_day_before_yesterday – vorgestern”, on the other hand, the object language word “vorgestern” does not contain the elements “the”, “day”, “before”, and “yesterday” as four separate units. “The day before yesterday” is rather a fixed combined phrase.
But “vorgestern” does contain the elements “before” and “yesterday”!
In the spirit of the Compact Phrase Joining Rule, one may therefore gloss “vorgestern” either as “before.yesterday” or “the_day_before_yesterday”.


Many object language words = one gloss element[edit | edit source]

(2c) Standard Joining Rule for object language words
If two or more object language words corresponds to one element in the gloss, these elements have to be joined by a punctuation mark. The standard punctuation mark for joining object language words that correspond to one single gloss is the underscore “_” (rather than the period “.”). [5]
Example
I came back from a short vacation the_day_before_yesterday
ich kam zurück von ein kurz Urlaub vorgestern
‘Vorgestern bin ich aus einem Kurzurlaub zurückgekommen.’
 

But not:

I came back from a short vacation the day before yesterday
ich kam zurück von ein kurz Urlaub vorgestern


Analyzing grammatical categories[edit | edit source]

Grammatical morphemes[edit | edit source]

(3) Grammatical categories markup rule
Grammatical categories marked on or inherent to the object language word may be analyzed in the gloss. These grammatical categories have to be typeset in small caps (small capital letters), or else – but less elegant – in normal capital letters.
For the sake of space, frequent grammatical categories are usually abbreviated. [6]

For common glossing abbreviations, see the Glossing Abbreviations section.

Example
Vorgestern bin ich aus einem Kurzurlaub zurückgekommen.
the_day_before_yesterday be.PRS.1SG 1SG.NOM out ART.INDF.SG.M.DAT short.vacation.M.SG.DAT back.come.PTCP.PRF
‘I came back from a short vacation the day before yesterday.’
 

Alternatively, one might want to leave some elements unanalyzed:

Vorgestern bin ich aus einem Kurzurlaub zurückgekommen.
the_day_before_yesterday am I out a.SG.M.DAT short.vacation.M.SG.DAT back.come.PTCP.PRF


Ambiguous morphemes[edit | edit source]

(4) Ambiguous polysemous morphemes recommendation
If a morpheme has two or more different meanings, i.e. if it is polysemous, the encoder might optionally want to give two or more of the meanings separated by a slash “/”. [7]

Cf. the following paradigm:

Number, case Word Gloss
SG, NOM Urlaub vacation.SG.NOM or vacation.SG.NOM/ACC/DAT or vacation.SG.NGEN
SG, GEN Urlaubs vacation.SG.GEN
SG, ACC Urlaub vacation.SG.ACC or vacation.SG.NOM/ACC/DAT or vacation.SG.NGEN
SG, DAT Urlaub vacation.SG.DAT or vacation.SG.NOM/ACC/DAT or vacation.SG.NGEN
PL, NOM Urlaube vacation.PL.NOM or vacation.PL.NOM/GEN
PL, GEN Urlaube vacation.PL.GEN or vacation.PL.NOM/GEN
PL, ACC Urlauben vacation.PL.ACC or vacation.PL.ACC/DAT
PL, DAT Urlauben vacation.PL.DAT or vacation.PL.ACC/DAT



Optional rules: advanced mode[edit | edit source]

Some words are neatly separable into different morphemes, others are not. In an advanced mode of glossing the encoder may distinguish between separable morphemes, ‘joined’ by a colon (“:”), and inseparable morphemes, ‘joined’ by a period (“.”).

General marking of separable inflection[edit | edit source]

(5) Unspecified inflection markup
If one object language word corresponds to two or more elements in the gloss that can be distinguished between, theoretically, but the encoder is not able to or does not want to specify the type of inflection or the morpheme boundary, these elements may be joined (or rather separated) in the gloss by a colon “:” (rather than by a period “.”). [8]
Example
Vorgestern bin ich aus einem Kurzurlaub zurückgekommen.
the_day_before_yesterday be.PRS.1SG 1SG.NOM out ART.INDF.SG:M.DAT short:vacation.M:SG.DAT back:come:PTCP.PRF
‘I came back from a short vacation the day before yesterday.’
 

Rather than

Vorgestern bin ich aus einem Kurzurlaub zurückgekommen.
the_day_before_yesterday be.PRS.1SG 1SG.NOM out ART.INDF.SG.M.DAT short.vacation.M.SG.DAT back.come.PTCP.PRF

Note that, consequently, the period (“.”) has a more precise meaning than in the advanced mode (see below).


The period in advanced mode[edit | edit source]

(2a') The period in advanced mode
If one chooses to mark separable morphemes by a colon “:”, elements in a gloss should only be joined by a period “.”, if these are inseparably fused in the object language word, i.e. if they are part of a Portmanteau morpheme. [9]
Example
Vorgestern bin ich aus einem Kurzurlaub zurückgekommen.
the_day_before_yesterday be.PRS.1SG 1SG.NOM out a:M.DAT short:vacation(M)[SG.DAT] back:come:PTCP.PRF
‘I came back from a short vacation the day before yesterday.’
 



Optional rules: expert mode[edit | edit source]

An extra Glossing line[edit | edit source]

In the expert mode, inflections are marked more specifically as to its type and degree of attachment. Additionally, morpheme boundaries are not only indicated in the gloss but also in the object language. Consequently, the encoder needs to add an extra glossing transliteration line between the original object language line and the glossing line.

Example (to be explained below)
Original Vorgestern bin ich aus einem Kurzurlaub zurückgekommen.
Glossing
transliteration		 vorgestern [10] bin ich aus ein-em Kurz=urlaub zurück=ge-komm-en.
Glossing
line		 the_day_
before_yesterday		 be.PRS.1SG 1SG.NOM out a-M.DAT short=vacation(M)[SG.DAT] back=PTCP.PRF1-come-PTCP.PRF1
‘I came back from a short vacation the day before yesterday.’
 


One might then think about leaving out the ‘Original’ line. This is an issue that relates to the kind of one’s intended readers.

Example (to be explained below)
Glossing
transliteration		 Vorgestern bin ich aus ein-em Kurz=urlaub zurück=ge-komm-en.
Glossing
line		 the_day_
before_yesterday		 be.PRS.1SG 1SG.NOM out a-M.DAT short=vacation(M)[ SG.DAT] back=PTCP.PRF1-come-PTCP.PRF1
‘I came back from a short vacation the day before yesterday.’
 


Inflection markup rules[edit | edit source]

Affixes and clitics[edit | edit source]

(6) Affix markup rules
If one object language word contains a clearly and neatly separable affix (suffix or prefix), this affix should be attached to its stem in both, in the transcription and in the gloss, by a hyphen “-” (rather than by a period “.” or colon “:”). [11]
(7) Clitic morpheme markup rules
If an object language morpheme attaches to another word as a clitic (enclitic or proclitic), this clitic should be attached to its base in both, in the transcription and in the gloss, by an equal sign “=” (rather than by a hyphen “-”). [12]
Example
Vorgestern bin ich aus einem Kurzurlaub zurückgekommen.
Vorgestern bin ich aus ein-em Kurz=urlaub zurück=ge-komm-en.
the_day_before_yesterday be.PRS.1SG 1SG.NOM out a-M.DAT short=vacation.M.SG.DAT back=PTCP.PRF-come-PTCP.PRF
‘I came back from a short vacation the day before yesterday.’
 

Rather than

Vorgestern bin ich aus einem Kurzurlaub zurückgekommen.
the_day_before_yesterday be.PRS.1SG 1SG.NOM out a.M.DAT short.vacation.M.SG.DAT back.come.PTCP.PRF

For “einem”, cf. the following paradigm:

Gender, case Word Glossing transcription Gloss
M, NOM ein ein ART.INDF.SG.M.NOM (or rather ART.INDF.SG[M.NOM], see below)
M, GEN eines ein-es ART.INDF.SG-M.GEN
M, ACC eine' ein-en ART.INDF.SG-M.ACC
M, DAT eine' ein-em ART.INDF.SG-M.DAT
F, NOM eine ein-e ART.INDF.SG-F.NOM
... ... ... ...

Note that e.g. “bin” cannot neatly be separated into different morphemes. Therefore, all its semantic elements are still fused by periods ‘.’ in the gloss.


Circumfixes and other circum-morphemes[edit | edit source]

(8) Circum-morpheme markup recommendation
If a split object language morpheme encircles another word from both sides as a circumfix or ‘circum-clitic’, or if two object language words encircle other words, we recommend to simply repeat the same gloss for both elements identically and mark both glosses with the same subscript index. [13]
Examples
šipram taštaprī
šipr-am ta-štapr-ī
writing(M)-ACC.SG 2SG.F1-write.PST-2SG.F1
‘You have sent a letter.’
 


Vorgestern bin ich aus einem Kurzurlaub zurückgekommen.
Vorgestern bin ich aus ein-em Kurz=urlaub zurück=ge-komm-en.
the_day_before_yesterday be.PRS.1SG 1SG.NOM out a-M.DAT short=vacation.M.SG.DAT back=PTCP.PRF1-come-PTCP.PRF1
‘I came back from a short vacation the day before yesterday.’
 


Je ne sais pas pourquoi.
1SG NOT1 know.PRS.1SG NOT1 why
‘I don’t know why.’
 


Infixes[edit | edit source]

(9) Infix markup recommendation
If one object language word contains a clearly and neatly separable infix, this infix may optionally be marked in both, in the transcription and in the gloss, by angle brackets “< >” (rather than by periods “.”, colons “:”, or hyphens “-”). In the gloss, the brackets might either follow or precede the gloss of the element with the infix.[14]
Example
šipram taštaprī
šipr-am ta-š<ta>pr-ī
letter(M)-ACC.SG 2SG.F1-write<PST>-2SG.F1
‘You have sent a letter.’
 


Reduplication phenomena[edit | edit source]

(10) Reduplication markup recommendation
Categories that are expressed by a regular reduplication phenomenon in a paradigm may optionally be marked in both, in the transcription and in the gloss, with a tilde “~” (rather than with a period “.”, colon “:”, or hyphen “-”). [15]

Cf. the following Egyptian paradigm:

Verbal Number Word Glossing transliteration Gloss Translation
(unmarked) jrt jr-t do.PTCP-F ‘(she) who does/did’
DISTR jrrt jr~r-t do~PTCP.DISTR-F ‘(she) who (repeatedly, ...) does/used to do’


Correct sequential alignment rule[edit | edit source]

If affixes, clitics, reduplications and/or infixes are marked by “-”, “=”, “~”, and “< >”, respectively, it is mandatory to obey the following rule:

(11) Correct sequential alignment rule
The number and sequence of hyphens “-”, equal signs “=”, tildes “~”, and angle brackets “< >” must always be exactly the same in the object language transliteration and the gloss. [16]

Cf. for example:

Correct Wrong Wrong Correct Wrong
jrrtf jrrtf jrrtf ambulabam ambulabam
jr~r-t=f jrr-t=f jr~r.t=f ambula-ba-m
do~DISTR.REL-F=3SG.M do~DISTR.REL-F=3SG.M do~DISTR.REL-F=3SG.M walk-IPFV-1SG walk-IPFV-1SG
‘what he used to do’ ‘I walked’


Missing inflection[edit | edit source]

(12) Missing inflection markup recommendation
If one can determine a grammatical category of a word only by the fact that a morpheme (ending, affix, infix, ...) is missing, this category should be attached to the gloss in square brackets “[ ]” (rather than by a period “.” or colon “:”). [17]

Cf. the following paradigm:

Number, case Word Glossing transliteration Gloss
SG, NOM Urlaub Urlaub vacation[SG.NOM] (or vacation[SG.NGEN])
SG, GEN Urlaubs Urlaub-s vacation-SG.GEN
SG, ACC Urlaub Urlaub vacation[SG.ACC] (or vacation[SG.NGEN])
SG, DAT Urlaub Urlaub vacation[SG.DAT] (or vacation[SG.NGEN])
PL, NOM Urlaube Urlaub-e vacation-PL.NOM (or vacation-PL.NOM/GEN)
PL, GEN Urlaube Urlaub-e vacation-PL.GEN (or vacation-PL.NOM/GEN)
PL, ACC Urlauben Urlaub-e vacation-PL.ACC (or vacation-PL.ACC/DAT)
PL, DAT Urlauben Urlaub-e vacation-PL.DAT (or vacation-SG.ACC/DAT)
Example
Vorgestern bin ich aus einem Kurzurlaub zurückgekommen.
Vorgestern bin ich aus ein-em Kurz=urlaub zurück=ge-komm-en.
the_day_before_yesterday be.PRS.1SG 1SG.NOM out a-M.DAT short=vacation.M[SG.DAT] back=PTCP.PRF1-come-PTCP.PRF1
‘I came back from a short vacation the day before yesterday.’
 

Rather than

Vorgestern bin ich aus einem Kurzurlaub zurückgekommen.
Vorgestern bin ich aus ein-em Kurz=urlaub zurück=ge-komm-en.
the_day_before_yesterday be.PRS.1SG 1SG.NOM out a-M.DAT short=vacation.M.SG.DAT back=PTCP.PRF1-come-PTCP.PRF1

Alternatively, one might want to explicitly mark the paradigmatic missing of a morpheme (ending, affix, infix, ...) in the transcription by the means of a ‘zero-morpheme’ affix “-ø”. (Cf. the Affix Markup Recommendation above.)

Example
Vorgestern bin ich aus einem Kurzurlaub zurückgekommen.
Vorgestern bin ich aus ein-em Kurz=urlaub-ø zurück=ge-komm-en.
the_day_before_yesterday be.PRS.1SG 1SG.NOM out a-M.DAT short=vacation.M-SG.DAT back=PTCP.PRF1-come-PTCP.PRF1
‘I came back from a short vacation the day before yesterday.’
 


Covert, inherent categories[edit | edit source]

(13) Inherent categories markup recommendation
Categories that are never expressed by a morpheme in a paradigm, i.e. categories that are rather inherent to a lexeme, may optionally be attached to the respective gloss in parentheses “( )” (rather than by a period “.” or square brackets “[ ]”). [18]
Example
Vorgestern bin ich aus einem Kurzurlaub zurückgekommen.
Vorgestern bin ich aus ein-em Kurz=urlaub zurück=ge-komm-en.
the_day_before_yesterday be.PRS.1SG 1SG.NOM out a-M.DAT short=vacation(M)[SG.DAT] back=PTCP.PRF1-come-PTCP.PRF1
‘I came back from a short vacation the day before yesterday.’
 

Rather than

Vorgestern bin ich aus einem Kurzurlaub zurückgekommen.
Vorgestern bin ich aus ein-em Kurz=urlaub zurück=ge-komm-en.
the_day_before_yesterday be.PRS.1SG 1SG.NOM out a-M.DAT short=vacation.M[SG.DAT] back=PTCP.PRF1-come-PTCP.PRF1

Caution: This rule may eventually generate some difficult questions, like whether e.g. “ich” should be glossed as “1SG.NOM” or “1SG(NOM)”.


Ablaut phenomena[edit | edit source]

(14) Ablaut markup recommendation
Categories that are expressed by a regular ablaut phenomenon in a paradigm may optionally be attached to the gloss with a back slash “\” (rather than with a period “.” or colon “:”). [19]

Cf. the following paradigm:

Number Word Gloss
SG Vater father(M).SG or better father(M)[SG]
PL Väter father(M):PL or better father(M)\PL


Transfix (root-and-pattern morphology)[edit | edit source]

In some languages, like many Afro-Asiatic languages, one can neatly separate (a) a word root and (b) a vowel pattern, although they are intertwined like two cogwheels. This phenomenon is known as ‘root-and-pattern morphology’ or ‘transfixation’.

(15) Transfix markup recommendation
Categories that are expressed by a transfix, i.e. a complex regular vocalic pattern applied to a (consonantal) root in a paradigm, may be marked as unspecified inflection (“:”, see above).
Some scholars suggest to use the ablaut backslash “\” (see above) also for transfixation. [20].
Discussion
Alternatively, Daniel Werning suggests to use a ‘new’ punctuation mark, e.g. “^”, to mark transfixation.
Current recommendation
Currently this Wiki uses “\” as a mark.

Cf. the following examples from Akkadian:

šapārum šapār-um write:INF-NOM.SG or write\INF-NOM.SG ‘(to) write; (to) send’
ašpur a-špur 1SG-write:PST or 1SG-write\PST ‘I sent’
ašappar a-šappar 1SG-write:IPFV or 1SG-write\IPFV ‘I send, I will send’
aštapar a-š<ta>par 1SG-write<PST> or 1SG-write\PST ‘I have sent’
šiprum šipr-um writing(M)-NOM.SG ‘message, writing; work’


The period and the colon in expert mode[edit | edit source]

(2a") The period and the colon in expert mode
If one chooses to mark affixes, clitics, reduplications and/or infixes by “-”,“=”, “~”, and “< >”, respectively,
– elements in a gloss should only be joined by a colon “:” as a last resort for difficult cases like e.g. transfixation, and
– elements in a gloss should only be joined by a period “.”, if these are inseparably fused in the object language word, i.e. if they are part of a Portmanteau morpheme. [21]
Example
Vorgestern bin ich aus einem Kurzurlaub zurückgekommen.
Vorgestern bin ich aus ein-em Kurz=urlaub zurück=gekommen.
the_day_before_yesterday be.PRS.1SG 1SG.NOM out a-M.DAT short=vacation(M)[SG.DAT] back=come:PTCP.PRF
‘I came back from a short vacation the day before yesterday.’
 

However, the encoder may of course choose to use the colon “:” instead of any of the other indications of separable morphemes (“-”, “=”, “< >”, “~”, “\”) – but not for Portmanteau morphemes. But remember that, differently to the cases of “-”, “=”, “< >”, and “~”, the colon “:” in the gloss is not supposed to match with a colon “:” in the Glossing transliteration line.

Note that a separate glossing transcription line is not necessary if the encoder uses only periods “.”, colons “:”, backslashes “\”, parentheses “( )”, and square brackets “[ ]”.



References[edit | edit source]

  1. ↑ LGR (2008): rule 1; cf. Lehmann (2004: R27).
  2. ↑ Cf. LGR (2008): rule 4.
  3. ↑ LGR (2008): rule 5.
  4. ↑ LGR (2008): rule 4a; Lehmann (2004: R23).
  5. ↑ Lehmann (2004: R11).
  6. ↑ Cf. LGR (2008): rule 3; Lehmann (2004: R29).
  7. ↑ Lehmann (2004: §3.5, tab. 6.2).
  8. ↑ LGR (2008): rule 4c; cf. Lehmann (2004: R13).
  9. ↑ Cf. Lehmann (2004: R21). LGR (2008: rule 4B) suggest the semi-colon “;” as an alternative.
  10. ↑ For the lower case, cf. Lehmann (2004: R31).
  11. ↑ LGR (2008): rule 2; Lehmann (2004: R12).
  12. ↑ LGR (2008): rule 2; Lehmann (2004: R15).
  13. ↑ Cf. LGR (2008): rule 8 (there without index) and Lehmann (2004: R17) with alternative suggestions.
  14. ↑ LGR (2008): rule 9; Lehmann (2004: R18).
  15. ↑ LGR (2008): rule 10; Lehmann (2004: R19).
  16. ↑ Lehmann (2004: R9, R10).
  17. ↑ LGR (2008): rule 6. Lehmann (2004: R24, R16) used “[ ]” and “( )” differently.
  18. ↑ LGR (2008): rule 7.
  19. ↑ LGR (2008): rule 4d; cf. Lehmann (2004: R20).
  20. ↑ Cf. Lehmann (2004: R20).
  21. ↑ Cf. Lehmann (2004: R21).

Bibliography[edit | edit source]


Expert Glossing Punctuation
X:C X-C X=C X~C X<C> C1...C1 X\C X\C X[C] X.C X(C) X_Y C/D
unspecified affix clitic reduplication infix circumfix ablaut transfix ø morpheme Portmanteau inherent phrase polysemous
Retrieved from "https://wikis.hu-berlin.de/interlinear_glossing/w/index.php?title=Glossing_Rules&oldid=11283"