Comments (8)
I've had a look at the file. All looks good to me; the only problem I've spotted is the reference Nurhadi Magetsari+al1979_01, from which the space needs to be deleted.
from tfc-nusantara-epigraphy.
Eko: I am happy to see that you have mastered the technique of closing an issue by using the right commit message. But I had asked you to let us know when you were not, not to close the issue :) So I am reopening it now.
Dan: thanks. Could you confirm that what Eko has done at the end of the text is alright? This is the first and only plate of what was originally a multiplate set. I am wondering if we should have something like <gap reason="lost" extent="unknown" unit="plate">
. I suppose we have some guidance on what to do in such a case in the EG, but I cannot easily find it.
Axelle: could you take a look at the file too?
from tfc-nusantara-epigraphy.
Good point, I wasn't paying enough attention. The EG does have instructions for "lost copper plates" and "massive lacunae" (under §5.4), but actually some of the latter is not quite clear.
My basic attitude is that there is no point in encoding the lost plate: I have thought of that and rejected the idea because it does not serve a useful function. The fact will be mentioned in the metadata and is only important to human readers.
What should definitely be done is:
- delete the hyphen from ri- at the end of the extant text.
- add @part="I" (for "initial part") to the last
element in the extant text, to encode the fact that this is an incomplete paragraph.
After this, there are basically two options as per the present state of the EG:
- make no further changes. I prefer this simpler solution.
or 2. instead of mentioning the apparatus, encode "ripta" as a restoration. But if this is done, then the second page does need to be encoded as per the EG section on massive lacunae:
ri
pta
Do you agree with the above approach? I think option 2 should be limited to cases with a more substantial restoration. If you agree, I'll make that explicit in the guide, noting that short or uncertain restorations should be mentioned in the apparatus instead of all that code.
I'll also make it clearer under "Lost copper plates" that option 2 is available, since it is only discussed under "Massive lacunae" (to which "Lost copper plates" refers, but that is a bit vague at the moment).
from tfc-nusantara-epigraphy.
I have taken a look, you already have spotted the issues for the point not aligned on the EG.
from tfc-nusantara-epigraphy.
@ajaniak : thanks.
@danbalogh : thanks also. I agree with option 1.
@ekobastiawan : please carry out my corrections suggested in the file, as well as Dan's correction indicated above, and the close this issue.
from tfc-nusantara-epigraphy.
Arlo, just to be clear: options 1 and 2 are both there in the EG, not as options, but as "if there is no restoration" and "if there is restoration". The question, apart from the issue at hand is: should I point it out in the Guide that short and simple restorations may be treated as "no restoration" and handled in the apparatus instead of the edition. Please confirm you agree with that in general.
from tfc-nusantara-epigraphy.
from tfc-nusantara-epigraphy.
Eko: I have revised the file one last time. Please go through it and close this issue when you're done. (You can try git commit -m "resolves #4" once again!)
from tfc-nusantara-epigraphy.
Related Issues (20)
- Update DHARMA_INSIDENKKaladi.xml error HOT 5
- DHARMA_INSIDENKBarsahan HOT 1
- DHARMA_INSIDENKWatuKuraI HOT 1
- pipeline jammed? HOT 1
- start revising DHARMA_INSIDENKPucangan.xml HOT 1
- A.S. Wibowo ZSTs HOT 1
- deal with explicit line-breaking hyphens in autoencoded xml files
- bibliogr. HOT 1
- ROD1923 HOT 1
- zotero items with "Bosch, F. D. K." HOT 1
- parujar and pakaraṇān translations HOT 4
- encode script class and script maturity HOT 1
- revise <abbr>mā></mā> etc. HOT 4
- supplying low-level punctuation HOT 4
- Hampran HOT 3
- encoding Airlangga bibliographies
- system down? HOT 1
- replace value of @reason in <supplied reason="omitted">,</supplied> HOT 1
- attributes on <div type="edition">
- problem in https://dharmalekha.info/texts/INSIDENKNglumbangDungik HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from tfc-nusantara-epigraphy.