Permalink
Browse files

Initial commit. This contains the xml files that are currently being

used in SARIT (http://sarit.indology.info/), as well as a README file.
Please change the .org version of this file (http://orgmode.org/),
which can be edited with any plain text editor (most easily with Emacs).
  • Loading branch information...
0 parents commit a5782adeb5c689d002188c6930bec21befaf5fe0 @paddymcall committed Mar 31, 2011
Showing with 184,497 additions and 0 deletions.
  1. +267 −0 README.html
  2. +80 −0 README.org
  3. +116 −0 README.txt
  4. +49,435 −0 astangahrdayasamhita.xml
  5. +703 −0 ayurvedasutram.xml
  6. +75,259 −0 brahmapurana.xml
  7. +21,601 −0 caryamelapakapradipa.xml
  8. +13,909 −0 kautalyarthasastra.xml
  9. +17,641 −0 manusmrti.xml
  10. +5,486 −0 naradasmrti.xml
@@ -0,0 +1,267 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+lang="en" xml:lang="en">
+<head>
+<title>The SARIT repository</title>
+<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
+<meta name="generator" content="Org-mode"/>
+<meta name="generated" content="2011-03-31 13:26:41 CEST"/>
+<meta name="author" content="patrick mc allister"/>
+<meta name="description" content=""/>
+<meta name="keywords" content=""/>
+<style type="text/css">
+ <!--/*--><![CDATA[/*><!--*/
+ html { font-family: Times, serif; font-size: 12pt; }
+ .title { text-align: center; }
+ .todo { color: red; }
+ .done { color: green; }
+ .tag { background-color: #add8e6; font-weight:normal }
+ .target { }
+ .timestamp { color: #bebebe; }
+ .timestamp-kwd { color: #5f9ea0; }
+ .right {margin-left:auto; margin-right:0px; text-align:right;}
+ .left {margin-left:0px; margin-right:auto; text-align:left;}
+ .center {margin-left:auto; margin-right:auto; text-align:center;}
+ p.verse { margin-left: 3% }
+ pre {
+ border: 1pt solid #AEBDCC;
+ background-color: #F3F5F7;
+ padding: 5pt;
+ font-family: courier, monospace;
+ font-size: 90%;
+ overflow:auto;
+ }
+ table { border-collapse: collapse; }
+ td, th { vertical-align: top; }
+ th.right { text-align:center; }
+ th.left { text-align:center; }
+ th.center { text-align:center; }
+ td.right { text-align:right; }
+ td.left { text-align:left; }
+ td.center { text-align:center; }
+ dt { font-weight: bold; }
+ div.figure { padding: 0.5em; }
+ div.figure p { text-align: center; }
+ textarea { overflow-x: auto; }
+ .linenr { font-size:smaller }
+ .code-highlighted {background-color:#ffff00;}
+ .org-info-js_info-navigation { border-style:none; }
+ #org-info-js_console-label { font-size:10px; font-weight:bold;
+ white-space:nowrap; }
+ .org-info-js_search-highlight {background-color:#ffff00; color:#000000;
+ font-weight:bold; }
+ /*]]>*/-->
+</style>
+<script type="text/javascript">
+<!--/*--><![CDATA[/*><!--*/
+ function CodeHighlightOn(elem, id)
+ {
+ var target = document.getElementById(id);
+ if(null != target) {
+ elem.cacheClassElem = elem.className;
+ elem.cacheClassTarget = target.className;
+ target.className = "code-highlighted";
+ elem.className = "code-highlighted";
+ }
+ }
+ function CodeHighlightOff(elem, id)
+ {
+ var target = document.getElementById(id);
+ if(elem.cacheClassElem)
+ elem.className = elem.cacheClassElem;
+ if(elem.cacheClassTarget)
+ target.className = elem.cacheClassTarget;
+ }
+/*]]>*///-->
+</script>
+
+</head>
+<body>
+<div id="content">
+
+<h1 class="title">The SARIT repository</h1>
+
+<p>Welcome, you are reading the description of the SARIT archive of Indic
+e-texts. SARIT is short for "Search and Retrieval of Indic Texts."
+(cf. <a href="http://sarit.indology.info/">http://sarit.indology.info/</a>)
+</p>
+<p>
+This collection of files is special in that any changes you make to
+your files can, if you choose so, be shared with other people. So if
+you correct, annotate, or otherwise improve any file in this directory
+or one of the directories below it, you might consider sharing your
+work with others (and hope that they will share their work with you).
+</p>
+<p>
+We hope that this will lead to incremental but continuous improvement
+of these files, and of files you wish to add.
+</p>
+
+
+<div id="table-of-contents">
+<h2>Table of Contents</h2>
+<div id="text-table-of-contents">
+<ul>
+<li><a href="#sec-1">1 What to do next? </a></li>
+<li><a href="#sec-2">2 Where can I get help? </a>
+<ul>
+<li><a href="#sec-2_1">2.1 Editing files </a></li>
+<li><a href="#sec-2_2">2.2 Sharing/organizing files </a></li>
+</ul>
+</li>
+<li><a href="#sec-3">3 How does sharing work? </a>
+<ul>
+<li><a href="#sec-3_1">3.1 You changed different parts of a file </a></li>
+<li><a href="#sec-3_2">3.2 You changed the same part of a file </a></li>
+</ul>
+</li>
+<li><a href="#sec-4">4 What are these XML files? </a></li>
+</ul>
+</div>
+</div>
+
+<div id="outline-container-1" class="outline-2">
+<h2 id="sec-1"><span class="section-number-2">1</span> What to do next? </h2>
+<div class="outline-text-2" id="text-1">
+
+
+</div>
+
+</div>
+
+<div id="outline-container-2" class="outline-2">
+<h2 id="sec-2"><span class="section-number-2">2</span> Where can I get help? </h2>
+<div class="outline-text-2" id="text-2">
+
+
+<p>
+That depends on the area you need help with:
+</p>
+
+</div>
+
+<div id="outline-container-2_1" class="outline-3">
+<h3 id="sec-2_1"><span class="section-number-3">2.1</span> Editing files </h3>
+<div class="outline-text-3" id="text-2_1">
+
+
+</div>
+
+</div>
+
+<div id="outline-container-2_2" class="outline-3">
+<h3 id="sec-2_2"><span class="section-number-3">2.2</span> Sharing/organizing files </h3>
+<div class="outline-text-3" id="text-2_2">
+
+
+
+</div>
+</div>
+
+</div>
+
+<div id="outline-container-3" class="outline-2">
+<h2 id="sec-3"><span class="section-number-2">3</span> How does sharing work? </h2>
+<div class="outline-text-2" id="text-3">
+
+
+<p>
+Three steps are involved in sharing these files:
+</p>
+<ol>
+<li>
+Getting <a name="what==other==people==changed" class="target">what other people changed</a> .
+</li>
+<li>
+Letting other people <a name="get==what==you==changed" class="target">get what you changed</a> .
+</li>
+<li>
+<a name="Merging==the==changes" class="target">Merging the changes</a> together.
+</li>
+</ol>
+
+
+<p>
+To do this in an organised fashion, we are using a program called
+<a href="http://git-scm.com/">git</a>. It keeps track of changes to the files in this directory, and can
+`pull' (<a href="#what==other==people==changed">point 1 above</a>) and `push' (<a href="#get==what==you==changed">point 2 above</a>) from or to another
+instance of these files likewise controlled by git. What it pushes are
+the changes you have made to these files, and what it pulls are the
+changes another person (or a group of other persons) has made to these
+files.
+</p>
+<p>
+When it does this, two things can happen:
+</p>
+
+</div>
+
+<div id="outline-container-3_1" class="outline-3">
+<h3 id="sec-3_1"><span class="section-number-3">3.1</span> You changed different parts of a file </h3>
+<div class="outline-text-3" id="text-3_1">
+
+
+<p>
+When, say, Jane corrects paragraph 1, and Jack corrects paragraph 2 of
+the same file, git will be able to `merge' (<a href="#Merging==the==changes">point 3 above</a>) . So if
+Jack `pulls' Jane's changes, paragraph 1 of his file will
+automatically be changed to paragraph 1 of Jane's file. Likewise, if
+Jane `pulls' Jack's changes, her file will automatically be changed in
+paragraph 2 according to Jack's changes. So they each edited only one
+paragraph, but both have the same version of the file now, with both
+paragraphs corrected.
+</p>
+</div>
+
+</div>
+
+<div id="outline-container-3_2" class="outline-3">
+<h3 id="sec-3_2"><span class="section-number-3">3.2</span> You changed the same part of a file </h3>
+<div class="outline-text-3" id="text-3_2">
+
+
+<p>
+In case both Jane and Jack change the same part of a file, git will
+refuse to `merge' the files (since it doesn't know which change is the
+correct one). In this situation, either Jack or Jane will have to
+review the other person's changes, and decide which version to keep
+(or make a third version that contains the changes of both). After
+making these changes, git will understand that either Jack or Jane
+have resolved the conflict, and they can continue to work in the
+normal fashion.
+</p>
+
+
+
+</div>
+</div>
+
+</div>
+
+<div id="outline-container-4" class="outline-2">
+<h2 id="sec-4"><span class="section-number-2">4</span> What are these XML files? </h2>
+<div class="outline-text-2" id="text-4">
+
+
+<p>
+The files in this directory try to adhere to the Text Encoding
+Initiatives standards in version P5 (<a href="http://www.tei-c.org/Guidelines/P5/">TEI P5</a>). These standards define a
+vocabulary for describing things about a text: who is its author,
+which other texts is it referring to, which page of a printed edition
+is this paragraph on, who is "asya" referring to, etc.
+</p>
+
+
+</div>
+</div>
+<div id="postamble">
+<p class="author"> Author: patrick mc allister
+</p>
+<p class="date"> Date: 2011-03-31 13:26:41 CEST</p>
+<p class="creator">HTML generated by org-mode 7.4 in emacs 23</p>
+</div>
+</div>
+</body>
+</html>
@@ -0,0 +1,80 @@
+#+TITLE: The SARIT repository
+
+Welcome, you are reading the description of the SARIT archive of Indic
+e-texts. SARIT is short for "Search and Retrieval of Indic Texts."
+(cf. http://sarit.indology.info/)
+
+This collection of files is special in that any changes you make to
+your files can, if you choose so, be shared with other people. So if
+you correct, annotate, or otherwise improve any file in this directory
+or one of the directories below it, you might consider sharing your
+work with others (and hope that they will share their work with you).
+
+We hope that this will lead to incremental but continuous improvement
+of these files, and of files you wish to add.
+
+
+* What to do next?
+
+* Where can I get help?
+
+That depends on the area you need help with:
+
+** Editing files
+
+** Sharing/organizing files
+
+
+* How does sharing work?
+
+Three steps are involved in sharing these files:
+
+1) Getting <<what other people changed>>.
+2) Letting other people <<get what you changed>>.
+3) <<Merging the changes>> together.
+
+To do this in an organised fashion, we are using a program called
+[[http://git-scm.com/][git]]. It keeps track of changes to the files in this directory, and can
+`pull' ([[what%20other%20people%20changed][point 1 above]]) and `push' ([[get%20what%20you%20changed][point 2 above]]) from or to another
+instance of these files likewise controlled by git. What it pushes are
+the changes you have made to these files, and what it pulls are the
+changes another person (or a group of other persons) has made to these
+files.
+
+When it does this, two things can happen:
+
+** You changed different parts of a file
+
+When, say, Jane corrects paragraph 1, and Jack corrects paragraph 2 of
+the same file, git will be able to `merge' ([[Merging%20the%20changes][point 3 above]]) . So if
+Jack `pulls' Jane's changes, paragraph 1 of his file will
+automatically be changed to paragraph 1 of Jane's file. Likewise, if
+Jane `pulls' Jack's changes, her file will automatically be changed in
+paragraph 2 according to Jack's changes. So they each edited only one
+paragraph, but both have the same version of the file now, with both
+paragraphs corrected.
+
+** You changed the same part of a file
+
+In case both Jane and Jack change the same part of a file, git will
+refuse to `merge' the files (since it doesn't know which change is the
+correct one). In this situation, either Jack or Jane will have to
+review the other person's changes, and decide which version to keep
+(or make a third version that contains the changes of both). After
+making these changes, git will understand that either Jack or Jane
+have resolved the conflict, and they can continue to work in the
+normal fashion.
+
+
+
+
+* What are these XML files?
+
+The files in this directory try to adhere to the Text Encoding
+Initiatives standards in version P5 ([[http://www.tei-c.org/Guidelines/P5/][TEI P5]]). These standards define a
+vocabulary for describing things about a text: who is its author,
+which other texts is it referring to, which page of a printed edition
+is this paragraph on, who is "asya" referring to, etc.
+
+
+
Oops, something went wrong. Retry.

0 comments on commit a5782ad

Please sign in to comment.