Switch branches/tags
Nothing to show
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
152 lines (139 sloc) 8.42 KB
<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:id="sarit__XML-ID_HERE" xmlns="">
<teiHeader xml:lang="en">
<!-- this is where you describe this e-text (i.e.,
the computer file, not the book from which it was derived.) -->
<title type="main">The Title</title>
<title type="sub">A SARIT edition</title>
<author><!-- Author --></author>
<author><!-- Author 2 --></author>
<persName><!-- Encoder's name --></persName>
<resp>Creation of machine-readable version.</resp>
<authority>SARIT: Search and Retrieval of Indic Texts</authority>
<availability status="restricted">
<p>Copyright Notice</p>
<p>Copyright 2014 SARIT</p>
<!-- Who typed it? And SARIT.
There has to be a copyright-holder, because only the copyright-holder
can give permission for the file to be distributed under a Creative Commons license. -->
<ref target="" type="licence"
>Distributed by <ref target="" type="url"
>SARIT</ref> under a Creative Commons Attribution-ShareAlike 4.0
International License. </ref>
<p>Under this licence, you are free <list>
<item>to Share — to copy, distribute and transmit the work</item>
<item>to Remix — to adapt the work </item>
<p>Under the following conditions:</p>
<item>Attribution — You must attribute the work in the manner specified
by the author or licensor (but not in any way that suggests that
they endorse you or your use of the work).</item>
<item>Share Alike — If you alter, transform, or build upon this work,
you may distribute the resulting work only under the same or similar
license to this one.</item>
<p>More information and fuller details of this license are given on the Creative
Commons website.</p>
<p>SARIT assumes no responsibility for unauthorised use that infringes the
rights of any copyright owners, known or unknown.</p>
<note><!-- This gets printed by Philologic as a trailing note to the main bibliographical entry.
A good place to give brief info. on what this e-text is (because Philologic annoyingly
prints the sourceDesc not the fileDesc for each file.)--></note>
<!-- this is where you describe the physical edition
or manuscript from which the e-text is derived. -->
<title><!-- --></title>
<editor><!-- --></editor>
<publisher><!-- --></publisher>
<pubPlace><!-- --></pubPlace>
<date><!-- --></date>
<note><!-- --></note>
<!-- Pick and choose bits of the following, as appropriate -->
<p>The published edition from which this e-text was transcribed is printed in the
Devanāgarī script. The electronic text below is in a lossless transliteration
using the Latin alphabet. The transliteration scheme used is the IAST (<ref
>The International Alphabet of Sanskrit Transliteration</ref>). IAST differs
in small ways from ISO 15919, but is preferred by most working Sanskrit
scholars. Conversion of this file to ISO 15919 can be achieved by performing the
following replacements throughout the file: <code> ṛ -> r̥ and ṃ -> ṁ </code>
<p>Text division is as Devanāgarī ("ityevam" not "ity evam".) </p>
<p>Initial vowel elision for avagraha is reversed and marked with a + sign:
e.g., "prathamo+adhyāyaḥ"</p>
<p>Similarly, external sandhis are undone and marked: "yathā+amarā"</p>
<p>The ampersand (&amp;) was used by the inputters as an anchor to mark places in
the e-text where the printed edition has a footnote, and again with the text of
the related footnote being placed nearby in the e-text. I have regularized these
footnotes in many, but not all, cases, changing them to <tag>note</tag>s. The
use of the ampersand may still be irregular in places, and needs to be checked
against the edition, and some notes have been omitted and need to be added from
the edition.</p>
<p>The notes by Trivikramātmaja Ācārya are included in the e-text . using the
<tag>note</tag> element. </p>
<p>A first cut has been made at distinguishing verse and prose. Prose passages
are enclosed in the normal <tag>p</tag> tags. Verse passages are grouped
within the line-group tag, <tag>lg</tag>, and individually tagged as verse
lines, <tag>l</tag>.</p>
<p>Inserted comments <tag>!-- subdivision --</tag> and <tag>!-- /subdivision
--</tag> around passages where the text section is subdivided into a
level below that of the surrounding text. These comment tags need to be
replaced with something better, but we can't use <tag>div3</tag>, for
example, because of the problem of TEI's policy on tessellation. See TEI
Guidelines P5, section 4.3.2, et passim. Nor are these subdivisions floating
text, or groups, or other obvious units. They could be marked with
<tag>span</tag>s (<tag>span type="interesting" spanTo="#xy"</tag>
...<tag>anchor xml:id="xy"</tag>) or <tag>milestone</tag>s, but these
mechanisms seem clumsy. The question stands for now. </p>
<revisionDesc><!-- This is really important. Keep track of who has done what to this file, and when. For guidance on what to write here, and how it differs from what you put in the Git log, see "A change log is ... a curated, chronologically ordered list of notable changes for each version of a project.... It's made for humans, not machines, so legibility is crucial."-->
<change when="2011-07-07" who="???">
<!-- I did this and that. -->
<!-- or you can make a list of changes for one date and person, if you like: -->
<item>Added TEI encoding.</item>
<item><!-- other changes -->
<text xml:id="set-an-id-here" xml:lang="sa-Deva">
<!-- or sa-Latn -->
<body xml:lang="sa-Latn">
<!-- or sa-Latn -->
<!-- The encoded e-text itself -->