<?tei:SOF p2cohq.odd ?>
<!-- $Id: p2cohq.odd,v 1.3 1994/03/27 21:45:15 msmcq Exp $ -->
<!-- $Log: p2cohq.odd,v $
# Revision 1.3  1994/03/27  21:45:15  msmcq
# Correction of typos from DB, JL, HG, and WWP
# -->
 
<div2 id=COHQ><head>Highlighting and Quotation</head>
 
<!-- Revisions:                                               -->
<!-- 94-03-26 : MSM : corrections, changes from WWP team      -->
<!-- 94-03-26 : MSM : corrections from DB                     -->
<!-- 94-03-25 : MSM : typos corrected as per J. Lavagnino     -->
<!-- 94-03-24 : MSM : disambiguation of term, q (code, ident) -->
<!-- 92-12-10 : MSM : change xref to SP (now TS)              -->
<!-- 92-12-09 : MSM : retag new citn using toy tag, not new tag -->
<!-- 92-12-09 : MSM : spellcheck for publication              -->
<!-- 92-12-09 : MSM : touchups for publication                -->
<!-- 92-12-09 : MSM : add space after some end-tags           -->
<!-- 92-12-09 : MSM : fixes as per LB, MSM agreements         -->
<!-- 92-12-07 : MSM : suppress Q/Free attribute               -->
<!-- 92-12-07 : MSM : correct syntax error in OED gloss       -->
<!-- 92-12-07 : MSM : come down handsomely with OED citation  -->
<!-- 92-12-06 : MSM : revise for publication                  -->
<!-- 92-11-09 : MSM : retag two EGs as Qs                     -->
<!-- 92-11-09 : MSM : suppress leading blanks in some elements -->
<!-- 25-7 Oct  LB : introduce quote, reorder                  -->
<!-- 19 Oct 92 LB : change ids to match EDW23                 -->
<!--           changed marked to distinct                     -->
<!-- 26 May 92 : MSM : fix div levels                         -->
<!-- 15 May 92 : LB : finish, check out to MSM                -->
 
<p>This section deals with a variety of textual features, all of
which have in common that they are frequently realized in conventional
printing practice by the use of such features as underlining, italic
fonts, or quotation marks, collectively referred to here as
<term>highlighting</term>.  After an initial discussion of this
phenomenon and alternate approaches to encoding it, this section
describes ways of encoding the following textual features, all
of which are conventionally rendered using some kind of highlighting:
<list>
<item>emphasis, foreign words and other linguistically distinct uses
of highlighting
<item>representation of speech and thought, quotation, etc.
<item>technical terms, glosses, etc.
</list>
 
<div3 id=COHQW><head>What Is Highlighting?</head>
 
<p>By <cited>highlighting</cited> we mean the use of any combination of
<indexed level1='highlighting'> typographic features (font, size, hue,
etc.) in a printed or written text in order to distinguish some passage
of a text from its surroundings.<note>Although the way in which a spoken
text is performed, (for example, the voice quality, loudness, etc.)
might be regarded as analogous to <soCalled>highlighting</soCalled> in
this sense, these Guidelines recommend distinct elements for the
encoding of such <soCalled>highlighting</soCalled> in spoken texts.  See
further section <xref target=TSSASH>.</note> The purpose of highlighting
is generally to draw the reader's attention to some feature or
characteristic of the passage highlighted; this section describes the
elements recommended by these Guidelines for the encoding of such
textual features.
 
<p>In conventionally printed modern texts, highlighting is often
employed to identify words or phrases which are regarded as being one or
more of the following:
 
<list type=bullets>
<item>distinct in some way --- as foreign, dialectal,
archaic, technical, etc.
<item>emphatic, and which would for example be stressed when spoken
<item>not part of the body of the text, for example cross references,
titles, headings, labels, etc.
<item>identified with a distinct narrative stream, for example an
internal monologue or commentary.
<item>attributed by the narrator to some other agency, either within the
text or outside it:  for example, direct speech or quotation.
<item>set apart from the text in some other way:  for example,
proverbial phrases, words mentioned but not used, names of persons and
places in older texts, editorial corrections or additions, etc.
</list>
 
<p>The textual functions signalled by highlighting may not be rendered
consistently in different parts of a text or in different texts.  (For
example, a foreign word may appear in italics if the surrounding text is
in roman, but in roman if the surrounding text is in italics.)  For this
reason, these Guidelines distinguish between the encoding of rendering
itself and the encoding of the underlying feature expressed by it.
 
<p>Highlighting as such may be encoded by using the global
<att>rend</att> attribute which can be specified for any element in the
TEI scheme.  This allows the encoder both to specify the function of a
highlighted phrase or word, by selecting the appropriate element
described here or elsewhere in the Guidelines, and to further describe
the way in which it is highlighted, by means of the <att>rend</att>
attribute.  If the encoder wishes to offer no interpretation of the
feature underlying the use of highlighting in the source text, then the
<gi>hi</gi> element may be used, which indicates only that the text so
tagged was highlighted in some way.
 
<p>The possible values carried by the <att>rend</att> attribute are not
formally defined in this version of the Guidelines.  Since the
<att>rend</att> attribute may be used to document any peculiarity of the
way a given segment of text was rendered in the original source text, it
may need to express a very large range of typographic features, by no
means restricted to type face, type size, etc.
 
<!-- For more discussion see the chapter on physical          -->
<!-- rendition (section <xref target=PH>).                    -->
 
<p>Where it is both appropriate and feasible, these Guidelines recommend
that the textual feature marked by the highlighting should be encoded,
rather than just the simple fact of the highlighting.  This is for the
following reasons:
 
<list>
<item>the same kind of highlighting may be used for different purposes
in different contexts
<item>the same textual function may be highlighted in different ways in
different contexts
<item>for analytic purposes, it is in general more useful to know the
intended function of a highlighted phrase than simply that it is
distinct.
</list>
 
<p>In many, if not most, cases the underlying function of a highlighted
phrase will be obvious and non-controversial, since the distinctions
indicated by a change of highlighting correspond with distinctions
discussed elsewhere in these Guidelines.  It should be recognized,
however, that cases do exist in which is it not economically feasible to
mark the underlying function of highlighting (e.g. in the preparation of
large text corpora), as well as cases in which it is not intellectually
appropriate (as in the transcription of some older materials, or in the
preparation of material for the study of typographic practice).  In such
cases, the <gi>hi</gi> element should be used, as further discussed
below.
 
<p>Elements which are sometimes realized by typographic distinction but
which are not discussed in this section include <gi>title</gi>
(discussed in section <xref target=COBI>) and <gi>name</gi> (discussed
in section <xref target=CONARS>).
 
<div3 id=COHQH><head>Emphasis, Foreign Words, and Unusual Language</head>
 
<p>This subsection discusses the following elements:
 
<tagList>
<tagDesc tagDoc=FOREIGN atts=lang>
<tagDesc tagDoc=EMPH>
<tagDesc tagDoc=HI atts=rend>
<tagDesc tagDoc=DISTINCT atts="type time space social">
</tagList>
 
<div4 id=COHQHF><head>Foreign Words or Expressions</head>
 
<p>Words or phrases which are not in the main language of the text
should be tagged as such, at least where the fact is indicated in the
text.  Where the word or phrase concerned is already distinguished from
the rest of the text by virtue of its function (for example, because it
is a name, a technical term, a quotation, a mentioned word, etc.) then
the global <att>lang</att> attribute should be used to specify
additionally that its language distinguishes it from the surrounding
text.  Any element in the TEI scheme may take a <att>lang</att>
attribute, which specifies both the writing system and the language used
by its content (see section <xref target=CHSH> for discussion of this
attribute).  Where there is no other applicable element, the tag
<tag>foreign</tag> may be used to provide a peg onto which the
<att>lang</att> may be attached.
 
<eg> <![CDATA[
<q>Aren't you confusing <foreign lang=la>post hoc</foreign>
with <foreign lang=la>propter hoc</foreign>?</q> said the
Bee Master.  <q>Wax-moth only succeed when weak bees let
them in.</q>
]]>
</eg>
<!-- R Kipling 'The mother hive' in Actions and Reactions, 1909 -->
<!-- these could be tagged as TERM, of course. -MSM -->
 
<p>The <tag>foreign</tag> tag should not be used to encode foreign words
which are mentioned or glossed within the text:  for these use the
appropriate element from section <xref target=COHQU> below.  Compare the
following example sentences:
 
<eg> <![ CDATA [
John eats a <foreign lang=fr>croissant</foreign> every morning.
]]>
</eg>
 
<eg> <![ CDATA [
<mentioned lang=fr>Croissant</mentioned> is difficult to
pronounce with your mouth full.
]]>
</eg>
 
<eg> <![ CDATA [
A <term lang=fr>croissant</term> is a crescent-shaped piece
of light, buttery, pastry that is usually eaten for
breakfast, especially in France.
]]>
</eg>
 
<!-- Collins COBUILD English Language Dictionary, ed. John    -->
<!-- Sinclair (London and Glasgow:  Collins, 1987), p. 337    -->
<!-- s.v. croissant.                                          -->
 
<p>The <gi>foreign</gi> element is formally defined as follows:
 
<dtdFrag id=DCOHQ n='Highlighted phrases'>
<tagDecl tagDoc=FOREIGN>
</dtdFrag>
 
<div4 id=COHQHE><head>Emphatic Words and Phrases</head>
 
<p>The <gi>emph</gi> element is provided to mark words or phrases which
are <emph>linguistically</emph> emphatic or stressed.  Text which is
only typographically <soCalled>emphasized</soCalled> falls into the
class of highlighted text, and may be tagged with the <gi>hi</gi>
element.  In printed works, emphasis is generally indicated by devices
such as the use of an italic font, a large typeface or extra wide letter
spacing; in manuscripts and typescripts, it is usually indicated by the
use of underlining.
 
As the following examples demonstrate, an encoder may choose whether or
not to make explicit the particular type of rendition associated with
the emphasis, by use of the <att>rend</att> attribute.  If a source text
consistently renders a particular feature (e.g. emphasis or words in
foreign languages) in a particular way, the rendering associated with
that feature may be described in the TEI header and the <att>rend</att>
attribute used only to describe examples which deviate from the norm.
 
<eg><![ CDATA [
<q>Sex, sir, is <emph>purely</emph> a question of appetite!</q>
   Tarr exclaimed.
]]>
</eg><!-- Wyndham Lewis, Tarr (1928), Jupiter ed 1968, p.17 -->
 
<eg><![ CDATA [
<q>What it all comes to is this,</q> he said.
<q><emph rend=italic>What does Christopher
Robin do in the morning nowadays?</emph></q>
]]>
</eg><!-- Milne, House at Pooh Corner (1928), p83 -->
 
<eg><![ CDATA [
<l>Here Thou, great <name rend=italics>Anna</name>!
      whom three Realms obey,
<l>Doth sometimes Counsel take &mdash;
      and sometimes <emph rend=italic>Tea</emph>.
]]>
</eg><!-- Pope, Rape of the Lock (1744) III.8 -->
 
<p>The <gi>hi</gi> element is used to mark words or phrases which are
highlighted in some way, but for which identification of the intended
distinction is difficult, controversial or impossible.  It enables an
encoder simply to record the fact of highlighting, possibly describing
it by the use of a <att>rend</att> attribute, as discussed above,
without however taking a position as to the function of the
highlighting.  This may also be useful if the text is to be processed in
two stages:  representing simply typographic distinctions during a first
pass, and then replacing the <tag>hi</tag> tags with more specific tags
in a second pass.
 
<p>Some simple examples:
 
<eg><![ CDATA [
<hi rend=gothic>And this Indenture further witnesseth</hi>
that the said <hi rend=italic>Walter Shandy</hi>, merchant,
in consideration of the said intended marriage ...
]]>
</eg><!-- Sterne, Tristram Shandy (1760), p.82 -->
 
In this example, the first highlighted phrase uses black letter or
gothic print to mimic the appearance of a legal document, and italic to
mark <cited>Walter Shandy</cited> as a name.  In a second pass, the
elements <gi>head</gi> or <gi>label</gi> might be appropriate for the
first use, and the element <gi>name</gi> for the second.
 
<eg><![ CDATA [
The heaviest rain, and snow, and hail, and sleet, could
boast of the advantage over him in only one respect.  They
often <hi rend=quoted>came down</hi> handsomely, and
Scrooge never did.
]]>
</eg><!-- Dickens Xmas Carol  p 12 -->
 
In this example, the phrase <cited>came down</cited> uses inverted
commas to indicate a play on words.<note>The Oxford English Dictionary
documents the phrase <cited>to come down</cited> in the sense <gloss>to
bring or put down; <hilited rend=it>esp.</hilited> to lay down money; to
make a disbursement</gloss> as being in use, mostly in colloquial or
humorous contexts, from at least 1700 to the latter half of the 19th
century.
<!-- In early Victorian English slang,                        -->
<!-- < q >to come down handsomely< / q >                      -->
<!-- might be glossed as < q >to pay out                      -->
<!-- handsomely< / q >.                                       -->
</note>
<!-- a ref to OED would be handy here if you have time to find one -->
In a second pass, the element <gi>soCalled</gi> might be preferred.
 
<!-- WWP proofer asks why. (msm)                              -->
 
<p>The <gi>emph</gi> and <gi>hi</gi> elements are formally defined as
follows:
 
<dtdFrag id=DCOHQ1 contin=DCOHQ>
<tagDecl tagDoc=EMPH>
<tagDecl tagDoc=HI>
</dtdFrag>
 
<div4 id=COHQHD><head>Other Linguistically Distinct Material</head>
 
<p>For some kinds of analysis, it may be desirable to encode the
linguistic distinctiveness of words and phrases with more delicacy than
is allowed by the <gi>foreign</gi> element.  The <gi>distinct</gi>
element is provided for this purpose.  Its attributes allow for
additional information characterizing the nature of the linguistic
distinction to be made in two distinct ways:  the <att>type</att>
attribute simply assigns a user-defined code of some kind to the word or
phrase which assigns it to some register, sub-language, etc.  No
recommendations as to the set of values for this attribute are provided
at this time, as little consensus exists in the field.
 
<p>Alternatively, the remaining three attributes may be used in
combination to place a word or phrase on a three-dimensional scale
sometimes used in descriptive linguistics.<note>See, for example,
<citation><title>Sociolinguistics/Soziolinguistik (An international
handbook of the science of language and society.  Ein internationales
Handbuch zur Wissenschaft von Sprache und Gesellschaft)</title> (Berlin,
New York:  De Gruyter, 1988), I, pp. 271 and 274.</citation></note>
The <att>time</att> attribute places a word
<term rend='noindex'>diachronically</term>,
<indexed level1='diachronic information'>
for example as archaic, old-fashioned, contemporary, futuristic, etc.;
the <att>space</att> attribute places a word
<term rend='noindex'>diatopically</term>,
<indexed level1='diatopic information'>
that is, with respect to a geographical classification, for example as
national, regional, international, etc.; the <att>social</att> attribute
places a word <term rend='noindex'>diastatically</term>,
<indexed level1='diastatic information'>
that is, with respect to a social classification, for example as
technical, polite, impolite, restricted, etc.  Again, no recommendations
are made for the values of these attributes at this time; the encoder
should provide a description of the scheme used in the appropriate
section of the header (see section <xref target=HD5>).
 
<p>Examples:
 
<eg><![ CDATA [
Next morning a boy in that dormitory confided to his
bosom friend, a <distinct type=psSlang>fag</distinct> of
Macrea's, that there was trouble in their midst which
King <distinct type=archaic>would fain</distinct> keep
secret.
]]>
</eg><!-- Kipling, Stalky & Co. (1899), Library ed 1950, p.83) -->
 
<eg><![ CDATA[
Next morning a boy in that dormitory confided to his
bosom friend, a
<distinct time=1900 social=publicschool space=GB>fag</distinct>
of Macrea's, that there was trouble in their midst which
King <distinct time=archaic>would fain</distinct> keep
secret.
]]>
</eg>
 
Where more complex (or more rigorous) interpretive analyses of the
associations of a word are required, the more detailed and general
mechanisms described in chapter <xref target=FS> should be preferred to
these simple characterizations.  It may also be preferable to record the
kinds of analysis suggested here by means of the simple annotation
element <gi>note</gi> described in section <xref target=CONO>, or the
<gi>span</gi> element described in section <xref target=AISP>.
 
<p>The <gi>distinct</gi> element has the following formal definition:
 
<dtdFrag id=DCOHQ3 contin=DCOHQ>
<tagDecl tagDoc=DISTINCT>
</dtdFrag>
 
<!>
<!-- P2, ch 23, sec 7.                                        -->
<!-- Revisions:                                               -->
<!-- 19 Oct 92 : LB change xrefs and div levels again        -->
<!-- 26 May 92 : MSM : fix div levels                         -->
<!-- 15 May 92 : LB : check out to MSM                        -->
 
<div3 id=COHQQ><head>Quotation</head>
 
<p>This section discusses the following elements, all of which are often
rendered by the use of quotation marks:
 
<tagList>
<tagDesc tagDoc=Q atts="who type direct">
<tagDesc tagDoc=QUOTE>
<tagDesc tagDoc=CIT>
<tagDesc tagDoc=SOCALLED>
</tagList>
 
<p>One form of presentational variation found particularly frequently in
written and printed texts is the use of quotation marks.  As with the
typographic variations discussed in the preceding section, it is
generally helpful to separate the encoding of the underlying textual
feature (for example, a quotation or a piece of direct speech) from the
encoding of its rendering (for example, the use of a particular style of
quotation marks).
 
<p>The most common and important use of quotation marks is, of course,
to mark <term>quotation</term>, by which we mean simply any part of the
text attributed by the author or narrator to some agency other than the
narrative voice.  Typical examples include passages cited from other
works, for which the element <gi>quote</gi> may be used, and words or
phrases attributed to other voices within the current work, for which
the element <gi>q</gi> may be used.  If this distinction between
intra-textual and inter-textual voices cannot be made reliably, or is
not of interest, then all quoted matter may simply be marked using the
<gi>q</gi> tag.  The editorial policy in this respect should be stated
in the encoding description of the TEI Header.  The <gi>soCalled</gi>
element is used for cases where the author or narrator distances him or
herself from the words in question without however attributing them to
any other voice in particular.
 
<!-- The following discussion of rendering seems rather long-winded -->
<!-- to me, but I am not sure where else it goes. Maybe some of it  -->
<!-- should migrate to PH?                                          -->
 
<p>Quotation may be rendered by changes in type face, by special
punctuation marks (single or double or angled quotes, dashes, etc.) and
by layout (indented paragraphs, etc.).  If these characteristics are of
interest, an appropriate value for the <att>rend</att> attribute should
be given, to record how the <gi>q</gi> or <gi>quote</gi> element is
rendered.  For discussion of suggested values for this attribute, see
below.
 
<!-- , and also chapter <xref target=PH>.                     -->
 
<p>Quotation marks themselves may, like other punctuation marks, be felt
for some purposes to be worth retaining within a text, quite
independently of their description by the <att>rend</att> attribute.
Where this is done, an appropriate entity reference should be chosen
from the standard entity sets listed in chapter <xref target=XW>;
<!-- not sure if this is the right target: somewhere we should -->
<!-- reference the standard entity sets -->
this has the advantage that the entity may be redefined as null when the
punctuation is to be ignored for some analytic purpose.  Well-known
ambiguities, such as whether the character ' represents an apostrophe or
a closing single quotation mark, or whether the character " represents
an opening or closing double quotation mark may all be resolved by the
use of appropriate entity references, as discussed in section <xref
target=COPU>.
<!-- This is not true.                                        -->
 
<p>Alternatively, the encoder may suppress all quotation marks, possibly
recording their form using the <att>rend</att> attribute.  Where this is
done, the following list of entity names (taken from the public entity
sets <ident type=entset>ISOpub</ident> and <ident
type=entset>ISOnum</ident>) may be found useful to describe
quotation-mark styles common in European and American typesetting:
 
<!-- list restored under (mild) protest and with one necessary  -->
<!-- addition                                     LB, oct 92    -->
 
<list type=gloss>
<label>ldquo  <item>double inverted comma (shaped like 66, superscript)
<label>lsquo  <item>single inverted comma (shaped like 6, superscript)
<label>rdquo  <item>double apostrophe (shaped like 99, superscript)
<label>rsquo  <item>single apostrophe (shaped like 9, superscript)
<label>ldquor <item>double comma (shaped like 99, printed on base line)
<label>lsquor <item>single comma (shaped like 9, printed on base line)
<label>laquo  <item>double guillemet open to the right
<label>lsaquo <item>single guillemet open to the right
<label>raquo  <item>double guillemet open to the left
<label>rsaquo <item>single guillemet open to the left
<label>mdash  <item>dash the width of a lowercase <cited>m</cited>
</list>
 
<!-- J.Lavagnino suggests revisiting the issue of mdash in    -->
<!-- P4:  perhaps this is too print-centered?  (msm)          -->
 
These may be used in the <att>rend</att> attribute to show how the
quotation was opened and closed.  For example, if the words
<cited>pre</cited> and <cited>post</cited> are used to indicate
preceding and following punctuation, then the following example would
describe a conventional American book printed using single quotation
marks:
 
<eg>
<![ CDATA [
<q rend='PRE lsquo POST rsquo'>Who-e debel you?</q>
&mdash he at last said &mdash <q
rend='PRE lsquo POST rsquo'>you no speak-e,
damme, I kill-e.</q>  And so saying,
the lighted tomahawk began flourishing
about me in the dark.
]]>
</eg><!-- Melville, Moby Dick (but where?) -->
 
The following example demonstrates alternative policies which may be
adopted with respect to encoding of the punctuation used to mark
quotation:
 
<eg>
<![ CDATA[
 
Adolphe se tourna vers lui :
<q>&mdash Alors, Albert, quoi de neuf?</q>
<q>&mdash Pas grand-chose.</q>
<q>&mdash Il fait beau,</q> dit Robert.
]]>
</eg><eg>
<![ CDATA[
 
Adolphe se tourna vers lui :
<q rend='PRE mdash'>Alors, Albert, quoi de neuf ?</q>
<q rend='PRE mdash'>Pas grand-chose.</q>
<q rend='PRE mdash'>Il fait beau,</q> dit Robert.
]]>
</eg><!-- Queneau, Exercices de style (1947) p.192 -->
 
To make explicit who is speaking, which is not always stated in the
above example, the <att>who</att> attribute should be used:
 
<eg>
<![ CDATA [
Adolphe se tourna vers lui :
<q who='Adolphe'>&mdash Alors, Albert, quoi de neuf?</q>
<q who='Albert'>&mdash Pas grand-chose.</q>
<q who='Robert'>&mdash Il fait beau,</q> dit Robert.
]]>
</eg>
<!-- should show QUOTATION declarations for these -->
 
The <att>who</att> attribute is also useful as a means of supplying a
normalized form of the speaker's name, to facilitate selection of text
by particular speakers.  As indicated above, it may be supplied whether
or not an indication of the speaker is given explicitly in the text.
 
<p>Where investigation of <soCalled>narrative voice</soCalled> is the
primary object of the encoding, it may be convenient to identify each
speaker as a <term rend=noindex>participant</term> in the work, and to
associate individual speeches with them by means of SGML's ID/IDREF
mechanism.  See section <xref target=CCAHPA> for discussion of the
<term>participant description</term> component of the TEI Header.
 
<p>For such analyses, it may also be useful to distinguish
representations of speech from representations of thought, in modern
printed texts often indicated by a change of typeface.  The
<att>type</att> attribute should be used for this purpose, as in this
example:
 
<eg>
<![ CDATA [
<q type=speech>Oh yes,</q> said Henry, <q type=speech>I mean
Gordon Macrae, for example...</q>
<q type=thought>Jungian Analyst with Winebox! That's what you
called him, you callous bastard, didn't you? Eh? Eh?</q>
]]>
</eg><!-- N Williams, The Wimbledon Poisoner, p 204 -->
 
<p>Quoted matter may be embedded within quoted matter, as when one
speaker reports the speech of another:
 
<eg>
<![ CDATA[
<q who=Wilson>Spaulding, he came down into the office just this
day eight weeks with this very paper in his hand, and he
says:&mdash;<q who=Spaulding>I wish to the Lord, Mr. Wilson, that
I was a red-headed man.</q></q>
]]>
</eg><!-- A C Doyle, Red headed league (but where?) -->
 
<p>Direct speech nested in this way is treated in the same way as
elsewhere:  a change of rendition may occur, but the same
element should be used.  An encoder may however choose to distinguish
between direct speech which contains quotations from extra-textual
matter and direct speech itself, as in the following example:
 
<eg>
<![ CDATA [
<p><q>The Lord! The Lord! It is Sakya Muni himself,</q> the
lama half sobbed; and under his breath began the wonderful
Buddhist invocation:-
<q><quote><l>To Him the Way -- the Law -- Apart --
<l>Whom Maya held beneath her heart
<l>Ananda's Lord -- the Bodhisat
</quote>
And He is here! The Most Excellent Law is here also.  My
pilgrimage is well begun.  And what work! What work!</q>
]]>
</eg> <!-- R.Kipling, Kim, Macmillan, 1917(1901) p9 -->
 
<p>Quotations from other works are often accompanied by a reference to
their source.  The <gi>cit</gi> element may be used to group together
the quotation and its associated bibliographic reference, which should
be encoded using the elements for bibliographic references discussed in
section <xref target=COBI>, as in the following example.
 
<eg>
<![ CDATA [
<div id=MM01 type=chapter><head>Chapter 1</head>
<epigraph>
  <cit><quote><l>Since I can do no good because a woman
  <l>Reach constantly at something that is near it.</quote>
  <bibl><title>The Maid's Tragedy</title>
        <author>Beaumont and Fletcher</author></bibl>
  </cit>
</epigraph>
<p>Miss Brooke had that kind of beauty which seems to be thrown into
relief by poor dress...
]]>
</eg><!-- G. Eliot, Middlemarch, p 1 -->
<!-- apostrophe added to "Maid's" as per J. Lav, who says     -->
<!-- Penguin has it. (msm)                                    -->
 
Like other bibliographic references, the citation attached to a
quotation may be represented simply by a pointer, as in this example:
 
<eg><![ CDATA[
Lexicography has shown little sign of being affected by the
work of followers of J.R. Firth, probably best summarized
in his slogan, <cit><quote>You shall know a word by the company it
keeps.</quote> <ref target=FI57>(Firth, 1957)</ref></cit>
]]>
</eg>
<!-- Hanks, in Looking Up, ed Sinclair, (1987) p.121 -->
 
Unlike most of the other elements discussed in this chapter, direct
speech and quotations may frequently contain other high-level elements
such as paragraphs or verse lines, as well as being themselves contained
by such elements.  Three possible solutions exist for this well-known
structural problem:
 
<list type=bullets>
<item>the quotation is broken into segments, each of which
is entirely contained within a paragraph
<item>the quotation is marked up as part of a concurrent but
independent hierarchy
<item>the quotation boundaries are represented by empty milestone
tags
</list>
 
For further discussion, and several examples, see chapter <xref
target=NH>.
 
<p>Finally, in this section, the element <gi>soCalled</gi> is provided
for all cases in which quotation marks are used to distance the quoted
text from the narrator or speaker.  Common examples include the
<soCalled>scare</soCalled> quotes often found in newspaper headlines and
advertising copy, where the effect is to cast doubts on the veracity of
an assertion:
 
<eg>
<![ CDATA [
<head>PM dodges <soCalled>election threat</soCalled>
in interview</head>
]]>
</eg><!-- The Guardian, p2, 26 Oct 1992  -->
 
<p>The same element should be used to mark a variety of special ironic
usages.  Some further examples follow:
 
<eg><![ CDATA[
He hated <soCalled>good</soCalled> books.
 
<soCalled>Croissants</soCalled> indeed! toast not good enough for you?
]]>
</eg><!-- some "real" examples would be better -->
 
<eg>
<![ CDATA [
Although Chomsky's decision that all NL sentences are finite
objects was never justified by arguments from the attested
properties of NLs, it did have a certain
<soCalled>social</soCalled> justification.  It was
commonly assumed in works on logic until fairly recently
that the notion <mentioned>language</mentioned> is
necessarily restricted to finite strings.
]]>
</eg><!-- Langendoen and Postal, Vastness of NLs, p. 24 note 12.        -->
 
<p>The elements discussed in this section are formally defined as
follows:
 
<dtdFrag id=DCOHQQ n='Quotation' contin=DCOHQ>
<tagDecl tagDoc=Q>
<tagDecl tagDoc=QUOTE>
<tagDecl tagDoc=CIT>
<tagDecl tagDoc=SOCALLED>
</dtdFrag>
 
<!-- P2, ch 23, sec 8                                         -->
<!-- Revisions                                                -->
<!-- 24-27 Oct LB     reorganise slightly                     -->
<!-- 26 May 92 : MSM : fix div levels                         -->
<!-- 15 May 92 : LB : check out to MSM                        -->
<div3 id=COHQU><head>Terms, Glosses, and Cited Words</head>
 
<p>This section describes the following textual elements, all of which
have in common that they may be variously realized using italics,
quotation marks or other devices:
 
<tagList>
<tagDesc tagDoc=TERM>
<tagDesc tagDoc=GLOSS>
<tagDesc tagDoc=MENTIOND>
</tagList>
 
<p>Technical terms are often italicized or emboldened upon first mention
in printed texts; an explanation or gloss is sometimes given in
quotation marks.  Linguistic analyses conventionally cite words in
languages under discussion in italics, providing a gloss immediately
following marked with single quotation marks.  Other texts in which
individual words or phrases are <term rend=noindex>mentioned</term> (for
<indexed level1='mention' level2='vs. use'>
<indexed level1='use' level2='vs. mention'>
example, as examples) rather than <term rend=noindex>used</term> may
mark them either with italics or with quotation marks, and will gloss
them less regularly.
 
<p>A <gi>term</gi> may appear with or without a gloss, as may a
<gi>mentioned</gi> element.  Where the <gi>gloss</gi> is present, it may
be linked to the term it is glossing by means of SGML's ID/IDREF
mechanism.  To establish such a link, the encoder should give an
<att>id</att> value to the <gi>term</gi> or <gi>mentioned</gi> element
and provide that id as the value of the <att>target</att> attribute on
the <gi>gloss</gi> element.  The following examples demonstrate this
facility:  for more discussion of this and other kinds of linkage within
TEI documents, see chapter <xref target=SA>.
 
<p>Examples:
<!>
<eg><![ CDATA [
We may define <term rend=sc id=TDPV>discoursal point of view</term>
as <gloss target=TDPV>the relationship, expressed through discourse
structure, between the implied author or some other addresser,
and the fiction.</gloss>
]]>
</eg>
<!-- Leech, Style in Fiction, (1981) p272 -->
 
<eg><![ CDATA [
<gloss target=T1 rend=unmarked>A computational device
that infers structure from grammatical strings of words</gloss>
is known as a <term id=T1>parser</term>, and much of the
history of NLP over the last 20 years has been occupied with
the design of parsers.
]]>
</eg>
<!-- Gazdar and Mellish, NLP in Prolog, p. 5   -->
 
<eg><![ CDATA [
There is thus a striking accentual difference between a
verbal form like <mentioned lang=grc
id=cw234>eluthemen</mentioned> <gloss target=CW234>we
were released,</gloss> accented on the second
syllable of the word, and its participial derivative
<mentioned id=CW235 lang=grc>lutheis</mentioned>
<gloss target=CW235>released,</gloss> accented on the last.
]]>
</eg>
<!-- Sapir, Language (HBJ paperback), p. 79                        -->
 
<!>
<p>The elements discussed in this section have the following formal
definitions:
<dtdFrag id=DCOHQU n='Terms, glosses, etc.' contin=DCOHQ>
<tagDecl tagDoc=TERM>
<tagDecl tagDoc=MENTIOND>
<tagDecl tagDoc=GLOSS>
</dtdFrag>
 
<div3 id=COHQHEG><head>Some Further Examples</head>
 
<p>As a simple example of the elements discussed here, consider the
following sentence:
 
<!-- Theodore M. Andersson, Preface to the Nibelungenlied, p. 3 -->
<q rend=display>
On the one hand the <title>Nibelungenlied</title> is
associated with the new rise of romance of twelfth-century
France, the <foreign>romans d'antiquit&eacute;</foreign>,
the romances of Chr&eacute;tien de Troyes, and the German
adaptations of these works by Heinrich van Veldeke,
Hartmann von Aue, and Wolfram von Eschenbach.
</q>
A first approximation to the encoding of this sentence, might be simply
to record the fact that the phrases printed above in italics are
highlighted, as follows:
<!>
<eg>
<![ CDATA[
On the one hand the <hi rend=italic>Nibelungenlied</hi> is
associated with the new rise of romance of twelfth-century
France, the <hi rend=italic lang=fr>romans
d'antiquit&eacute;</hi>, the romances of Chr&eacute;tien de
Troyes, ...
]]>
</eg>
This encoding would however lose the important distinction between
an italicized title and an italicized foreign phrase.  Many other
phrases might also be italicized in the text, and a retrieval
program seeking to identify foreign terms (for example) would not
be able to produce reliable results by simply looking for italicized
words.  Where economic and intellectual constraints permit, therefore,
it would be preferable to encode both the function of the
highlighted phrases and their appearance, as follows:
<!>
<eg>
<![ CDATA[
On the one hand the <title
rend=italic>Nibelungenlied</title> is associated with the
new rise of romance of twelfth-century France, the <foreign
rend=italic>romans d'antiquit&eacute;</foreign>, the
romances of Chr&eacute;tien de Troyes, ...
]]>
</eg>
<p>In this example, the decision as to which textual features
are distinguished by the highlighting is relatively
uncontroversial.  As a less straightforward example, consider the
use of italic font in the following passage
from Samuel Richardson's <title>Clarissa</title> (1747).
<!-- NB this is NOT a P2 example!! -->
<!-- replaced < ital > by < hilited rend=it > added entity ref -->
<q rend=display>
A pretty common case, I believe; in all
<hilited rend=it>vehement</hilited> debatings.  She says I am
<hilited rend=it>too witty</hilited>; Anglic&eacute;,
<hilited rend=it>too pert</hilited>; I, that she is
<hilited rend=it>too wise</hilited>; that is to say, being
likewise put into English, <hilited rend=it>not so young as
she has been</hilited>:  in short, she is grown so much into
a <hilited rend=it>mother</hilited>, that she had forgotten
she ever was a <hilited rend=it>daughter</hilited>. ...
</q>
 
<p>Clearly, the word <cited>vehement</cited> is not italicized for the
same reason as the phrase <cited>not so young as she has been</cited>;
the former is emphasized, while the latter is proverbial.  It also
provides an ironic gloss for the words <cited>too wise</cited>, in the
same way as <cited>too pert</cited> glosses <cited>too witty</cited>.
The glossed phrases are not however technical terms or cited words, but
quoted phrases, as if Clarissa were putting words into her own and her
mother's mouths.  Finally, the words <cited>mother</cited> and
<cited>daughter</cited> are apparently italicized simply to oppose them
in the sentence; certainly they do not fit into any of the categories so
far proposed as reasons for italicizing.  Note also that the word
<cited>Anglic&eacute</cited> is not italicized although it is not
generally considered an English word.
 
<p>The following sample encoding for the above passage attempts to take
into account all the above points:
 
<eg>
<![ CDATA [
A pretty common case, I believe; in all
<emph>vehement</emph> debatings.  She says I am
<q rend=italic>too witty</q>; <foreign lang=la
rend=roman>Anglic&egrave;</foreign>, <gloss rend=italic>too
pert</gloss>; I, that she is <q rend=italic>too wise</q>;
that is to say, being likewise put into English, <gloss
rend=italic>not so young as she has been</gloss>:  in short,
she is grown so much into a <hi rend=italic>mother</hi>,
that she had forgotten she ever was a
<hi rend=italic>daughter</hi>.
]]>
</eg>
 
<!-- WWP proofer points out inconsistency between tagging     -->
<!-- and commentary.  "too witty" and "too wise" retagged     -->
<!-- from TERM (which the prose says they are *not*) to Q     -->
<!-- (which the prose says they *are*).  WWP proofer also     -->
<!-- suggests EMPH for 'mother' and 'daughter', but our       -->
<!-- imaginary interpretation says we don't understand the    -->
<!-- italics there, so we leave it undisambiguated.  (msm)    -->
<?tei:EOF p2cohq.odd ?>
