Editing Glossing Rules

From Glossing Ancient Languages

Jump to: navigation, search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
== Core rules ==
== Core rules ==
{{Separating bar}}
=== 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.</ref>  


; Example:
; Example:
Line 27: Line 24:


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.)
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.)
{{Separating bar}}


=== 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 58: Line 51:
</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>''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>Cf. ''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 [[#Punctuation_period_expert|The Period in 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 [[#The period in the expert mode|The Period in the Expert Mode section]] below.  
 
{{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.</ref>
</div>


; Example:
; Example:
Line 78: Line 65:
| ''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 || short.vacation || back.come
| 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
|}
|}


Line 87: Line 74:
| ''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 || short.vacation || back.come
| 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
|}
|}
</small>
</small>
Line 97: Line 84:
: ''But ''“vorgestern”'' does contain the elements ''“before”'' and ''“yesterday”''!''   
: ''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 “befor'''e.y'''esterday” or “'''the_day_b'''efor'''e_y'''esterday”.
: In the spirit of the Compact Phrase Joining Rule, one may therefore gloss “vorgestern” either as “befor'''e.y'''esterday” or “'''the_day_b'''efor'''e_y'''esterday”.
{{Separating bar}}


==== 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 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>
: 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>Kutscher &amp; Werning (forthc.): xxv. This rule is not part of the ''LGR'' (2008); but cf. ''LGR'' (2008): rule 4.</ref>
</div>


; Example:
; Example:
Line 124: Line 107:
|}
|}
</small>
</small>
{{Separating bar}}


=== Analyzing grammatical categories ===
=== Analyzing grammatical categories ===
==== Grammatical morphemes ====
; (3) Categories Markup Rule
<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.</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 154: Line 132:
|}
|}


{{Separating bar}}
== Optional expert recommendations ==
 
=== Inflection markup recommendations ===
==== 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'''
|}
 
{{Separating bar}}
{{Separating bar}}
 
== Optional rules: advanced mode ==
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 ===
<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>
</div>
 
; Example:
{| {{Glossing table}}
|-
| ''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
|}
{{Translation|‘I came back from a short vacation the day before yesterday.’}}
 
<small>
Rather than
{| {{Wrong glossing table}}
|-
| ''Vorgestern'' || ''bin'' || ''ich'' || ''aus'' || ''einem'' || ''Kurzurlaub'' || ''zurückgekommen''.
|-
| 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
|}
</small>
 
Note that, consequently, the period (“.”) has a more precise meaning than in the advanced mode (see [[#Punctuation_period_advanced|below]]).
 
{{Separating bar}}
 
=== The period in advanced mode ===
<div id="Punctuation_period_advanced">
; (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). ''LGR'' (2008: rule 4B) suggest the semi-colon “;” as an alternative.</ref>
</div>
 
; Example:
{| {{Glossing table}}
|-
| ''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'''
|}
{{Translation|‘I came back from a short vacation the day before yesterday.’}}
 
{{Separating bar}}
{{Separating bar}}
 
== Optional rules: expert mode ==
=== 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.
</div>
 
; Example (to be explained below):
{| {{Glossing table}}
|-
| '''Original''' || ''Vorgestern'' || ''bin'' || ''ich'' || ''aus'' || ''einem'' || ''Kurzurlaub'' || ''zurückgekommen''.
|-
| '''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>
|}
{{Translation|‘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 table}}
|-
| '''Glossing <br/>transliteration''' || ''Vorgestern'' || ''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>
|}
{{Translation|‘I came back from a short vacation the day before yesterday.’}}
 
{{Separating bar}}
 
=== Inflection markup rules ===
==== Affixes and clitics ====
==== Affixes and clitics ====
<div id="Punctuation_hyphen">
; (4a) Affix markup recommendation
; (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 “.”). <ref>''LGR'' (2008): rule 2.</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>


<div id="Punctuation_equal_sign">
; (4b) Clitic morpheme markup recommendation
; (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.</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 306: Line 167:
! 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 [[#Punctuation_square_brackets|below]]'')
| M, NOM || ''ein'' || ein || ART.INDF.SG.M.NOM (''or rather'' ART.INDF.SG[M.NOM], ''see [[#Missing inflection|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 320: Line 181:


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.   
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.   
{{Separating bar}}


==== Circumfixes and other circum-morphemes ====
==== Circumfixes and other circum-morphemes ====
<div id="Punctuation_circumfix">
; (4c) Circum-morpheme markup recommendation
; (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 superscript index'''. <ref>Cf. ''LGR'' (2008): rule 8 (there without index) with some alternative suggestions.</ref>
: 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 336: Line 193:
| šipr-am || '''ta-'''štapr'''-ī'''  
| šipr-am || '''ta-'''štapr'''-ī'''  
|-
|-
| writing(M)-ACC.SG || '''2SG.F<sub>1</sub>'''-write.PST-'''2SG.F<sub>1</sub>'''
| writing(M)-ACC.SG || '''2SG.F<sub>1</sub>'''-write.PRF-'''2SG.F<sub>1</sub>'''
|}
|}
{{Translation| ‘You have sent a letter.’}}
{{Translation| ‘You have sent a letter.’}}
Line 359: Line 216:
|}
|}
{{Translation|‘I don’t know why.’}}
{{Translation|‘I don’t know why.’}}
{{Separating bar}}


==== Infixes ====
==== Infixes ====
<div id="Punctuation_angle_brackets">
; (4d) Infix markup recommendation
; (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 a period “.” 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.</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 375: Line 228:
| š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;PST&gt;'''-2SG.F<sub>1</sub>
| letter(M)-ACC.SG || 2SG.F<sub>1</sub>-write'''&lt;PRF&gt;'''-2SG.F<sub>1</sub>
|}
|}
{{Translation|‘You have sent a letter.’}}
{{Translation|‘You have sent a letter.’}}
{{Separating bar}}


==== Reduplication phenomena ====
==== Reduplication phenomena ====
<div id="Punctuation_tilde">
; (4e) Reduplication markup recommendation
; (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 hyphen -” or period .”). <ref>''LGR'' (2008): rule 10.</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 396: Line 245:
| DISTR || ''jrrt'' || jr'''~r'''-t || d'''o~P'''TCP.DISTR-F || ‘(she) who (repeatedly, ...) does/used to do’
| DISTR || ''jrrt'' || jr'''~r'''-t || d'''o~P'''TCP.DISTR-F || ‘(she) who (repeatedly, ...) does/used to do’
|}
|}
{{Separating bar}}


==== Correct sequential alignment rule ====
==== Correct sequential alignment rule ====
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:


<div id="Correct_sequential_alignment">
; Correct sequential alignment rule
; (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.
: 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 420: Line 265:
| ‘what he used to do’ || || || ‘I walked’
| ‘what he used to do’ || || || ‘I walked’
|}
|}
{{Separating bar}}


==== Missing inflection ====
==== Missing inflection ====
<div id="Punctuation_square_brackets">
; (5) Missing inflection markup recommendation
; (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 else). <ref>''LGR'' (2008): rule 6.</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 442: Line 283:
| 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 474: Line 315:
</small>
</small>


<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 [[#Affix markup recommendation|Affix Markup Recommendation]] above.)
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 488: Line 327:
|}
|}
{{Translation|‘I came back from a short vacation the day before yesterday.’}}
{{Translation|‘I came back from a short vacation the day before yesterday.’}}
{{Separating bar}}


==== Covert, inherent categories ====
==== Covert, inherent categories ====
<div id="Punctuation_parentheses">
; (6) Inherent categories markup recommendation
; (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 522: Line 357:
Caution: This rule may eventually generate some difficult questions, like whether e.g. “ich” should be glossed as “1SG.NOM” or “1SG(NOM)”.  
Caution: This rule may eventually generate some difficult questions, like whether e.g. “ich” should be glossed as “1SG.NOM” or “1SG(NOM)”.  


{{Separating bar}}
==== ''Ablaut'' phenomena ====


==== ''Ablaut'' phenomena ====
; (7) ''Ablaut'' markup recommendation
<div id="Punctuation_backslash">
: 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.</ref>
; (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>
</div>


Cf. the following paradigm:
Cf. the following paradigm:
Line 540: Line 372:
|}
|}


{{Separating bar}}
==== 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.
==== 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 as ‘root-and-pattern morphology’ or ‘transfixation’.
 
<div id="Punctuation_transfix">
; (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:
: Alternatively, Daniel Werning suggests to use a ‘new’ punctuation mark, e.g. “^”, to mark transfixation.


; Current recommendation:
; (8) Root-and-pattern morphology markup recommendation
: Currently this Wiki uses '''“{{tf}}'''  as a mark.
: Categories that are expressed by a complex regular vocalic pattern applied to a (consonantal) root in a paradigm may either be marked as ''ablaut'' phenomenon (“\”; see [[#Ablaut phenomena|above]]) or – preferably – left unspecified (:, see [[#Leaving inflection type unspecified |below]]).


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 ''or'' writ'''e{{tf}}I'''NF-NOM.SG || ‘(to) write; (to) send’
| ''šapārum'' || š'''a'''p'''ā'''r-um || writ'''e:I'''NF-NOM.SG || ‘(to) write; (to) send’
|-  
|-  
| ''ašpur'' || a-šp'''u'''r || 1SG-writ'''e:P'''ST ''or'' 1SG-writ'''e{{tf}}P'''ST || ‘I sent’
| ''ašpur'' || a-šp'''u'''r || 1SG-writ'''e:P'''ST || ‘I sent’
|-  
|-  
| ''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šappar''  || a-š'''a'''p'''pa'''r  || 1SG-writ'''e:I'''PFV || ‘I send, I will send’
|-  
|-  
| ''aštapar'' || a-š'''&lt;ta&gt;'''p'''a'''r || 1SG-write'''&lt;PST&gt;''' ''or'' 1SG-writ'''e{{tf}}P'''ST || ‘I have sent’
| ''aštapar'' || a-š'''&lt;ta&gt;'''p'''a'''r || 1SG-write'''&lt;PRF&gt;''' || ‘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’
|}
|}


{{Separating bar}}
=== Leaving inflection type unspecified ===
; (9) Unspecified inflection markup recommendation
: 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.</ref>


=== The period and the colon in expert mode ===
Consequently, the encoder may choose to use the colon :” instead of any of the other indications of separable morphemes (“-”, “=”, “&lt;&nbsp;&rt;”, “~”, “\” – but not for [#Portmanteau morphemes|''Portmanteau'' morphemes]). Note 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.  
<div id="Punctuation_period_expert">
Note that a separate glossing transcription line is not necessary if the encoder uses only periods “.”, colons “:”, backslashes “\”, parentheses “(&nbsp;)”, and square brackets “[&nbsp;]”.
; (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,  
: – 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. <ref>Cf. Lehmann (2004: R21).</ref>
</div>


; Example:
; Example:
Line 586: Line 404:
| ''Vorgestern'' || ''bin'' || ''ich'' || ''aus'' || ''einem'' || ''Kurzurlaub'' || ''zurückgekommen''.
| ''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 || 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 || a-'''M.DAT''' || short=vacation(M)['''SG.DAT'''] || back=com'''e:PTCP.PRF'''
|}
|}
{{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;&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.  
<small>
Rather than
{| {{Wrong glossing table}}
|-
| ''Vorgestern'' || ''bin'' || ''ich'' || ''aus'' || ''einem'' || ''Kurzurlaub'' || ''zurückgekommen''.
|-
| the_day_before_yesterday || be.PRS.1SG || 1SG.NOM || out || a-M.DAT || short=vacatio'''n(M)'''[SG.DAT] || back=PTCP.PRF<sub>1</sub>-come-PTCP.PRF<sub>1</sub>
|}
</small>


Note that a separate glossing transcription line is not necessary if the encoder uses only periods .”, colons :”, backslashes \”, parentheses (&nbsp;), and square brackets [&nbsp;]”.
=== The period in the expert mode ===
; (10) ''Portmanteau'' morpheme rule
: If one chooses to mark affixes, clitics, reduplications and/or infixes by -”,“=”, “~”, and &lt;&nbsp;&gt;”, respectively, or if one chooses to mark separable morpheme by a colon “:” (leaving the type of inflection unspecified), elements in a gloss should only be joined by a period ., if these are inseparably fused in the object language word (''Portmanteau'' morpheme).


{{Separating bar}}
; Example:
{{Separating bar}}
{| {{Glossing table}}
|-
| ''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'''<sub>1</sub>-come-'''PTCP.PRF'''<sub>1</sub>
|}
{{Translation|‘I came back from a short vacation the day before yesterday.’}}


== References ==
== References ==
Line 604: Line 438:
== 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.) (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.
* 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.
* 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.
{{Punctuation bar}}
Please note that all contributions to Glossing Ancient Languages may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Glossing Ancient Languages:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please enter the words that appear below in the box (more info):

Refresh
Cancel Editing help (opens in new window)

Templates used on this page: