SIG:IndicTexts - Revision history

Andrew ollett at 02:58, 10 April 2018

2018-04-10T02:58:26Z

Andrew ollett at 02:46, 10 April 2018

2018-04-10T02:46:08Z

Andrew ollett at 19:29, 4 April 2018

2018-04-04T19:29:59Z

Andrew ollett at 19:29, 4 April 2018

2018-04-04T19:29:30Z

Andrew ollett at 18:58, 4 April 2018

2018-04-04T18:58:34Z

Andrew ollett at 17:31, 4 April 2018

2018-04-04T17:31:49Z

Patrick McAllister: Created page with "The purpose of the TEI Special Interest Group “Indic Texts” is to allow scholars engaged in the study of Indic texts to develop and document best practices in applying the TE..."

2018-01-26T17:23:41Z

Created page with "The purpose of the TEI Special Interest Group “Indic Texts” is to allow scholars engaged in the study of Indic texts to develop and document best practices in applying the TE..."

New page

The purpose of the TEI Special Interest Group “Indic Texts” is to
allow scholars engaged in the study of Indic texts to develop and
document best practices in applying the TEI’s Guidelines to these
kinds of texts. To participate, please join the mailing list at
http://lists.lists.tei-c.org/mailman/listinfo/indic-texts.

There are several respects in which the applicability of the TEI
guidelines to these texts is less than obvious. These relate to
distinctive features of Indic textuality, including:

* the use of syllabic scripts, and the non-coincidence of grapheme- (syllable-) and word-boundaries;
* the application of phonotactic rules (sandhi) that further obscures the boundaries between words; extensive compounding;
* the use of distinctive media and writing supports (such as birch bark, palm leaves, and copper plates);
* distinctive metrical patterns with different types of caesuras;
* the prominence of the commentary as a genre, and the depth of intertextual relations this implies;
* the frequent reuse of texts in other texts, which requires careful and deliberate application of the "quoteLike" module.

The expected outcome of the SIG’s work is a practical guide that
analyzes common cases in the markup of Indic texts and proposes ways
in which the analytical tools provided by the TEI Guidelines might
best be used in these cases, discussing benefits and drawbacks of the
solutions possible. Ideally, this guide will become a part of the TEI
Guidelines.

@@ Line 38: / Line 38: @@
 * In transliteration, the deletion of one vowel must be accompanied by the addition of the inherent vowel, although there is no addition marked as such in the manuscript.
-The consensus seems to be: wrap the consonant, to which these modifications are referred, in the &lt;subst&gt; element, and use the &lt;@place="implicit"&gt; attribute on &lt;add&gt; in reference to the vowel, as follows:
+There are two possible solutions that came up on the list. Both involve the use of the &lt;subst&gt; element, which contains the akṣara that is subject to scribal modification, and within it, the <code language="xml">&lt;add&gt;</code> and <code language="xml">&lt;del&gt;</code> elements.
 <code language="xml">
@@ Line 44: / Line 52: @@
 </code>
-(Of course projects might not require this degree of markup.)
+Of course not all projects will require markup of this granularity.
 === Floating consonants ===

@@ Line 29: / Line 29: @@
 === Cancelling dependent vowels ===
-In manuscripts, dependent vowel markers can be cancelled, and the consonant is then read with the inherent vowel ''a''. If you want to encode this kind of change, there are technical problems, whether one is using an Indic script or an alphabetic transliteration system (like IAST or ISO-15919):
+In manuscripts, dependent vowel markers can be cancelled, and the consonant is then read with the inherent vowel ''a''.
 * In Indic scripts, rendering problems are likely if the cancelled vowel marker is enclosed within the <code language="xml">&lt;del&gt;&lt;/del&gt;</code> tags, since it is a combining character;
 * In transliteration, the deletion of one vowel must be accompanied by the addition of the inherent vowel, although there is no addition marked as such in the manuscript.
@@ Line 48: / Line 53: @@
 </code>
-But when the orthographic sequence of consonants differs from the canonical sequence of consonants, this is not possible, and it necessary the out-of-sequence consonant could be specifically marked as such:
+But when the orthographic sequence of consonants differs from the canonical sequence of consonants, this is not possible.
 <code language="xml">
@@ Line 54: / Line 63: @@
 </code>
-In this case a processor should be able to "fix" the sequence of characters given this markup.
+In this case a processor should be able to "fix" the sequence of characters given this markup. But the group advised that this level of markup was not generally required.
 === Floating vowel markers ===

@@ Line 45: / Line 45: @@
 <code language="xml">
-&lt;śa&lt;space type="binding-hole"/&gt;ḥ
+śa&lt;space type="binding-hole"/&gt;ḥ
 </code>

← Older revision		Revision as of 19:29, 4 April 2018
Line 38:		Line 38:
	<subst>ḷ<del type="cancelled">o</del><add place="implicit">a</add></subst>		<subst>ḷ<del type="cancelled">o</del><add place="implicit">a</add></subst>
	</code>		</code>
		+
		+	(Of course projects might not require this degree of markup.)
		+
		+	=== Floating consonants ===
		+	When an orthographically dependent consonant is separated from another consonant, for instance by a binding hole, it can generally be transcribed without any special markup:
		+
		+	<code language="xml">
		+	<śa<space type="binding-hole"/>ḥ
		+	</code>
		+
		+	But when the orthographic sequence of consonants differs from the canonical sequence of consonants, this is not possible, and it necessary the out-of-sequence consonant could be specifically marked as such:
		+
		+	<code language="xml">
		+	māgg<space type="binding-hole"/><g ref="#floating-r">r</g>
		+	</code>
		+
		+	In this case a processor should be able to "fix" the sequence of characters given this markup.
		+
		+	=== Floating vowel markers ===

@@ Line 26: / Line 26: @@
 == Manuscript Transcription ==
-Canonically, an akṣara makes up a single "grapheme," and this is reflected in Unicode representations of Indic scripts, where consonants and independent vowels are encoded first, and then vowel-markers (and dependent consonants like ''anusvāraḥ'' and ''visargaḥ'') are encoded subsequently as combining characters. Unless marked with a combining vowel character, or a cancellation character, consonants are understood to have an inherent vowel ''a''.
+Canonically, an akṣara makes up a single "grapheme," and this is reflected in Unicode representations of Indic scripts, where consonants and independent vowels are encoded first, and then vowel-markers (and dependent consonants like ''anusvāraḥ'' and ''visargaḥ'') are encoded subsequently as combining characters. Unless marked with a combining vowel character, or a cancellation character, consonants are understood to have an inherent vowel ''a''. The sequence of consonants within conjuncts is also canonically the same as their phonological sequence. Thus in the conjunct "rg", the "r" is represented before the "g" in transliteration, in Devanagari र्ग (0930 + 094D + 0917) and in Kannada ರ್ಗ (0CB0 + 0CCD + 0C97), although it is rendered on top of the "g" in Devanagari and to the right of the "g" in Kannada.
 === Cancelling dependent vowels ===
 In manuscripts, dependent vowel markers can be cancelled, and the consonant is then read with the inherent vowel ''a''. If you want to encode this kind of change, there are technical problems, whether one is using an Indic script or an alphabetic transliteration system (like IAST or ISO-15919):
-* In Indic scripts, rendering problems are likely if the cancelled vowel marker is enclosed within the <code language="xml">&lt;del&gtl;&lt;/del&gt;</code> tags, since it is a combining character;
+* In Indic scripts, rendering problems are likely if the cancelled vowel marker is enclosed within the <code language="xml">&lt;del&gt;&lt;/del&gt;</code> tags, since it is a combining character;
 * In transliteration, the deletion of one vowel must be accompanied by the addition of the inherent vowel, although there is no addition marked as such in the manuscript.

← Older revision		Revision as of 17:31, 4 April 2018
Line 22:		Line 22:
	solutions possible. Ideally, this guide will become a part of the TEI		solutions possible. Ideally, this guide will become a part of the TEI
	Guidelines.		Guidelines.
		+
		+
		+	== Manuscript Transcription ==
		+
		+	Canonically, an akṣara makes up a single "grapheme," and this is reflected in Unicode representations of Indic scripts, where consonants and independent vowels are encoded first, and then vowel-markers (and dependent consonants like ''anusvāraḥ'' and ''visargaḥ'') are encoded subsequently as combining characters. Unless marked with a combining vowel character, or a cancellation character, consonants are understood to have an inherent vowel ''a''.
		+
		+	=== Cancelling dependent vowels ===
		+	In manuscripts, dependent vowel markers can be cancelled, and the consonant is then read with the inherent vowel ''a''. If you want to encode this kind of change, there are technical problems, whether one is using an Indic script or an alphabetic transliteration system (like IAST or ISO-15919):
		+	* In Indic scripts, rendering problems are likely if the cancelled vowel marker is enclosed within the <code language="xml"><del&gtl;</del></code> tags, since it is a combining character;
		+	* In transliteration, the deletion of one vowel must be accompanied by the addition of the inherent vowel, although there is no addition marked as such in the manuscript.