-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Separate grouping for certain <add> items #56
Comments
I think I've been using |
Deepro has been doing the same. But they don't get collated, do they? In tests yesterday we got a funny output with collation but in the main text-body, not in the right margin. But we tried several options and to be honest I now can't be sure which result was which. But I know we never quite got what Deepro is after. |
|
Ah, we tried "include" and didn't get what we wanted. Deepro - try "ignore
tags".
|
|
It looks like maybe you're missing an |
Thanks for your response, Charles. I didn't use the The example is from |
Do you have a link to |
Ah I see... you have nested |
Ah, I understand now. Thank you very much, Charles. I removed the xml:ids.
And it works well now.
I have another problem with the collation. In a verse, ms B₂ reads *dhātum *at
the place of *dātum. *On the edition page
<https://saktumiva.org/wiki/chakraborty/balabodhini/sandhiprakarana/edition?upama_ver=he0phtdaju>,
it collates against a daṇḍa at the end of the previous line.
[image: Screenshot from 2023-05-16 13-24-20.png]
And it shows that there is no variation in dātum.
[image: Screenshot from 2023-05-16 13-29-34.png]
And the pop-up window shows a wrong transcription.
[image: image.png]
B₂ was not transcribed as *dhātum dātu*m. There is just one word, *dātum*.
Do you know why this is happening?
…On Tue, May 16, 2023 at 1:17 PM chchch ***@***.***> wrote:
Ah I see... you have nested xml:ids which makes it complicated to
collate. So I guess you should either put the note in a separate <p>, or
remove the xml:ids on the note, so that it gets collated together with
the verse.
—
Reply to this email directly, view it on GitHub
<#56 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIIRWBIPX3O4TAIMA6X3VR3XGPHCXANCNFSM6AAAAAAYCW3FDM>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Deepro Chakraborty
(he/him)
PhD candidate
Department of History, Classics, and Religion
University of Alberta
*The University of Alberta acknowledges that we are located on ᐊᒥᐢᑿᒌᐚᐢᑲᐦᐃᑲᐣ
(Amiskwacîwâskahikan) Treaty 6 territory, and respects the history,
languages, and cultures of the First Nations, Métis, Inuit, and all First
Peoples of Canada, whose presence continues to enrich our institution.*
|
Hmm... that might be a bug in the program. Do you get the same problem if you remove the daṇḍa or the |
After removing the daṇḍa in the main edition, it works well. |
Ok let me take a look at the code... for now, maybe try |
Thanks, Charles. Yes, I tried |
Dear Charles,
Deepro has some manuscripts where there are marginal notes. And the same marginal note appears in more than one witness. Saktumiva already represents
<add>
content in red in the apparatus. We would like these marginal notes to be collated but also to be distinguished or marked off in some way in the apparatus. Perhaps in a different colour, or size or location. Can that be done?Input will probably be something like this:
So
type="commentary"
is distinguishing these additions from other more generic scribal additions.At the moment, this looks like the following:
Have you perhaps had to think about such issues in the context of your Paris paratexts project?
The text was updated successfully, but these errors were encountered: