- text quoted from a primary source in the original language, to be displayed in italics without quotation marks, shall not be marked up in this way, but must be tagged as <foreign> as per §10.3.3

### 10.4.4. Quoting published material

- to encode direct quotations from a published source, proceed as follows

- within the `<p>` element in which you quote some text, create the wrapper `<cit>`

- within `<cit>`, wrap the quoted text in the element `<quote>`

- also within `<cit>`, but outside (and immediately after) `<quote>`, add a bibliographic citation as per §10.4.5 to specify the source of the quotation<fnref n="49" />

- do not add quotation marks to the text, as these will be automatically produced in display in the correct form

- to create a block quote, proceed as above but add `@rend="block"` to the `<quote>` element

- text quoted in this way will be displayed as a separate indented paragraph without quotation marks

- when citing text from a publication with `<quote>`, any **transliterated words** in the cited text shall be retained **in their original form** rather than being converted to our transliteration system

- but any text adopted without `<quote>`, for example in apparatus readings, translations and paraphrased/summarised opinions, should be converted to our transliteration system

### 10.4.5. Bibliographic citations

- bibliographic citations may be used in any part of your XML document where modern-language text is permitted, and must be mandatorily listed in the bibliography as discussed under §9.4

- a citation is encoded in the form of the element `<bibl>`

- the empty element `<ptr/>` (pointer) must mandatorily appear as the first element within `<bibl>`

- with the mandatory attribute `@target`, whose value shall be the Zotero Short Title of the cited publication, prefixed with the string “bib:”

- e.g. `<bibl><ptr target="bib:Agrawala1983_01"/></bibl>`

- **to limit the citation** to a specific part of the publication, add the element `<citedRange>` after the `<ptr/>` element but within the `<bibl>` element, wrapping the details of the citation in the following manner

- by default, `<citedRange>` will be understood to refer to page numbers, so references to pages without additional detail can simply be added as the content of this element, e.g.
    `<citedRange>12</citedRange>`

- use a hyphen to record a range of pages, e.g. `<citedRange>12-21</citedRange>`

- the number of the last page should always be recorded in full, e.g. `<citedRange>123-124</citedRange>` (not 123-4 or 123-24)

- use a comma (followed by a space) to list non-adjacent pages, e.g. `<citedRange>12, 24</citedRange>`

- to refer to an entity other than a page, add the attribute `@unit` to `<citedRange>` with one of the following values

- "page" for page numbers where this needs to be made explicit (see below)

- "part" to distinguish sections of publications where identical page numbers re-occur within a single volume (such as Epigraphia Carnatica)

- "volume" for multi-volume publications

- "note" for a numbered (foot or end) note

- "item" for a number in an anthology of editions, or an item in a numbered list (to be displayed as Nº)

- "entry" for an entry in a dictionary or encyclopaedia (to be displayed as s.v.)

- "figure", "plate", "table", "appendix" etc. as applicable, for visual material

<footnote n="49">⁴⁹ It is, in principle, possible to add `@source` (§10.6.2) to a `<quote>` element, but this would not be sufficient in many cases, because it does not allow referring to a page. We shall therefore refrain from doing so and always use a full citation.</footnote>
- note that the values of `@unit` should always be English regardless of the language of the publication, e.g. use `"appendix"` for an original *bijlage*

- should you feel the need to use a different value, please contact the authors and the XML-TEI Data Manager to discuss the matter

- as per ZG §4.4 and §4.6, numerals other than Arabic ones (e.g. Roman and Devanagari) should be converted in your citations to Arabic numbers unless this results in an ambiguity (because Arabic and non-Arabic numerals are both used within a publication, for the same unit of citation, e.g. Roman page numbers in the front matter and Arabic page numbers in the main text)

- where necessary, it is possible to add more than one `<citedRange>` element (e.g. to encode a reference to a certain figure on a certain page)

- in this case, page references must be explicitly encoded with `@unit="page"`

- the `<citedRange>` elements must appear in the order in which they are eventually to be displayed, e.g. a volume number must precede a page number and a page number must precede a note number

- see the examples below for the use of `<citedRange>` in various combinations

- **to add a year to a citation** where the corresponding Zotero entry does not include one (in serial publications recorded as a single Zotero entry, ZG §4.4)

- include a `<date>` element containing the year, at the point where it should appear in the citation (within `<bibl>`, but not within `<citedRange>`)

- see Example 10.4.5.D and Example 10.4.5.E below

- note that not all serial publications will be recorded as a single entry in our Zotero library; see Example 10.4.5.H for an illustration involving ARIE, where each volume is recorded separately

- a citation encoded in this way will be ultimately **displayed** as a human-readable author-date citation

- the internal details of citations will be automatically styled according to project conventions (with some details yet to be finalised)

- parentheses will not be automatically produced around citations and will have to be added in the surrounding text wherever you need them

- if the name of the author(s) is an integral part of your text and must thus appear **independently of the citation**:

- add the attribute `@rend` with the value `"omitname"` to the `<bibl>` element, which will cause the pointer to display without the name

- add the author's name wherever you require in the text outside the `<bibl>` element

- see Example 10.4.5.F below for an illustration

- if you wish to **show "ibid." instead of the name of the author(s)**:

- add the attribute `@rend` with the value `"ibid"` to the `<bibl>` element, which will display "ibid." instead of the name and will not use parentheses

- depending on your context, parentheses may be avoided altogether or used further away from the citation

- see Example 10.4.5.G below for an illustration

### Example 10.4.5.A: encoding a basic citation

```
>Majumdar 1943: 23-28
<bibl>
<ptr target="bib:Majumdar1943_01"/>
<citedRange>23-28</citedRange>
</bibl>
```

### Example 10.4.5.B: encoding a citation with a page and a figure number

```
>Majumdar 1943: 23-28, fig. 12
<bibl>
<ptr target="bib:Majumdar1943_01"/>
<citedRange unit="page">23-28</citedRange>
<citedRange unit="figure">12</citedRange>
</bibl>
```
### Example 10.4.5.C: encoding a citation with a volume and page number

Majumdar 1943, vol. 1: 23–28

```xml
<bibl>
  <ptr target="bib:Majumdar1943_01"/>
  <citedRange unit="page">23-28</citedRange>
  <citedRange unit="figure">12</citedRange>
</bibl>
```

### Example 10.4.5.D: encoding a citation of a serial publication without a named author

NBG 8, 1870: 72, 78

```xml
<bibl>
  <ptr target="bib:NBG"/>
  <citedRange unit="volume">8</citedRange>
  <date>1870</date>
  <citedRange unit="page">72, 78</citedRange>
</bibl>
```

### Example 10.4.5.E: encoding a citation of an appendix of a serial publication without a named author

OV 1918: Q, 169

```xml
<bibl>
  <ptr target="bib:OV"/>
  <date>1918</date>
  <citedRange unit="appendix">Q</citedRange>
  <citedRange unit="page">169</citedRange>
</bibl>
```

### Example 10.4.5.F: encoding a citation with parentheses only around the year and pages

Majumdar (1943: 23–28)

```xml
<bibl rend="omitname">
  <ptr target="bib:Majumdar1943_01"/>
  <citedRange>23-28</citedRange>
</bibl>
```

### Example 10.4.5.G: encoding a citation with *ibid*.

*ibid.: 23–28

```xml
<bibl rend="ibid">
  <ptr target="bib:Majumdar1943_01"/>
  <citedRange>23-28</citedRange>
</bibl>
```

### Example 10.4.5.H: encoding a citation of the Annual Report on Indian Epigraphy

```xml
<bibl>
  <ptr target="bib:ARIE1962-1963"/>
  <citedRange unit="page">157</citedRange>
  <citedRange unit="appendix">C/1945-1946</citedRange>
  <citedRange unit="item">1</citedRange>
</bibl>
```

please always follow this example when citing the ARIE appendices, i.e. always include the year (or range of years written out in full) mentioned in the title of the appendix, separated with a slash from the letter of the appendix

## 10.4.6. Referring to inscriptions in the DHARMABase

- to refer to another inscription in the DHARMABase, use the element `<ref>`

- such references may be included in any freeform text, but will at the present stage most likely to be used in an apparatus note or inside a `<p>` element in the `<div type="commentary">`

- unlike the `<ptr/>` element used in bibliographic citations (§10.4.5), `<ref>` is not an empty element: it must contain a human-readable reference
- we recommend keeping the contents limited to the identifier of the inscription you want to quote

- any specification of the line (or other details) to which you are referring may be added after the `<ref>` element, e.g. `<ref>C. 7</ref>`, line 5

- in order for this markup to allow us to generate a hyperlink to the intended edition in the online presentation of the DHARMABase, the attribute `@target` has to be used to establish the link to the relevant xml file

- for files kept in the same repository, the value of this attribute shall be the filename of the inscription, e.g. `<ref target="C00007.xml">C. 7</ref>`

- for files kept in different repositories, add a further attribute `@n`, containing the name of the GitHub repository where the file is located, e.g. `<ref n="tfa-pallava-epigraphy" target="Pallava00001.xml">Pallava 1</ref>`

- the same method can also be used to create a link toward an external database

- in this case, the value of the `@target` element should contain a permanent URL

## 10.5. Encoding Names

- see §7.4 about the optional encoding of names within the edition

- names (contemporary or pre-modern) may, in principle, be tagged anywhere in a document, but we do not recommend doing so in any content except where explicitly called for in another section of this guide

- at present the Responsibility Statement (§11.1.2) is the only section which calls for name markup outside the edition

### 10.5.1. Tagging contemporary names

- when a contemporary name requires a tag, wrap the entire name in the element `<persName>

- if the name is that of a DHARMA project participant (such as your own name), add the attribute `@key`

- the value of this attribute shall be the personal identifier<fnref n="50" /> of the participant, with the prefix “part:” (as an abbreviated reference to the file listing participants of the project)

- within this element

- either apply the tags `<forename>` and `<surname>` to the respective components of the name

- or apply `<name>` to the whole of a name if it cannot be broken down in this way

- note that in this case `<persName>` must still wrap `<name>

**Example 10.5.1.A: encoding the name of a project participant**

```xml
<persName key="part:argr">
<forename>Arlo</forename>
<surname>Griffiths</surname>
</persName>
```

## 10.6. Attributes as Referencing Systems

### 10.6.1. Encoding authorship with @resp

- the attribute `@resp` (for “responsibility”) may be added to any XML element to encode the fact that a particular project participant is the author of that particular item, without explicitly writing their name in the text (for which see §10.5.1)

- in the initial stages of our project, most of our XML documents will be the products of a single individual or a small number of people, who will be recorded as authors in the TEI header (§11.1.2) of each file

- therefore, this attribute will only be necessary where specifically called for in this guide, namely

- to explicitly encode your authorship for translations (§9.2.1)

<footnote n="50">⁵⁰ Our personal identifiers are available at https://github.com/erc-dharma/project-documentation/blob/master/DHARMA_IdListMembers_v01.xml</footnote>
- to encode the authorship of individual notes in a translation by someone other than the author of the note (§9.2.4)

- later on, however, many of our documents will probably be revised and improved by other project members

- to facilitate the tracking of such revisions and to have a record of credit, @resp may be added to any element

- the value of @resp shall be the personal identifier of a project participant<fnref n="51" /> with the prefix “part:”

- to credit more than one participant, simply include several personal identifiers (each prefixed as above) within a single @resp attribute, separating them with nothing but a space

### 10.6.2. Crediting publications with @source

- the contents of certain markup elements as a whole may need to be credited to a publication, including in particular

- lemmas and/or readings in a critical apparatus (§9.1.3, §9.1.4)

- notes (§10.4.1)

- translations as a whole (§9.2.1)

- to credit a previous publication, the attribute @source must be added to the XML entity representing the item you wish to credit

- the value of @source shall be the Zotero Short Title of the publication containing the reading you are crediting, prefixed with the string “bib:”

- do not include additional reference details such as a page number or an item number in a compilation: this cannot be done in this referencing system

- wherever a page or item number is essential (because your XML document does not include a full citation of the publication concerned), you will need to use a full citation (§10.4.5) in your text instead of the attribute @source

- to credit more than one publication (e.g. because more than one scholar has suggested or endorsed a certain reading, or because a note was published in several publications)

- the relevant prefixed short titles must appear, in chronological sequence (earlier publications precede later ones), within a single @source attribute, separated by nothing but a space, e.g. `<rdg source="bib:Devadatta1863_01 bib:Doe2019_01">`

### 10.6.3. Identifying persons and places with @key

- to encode the common (standard) name of a person or place designated in your text by an alternative name, add the optional attribute @key to the `<persName>` or `<placeName>` element, recording the standard name as the value of this attribute, e.g.

- `<persName key="Śiva">Pinākin</persName>`

- `<placeName key="Pāṭaliputra">Kusumapura</placeName>`

- this attribute may be used whenever you feel that a name needs identification or disambiguation,

- in conjunction with the attributes for classifying names discussed above; or

- with a `<persName>` or `<placeName>` element created solely for the purpose of adding this attribute

- the use of this attribute does not produce a fully machine-actionable encoding and is intended as a first step toward the possible eventual creation of a prosopography and gazetteer

- to this end, the values used in the corpus may be harvested at a later time for standardisation and verification, which may be followed by replacing this attribute with a fully machine-actionable linking mechanism

### 10.6.4. Identifying elements with @xml:id

- the attribute @xml:id may be used to assign a unique identifier to any XML element

<footnote n="51">⁵¹ Our personal identifiers are available at https://github.com/erc-dharma/project-documentation/blob/master/DHARMA_IdListMembers_v01.xml</footnote>
- at the present stage, the use of `@xml:id` is prescribed by this guide only for a few situations, but we shall probably use this attribute more extensively in the future

- with this in mind, we prefer to make all our XML identifiers unique across the project's corpus, even though many practical applications of this identifier require only that it be unique within a particular document

- to achieve this, an `@xml:id` shall in our project always begin with the **filename** (without extension) of the document, and be followed by the specific identifier of the item in question, with an underscore character separating the two

- for example, to create XML identifiers for hands numbered "hand1" and "hand2" in the file "Pallava00001.xml", use "Pallava00001_hand1" and "Pallava00001_hand2"

## 10.7. Punctuation and Style in Modern Languages

- in general, observe the conventions of whichever modern language you are writing in and avoid imposing the conventions of another language

- when writing in French, it is not necessary to create the *espace insécable devant ponctuation*, which can be added automatically later on
# 11. The TEI Header

- the TEI header presents marked-up metadata about the XML document and about the inscription and artefact(s) it concerns

- the header may be composed of several high-level elements, the most prominent of which is the File Description

- the sections below outline the header elements used in our project and their contents

- at the present stage (as of May 2020), we encode only a bare minimum of data directly within the TEI header

- the guidelines below are intended to help you understand the functions and structure of the TEI header, but you need not be able to create such a header from scratch

- instead, rely on the most recent version of the project's EpiDoc template<fnref n="52" /> and add data to the header only where comments in the template instruct you to do so

## 11.1. Describing the XML Document

- the mandatory File Description is enclosed in the element `<fileDesc>`, which precedes a description of the original document

- in our practice, the mandatory contents of the File Description shall be as follows

- a Title Statement, wrapped in the element `<titleStmt>`, with the following items

- information about the title of the digital document

- information about the persons responsible for its content

- a Publication Statement, tagged as `<publicationStmt>` and serving to group together information concerning the publication of the digital document

### 11.1.1. The title

- the contents of the `<title>` element shall be plain text in English, without any additional markup

- this title will also be used in the web publication of the digital edition

- use a title that clearly and unambiguously identifies the inscription

- see Appendix E for guidance concerning title creation

- variant names applied to the inscription in question in previous publications shall be recorded in the metadata spreadsheet (and will be made searchable once imported from there into our TEI headers)

### 11.1.2. The responsibility statement

- after the title but still within `<titleStmt>` the wrapper `<respStmt>` is used for crediting contributors

- short descriptions of the principal roles that we wish to record are wrapped in the tag `<resp>`

- the names of the contributors are encoded with the markup introduced in §10.5.1

- follow the instructions found in the current template to fill out the contents of this statement<fnref n="53" />

<caption>Example 11.1.2.A: the responsibility statement</caption>

```xml
<respStmt>
<resp>EpiDoc encoding</resp>
<persName ref="part:jodo">
<forename>John</forename>
<surname>Doe</surname>
</persName>
</respStmt>
```

### 11.1.3. The publication statement

- the structure and most of the contents of this statement will be provided in our template, but you will have to add the following data as instructed by comments in the template

<footnote n="52">⁵² Available under https://github.com/erc-dharma/project-documentation/tree/master/templates</footnote>

<footnote n="53">⁵³ The precise details to be recorded here are still in flux at the time of finalising this version of the EGD. You can expect more detailed instructions either here in a future version or in the template itself.</footnote>
- the place where you work in `<pubPlace>`

- the name of the file itself, encoded as an identification number in the element `<idno>` with the attribute `@type` bearing the value `"filename"`

- the name of the copyright holder

<caption>Example 11.1.3.A: the publication statement</caption>

```xml
<publicationStmt>
  <authority>DHARMA
    <note>This project has received funding from the European Research Council ERC under the
    European Union's Horizon 2020 research and innovation programme grant agreement no 809994.
  </note>
</authority>
<pubPlace>Paris</pubPlace>
<idno type="filename">Pallava00001</idno>
<availability>
  <licence target="https://creativecommons.org/licenses/by/4.0/">
    <p>This work is licensed under the Creative Commons Attribution 4.0 Unported Licence. To
    view a copy of the licence, visit https://creativecommons.org/licenses/by/4.0/ or send a letter
    to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA.</p>
    <p>Copyright c 2019-2025 by Emmanuel Francis.</p>
  </licence>
</availability>
<date from="2019" to="2025">2019-2025</date>
</publicationStmt>
```

## 11.2. Describing the Original Document

- the final element of the `<fileDesc>` is the source description, `<sourceDesc>`

- this mandatory element records details of the original from which the digital text is derived

- TEI permits the use of various elements in a source description, but in the case of epigraphic documents its only child element is `<msDesc>`, signifying "manuscript description" and applicable to any text-bearing object besides manuscripts in the strict sense

- at present, you only need to encode the data explicitly called for in the subsections below

- other metadata shall be recorded in spreadsheets for the time being and they will, at a later stage, be integrated with the TEI header through a largely automated process

- however, this Guide does frequently recommend that you discuss this or that matter 'in your metadata'

- whenever there is no evident way to do so in a metadata spreadsheet, or if you do not have access to such a spreadsheet, or if for any other reason it is more convenient, we suggest that you insert a `<!-- comment -->` at the very bottom of your file and fill it with any content that will eventually need to find its place in the TEI header of that file

- please be aware that data stored in such comments will not be automatically moved to a spreadsheet or to a TEI header: at some point they will have to be moved manually to their proper place

### 11.2.1. The hand description

- basic designations of script names (Gupta Brahmi, Tamil, Grantha, Khmer, Kawi, etc.) will be recorded in our metadata spreadsheets and imported from there into our TEI Headers in due course

- if you wish to record any further **palaeographic observations** pertaining to the inscription as a whole (rather than to a specific locus), you may do so in the `<handDesc>` section of the TEI header

- to record your observations, use the element `<p>` within `<handDesc>`, filing it with free prose

- you may create additional `<p>` elements for a longer description

- it is not mandatory to create content in `<handDesc>`, but if you have such information to record, do it here

- it will normally be necessary to discuss only those elements that seem uncommon/exceptional given the general knowledge that the informed reader may be assumed to have of the script(s) in question

- subjects that are of projectwide interest and should in general be recorded include:
- the use of any other type of vowel killer than the ‘normal’ *virāma/puṇṇi* (e.g., miniature/subscript consonants, see TG §3.3.1)

- the use of ornamental lettering in whole or part of the text

- you may cite examples of every phenomenon with free-text reference to the line or lines where they are found, e.g. <p> ... Final consonants <foreign>K</foreign> and <foreign>T</foreign> are found in lines 3 and 8. ...</p>

- also mention here any perceived similarity to hands seen in other inscriptions (using the mode of reference to other inscriptions prescribed in §10.4.6)

- in addition to a <p> element with free text, the <handDesc> element may include a structured description of multiple hands

- we shall only use this method when more than one hand can be clearly identified within a single document

- in this case, you will need to take the following steps:

- within <handDesc>, wrap the <p> element pre-built into your template in the element <summary>, whether or not you have added any content inside this <p>

- if you have created more than one <p> element here, wrap all of them together in a single <summary>

- after the <summary> element, create one <handNote> element for each hand, with the mandatory attribute @xml:id to serve as a unique identifier for each hand (see also §10.6.4 about XML identifiers)

- the values of this attribute shall be "hand1", "hand2" and so on for the required number of hands, prefixed with the filename (without extension) and an underscore _ character

- in the contents of the <handNote> element, write a concise, freeform description of the hand

- e.g. <handNote xml:id="Pallava00001_hand1">A neat hand with a tendency to use northern character forms.</handNote>

- once the hands have been encoded in the header as above, use <handShift/> within your edition to indicate hands, as described in §4.4

### 11.3. Keeping Track of File History

- from the moment it is created, the life-cycle of any xml file is liable to include any number of events, such as additions, updates, corrections, or transformations

- the history of the file is to be recorded in the Revision Description, encoded in <revisionDesc> as the final high-level element in the TEI header

- once basic encoding has reached the first significant milestone, no further significant changes should be made in the file without a notification in the revision description

- recording changes at a manageable yet still meaningful level of detail can become an asset for the management and control of the files, for instance by helping

- to resolve issues regarding the encoding choices that can arise when files are being edited by multiple team members

- to gain a quick overview of the latest changes made when you return to work on a file after some time

- we therefore recommend that you always check this part of the file before resuming your work to be sure that you have a clear understanding of the state of the encoding and avoid deleting changes made by others

- within <revisionDesc>, create one <change> element for each significant change, with the following attributes:

- mandatorily, @who, the value of which shall be the personal identifier<fnref n="54" /> of the person(s) making the change, i.e. normally yours, with the prefix “part:” (as an abbreviated reference to the file listing participants of the project)

<footnote n="54">⁵⁴ Our personal identifiers are available at https://github.com/erc-dharma/project-documentation/blob/master/DHARMA_IdListMembers_v01.xml</footnote>
- to record multiple identifiers, prefix each as above and separate them by a space

- mandatorily, @when, the value of which shall be the date of the change in ISO format, i.e. YYYY-MM-DD

- optionally as needed, @status, to help keep track of significant milestones in the history of the file, with one of the following values

- "draft"

- "candidate"

- "approved"

- "published"

- "withdrawn"

- the contents of <change> shall be a freeform description of the modification

- please be concise, but avoid generic formulations and favour precise ones

- keep in mind that changes should be logged in reverse order, i.e. the most recent change should appear at the top of the list

Example 11.2.1.A: the revision description

```xml
<revisionDesc>
  <change who="part:daba" when="2019-12-10">Encoding of the translation</change>
  <change who="part:daba" when="2019-12-01" status="draft">Creation of the file and basic structural encoding of the inscription</change>
</revisionDesc>
```
# Appendices

## Appendix A. Converting CII/EI Markup Conventions to EpiDoc

- word segmentation

- spaces (indicating non-compound word separation) remain spaces

- hyphens

- used for compound segmentation between words fused in vowel sandhi (e.g. *parākkram-āṅka* = *parākkrama+āṅka*) are discarded (*parākkramāṅka*)

- used for compound segmentation and not affected by sandhi fusion are optionally retained as per TG §2.6.2

- inserted at the ends of printed lines (when an epigraphic line is too long to fit in one printed line) are normally discarded

- if they also serve for compound segmentation, they may be optionally retained as above

- inserted at the ends of epigraphic lines (when a line end is not the end of a word) are to be converted into markup by adding `@break="no"` to the following `<lb>` element (see §3.2.4/)

- if such a hyphen also serves for compound segmentation, optionally retain the hyphen, but move it after the line beginning tag

- double hyphens (or equal signs)<fnref n="55" /> normally become spaces

- but when used between words fused in vowel *saṁdhi* (e.g. *c=āpi*), they are discarded

- round parentheses () are used in two ways:

- with text inside, e.g. *sa* to mark an editorial correction of the text preceding the parenthetical text

- the scope is normally the same number of *akṣaras* as there are within the parentheses (in most cases, exactly one *akṣara*)

- the corresponding markup in EpiDoc is correction or normalisation by substitution (§6.2.2, §6.3.2), which we can apply to any segment, from a single phoneme to a longer string

- with a question mark inside, (?) to flag the preceding text (usually one *akṣara*) as very uncertainly read

- in our terms, this is “unclear” with low certainty (§5.3.2)

- with text and a question mark inside, used in some publications as follows:

- (?)abc), with the question mark before the text, to indicate a possible alternative reading (§5.3.3)

- (abc?), with the question mark after the text, to indicate a tentative emendation (which we do not encode as such; the tentativeness of an emendation encoded as per §5.5 may be indicated in an apparatus note)

- square brackets [] are used for no less than four functions

- 1. to wrap “letters which are much damaged and nearly illegible in the original”

- this normally corresponds to our “unclear” category (§5.3.1), in some cases with low certainty

- 2. to wrap “letters ... which, being wholly illegible, can be supplied with certainty”

- i.e. normally “supplied” in our terminology (§5.5)

- it is usually not possible to distinguish 2 from 1 without studying a facsimile of the inscription; if you cannot do this and you are only transcribing a printed edition to EpiDoc, use “unclear” for both

- 3. text followed by a question mark in square brackets, [abc?] is used by some editors to indicate tentatively or conjecturally read text

- this usually corresponds to “unclear” with low certainty (§5.3.2)

- 4. text followed by an asterisk in square brackets, [abc*] in principle means editorial restoration of characters omitted by the original scribe, but in the actual practice of some editors it seems to be used for function 2 above

- for editorial correction of omissions, see §6.2.4

<footnote n="55">⁵⁵ Double hyphens are used in CII convention to indicate non-compound word separation where the end of the first and the beginning of the second word belong to the same *akṣara* of the original. Their primary function is to distinguish regular *akṣaras* from *halanta* consonants and initial vowels (e.g. तदाहु: > tad=āhuḥ; तद् आहु: > tad āhuḥ). We achieve this distinction by means of uppercase characters (TG §3.3.1 and §3.3.3).</footnote>
- note that earlier editors usually supply punctuation marks and numbers in stanzas, which you should not do (see §6.1.3)

- if possible, look at a facsimile to check whether this editorial markup stands for a scribal omission or for lost and supplied text; if this is not possible, assume that square brackets with an asterisk stand for scribal omission

5. prosodic notation in square brackets indicates a lacuna of known metre, to be marked up as per §5.4.4

- plain transliterated text

- bear in mind that unclear markup in EpiDoc should be used when the interpretation of a character would be ambiguous without its context, i.e. more frequently than in most earlier printed editions

- the same applies, to a lesser degree, to restorations: if a character (or component) is completely indistinct in a good facsimile or the original support, feel free to mark it up as supplied even if the print edition shows it as merely unclear or even as clearly read

- **dots** or other signs indicating lacunae

- CII normally uses dots for lacunae, roughly indicating their size by the rule of “two dots correspond to one akṣara” (single dots may mean a lost vowel or a lost consonant)

- other editors may use asterisks or underscores, each corresponding to an *akṣara*, though this correspondence may be extremely inaccurate in some editions

- see §5.4 about handling lacunae in EpiDoc

# Appendix B. Metre (Prosody)

## Looking up Sanskrit metres

- to identify the metre of a Sanskrit stanza, check the lists of syllabic and moraic metres below and use Apte's (1957) Appendix A to identify metres not listed here

- to accelerate your identification, you can try one of these online tools:

- https://sanskritmetresSpot.com/ requires a full stanza as input but will tolerate mistakes and lacunae and produce an approximate match

- http://sanskritlibrary.org:8080/MeterIdentification/ recognises a very large number of metres and accepts half or quarter stanzas as input (but does not tolerate errors); it accepts several transliteration schemes but these need to be selected manually instead of being recognised automatically

- if you have identified a metre not already listed in the Table 3 below, please get in touch with the authors of this guide to add its name and pattern to the table

## Syllable length

- quantitative and syllabo-quantitative verse in the languages we work with relies on the distinction of short and long syllables for producing rhythm in verse, therefore we prefer the terms “length”, “long” and “short” to the corresponding triad “weight” (or “quantity”), “heavy” and “light” often used in discussions of verse in other languages

- a mora is defined as the duration of a short syllable, and a long syllable is always equivalent to two morae

- as a reminder, syllable length is essentially determined as follows:

- a **short syllable** is one whose vowel is short (in Sanskrit: a, i, u, ṛ, l) and is followed by no more than one consonant (without regard to whether a word boundary is also present)

- a **long syllable** is one that does not meet both of the above conditions for a short syllable; specifically, a syllable is called

- long by nature, if its vowel is long (in Sanskrit: ā, ī, ū, ṛ, e, ai, o, au)

- long by position, if its vowel is short but is followed by two or more consonants

- *anusvāra* and *visarga* normally count as consonants in determining syllable length, but

- in Prakrit languages, *anunāsika* (usually not distinguished in writing from *anusvāra*) indicates the nasalisation of a vowel rather than a nasal consonant following the vowel, and a nasal vowel followed by a single consonant may still count as short
- should you encounter this phenomenon, accept the metre as legitimate, and preferably encode a normalisation (§6.3.2) of *anusvāra* to *anunāsika*

- in Sanskrit verse (though generally only in pre-classical Sanskrit), *anusvāra* may cause the preceding vowel to be long even when followed by another vowel

- should you encounter this phenomenon in a classical metre, treat it as a metrical anomaly and add @real to the encoding of verse lines that exhibit it (§2.3.5)

- certain schools of versification permit some kinds of licence in determining syllable length, the most common licence being that a short vowel followed by a voiceless stop and an *r* or *l* may count as a short syllable

- our strategy is to encode the use of such licence as a metrical anomaly in order to facilitate research

- thus, @real must be added to the encoding of verse lines that employ it (§2.3.5)

## Prosodic code

- the signs set out below are to be used in values of XML attributes that require prosodic notation, namely in the following contexts

- 1, @met used in <lg> to encode the metre for which a conventional name is not available (see §2.3.4)

- 2, @met used in <seg> to encode the prosody of a lacuna (see §5.4.4 and §5.4.5)

- 3, @real used in <l> to encode the actual prosody of a metrically deviant verse line (see §2.3.5)

- the final column of the table shows which of these contexts permit the use of each particular sign; the general rules are as follows

- in the attribute @real, use only the signs + and - to encode the exact prosody of a metrical realisation

- exceptionally, anceps or moraic notation is permitted in @real when necessitated by partial lacunae for which only the template, not the actual realisation, is known

- in @met, use the notation for anceps (rather than for a long syllable) at the end of each line of syllabic verse

- caesurae and odd/even quarter boundaries shall only be noted in context 1, and the latter only when the metre has a different template for odd and even lines (*ardhasamavytta*)

- prosodic code must not contain spaces

- the table also shows the equivalent conventional signs (where available), which will be used for displaying metrical notation

- when using **numbers to encode moraic feet or cola**, be aware of the following

- numbers used in prosodic code (for moraic metre) must always be delimited by the foot boundary sign |

- this allows multi-digit numbers to be used when necessary; however, consider whether large moraic units can be analysed into combinations of smaller feet

- moraic feet may be constrained (e.g. the pattern ु-ु is prohibited in many tetramoraic feet), but this depth of prosodic analysis is not desirable in our encoding of metre: simply encode all tetramoraic feet as 4 regardless of whether or not they exclude certain patterns

- for partially lacunose feet, show only the number of lost morae

- e.g. to encode the prosody of a partially lost tetramoraic foot of which one light syllable is extant at the end, use “3-”

<table><caption>Table 2. Prosodic notation</caption><thead><tr><td>Description</td><td>Code</td><td>Conventional notation</td><td>Context</td></tr></thead><tbody><tr><td>one short/light syllable</td><td>-</td><td>ु</td><td>1, 2, 3</td></tr><tr><td>one long/heavy syllable</td><td>+</td><td>-</td><td>1, 2, 3</td></tr><tr><td>one syllable of indeterminate length (anceps)</td><td>=</td><td>॥</td><td>1, 2, (3)</td></tr></tbody></table>
<table><tr><td>two morae (one long or two short syllables)</td><td>2</td><td>॥</td><td>1, 2, (3)</td></tr><tr><td>larger moraic foot or colon</td><td>numeral(s)</td><td></td><td>1, 2, (3)</td></tr><tr><td>foot boundary</td><td>|</td><td>|</td><td>1, 2, (3)</td></tr><tr><td>caesura</td><td>||<sup>56</sup></td><td>||</td><td>1</td></tr><tr><td>boundary of odd and even quarter</td><td>/</td><td></td><td>1<sup>57</sup></td></tr></table>

## Sanskrit syllabic metres

- the names listed below are to be used as values of @met in <lg>

- always use metre names exactly in the form shown there (rather than legitimate variant or alternative names)

- the XML notation shown below uses the prosodic code introduced on page 133 above

- caesurae are indicated in conventional notation for the sake of accuracy and to help you in metre identification, but are not shown in the XML notation, so if you wish, you can copy and paste segments of this notation for use in the @met attribute of lost text (encoded as per §5.4.4)

<table><caption>Table 3. Sanskrit syllabic metres</caption><thead><tr><th>Syllables</th><th>Name</th><th>XML notation</th><th>Conventional notation</th></tr></thead><tbody><tr><td>7/7</td><td>sumānikā<sup>58</sup></td><td>+---+--=-</td><td>-U-U-U-<sup>59</sup></td></tr><tr><td>8/8</td><td>anuṣṭubh<sup>59</sup></td><td>========++=/<br>========+-=-</td><td><sup>59</sup>><sub>58</sub><sup>59</sup> U---U-<sup>60</sup><sub>61</sub><br><sup>59</sup>><sub>58</sub><sup>59</sup> U-U-<sup>60</sup><sub>61</sub></td></tr><tr><td>10/11</td><td>vegavatī</td><td>--+---+--+-=/<br>+---+---+--+=</td><td>U-U-U-U-U-<sup>62</sup><sub>63</sub>/<br>-U-U-U-U-U-<sup>62</sup><sub>63</sub></td></tr><tr><td>10/11</td><td>viyoginī<sup>60</sup></td><td>--+---+--+-=/<br>--+---+--+-=-</td><td>U-U-U-U-U-<sup>62</sup><sub>63</sub>/<br>U-U-U-U-U-<sup>62</sup><sub>63</sub></td></tr><tr><td>11</td><td>triṣṭubh<sup>61</sup></td><td></td><td></td></tr><tr><td>11</td><td>dodhaka</td><td>+---+---+--+=</td><td>-U-U-U-U-U-<sup>64</sup></td></tr><tr><td>11</td><td>indravajrā</td><td>++---+---+-+=</td><td>--U---U-U-<sup>65</sup></td></tr><tr><td>11</td><td>rathoddhatā</td><td>+---+---+-+=</td><td>-U-U-U-U-<sup>66</sup><sub>67</sub></td></tr><tr><td>11</td><td>śālinī</td><td>+++++---+--+=</td><td>-----|-U---U-<sup>68</sup></td></tr><tr><td>11</td><td>svāgatā</td><td>+---+---+--+=</td><td>-U-U-U-U-U-<sup>69</sup><sub>70</sub></td></tr><tr><td>11</td><td>upajāti<sup>62</sup></td><td>=+---+---+--+=</td><td><sup>69</sup>><sub>70</sub>-U---U-U-<sup>71</sup></td></tr></tbody></table>

<footnote n="56">56 Two iterations of | [U+007C Vertical Line], not a || double vertical bar character.</footnote>

<footnote n="57">57 Use only in @met for stanzas where a conventional metre name is not available and the metre has a different template for odd and even lines (ardhasamavṛtta).</footnote>

<footnote n="58">58 In assigning a name to this very rare metre, we follow Damais (1952: 25) who in turn relies on an editorial (correction) to a list of metres in Colebrooke (1873: 141, n.1). It appears from Velankar (1949: ٤٢٨) that no two traditional authorities agree on a name for this metre. The names cited there from treaties on poetics are: uṣṇih (which is also the class name for 7-syllable samavṛttas), kāminī, kheṭaka, gominī, raktā, śikhā and samānikā.</footnote>

<footnote n="59">59 Also known as śloka, vaktra. See also the Notes on anuṣṭubh on page 136 below.</footnote>

<footnote n="60">60 If a verse matches this template, do not classify it as vaitālīya; see the Notes on the vaitālīya family on page 137 below.</footnote>

<footnote n="61">61 Used as an umbrella term for 11-syllable metres not conforming to one of the specific schemes listed here; see Vedic trimeter on page 138 below.</footnote>

<footnote n="62">62 Also known as triṣṭubh upajāti; see the Notes on the upajāti family on page 137 below.</footnote>
<table><thead><tr><th>Syllables</th><th>Name</th><th>XML notation</th><th>Conventional notation</th></tr></thead><tbody><tr><td>15</td><td>mālinī</td><td>-------++++-++-+=</td><td>uuuuu--|----u-ü</td></tr><tr><td>17</td><td>hariṇī</td><td>------++++-+--+-=</td><td>uuuuu-|----|u-uu-ü</td></tr><tr><td>17</td><td>mandākrāntā</td><td>++++---++-+-+=</td><td>----|uuuuu-|----u-ü</td></tr><tr><td>17</td><td>nardaṭaka</td><td>----+-+---++-+-=</td><td>uuuu-v-uuu-uu-uuü</td></tr><tr><td>17</td><td>pṛthvī</td><td>-+---+-+---++-+=</td><td>v-uuu-v-|uuu-uu-vü 70</td></tr><tr><td>17</td><td>śikharinī</td><td>-++++---++---=</td><td>u------|uuuuu-uuuü</td></tr><tr><td>19</td><td>śārdūlavikrīḍita</td><td>++++-+---++-+-+=</td><td>----v-v-v-vv-|----v-vü</td></tr><tr><td>19</td><td>sumadhurā</td><td>++++-+---++---=</td><td>----v--|uuuuu-|----uuü</td></tr><tr><td>20</td><td>mattebhavikrīḍita</td><td>--++++-+---++-+-+=</td><td>uuu-v-v-v-vv-|----v-vü</td></tr><tr><td>20</td><td>suvadanā</td><td>++++-+---++---=</td><td>----v--|uuuuu-|----uuü</td></tr><tr><td>21</td><td>sragdharā</td><td>++++-+---++-+-+=</td><td>----v--|uuuuu-|----v-vü</td></tr></tbody></table>

## Notes on anuṣṭubh

- we use anuṣṭubh as an umbrella term and shall not make a distinction between Vedic anuṣṭubh, and classical vaktra/śloka in our classification

- when encoding the prosody of lost text (§5.4.4), the first four syllables of each anuṣṭubh quarter shall be marked up as indeterminate, as shown in the list of syllabic metres above

- there are in fact some additional restrictions for these syllables, set out in Table 4 below

- if you wish, feel free to mark up any non-conformant lines as metrically deviant (§2.3.5)

- note that vipulā variations (alternative cadences in the odd quarters) do not require any explicit markup but may be encoded as metrically deviant lines (§2.3.5)

<table><caption>Table 4. Permitted patterns in pathyā anuṣṭubh</caption><thead><tr><th></th><th>1</th><th>2-4</th><th>5</th><th>6</th><th>7</th><th>8</th></tr></thead><tbody><tr><th>odd</th><td>ü</td><td>--ü<br>u-ü<br>-uü</td><td>ü</td><td>-</td><td>-</td><td>ü</td></tr><tr><th>even</th><td>ü</td><td>--ü<br>u-ü<br>-uu</td><td>ü</td><td>-</td><td>ü</td><td>ü</td></tr></tbody></table>

<footnote>often observe a caesura after the 8th syllable of a vasantatilakā line. (For further discussion see Pollock 1977, 73-74.)</footnote>

<footnote n="70">⁷⁰ The caesura in pṛthvī is not observed by all poets.</footnote>
<table><caption>Table 5. Recognised vipulā anuṣṭubh patterns (even lines only)</caption><thead><tr><th></th><th>1</th><th>2-4</th><th>5</th><th>6</th><th>7</th><th>8</th></tr></thead><tbody><tr><th>na-vipulā</th><td>~</td><td>---</td><td>~</td><td>~</td><td>~</td><td>~</td></tr><tr><th>bha-vipulā</th><td>~</td><td>-~-</td><td>-</td><td>~</td><td>~</td><td>~</td></tr><tr><th>ma-vipulā</th><td>~</td><td>-~-</td><td>-|</td><td>-</td><td>-</td><td>~</td></tr><tr><th>ra-vipulā</th><td>~</td><td>---</td><td>|-</td><td>~</td><td>-</td><td>~</td></tr></tbody></table>

## Notes on the *upajāti* family

- this family of metres includes 11 and 12-syllable metres which vary in the length of the first syllable and thus give rise to ambiguities concerning classification

- *upajāti* or *triṣṭubh* *upajāti*, a free mix of *indravajrā* and *upendravajrā*

- *vaṁśamālā* or *jagatī* *upajāti*, a free mix of *indravaṁśa* and *vaṁśastha*

- when every line of a stanza is in one of the “pure” metres (e.g. *indravajrā*), that stanza should normally be classified as that pure metre, whereas stanzas with one or more lines in the other child metre should be classified as the “mixed metre” (e.g. *upajāti*)

- however, the mixed metres are more widely used than the pure ones, therefore

- if an inscription includes several successive stanzas of a mixed metre among which one or a few stanzas are in a pure metre, then it makes better sense to classify the pure stanza(s) as being also of the mixed metre (assuming that the poet was composing in the mixed metre and by chance all lines of that particular stanza turned out in one of the pure metres)

- if an inscription includes a stanza in one of these metres with at least one line-initial syllable lost, then it is better to assume the stanza to be in the mixed metre even if all the fully extant lines are in one of the pure metres

- there may always be cases where the above considerations do not apply; for example when a composer shows off his skill by employing a wide variety of metres

## Notes on the *vaitālīya* family

- this family of *ardhasama* metres also gives rise to ambiguities of classification because it uses a loose moraic template for the first part of each line and a syllabic template for the cadence (final part) of each line:

- *vaitālīya*, with the pattern ~~vv~~ -~~v~~ -~~v~~ / ~~vv~~ -~~v~~ -~~v~~

- *aupacchandasika*, with the pattern ~~vv~~ -~~v~~ -~~v~~ / ~~vv~~ -~~v~~ -~~v~~

- and the much rarer *āpātalikā*, with the pattern ~~vv~~ -~~v~~ -~~v~~ / ~~vv~~ -~~v~~ -~~v~~

- in addition, there exist a small number of fully syllabic templates which are specific, constrained instantiations of the above, partly moraic templates:

- *vaitālīya* may be realised as *vīyoginī* or *aparavaktra* (see Table 3 for the patterns)

- *aupacchandasika* may be realised as *mālabhāriṇī* or *puṣpitāgrā*

- *āpātalikā* may be realised as *vegavatī*

- in actual poetic practice, these fully syllabic instantiations are much more common than the less constrained moraic templates

- nonetheless, many editors of Indic texts prefer to classify such stanzas by the generic metre and not by the specific instantiation

- you should avoid this and, if a previous edition identifies a stanza as one of these generic metres or if you are editing a previously unedited text, check whether the stanza in fact conforms to one of the specific metres, and if it does, mark it up as such
## Vedic trimeter

- though rare in our epigraphic corpus, some stanzas may be composed in lines of 11 or 12 syllables that do not observe any of the strict schemes named in Table 3 above; instead,

- lines consist of 11±1 or 12±1 syllables, with varying line number permitted within a stanza

- the initial colon (the “opening”, before a more or less clear caesura) is relatively free, but predominantly trochaic

- the caesura is generally followed by a pair of short syllables (“break”)

- the final colon (cadence) of each line is relatively fixed in a trochaic pattern

- such metres shall be collectively referred to as trimeter, following Arnold (1905:7, 11-14)

- we judge that a rough typology of metrical patterns serves our needs better than a detailed encoding that could give due consideration to the intricacies of these metres

- therefore, use the following values of @met for stanzas in such metres

- "triṣṭubh" for stanzas of predominantly 11-syllable lines which predominantly conform to either of the following patterns

— ਕੁ-ਕੁ-ਕੁ||ੁੁ-ੁ-ੁ

— ਕੁ-ਕੁ-ਕੁ||ੁੁੁ-ੁ-ੁ

- "jagatī" for stanzas of predominantly 12-syllable lines which predominantly conform to either of the following patterns

— ਕੁ-ਕੁ-ਕੁ||ੁੁੁ-ੁ-ੁ

— ਕੁ-ਕੁ-ਕੁ||ੁੁੁ-ੁ-ੁ

- "trimeter" as a general token for stanzas where the metrical pattern and/or length of the lines varies more than in the more specific metres named above

- depending on the level of your interest in metrical studies, feel free to encode the actual prosody of each line in @real

## Sanskrit/Prakrit moraic metres

- the metres of the āryā or gāthā family consist of two hemistichs, each comprised of eight feet which are tetramoraic except for the 6th (which is a single mora in some cases) and the 8th (which is usually bimoraic), with a caesura after the 3rd foot

each hemistich follows an exact template as listed in

- Table 7 below

- keep in mind that by our encoding convention, a hemistich in such a metre is encoded as one <1> element (definition of “line” in §2.3.1), with the number "ab" or "cd" (§2.3.2)

- the metre names listed below are to be used as values of @met in <1g>

- if you are encoding verse of this type with lacunae, it is not necessary to encode the prosody of lacunae more accurately than the generic template shown in the list below (but feel free to do so where you can)

the full detail of permitted metrical variation in the regular (pathyā) form is shown in

- Table 7 below, including the following variations:

- a hemistich in which the caesura after the third foot is ignored or displaced is called a *vipulā*, which may be marked up as an unobserved caesura (§2.3.2)

- a hemistich with a special constraint applied to the first 5 feet is called a *capalā*

- metrically anomalous and *capalā* lines may optionally be marked up using the attribute @real (§2.3.5)
<table><caption>Table 6. Names and general pattern of moraic metres</caption><thead><tr><th></th><th>Moraic feet</th><th>Template (see next table)</th></tr></thead><tbody><tr><td>āryā</td><td>4|4|4||4|4|4|4|2/ 4|4|4||4|4|1|4|2</td><td>A<br>B</td></tr><tr><td>gīti</td><td>4|4|4||4|4|4|4|2/ 4|4|4||4|4|4|4|2</td><td>A<br>A</td></tr><tr><td>upagīti</td><td>4|4|4||4|4|1|4|2/ 4|4|4||4|4|1|4|2</td><td>B<br>B</td></tr><tr><td>udgīti</td><td>4|4|4||4|4|1|4|2/ 4|4|4||4|4|1|4|2</td><td>B<br>A</td></tr><tr><td>āryāgīti</td><td>4|4|4||4|4|4|4|4/ 4|4|4||4|4|4|4|4</td><td>C<br>C</td></tr></tbody></table>

<table><caption>Table 7. Specifics of moraic metres</caption><thead><tr><th></th><th>1</th><th>2</th><th>3</th><th>4</th><th>5</th><th>6</th><th>7</th><th>8</th></tr></thead><tbody><tr><td>A</td><td>~~</td><td>~~</td><td>~~</td><td>~~</td><td>~~</td><td>~~</td><td>~~</td><td>~~</td></tr><tr><td>B</td><td>~~</td><td>~~</td><td>~~</td><td>~~</td><td>~~</td><td>~~</td><td>~~</td><td>~~</td></tr><tr><td>C</td><td>~~</td><td>~~</td><td>~~</td><td>~~</td><td>~~</td><td>~~</td><td>~~</td><td>~~</td></tr><tr><td>capalā</td><td>~~</td><td>~~</td><td>~~</td><td>~~</td><td>~~</td><td>~~</td><td>~~</td><td>~~</td></tr><tr><td>vipulā</td><td></td><td></td><td></td><td>~~</td><td>~~</td><td>~~</td><td>~~</td><td>~~</td></tr></tbody></table>

## Tamil metres

- due to practical considerations, Tamil metre shall be classified only by major types (pā), as shown in Table 8 below

- the names in the first column are to be used as values of @met in <lg>

<table><caption>Table 8. Tamil metres</caption><thead><tr><th>Major type</th><th>Included forms</th><th>Included subtypes (pāviṇam)</th></tr></thead><tbody><tr><td>veṇpā</td><td>kuṛa|-veṇpā (2 aṭis)<br>nēricai-veṇpā (4 aṭis)<br>iṇṇicai-veṇpā (4 aṭis)<br>cintiyal-veṇpā (3 aṭis)<br>paḳṛoṭai-veṇpā (5 to 12 aṭis)</td><td>kuṛa|l-veṇcentuṛai<br>kuṛa|l-tālīcai<br>veṇ-tālīcai<br>veṇ-tuṛai<br>veļi-viruttam</td></tr><tr><td>āciriyappā<br>(3 to 1000 aṭis)</td><td>nēricai-āciriyappā<br>iṇaikkuṛal-āciriyappā</td><td>āciriya-tālīcai<br>āciriya-tuṛai</td></tr></tbody></table>
<table><tr><td></td><td>nilaimanṭila-āciriyappā<br/>aṭimaṛimaṇṭila-āciriyappā</td><td>āciriya-viruttam</td></tr><tr><td>kalippā<sup>71</sup></td><td>ottālicai-kalippā (with 3 subforms)<br/>veṇ-kalippā<br/>koccaka (with 5 subforms, the 5th one having 3<br/>subsubforms)</td><td>kali-tālicai<br/>kali-tuṛai<br/>kali-viruttam<br/>kaṭṭalai-kalittuṛai<br/>kaṭṭalai-kalippā</td></tr><tr><td>vañcippā<sup>72</sup></td><td>(no forms)</td><td>vañci-tālicai<br/>vañci-tuṛai<br/>vañci-viruttam</td></tr><tr><td>maruṭpā</td><td>composed of elements of veṇpā and āciriyappā</td><td></td></tr></table>

## Appendix C. “Case Studies” in Encoding Complex Layout

### Case study 1: four-faced stele

<figure><img src="image_42.png" /></figure>

- this imaginary stele is an oblong quadrangle in cross-section

- all four sides are inscribed, with text starting on one of the broad faces

- each line of the text runs across one edge, onto the adjacent narrow face

- subsequent lines fill up the inscribed field of this pair of faces

- the text then flows on to the top of the next broad face and proceeds to fill up that face and the adjacent narrow face in the same way as the first pair of faces

- thus, the partition between the two pairs is pagelike (§3.5), therefore the virtual zones must be marked up using pagelike milestone elements (§3.5.3)

- the boundary between a wide face and the adjacent narrow face comprises a gridlike partition, since the text disregards the physical transition to a new surface

- such a pair of faces thus constitutes a single virtual zone, whose partition into two physical surfaces may be ignored in the markup or may be encoded by means of a gridlike milestone element (§3.6)

<footnote n="71">71 Contains up to 6 different types of elements which are: taravu, tālicai, arākam, ampōtaraṅkam, taṇiccol, curitakam.</footnote>

<footnote n="72">72 Contains elements which are: taṇiccol, akaval-curitakam.</footnote>
Case study 2A: copperplate charter with seal and other goodies

J R R
Tolkien

The Hobbit In a hole in the ground there lived a hobbit. Not
a nasty, dirty, wet hole, filled with the ends of worms
and an oozy smell, nor yet a dry, bare, sandy hole with

nothing in it to sit down on or to eat: it was a
hobbit-hole, and that means comfort. It had a perfectly
round door like a porthole, painted green, with a shiny

yellow brass knob in the exact middle. The door opened
on to a tube-shaped hall like a tunnel: a very
comfortable tunnel without smoke, with panelled walls.

and floors tiled and carpeted, provided with polished
chairs, and lots and lots of pegs for hats and coats.

29 September 2019

- this imaginary set of copper plates consists of

- an inscribed seal

- three plates, the first and the last inscribed only on their inner faces

- with foliation marks on the recto faces of the second and third plate

- with an inset initial text on the first page

- with a visually separated colophon on the last page

- the seal and the plates comprise a boxlike partition that must be encoded as two textpart divisions (§3.4)

- the second division is a virtual zone subdivided into pagelike partitions (§3.5), which are actual pages and must thus be encoded as <pb> elements

- the blank outer pages must also be encoded (§3.5.2)

- within the second division,

- text begins with a floating incipit, which must be marked up as a special line (§3.3.3)

- the foliation numbers comprise forme work (§3.3.5), each attached to the relevant page

- the special alignment of the colophon may optionally be encoded (§7.5.2)

<div type="textpart" n="A"><head xml:lang="eng">Seal</head><!--Seal as a division. Since the two divisions are different in nature, @subtype is not used, but a <head> is added for identification §3.4.3.--><!-By project convention, the seal is encoded before the text of the plates.--><ab><!-Seal text wrapped in a block-level element, in this case <ab> because it does not
qualify as a paragraph §2.2.2. -->
<lb n="1"/>J R R
<lb n="2"/>Tolkien
</ab>
</div>
<div type="textpart" n="B"><head xml:lang="eng">Plates</head>
<pb n="1r"/><!--Blank outer page; the page beginning is not inside a block-level element
§3.5.2. -->
<ab>
<pb n="1v"/><!--This page beginning is inside the first block-level container of the text,
which happens to be the <ab> wrapper for the incipit. This does not imply that the page break is
part of that <ab>. -->
<lb n="01"/>The Hobbit <!--Line numbers are mandatorily restarted in the second textpart
§3.4.4. The specially positioned incipit has the line number 01 §3.3.3. -->
</ab>
<p><!--First semantic paragraph of the text. -->
<lb n="1"/>In a hole in the ground there lived a hobbit. Not
<lb n="2"/>a nasty, dirty, wet hole, filled with the ends of worm
<lb n="3"/>and an oozy smell, nor yet a dry, bare, sandy hole with
<pb n="2r"/>
 <!--Within a textpart, line numbers are continued on subsequent pages as recommended under
 §3.2.2. Alternatively, they could be reset to 1 on each page, provided that the number of the
 current page is incorporated into each line number to maintain uniqueness. -->
<fw place="bot-left" n="2r">
 <!--Foliation encoded right after the page beginning, §3.3.5. -->
 <num value="2">2</num>
</fw>
<lb n="4"/>nothing in it to sit down on or to eat: it was a
<lb n="5"/>hobbit-hole, and that means comfort.
</p><!--Ending a semantic paragraph here and starting a new one. -->
<p>It had a perfectly
<lb n="6"/>round door like a porthole, painted green, with a shiny
<pb n="2v"/>
<lb n="7"/>yellow brass knob in the exact middle. The door opened
<lb n="8"/>on to a tube-shaped hall like a tunnel: a very
<lb n="9"/>comfortable tunnel without smoke, with panelled walls,
<pb n="3r"/>
<fw place="bot-left" n="3r">
 <!--Foliation right after the page beginning. -->
 <num value="3">3</num>
</fw>
<lb n="10"/>and floors tiled and carpeted, provided with polished
<lb n="11"/>chairs, and lots and lots of pegs for hats and coats.
</p>
<ab><!--The colophon is an incomplete sentence, so it gets an <ab> wrapper. -->
<lb n="12" style="text-align: right"/><!--Optionally marking up right-aligned line. -->
 <num value="29">29</num> September <num value="2019">2019</num>
</ab>
<pb n="3v"/><!--Blank outer page; the <pb/> element is not inside a block-level container. -->
</div>
Case study 2B: copperplate charter with a lost plate reconstructed

The Hobbit In a hole in the ground there lived a hobbit. Not a nasty, dirty, wet hole, filled with the ends of worms and an oozy smell, nor yet a dry, bare, sandy hole with

3

and floors tiled and carpeted, provided with polished
chairs, and lots and lots of pegs for hats and coats.

29 September 2019

- as a variation on Case Study 2A, we now have a partial set of plates where the middle plate is missing along with the seal

- from the presence of foliation marks (and from our intimate knowledge of the Middle Earth copper plate corpus) we can infer that exactly one plate was lost, therefore we include the lost plate in our edition instead of creating textpart divisions (§5.4.8)

- we can also infer that the lost plate would have been inscribed with exactly three lines on both faces, so this is also encoded in the edition

- extant details are encoded as in Case Study 2A above
Case study 2C: copperplate charter with a lost plate not reconstructed

J R R
Tolkien

The Hobbit In a hole in the ground there lived a hobbit. Not
a nasty, dirty, wet hole, filled with the ends of worms
and an oozy smell, nor yet a dry, bare, sandy hole with

and floors tiled and carpeted, provided with polished
chairs, and lots and lots of pegs for hats and coats.

29 September 2019

- as another variation on Case Study 2A, we again have a partial set of plates where the middle plate is missing

- this time, however, the seal is extant and there are no foliation marks, nor are we sufficiently familiar with any other Middle Earth plates, so we cannot confidently reconstruct the structure of the lost section

- our edition must therefore be divided into three textparts: one for the seal, one for the initial plate, and one for the final plate (§5.4.8)

- extant details are encoded as in Case Study 2A above

<div type="textpart" n="A"><head xml:lang="eng">Seal</head>
<ab>
<lb n="1"/>J R R
<lb n="2"/>Tolkien
</ab>
</div>
<div type="textpart" n="B"><head xml:lang="eng">Initial plate</head>
<pb n="1r"/>
<ab>
<pb n="1v"/>
<lb n="01"/>The Hobbit
</ab>
<p part="I"><!--Incomplete paragraph marked as an initial part. -->
<lb n="1"/>In a hole in the ground there lived a hobbit. Not
<lb n="2"/>a nasty, dirty, wet hole, filled with the ends of worm
<lb n="3"/>and an oozy smell, nor yet a dry, bare, sandy hole with
</p>
</div>

```xml
 <!--Nothing is encoded for the lacuna itself, since the use of textparts makes it clear that text
  is lost between the two; details go in the layout description and the commentary. -->
```

<div type="textpart" n="C"><head xml:lang="eng">Final plate</head>
<p part="F"><!--Incomplete paragraph marked as a final part. -->
```
```html
<pb n="1r"/>
 <!--Page and line numbering are reset to 1 in the second textpart §3.4.4. -->
<lb n="1"/>and floors tiled and carpeted, provided with polished
<lb n="2"/>chairs, and lots and lots of pegs for hats and coats.
</p>
<ab>
<lb n="3" style="text-align: right"/>
<num value="29">29</num> September <num value="2019">2019</num>
</ab>
<pb n="1v"/>
</div>
```

## Appendix D. Language Codes

- some of the languages that concern us do not yet have a language codes

- for these we must use provisional codes (starting with x) until our code requests (submitted on December 15 2019) yield the desired result.

- note that for Dravidian languages, we do not make a distinction between “Old” and “Modern” varieties

- by contrast, in the case of all vernacular languages of Southeast Asia, you must make this distinction, although we expect you will only very rarely have the need to use codes for modern Burmese, modern Cam, modern Javanese, modern Khmer, or Malay(sian)/Indonesian.

<table><caption>Table 9. ISO 639-3 language codes</caption><thead><tr><td>Language (and script)</td><td>code</td></tr></thead><tbody><tr><td>Undetermined language</td><td>unknown</td></tr><tr><td>Burmese, modern</td><td>mya</td></tr><tr><td>Burmese, old</td><td>obr</td></tr><tr><td>Cham, modern (of Phanrang)</td><td>cjm</td></tr><tr><td>Cham, old (generally known as “Cham”)</td><td>x-oldcham</td></tr><tr><td>Dutch</td><td>ndl</td></tr><tr><td>English</td><td>eng</td></tr><tr><td>French</td><td>fra</td></tr><tr><td>Indonesian</td><td>ind</td></tr><tr><td>Japanese</td><td>jpn</td></tr><tr><td>Javanese, modern</td><td>jav</td></tr><tr><td>Javanese, old</td><td>kaw</td></tr><tr><td>Kannada (modern or old)</td><td>kan</td></tr><tr><td>Khmer, modern</td><td>khm</td></tr><tr><td>Khmer, old</td><td>x-oldkhmer</td></tr><tr><td>Malay, modern (Bahasa Malaysia)</td><td>zlm</td></tr><tr><td>Malay, old</td><td>x-oldmalay</td></tr><tr><td>Mon, old</td><td>omx</td></tr><tr><td>Pali</td><td>pli</td></tr><tr><td>Prakrit</td><td>pra</td></tr><tr><td>Pyu</td><td>pyx</td></tr><tr><td>Sanskrit</td><td>san</td></tr><tr><td>Sundanese, old</td><td>x-oldsun</td></tr><tr><td>Tamil (modern or old)</td><td>tam</td></tr><tr><td>Telugu (modern or old)</td><td>tel</td></tr><tr><td>Vietnamese</td><td>vie</td></tr></tbody></table>
## Appendix E. Titling Conventions

- when assigning a title to the inscription you are encoding, it is in general recommended that you try to remain faithful to established names for inscriptions that have been edited before

- in cases where established names in a corpus follow significantly varying models, so that the need for some harmonization is felt, the team member(s) responsible for the corpus in question has/have the option to design a new system and apply it rigorously to all members of the corpus in question

- new inscriptions should, as a rule, be named on the analogy of established names within the same corpus

- in all cases, variant names applied to the inscription in question in previous publications shall be recorded in the metadata spreadsheet (and will be made searchable once imported from there into our TEI headers)

- when creating new titles, it is recommended (but not mandatory) that you compose your title by combining the following elements, in this order

1. **place:** start your title with a place name, using (if possible) one of the following options

a. **internal:** attempt to identify the name of the place(s) that is (or are) most fundamentally concerned by the transaction recorded in the inscription

- resort to a less important but more distinctive internal toponym if the toponym resulting from the above test is insufficiently distinctive

- if you are dealing with Indonesian inscriptions, represent the internal toponym free of diacritics, in EYD spelling (e.g., Sobhamerta for *sobhāmṛta*), and for further guidance, see Damais 1952: 6-9

b. **based on provenance:** use the name of the findspot, e.g. "Nalanda"

- provenance-based places may, if necessary, include the specification of a topographic feature or a monument, e.g. "rock", "cliff", "victory pillar", "Cave 16", "Vedānteśvara temple pillars", etc.

c. **based on custody:** a reference to the place or institution where the support is currently kept. E.g. BBRAS plates of Dhruvasena I, year 210

- place names based on custody should only be employed if neither a provenance-based, nor an internal place name is available

2. **artifact type or document type:** add a word or two describing the nature of the support or the text, using the cover term "inscription" only if no more satisfactory term can be found.

- use document type (e.g., "grant", "dedication" or "dedulatory inscription", "foundation", "label", "graffito", "eulogy") if the place name used in the title is an internal toponym

- e.g. "Raktamālā grant"

- use artifact type (e.g., "plate", "stele", "slab", "pillar", etc.) if the place name used in the title is based on provenance or custody

- e.g. "Nalanda plates", "British Museum pillar"

3. **the principal protagonist** of the inscription, if named in the text

- this is usually the person who issued/commissioned the inscription and/or the work commemorated in it, but may be another named person, such as the reigning ruler if the commissioner is another person who is not named

- preferably, use "of" before the name of the issuer

- preferably, use "of the time of" before the name of a reigning ruler who is not the protagonist

4. **supplementary details:** after the above elements, add further information whenever necessary for disambiguation, potentially including:

- calendrical or regnal year, if mentioned within the text

- optionally including further dating specifics noted in the text, if necessary for disambiguation, e.g. month and day in the case of several charters of the same provenance, same king, same year, and where a title based on the content does not work

- optionally using "undetermined year" if a year is mentioned in the text, but is lost or illegible

- any additional distinction, e.g.

- "Set 1" and "Set 2" to distinguish two sets of copper plates with the same provenance, issued by the same ruler on the same date
– “north column” and “south column” to distinguish two copies of an inscription engraved in duplicate

– the above items may be listed with commas or connected to one another by short English phrases as seems most suitable

– some examples of titles composed or elaborated along the above lines:

– Nalanda plate of Samudragupta (provenance, type and issuing ruler)

– Raktamālā grant of the time of Budhagupta, year 159 (internal place, type, reigning ruler, date)

– Vallam, Vedānteśvara temple pillars, foundation by Kantacēṇaṇ of the time of Mahendravarman I (provenance with monument details, type of inscription, issuing person, reigning ruler)

– Uttiramērūr, Sundaravaradaperumāl temple, southern wall of vimāna, donation of the time of Nandivarman II, year 16 (provenance with monument details, additional specification of location, type, reigning ruler, regnal year)

– Uttiramērūr, Vaikuṇṭhaperumāl temple, larger platform, southern base, inscription of the time of Dantivarman, year 8, larger platform, southern base (provenance with monument details, additional specification of location, no clear text type, reigning ruler, regnal year)

– Gunung Wukir stele of Sañjaya

– Hampran dedication of Bhānu

## Appendix F. Normalisation Suggestions

– this appendix contains some specific suggestions for encoding non-standard usage in various languages

– all of these are to be understood as no more than suggestions: when encoding any particular text, feel free to apply a stricter or more lenient approach to any phenomenon depending on what seems to be normal in that given text and in related texts

– if the prosody of metrical verse is affected (either spoiled or corrected) by normalisation, then the considerations outlined in §6.1.4 overrule the suggestions listed below

<table><caption>Table 10. Normalisation suggestions</caption><thead><tr><td>language</td><td>phenomenon</td><td>action</td></tr></thead><tbody><tr><td>Sanskrit in Cambodia</td><td>mismatch of dentals with retroflexes in conjuncts (e.g., ṇd, ṣth)</td><td>flag or normalise</td></tr><tr><td>Old Javanese</td><td>spelling of long <i>pepet</i> with a plus length mark<sup>73</sup></td><td>ignore</td></tr><tr><td>Old Javanese</td><td>use of Ṛ or Ṭ (and Ṛ or Ṭ) in words whose dictionary spelling has rə or lə (or rā or lā)</td><td>ignore</td></tr><tr><td>Old Khmer</td><td>absence of <i>virāma</i></td><td>ignore</td></tr><tr><td>Old Khmer</td><td>representation of final consonant C by the spelling CCa, including final /h/ represented as ḥha</td><td>ignore</td></tr><tr><td>Sundanese and Javanese</td><td>expected nasal+stop cluster spelt with only the stop</td><td>normalise</td></tr><tr><td>Sanskrit</td><td>sibilant doubled after r</td><td>ignore or flag</td></tr><tr><td>Sanskrit</td><td>any consonant doubled before r</td><td>ignore or flag</td></tr><tr><td>Sanskrit</td><td>use of tv where ttv is expected</td><td>ignore or flag</td></tr><tr><td>any</td><td>use of b where v is expected, or vice versa</td><td>flag</td></tr><tr><td>any</td><td>infidelity to the correct length of vowels in words borrowed from</td><td>ignore or flag</td></tr></tbody></table>

<footnote n="73">73 To be represented as a: as per TG §3.3.6.</footnote>
<table><thead><tr><th>language</th><th>phenomenon</th><th>action</th></tr></thead><tbody><tr><td></td><td>Sanskrit<sup>74</sup></td><td></td></tr><tr><td>any</td><td>use of <i>anusvāra</i> in place of a final <i>m</i> or <i>M</i> or vice versa</td><td>ignore or flag</td></tr><tr><td>any</td><td>use of a nasal consonant in place of an <i>anusvāra</i> before a sibilant or <i>h</i></td><td>ignore or flag</td></tr><tr><td>any</td><td>use of one nasal instead of another</td><td>ignore or flag</td></tr><tr><td>any</td><td>use of an aspirated consonant instead of its unaspirated counterpart or vice versa</td><td>ignore or flag</td></tr><tr><td>any</td><td>use of a dental consonant instead of its retroflex counterpart or vice versa</td><td>ignore or flag</td></tr><tr><td>any</td><td>use of one sibilant instead of another</td><td>ignore or flag</td></tr></tbody></table>

<footnote n="74">⁷⁴ See also TG §3.3.7 and EGD §6.3.7.</footnote>
References

Apte, Vaman Shivaram. 1957. *Revised and enlarged edition of Prin. V. S. Apte's The practical Sanskrit-English dictionary*. Edited by P. K. Gode and C. G. Karve. Poona: Prasad Prakashan.

Arnold, Edward Vernon. 1905. *Vedic Metre in Its Historical Development*. Cambridge: Cambridge University Press.

Birnbaum, David J. 2015. *What is XML and why should humanists care? An even gentler introduction to XML*. http://dh.obdurodon.org/what-is-xml.xhtml

Bodard, Gabriel. 2010. 'EpiDoc: Epigraphic Documents in XML for Publication and Interchange'. In *Latin on Stone: Epigraphic Research and Electronic Archives*, edited by Francisca Feraudi-Gruénais, 101-18. Lanham: Lexington Books. http://www.stoa.org/wordpress/wp-content/uploads/2010/09/Chapter05_EpiDoc_Bodard.pdf

Colebrooke, Henry Thomas. 1873. *Miscellaneous Essays*. Vol. 3. London: Trübner.

Damais, Louis-Charles. 1952. 'Études d'épigraphie indonésienne, III: liste des principales inscriptions datées de l'Indonésie'. *Bulletin de l'École française d'Extrême-Orient* 46 (1): 1-105. https://doi.org/10.3406/befeo.1952.5158

Fleet, John Faithfull. 1888. *Inscriptions of the Early Gupta Kings and Their Successors*. Corpus Inscriptionum Indicarum, III. Calcutta: Superintendent of Government Printing.

Pollock, Sheldon Ivan. 1977. *Aspects of Versification in Sanskrit Lyric Poetry*. American Oriental Society.

Roueché, Charlotte and Julia Flanders. *The Gentle Introduction to Mark-up for Epigraphers*, http://www.stoa.org/epidoc/gl/latest/intro-eps.html

Velankar, Hari Damodar. 1949. *Jayadāman A Collection of Ancient Texts on Sanskrit Prosody and a Classified List of Sanskrit Metres with an Alphabetical Index*. Haritoṣamālā 1. Bombay: Haritosha Samiti.