erc-dharma / tfd-sanskrit-philology

DHARMA project, task force D

tfd-sanskrit-philology

DHARMA project, task force D

Help and Guide

• A Guide for Git is provided in the project documentation repository https://github.com/erc-dharma/project-documentation at DHARMA_Git_guide_v01.md
• Schemas are available as well is the repository
  • a validation schema for manuscripts: DHARMA_Manuscripts_schema_v01.rng
  • the Epidoc validation schema : tei-epidoc-schema9.1.rng

Please be careful: a new release of the Epidoc Scheam has been done in October, if you are using a local version for the validation process, use the new one https://github.com/erc-dharma/project-documentation/blob/master/schema/tei-epidoc-schema9.1.rng`

tfd-sanskrit-philology's Issues

modifications to DHARMA_CritEdSarvavajrodaya.xml and CritEd schema

@ajaniak — thanks for importing this file and its Translation from LaTeX source code. At present, the files are not yet valid and hence cannot be displayed. I will list stuff to be changed in this checklist, to which I will gradually be making additions.

• 1. all cases of <rdg type="emn" wit="#XYZ">READING</rdg><witDetail wit="#XYZ" type="silently"/> should become <rdg wit="#XYZ">READING</rdg><witDetail wit="#XYZ" type="silemn"/> — this use of "silemn" is new
• 2. <lem type="emn" wit="#([A-Z]+)">(.+)</lem><witDetail wit="#([A-Z]+)" type="silently"/> should become <lem wit="#$1">$2</lem><witDetail wit="#$3" type="silemn"/>.
• 3. I think cases like this <app><lem type="emn" wit="#MSK">vajradhātvīśvaryā</lem><witDetail wit="#MSK" corresp="#KSP">($\leftarrow$ KSP, Tib.)</witDetail><rdg wit="#cod">vajradhātvīśvaryādi</rdg></app> can be represented as <app><lem type="emn" wit="#MSK" evidence="external">vajradhātvīśvaryā</lem><witDetail wit="#MSK" corresp="#KSP #Tib"/><rdg wit="#cod">vajradhātvīśvaryādi</rdg></app> — this use of @evidence on <lem> and the use of @corresp in <witDetail> are new. Alternative idea: <app><lem type="emn" wit="#MSK" evidence="external" corresp="#KSP #Tib">vajradhātvīśvaryā</lem><rdg wit="#cod">vajradhātvīśvaryādi</rdg></app>.
• 4. I think all cases of <hi rend="italic">$1</hi> can be replaced by <foreign xml:lang="san-Latn">$1</foreign>.
• 5. I have found a few cases where a little chunk of information from the LatEX source seems to have been lost in conversion. See XML line 3334 <note>incorrectly emends <hi rend="italic">raṅgaṁ rekhāyeta | paraṁ</hi></note> for last LaTeX-generated pdf "EdT incorrectly emends raṅgaṁrekhāyeta | paraṁ." Can you track down what has gone wrong here?
• 6. All cases like <app><lem>svahṛdgatavajre</lem><rdg>svahṛdgata[21v1]vajre</rdg></app> are actually only a way to mark the folio transitions in the codex unicus. If it is possible to isolate all these cases (<app>s without attributes on <lem> and <rdg> and with a sequence [##r/v#] inside <rdg>), they can be replaced by regular use of <pb edRef="#cod" n="$1"> inside the edited text (or a <lem>) and where relevant also in a <rdg> with @wit="#cod". Since this point does not lead to file invalidation, it is not a priority.
• 7. When we have a case like this: <note>STTS 72. The MS and the editions read the first half as follows: <rdg wit="#cod #Yed">aho hy anupaman tejaḥ satvadhātvavabhāsanam</rdg> <rdg wit="#Hed">aho hy anupamaṁ tejaḥ sattvadhātvavabhāsanam</rdg> </note>, do you see any convienent way to represent what is meant other than <note>STTS 72. The MS and the editions read the first half as follows: <ptr target="#cod #Yed">: <foreign xml:lang="san-Latn">aho hy anupaman tejaḥ satvadhātvavabhāsanam</foreign> <ptr target="#Hed">: <foreign xml:lang="san-Latn">aho hy anupamaṁ tejaḥ sattvadhātvavabhāsanam</foreign> </note>?
• 8. Cases like <rdg type="emn" wit="#S1">$2</rdg> should be replaced by <rdg wit="#$1">$2</rdg><witDetail wit="$1" type="emn"/> — this use of @type on <witDetail> is new, display should be "$2 $1 (em.)"
• 9. I now suggest that cases like <lem wit="$1">$2</lem><witDetail wit="$1" corresp="#$3"/> can b replaced by <lem wit="$1">$2</lem><note corresp="$3"/> — this use of <note> immediately after <lem> is new, display should be "$2] em. $1 (∥ $3)"
• 10. all cases of @wit="" inside <lem> can be removed if @wit="#MSK" and @wit="#cod" both appear in <rdg>

Of course I would appreciate your advice on the new encoding strategies that I propose. I am not sure @evidence="external" in (2) is necessary as I don't suppose there will be any computational use.

As a next step, I will need your or @michaelnmmeyer's help to make the necessary adjustments to the schema and XLST transformation in order for the usages not yet foreseen in EGC to be validated by the schema and properely displayed.

display of generatedhtml

Dear @michaelnmmeyer —

At the moment, a DiplEd html that is already generated does not yet get shown on the .io site.

See DHARMA_DiplEdSarvavajrodayaCodex.html at https://github.com/erc-dharma/tfd-sanskrit-philology/tree/master/docs/diplEd, not shown at https://erc-dharma.github.io/#tfd-collection. Can you correct this? Thanks.

modify automatic generation of derivate files

@michaelnmmeyer — it is a nuisance that every commit leads to an auto response from the system, as in 1e4a27a.

remote: Counting objects: 100% (19/19), done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 10 (delta 4), reused 10 (delta 4), pack-reused 0
Unpacking objects: 100% (10/10), 954 bytes | 11.00 KiB/s, done.
From https://github.com/erc-dharma/tfd-sanskrit-philology
   393082c..1e4a27a  master     -> origin/master
Merge made by the 'ort' strategy.
 docs/diplEd/DHARMA_DiplEdOSM-Dh95.html             | 2 +-
 docs/html/nityahnikatilaka_csaba_kiss/nat_tei.html | 2 +-
 docs/html/vrsasarasamgraha_csaba_kiss/vss_tei.html | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

Is it possible to let the machine apply its actions only to recently changed xml files, rather than to all xml files in the repo?

diplEd display

dear @michaelnmmeyer —

I am not sure why the folder containing html displays at tfd-sanskrit-philology is called docs (https://github.com/erc-dharma/tfd-sanskrit-philology/tree/master/docs). This seems confusing to me as elsewhere we have folders called docs that contain documentation. Can you reorganize the folder structure, paying attention also to where the small number of files delivered by colleagues based in Naples and Pondicherry (@csabakissgit, @FlorindaDS, @dg2018 ) are stored?

Furthermore, my latest commits 4b2cad7 and e42a96a have not led to the html for the file DHARMA_DiplEdSarvavajrodayaCodex.xml being updated, even though it has no validation problems. Can you push it through?