<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: "Calibri Light", "Helvetica Light", sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="font-family: Calibri, Helvetica, sans-serif;">Hi all,</span><span><br>
</span>
<div><br>
</div>
<div><span style="font-family: Calibri, Helvetica, sans-serif;">The representational issue raised by Christian arises because, historically and presently, authors use the first line of an interlinear gloss for different purposes, depending on the focus of that
piece of writing or its audience.</span><br>
</div>
<div><br>
</div>
<div><span style="font-family: Calibri, Helvetica, sans-serif;">Sometimes the first line is intended to be a (surface level)
</span><span style="font-family: Calibri, Helvetica, sans-serif;"><b>phonemic transcription</b></span><span style="font-family: Calibri, Helvetica, sans-serif;">. In this case, it makes sense that the transcription should include only graphemes that represent
phonemes in that language, and no punctuation, capitals, etc. The orthography could be IPA, but it could also be any other phonemic orthography used for that language. As an example, the
</span><a href="http://www.americanlinguistics.org/wp-content/uploads/IJAL-interlinear.pdf" title="http://www.americanlinguistics.org/wp-content/uploads/IJAL-interlinear.pdf"><span style="font-family: Calibri, Helvetica, sans-serif;">stylesheet for the International
Journal of American Linguistics</span></a><span style="font-family: Calibri, Helvetica, sans-serif;"> asks authors to use a phonemic transcription for the first line of interlinear examples.</span><br>
</div>
<div><br>
</div>
<div><span style="font-family: Calibri, Helvetica, sans-serif;">Sometimes the first line of the interlinear gloss is intended to be a
</span><span style="font-family: Calibri, Helvetica, sans-serif;"><b>transcript</b></span><span style="font-family: Calibri, Helvetica, sans-serif;">. In this case, the transcription would include extra-phonemic characters such as <,.?!>, whether those characters
are meant to indicate written conventions that group linguistic units logically, or prosodic conventions (like those used in Discourse Functional Transcription or Conversation Analysis) that group words by intonation unit or conversational turn, etc. When
Christian and others refer to an </span><span style="font-family: Calibri, Helvetica, sans-serif;"><b>orthographic representation</b></span><span style="font-family: Calibri, Helvetica, sans-serif;">, I believe they have in mind this notion of a transcript.
For publications aimed at speakers, learners, or general audiences, it is most common for the first line to be a transcript, following the standard writing conventions of that language. Sometimes a second, purely phonemic transcription is included as a second
line. Dianne Friesen’s </span><i><a href="https://langsci-press.org/catalog/book/118" title="https://langsci-press.org/catalog/book/118"><span style="font-family: Calibri, Helvetica, sans-serif;">A grammar of Moloko</span></a></i><span style="font-family: Calibri, Helvetica, sans-serif;">
(Language Science Press, 2017) is an example of a publication that uses a transcript for the first line of most interlinear examples.</span><br>
</div>
<div><br>
</div>
<div><span style="font-family: Calibri, Helvetica, sans-serif;">More rarely, the first line is used for a
</span><span style="font-family: Calibri, Helvetica, sans-serif;"><b>phonetic transcription</b></span><span style="font-family: Calibri, Helvetica, sans-serif;">, though more commonly the phonetic transcription is given as a second line beneath the transcript
or phonemic transcription. In this case, because the transcription is phonetic, it seems to me this transcription should always be in IPA, with no capitals or punctuation.</span><br>
</div>
<div><br>
</div>
<div><span style="font-family: Calibri, Helvetica, sans-serif;">Frequently authors omit any initial transcription and instead present a
</span><span style="font-family: Calibri, Helvetica, sans-serif;"><b>morphemic analysis</b></span><span style="font-family: Calibri, Helvetica, sans-serif;"> as the first line. While the morphemic analysis is obviously a kind of transcription, it is a transcription
of </span><span style="font-family: Calibri, Helvetica, sans-serif;"><i>morphemes
</i></span><span style="font-family: Calibri, Helvetica, sans-serif;">rather than the entire utterance, and therefore may not represent all morphophonemic sound changes, allomorphy, etc. Writers differ as to whether the morphemic analysis line should include
only underlying forms or allow allomorphs. (</span><a href="https://christianlehmann.eu/ling/ling_meth/ling_description/grammaticography/gloss/index.php?open=allomorphy" title="https://christianlehmann.eu/ling/ling_meth/ling_description/grammaticography/gloss/index.php?open=allomorphy"><span style="font-family: Calibri, Helvetica, sans-serif;">Christian’s
guidance</span></a><span style="font-family: Calibri, Helvetica, sans-serif;"> is that allomorphy should not be represented in the morphemic analysis.) Interlinear examples that start with a morphemic analysis rather than a transcript are a particularly linguist-oriented
representation. They are dispreferred by most speakers and learners because of their illegibility, and this practice is sometimes viewed as disrespectful (a point emphasized by Megan Lukaniec in her 2019 LSA talk as part of the
</span><a href="https://natives4linguistics.wordpress.com/natives4linguistics-and-lsa2019/" title="https://natives4linguistics.wordpress.com/natives4linguistics-and-lsa2019/"><span style="font-family: Calibri, Helvetica, sans-serif;">Natives4Linguistics symposium</span></a><span style="font-family: Calibri, Helvetica, sans-serif;">).</span><br>
</div>
<div><br>
</div>
<div><span style="font-family: Calibri, Helvetica, sans-serif;">The resolution to the dilemma raised by Christian is to be explicit about the type of information you are conveying in each line, and follow representational principles most suited to that type,
some suggestions for which I just briefly outlined above. Language Science Press’s style guide encourages this approach: As Sebastian mentioned, the LSP style guide gives authors the flexibility to choose which type of representation they are using for any
particular example, and asks them to be consistent within that line. Authors may essentially choose between a
</span><span style="font-family: Calibri, Helvetica, sans-serif;"><i>transcript</i></span><span style="font-family: Calibri, Helvetica, sans-serif;"> and a
</span><span style="font-family: Calibri, Helvetica, sans-serif;"><i>phonemic transcription</i></span><span style="font-family: Calibri, Helvetica, sans-serif;"> for any given example.</span><br>
</div>
<div><br>
</div>
<div><span style="font-family: Calibri, Helvetica, sans-serif;">Inconsistencies and conflicts arise when authors try to conflate these different purposes in a single line, or assume that this first line always has the same purpose, creating the illusion of
a forced dichotomy between using a transcript, a phonemic transcription, or something else. But the interlinear gloss is a wonderfully flexible convention in that authors can adjust it to their purpose and audience. Imposing a standard whereby authors are
required to include or exclude punctuation, would restrict the ability of authors to tailor their representations as appropriate.</span><br>
</div>
<div><br>
</div>
<div><span style="font-family: Calibri, Helvetica, sans-serif;">Allowing for this flexibility does
</span><span style="font-family: Calibri, Helvetica, sans-serif;"><i>not </i></span><span style="font-family: Calibri, Helvetica, sans-serif;">entail that we should be satisfied with any random way of structuring interlinear examples. It’s entirely reasonable
that editors impose formatting requirements; however, those requirements should be sensitive to the type of information being conveyed. For example, I suggested above that any line intended to be a phonetic representation must use IPA. Additionally, editors
could require some types of lines and disprefer others, similar to the way that IJAL requires a phonemic transcription line.</span><br>
</div>
<div><br>
</div>
<div><span style="font-family: Calibri, Helvetica, sans-serif;">So I agree with Christian, Jack, and Martin in that the “ban” on punctuation should be lifted, in the sense that editors should allow authors to use a transcript as the first line of interlinear
examples where appropriate. In fact, I think it would be great if this were the default policy for most publications, so as to make our research maximally readable and accessible. If needed, that transcript line could then be supplemented with other representations.</span><br>
</div>
<div><br>
</div>
<div><span style="font-family: Calibri, Helvetica, sans-serif;">For those interested, I created a specification for how to represent linguistic examples in a way that both follows traditional conventions but is nonetheless easily parseable by a script. In this
specification I define the various types of lines that appear in interlinear glosses, some of which I've mentioned above. You can view the complete specification at the link below.</span><br>
</div>
<div><br>
</div>
<div><a href="https://scription.digitallinguistics.io/" title="https://scription.digitallinguistics.io/"><span style="font-family: Calibri, Helvetica, sans-serif;">https://scription.digitallinguistics.io/</span></a><br>
</div>
<div><br>
</div>
<div><span style="font-family: Calibri, Helvetica, sans-serif;">best,</span><br>
</div>
<div><br>
</div>
<div><span style="font-family: Calibri, Helvetica, sans-serif;">Danny</span><br>
</div>
<span></span><br>
</div>
<div>
<div style="font-family: "Calibri Light", "Helvetica Light", sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="Signature">
<div></div>
<span style="font-family: Calibri, Helvetica, sans-serif;"></span>
<div></div>
<div></div>
<span style="font-family: Calibri, Helvetica, sans-serif;"></span>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0); background-color:rgb(255,255,255)">
<span style="font-family:"Calibri Light","Helvetica Light",sans-serif"><br>
</span><span style="font-family: Calibri, Helvetica, sans-serif;"></span></div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0); background-color:rgb(255,255,255)">
<span style="font-family: Calibri, Helvetica, sans-serif;"></span><span style="font-family: Calibri, Helvetica, sans-serif;">Daniel W. Hieber</span></div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0); background-color:rgb(255,255,255)">
<span style="font-family: Calibri, Helvetica, sans-serif;"></span><span style="font-family: Calibri, Helvetica, sans-serif;">Ph.D. Candidate in Linguistics</span></div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0); background-color:rgb(255,255,255)">
<span style="font-family: Calibri, Helvetica, sans-serif;"></span><span style="font-family: Calibri, Helvetica, sans-serif;">University of California, Santa Barbara</span></div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0); background-color:rgb(255,255,255)">
<span style="font-family: Calibri, Helvetica, sans-serif;"></span><span style="font-family:"Calibri Light","Helvetica Light",sans-serif"></span><a href="http://www.danielhieber.com" style=""><span style="font-family: Calibri, Helvetica, sans-serif;">danielhieber.com</span><span style="font-family: Calibri, Helvetica, sans-serif;"></span></a></div>
</div>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Lingtyp <lingtyp-bounces@listserv.linguistlist.org> on behalf of Nikolaus Himmelmann <n.himmelmann@uni-koeln.de><br>
<b>Sent:</b> Wednesday, March 25, 2020 12:43 PM<br>
<b>To:</b> lingtyp@listserv.linguistlist.org <lingtyp@listserv.linguistlist.org><br>
<b>Subject:</b> Re: [Lingtyp] orthography in formatted examples</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Dear colleagues<br>
<br>
I believe that different punctuation conventions should be used in <br>
accordance with the type of language a given example represents <br>
(Christian is alluding to this possibility). Essentially, linguistic <br>
examples in linguistics come from three different sources and ideally, <br>
punctuation would be part of marking the distinction.<br>
<br>
- originally written data (from a written source)<br>
- transcribed data (from a recording of unscripted speech)<br>
- invented data (including elicited data)<br>
<br>
Representing orginally spoken data in the conventions of (European) <br>
written languages ignores the fundamental differences that exist between <br>
the two modalities and leads to many of the putatively untractable <br>
problems such as defining "word".<br>
<br>
Therefore, I make point of representing spoken language differently from <br>
written and elicited/invented language. Not using punctuation and <br>
capitalization but representing intonation units. Whether it is <br>
worthwhile to invent a convention to distinguish the difference between <br>
orginally written data and invented data is an issue that may merit <br>
further debate.<br>
<br>
Of course there are many additional special case problems such as <br>
whether one should use punctuation in representing originally written <br>
language where the original does not use punctuation.<br>
<br>
Best regards<br>
Nikolaus<br>
<br>
<br>
On 25.03.2020 16:15, Peter Austin wrote:<br>
> Dear colleagues<br>
> <br>
> It seems to me that part of what Christian is alluding to is a failure <br>
> on the part of descriptive and documentary linguists to take <br>
> transcription (and orthographic representation) seriously and to come to <br>
> some agreements about how it should be handled in our various <br>
> representational schema. The "Leipzig glossing rules" don't discuss it <br>
> and this lacuna gives rise to conflicting practices, that Christian <br>
> observes.<br>
> <br>
> Epigraphers have thought long and hard about this matter and I would <br>
> recommend looking at their XML schema expressed in EpiDoc <br>
> (<a href="https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fepidoc%2Fwiki%2FHome%2F&data=02%7C01%7C%7C9705c6c4605340b18c5908d7d0e417f7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637207550379179827&sdata=QC6L0znF42soIuNdvmYxRtRnaaAfbvkLO6efLmQL87c%3D&reserved=0">https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fepidoc%2Fwiki%2FHome%2F&data=02%7C01%7C%7C9705c6c4605340b18c5908d7d0e417f7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637207550379179827&sdata=QC6L0znF42soIuNdvmYxRtRnaaAfbvkLO6efLmQL87c%3D&reserved=0</a>)
to get some idea of how a <br>
> whole field can approach the matter of transcription -- they don't only <br>
> deal with punctuation, but also with things like "missing" elements, <br>
> corrections, spacing etc. The Discourse Functional Transcription (DFT) <br>
> mentioned by Jack Du Bois could be one basis for starting a proper <br>
> discussion going and getting some basic agreements among researchers in <br>
> place. They are sorely needed.<br>
> <br>
> Best wishes,<br>
> Peter<br>
> <br>
> <br>
> On Wed, 25 Mar 2020 at 14:59, Françoise Rose <br>
> <francoise.rose@univ-lyon2.fr <<a href="mailto:francoise.rose@univ-lyon2.fr">mailto:francoise.rose@univ-lyon2.fr</a>>> wrote:<br>
> <br>
> Dear all,____<br>
> <br>
> It seems most grammars of languages without a written tradition do<br>
> use punctuation (although minimal) in the examples, if those are<br>
> full sentences. Capitalization maybe less systematically, probably<br>
> for the reason that Katharina has mentioned. “,” are important<br>
> sometimes to get an idea of the prosody, and the syntactic<br>
> structure, and I use “…” a lot to mark errors and hesitations.____<br>
> <br>
> I don’t see the problem of punctuation symbols being also used in<br>
> the gloss line: in different lines, the same symbols have different<br>
> meanings (and a different distribution anyway: “.” Is always used<br>
> after a word (i.e. before a space) in the example line and within<br>
> the gloss in a gloss line). The only problem me or my students have<br>
> been confronted with is when the “-“ is used in the orthography. If<br>
> in the gloss line, I usually replace it with “_”, as in<br>
> “grand_père”. If in the example line, I don’t have an ideal<br>
> solution.____<br>
> <br>
> Nice to have this discussion !____<br>
> <br>
> Keep safe,____<br>
> <br>
> Françoise____<br>
> <br>
> __ __<br>
> <br>
> __ __<br>
> <br>
> *De :*Lingtyp <lingtyp-bounces@listserv.linguistlist.org<br>
> <<a href="mailto:lingtyp-bounces@listserv.linguistlist.org">mailto:lingtyp-bounces@listserv.linguistlist.org</a>>> *De la part de*<br>
> Christian Lehmann<br>
> *Envoyé :* mercredi 25 mars 2020 12:15<br>
> *À :* LINGTYP LINGTYP <LINGTYP@listserv.linguistlist.org<br>
> <<a href="mailto:LINGTYP@listserv.linguistlist.org">mailto:LINGTYP@listserv.linguistlist.org</a>>><br>
> *Objet :* [Lingtyp] orthography in formatted examples____<br>
> <br>
> __ __<br>
> <br>
> Dear colleagues,____<br>
> <br>
> here is a little methodological problem which some may dismiss as<br>
> trivial but which needs to be solved if we care for standardizing<br>
> linguistic methodology. It concerns the orthographic representation<br>
> of linguistic data, esp. such as are provided with an interlinear<br>
> gloss.____<br>
> <br>
> In the past decades, it has become customary in linguistic<br>
> publications to omit punctuation in data which are formatted as<br>
> examples and provided by a gloss, like this:____<br>
> <br>
> __ __<br>
> <br>
> quo____<br>
> <br>
> <br>
> <br>
> usque____<br>
> <br>
> <br>
> <br>
> tandem____<br>
> <br>
> <br>
> <br>
> abutere____<br>
> <br>
> <br>
> <br>
> Catilina____<br>
> <br>
> <br>
> <br>
> patientia____<br>
> <br>
> <br>
> <br>
> nostra____<br>
> <br>
> whither____<br>
> <br>
> <br>
> <br>
> continually____<br>
> <br>
> <br>
> <br>
> finally____<br>
> <br>
> <br>
> <br>
> abuse:FUT:MID.2.SG <<a href="https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2FMID.2.SG&data=02%7C01%7C%7C9705c6c4605340b18c5908d7d0e417f7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637207550379179827&sdata=aWELTBCLq5XkPu5Iv4FopO9Dgg6jkU9MmTGIZi%2BdyjY%3D&reserved=0">https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2FMID.2.SG&data=02%7C01%7C%7C9705c6c4605340b18c5908d7d0e417f7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637207550379179827&sdata=aWELTBCLq5XkPu5Iv4FopO9Dgg6jkU9MmTGIZi%2BdyjY%3D&reserved=0</a>>____<br>
> <br>
> <br>
> <br>
> Catilina:VOC.SG <<a href="https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2FVOC.SG&data=02%7C01%7C%7C9705c6c4605340b18c5908d7d0e417f7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637207550379179827&sdata=lEyRg6eTdq2j6Sbh1w%2F%2FNd94JzTtAXOSgsWE666MzNg%3D&reserved=0">https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2FVOC.SG&data=02%7C01%7C%7C9705c6c4605340b18c5908d7d0e417f7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637207550379179827&sdata=lEyRg6eTdq2j6Sbh1w%2F%2FNd94JzTtAXOSgsWE666MzNg%3D&reserved=0</a>>____<br>
> <br>
> <br>
> <br>
> patience(F):ABL.SG <<a href="https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2FABL.SG&data=02%7C01%7C%7C9705c6c4605340b18c5908d7d0e417f7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637207550379179827&sdata=sjU5sroA13M%2FzvHS6cLE4foTTPVdRY8LtndA9s2RAM0%3D&reserved=0">https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2FABL.SG&data=02%7C01%7C%7C9705c6c4605340b18c5908d7d0e417f7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637207550379179827&sdata=sjU5sroA13M%2FzvHS6cLE4foTTPVdRY8LtndA9s2RAM0%3D&reserved=0</a>>
____<br>
> <br>
> <br>
> <br>
> our:F.ABL.SG <<a href="https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2FF.ABL.SG&data=02%7C01%7C%7C9705c6c4605340b18c5908d7d0e417f7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637207550379179827&sdata=GMe3FHe6lX4esAWu%2FgPFt7aQ8kQPebjkAay6hjFK5gk%3D&reserved=0">https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2FF.ABL.SG&data=02%7C01%7C%7C9705c6c4605340b18c5908d7d0e417f7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637207550379179827&sdata=GMe3FHe6lX4esAWu%2FgPFt7aQ8kQPebjkAay6hjFK5gk%3D&reserved=0</a>>____<br>
> <br>
> “ How far will you continue to abuse our patience, Catiline?” (Cic.<br>
> /Cat/. I, 1)____<br>
> <br>
> The example is actually taken from a text; and there it is, of<br>
> course, provided with initial capitalization, with commas in between<br>
> and with a final question mark. Many of us have gotten accustomed to<br>
> omitting these things in formatted examples. My own guidelines for<br>
> interlinear glosses____<br>
> <br>
> (christianlehmann.eu/ling/ling_meth/ling_description/grammaticography/gloss/<br>
> <<a href="https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fchristianlehmann.eu%2Fling%2Fling_meth%2Fling_description%2Fgrammaticography%2Fgloss%2F&data=02%7C01%7C%7C9705c6c4605340b18c5908d7d0e417f7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637207550379179827&sdata=gezuUNHDFXccq%2FGzSd6y%2BZHQ6JvYqVGkZcjXuYIvzh4%3D&reserved=0">https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fchristianlehmann.eu%2Fling%2Fling_meth%2Fling_description%2Fgrammaticography%2Fgloss%2F&data=02%7C01%7C%7C9705c6c4605340b18c5908d7d0e417f7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637207550379179827&sdata=gezuUNHDFXccq%2FGzSd6y%2BZHQ6JvYqVGkZcjXuYIvzh4%3D&reserved=0</a>>)<br>
> ____<br>
> <br>
> also recommend the omission. The practice seems inevitable for a<br>
> representation of a piece of text which is not in orthography but in<br>
> some more formal representation, say phonetic or morphophonemic.<br>
> Here I am talking about *orthographic representations*.____<br>
> <br>
> There are some reasons for the practice of omitting punctuation and<br>
> sentence-initial capitalization in glossed examples:____<br>
> <br>
> __1.__These orthographic marks may not figure in the original<br>
> source:____<br>
> <br>
> __a.__There is no published orthographic version which would need to<br>
> be cited literally; it is just a transcription of a recording.<br>
> Omission of punctuation signals this.____<br>
> <br>
> __b.__The quoted stretch of text is not (necessarily) a sentence, be<br>
> it in its original context, be it in the language system.____<br>
> <br>
> __2.__These orthographic marks would confuse the mapping of symbols<br>
> structuring the interlinear gloss onto the original text line:____<br>
> <br>
> __a.__Punctuation symbols like ‘.’, ‘:’ have a special function in<br>
> glosses which they do not have in a fully orthographic text line.<br>
> Others like ‘,’ and ‘!’ are inadmissible in the gloss. If such<br>
> symbols appeared in the original text line, they would map on<br>
> nothing in the gloss line.____<br>
> <br>
> __b.__Punctuation symbols like ‘-’ should have the same function in<br>
> the original text and in the gloss.____<br>
> <br>
> (Ad (1b): We are not talking about examples which are just syntagmas<br>
> below clause level. In some linguistic publications, such examples<br>
> are provided with a final full stop, too. This is plainly<br>
> unthinking.)____<br>
> <br>
> Here are some reasons for abandoning the ban on punctuation and<br>
> initial capitalization:____<br>
> <br>
> __1.__It makes the language exemplified appear as one which lacks an<br>
> orthography, thus dangerously evoking the attitude towards „an idiom<br>
> which does not even have a grammar“.____<br>
> <br>
> __2.__Punctuation, of course, fulfills a sensible function in<br>
> established orthographies: it reflects the syntactic or prosodic<br>
> structure of a piece of text. Omitting it from an example renders<br>
> this less easily intelligible.____<br>
> <br>
> __3.__Whenever a linguistic example is, in fact, quoted from a text<br>
> noted in established orthography, the quotation should be faithful,<br>
> including the punctuation.____<br>
> <br>
> __4.__Current practice allows for exceptions to the principle of<br>
> suppression of punctuation: at least question marks are commonly<br>
> set.____<br>
> <br>
> You may know of more reasons for or against the practice of<br>
> suppression of punctuation and of initial capitalization in<br>
> linguistic examples, or you may be able to invalidate some of the<br>
> above. I would be grateful for some discussion which helps to bring<br>
> this closer to a recommendation that most of us could share and that<br>
> would have a chance to find its way into style sheets.____<br>
> <br>
> Christian____<br>
> <br>
> -- ____<br>
> <br>
> Prof. em. Dr. Christian Lehmann<br>
> Rudolfstr. 4<br>
> 99092 Erfurt<br>
> Deutschland____<br>
> <br>
> Tel.:____<br>
> <br>
> <br>
> <br>
> +49/361/2113417____<br>
> <br>
> E-Post:____<br>
> <br>
> <br>
> <br>
> christianw_lehmann@arcor.de <<a href="mailto:christianw_lehmann@arcor.de">mailto:christianw_lehmann@arcor.de</a>>____<br>
> <br>
> Web:____<br>
> <br>
> <br>
> <br>
> <a href="https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.christianlehmann.eu&data=02%7C01%7C%7C9705c6c4605340b18c5908d7d0e417f7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637207550379179827&sdata=MyJCFneClRSoXuknMPNfulI6%2FDlPxCXvsChU517G%2FuE%3D&reserved=0____">
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.christianlehmann.eu&data=02%7C01%7C%7C9705c6c4605340b18c5908d7d0e417f7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637207550379179827&sdata=MyJCFneClRSoXuknMPNfulI6%2FDlPxCXvsChU517G%2FuE%3D&reserved=0____</a><br>
> <br>
> __ __<br>
> <br>
> _______________________________________________<br>
> Lingtyp mailing list<br>
> Lingtyp@listserv.linguistlist.org<br>
> <<a href="mailto:Lingtyp@listserv.linguistlist.org">mailto:Lingtyp@listserv.linguistlist.org</a>><br>
> <a href="https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Flistserv.linguistlist.org%2Fmailman%2Flistinfo%2Flingtyp&data=02%7C01%7C%7C9705c6c4605340b18c5908d7d0e417f7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637207550379179827&sdata=q4o%2BXQVNiJmvMmp%2BCYZamwcHkvEq2Sex4YC%2BeZHC7Aw%3D&reserved=0">
https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Flistserv.linguistlist.org%2Fmailman%2Flistinfo%2Flingtyp&data=02%7C01%7C%7C9705c6c4605340b18c5908d7d0e417f7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637207550379179827&sdata=q4o%2BXQVNiJmvMmp%2BCYZamwcHkvEq2Sex4YC%2BeZHC7Aw%3D&reserved=0</a><br>
> <br>
> <br>
> <br>
> -- <br>
> Prof Peter K. Austin<br>
> Humboldt Researcher, Frankfurt University (Nov 2019, Jan-March 2020)<br>
> Emeritus Professor in Field Linguistics, SOAS<br>
> Visiting Researcher, Oxford University<br>
> Foundation Editor, EL Publishing<br>
> Honorary Treasurer, Philological Society<br>
> <br>
> Department of Linguistics, SOAS<br>
> Thornhaugh Street, Russell Square<br>
> London WC1H 0XG<br>
> United Kingdom<br>
> <br>
> <br>
> _______________________________________________<br>
> Lingtyp mailing list<br>
> Lingtyp@listserv.linguistlist.org<br>
> <a href="https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Flistserv.linguistlist.org%2Fmailman%2Flistinfo%2Flingtyp&data=02%7C01%7C%7C9705c6c4605340b18c5908d7d0e417f7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637207550379179827&sdata=q4o%2BXQVNiJmvMmp%2BCYZamwcHkvEq2Sex4YC%2BeZHC7Aw%3D&reserved=0">
https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Flistserv.linguistlist.org%2Fmailman%2Flistinfo%2Flingtyp&data=02%7C01%7C%7C9705c6c4605340b18c5908d7d0e417f7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637207550379179827&sdata=q4o%2BXQVNiJmvMmp%2BCYZamwcHkvEq2Sex4YC%2BeZHC7Aw%3D&reserved=0</a><br>
> <br>
_______________________________________________<br>
Lingtyp mailing list<br>
Lingtyp@listserv.linguistlist.org<br>
<a href="https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Flistserv.linguistlist.org%2Fmailman%2Flistinfo%2Flingtyp&data=02%7C01%7C%7C9705c6c4605340b18c5908d7d0e417f7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637207550379179827&sdata=q4o%2BXQVNiJmvMmp%2BCYZamwcHkvEq2Sex4YC%2BeZHC7Aw%3D&reserved=0">https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Flistserv.linguistlist.org%2Fmailman%2Flistinfo%2Flingtyp&data=02%7C01%7C%7C9705c6c4605340b18c5908d7d0e417f7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637207550379179827&sdata=q4o%2BXQVNiJmvMmp%2BCYZamwcHkvEq2Sex4YC%2BeZHC7Aw%3D&reserved=0</a><br>
</div>
</span></font></div>
</body>
</html>