Tshig Don Mdzod

Tibetan Texts > Specific Tibetan Text Studies > mdzod bdun > tshig don mdzod

ཚིག་དོན་མཛོད།

Status Report on TDD (by Chris H; Updated January 7, 2009)

File Locations and Contents

NOTE THAT THE FILES AND NOTES ON TDD HAVE NOW BEEN MOVED TO JIRA (THLLIT-50); THIS COLLAB PAGE IS NOW OUT OF DATE

The most updated version of TDD is on the collab literary site. Please note that the most updated files are in: Tibetan Literature-THL > Resources > Tibetan Input E-Texts > TDD and TCD. Somehow these have found their way out of the "Nyingma Tantric Texts" folder. There are TCD/TDD materials still in the "Nyingma Tantric Texts" folder, but those are out of date, and I am unable to delete them.

There are six files in the current TDD folder:

  1. Tshig Don Dzod LATEST VERSION (TU August 2009 Edited Version).doc: This is our most updated version of TDD. This is the document that we received from Tibet University, where TDD received another round of proofreading in Aug. 2009. They began with our file that contained Tsering Gyurme's proofreading changes (i.e. document #2 in the list below), and then did an additional proofreading on top of that. They proofed it against the AD edition, for which we provided them a scan. This edition is still not perfect; see discussion of this in the "Notes on TDD Proofreading" link above.
  2. TDD with Tsering Gyurme proofreading changes merged.doc: This is completely marked-up, and has had proofreading changes from Tsering Gyurme merged into it. This should not be considered "proofread," as the proofreading was so problematic that it is still easy to find discrepancies between our electronic edition and the paper AD edition. However, the changes that Tsering Gyurme did make have been merged into this file. We were given two proofread files from him, and as they are different, I merged the changes from each one individually into our main file. Note that I simply accepted any change he made to any word in the text; i.e. I did not check his changes versus the paper AD edition. Note also that the proofreader did not pay careful attention to replicating the shads, so in addition to having a better proofreading done, we also need to make sure that the shads in our edition match those in the paper edition. This file also contains numerous footnotes, which are questions for David; David's classes also began doing a critical edition, so there are a very few footnotes in here that are notes from this critical edition work. This is the version that the Tibet University proofreaders began with.
  3. Our version of TDD before the proofreading changes were merged into it. This is now out of date, but I have put it here in case it is needed.
  4. The first "proofread" file that we received from Tsering Gyurme.
  5. The second "proofread" file that we received from Tsering Gyurme. The idea here was that the proofreader had initially given us the wrong file, and that this error was what made the work appear so poor. This second file has had more work done to it than the first, but it still does not represent a careful proofreading.
  6. Finally, there is a section from chapter 8 that is mis-ordered in the actual paper text of the SG edition. The text in the main file is ordered correctly and complete (this means a few of the SG page numbers will be out of order), but I have also created a separate file containing the mis-ordered text, as it appears in the paper edition, in case someone needs to know what it is. Note that this was created before we moved away from the SG edition and to the AD edition, so now this may not be necessary. Still, we should remember this issue if we do keep the page numbers from SG.

Folders in the TDD folder

  1. There is a folder containing work toward a critical edition, which was performed by students in David's classes. I have not modified these, and have not merged them into our main edition, as it is not clear to me what state the work is in, how complete it is, and so forth. Note that the text and markup in these files is out of date, so if the critical edition notes are used, they will need to be merged into the most updated version of TDD. Note also that these files have had the Dodrupchen page numbers added to them; the Dodrupchen page numers are formatted like: "184-2", where the "2" indicates that this is a Dodrupchen page number, rather than a SG page number.
  2. Secondly, there is a folder containing old and out-of-date versions of TDD. I can't imagine why we would need these, but there they are.

Status of the Project

Markup is complete on TDD. Below are issues that still need to be dealt with.

  • I put questions and comments for you (David G) in the footnotes. Most of these are small, localized issues for you to deal with. The initial project was to do a markup that matched the translation, so, any time I made a style choice, departed from the organization given in the translation, had a small question, etc., I just marked it in the notes. These will probably be tiresome and repetitive to deal with, but I wanted to let you have the opportunity to make the decisions/personal choices, rather than me just making a decision and then having it get buried.
  • I did not deal with the issue of untitled introductions and conclusions (i.e. introductory and concluding comments that seem to need their own section, but are not officially part of the sa bcad). Here is one issue I was thinking about. If we enumerate an "untitled introduction" at the beginning of the chapter, it is going to change the enumeration of the whole chapter. To me, this is going to look confusing. Say you have a "chapter two" that is divided into three parts, and there is an untitled section at the first of those three parts. The untitled section would be 2.2.1 (body, chap. 2, first division). So, then the first division will be 2.2.2, the second will be 2.2.3 and so forth. Especially when an outline gets very dense, I think it will be confusing to see the number 2.2.3 and then have the author say, "Now, for the second point…" Maybe we could devise a way of marking untitled introductions, but to also preserve the integrity of the author's enumeration. Maybe an untitled introduction could be numbered something like 2.2.i, and then the actual first point of the chapter could still be 2.2.1. Or maybe we could give them a subhead, but not include it in the enumeration.
  • In David's translation, some of the verse citations have enumerations in them; these numbers could be added in the unicode Tibetan edition, marked up as "added by editor"
  • Subheads display erratically. I think this is somehow related to the fact that they are based on Word’s pre-programmed subheads. For instance, Word’s preset “heading 8” is an italicized style, and our current Tibetan “heading 8,h8” also displays in italics regardless of how the style is defined. But maybe this is a non-issue as we will convert to XML.
  • The unicode Tibetan font often behaves strangely; place the cursor in one of the page numbers and use the right and left keys to scroll back & forth within the number, and you will see the problem. I don't know if this will effect conversion to XML.
  • Are we reproducing the rin chen spungs shad in this edition?
  • Shads in our edition do not match AD (i.e. double shads -vs- single shads)
  • We need to get the AD page numbers in our master file now; the page numbers in there currently are from SG.
  • It remains fairly easy to find errors in the electronic edition

Provided for unrestricted use by the external link: Tibetan and Himalayan Library