Skip to content
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

Open
wujastyk opened this issue May 15, 2023 · 16 comments
Open

Separate grouping for certain <add> items #56

wujastyk opened this issue May 15, 2023 · 16 comments

Comments

@wujastyk
Copy link

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:

   <l xml:id="SS.1.14.1">athātaḥ śoṇitavarṇanīyam
                        adhyāyaṃ vyākhyāsyāmaḥ <add type="commentary" place="margin">.Hello wirld!</add>|| </l>

So type="commentary" is distinguishing these additions from other more generic scribal additions.

At the moment, this looks like the following:
image

Have you perhaps had to think about such issues in the context of your Paris paratexts project?

@chchch
Copy link
Owner

chchch commented May 16, 2023

I think I've been using <note> for marginal annotations. That way I can easily separate annotations from additions (i.e., corrections). Do you use <note> for anything else?

@wujastyk
Copy link
Author

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.

@chchch
Copy link
Owner

chchch commented May 16, 2023

<note> is set to ignore all by default; I think if you set it to ignore tags only you should get the right output.

@wujastyk
Copy link
Author

wujastyk commented May 16, 2023 via email

@chchch
Copy link
Owner

chchch commented May 16, 2023

include means it includes the actual XML tags when it does the collation... it can be a little unpredictable at the moment, and probably works best for empty tags like <lb/>. I'll eventually get around to rewriting the collation algorithm...

@chakrabortydeepro
Copy link

Thanks for the response, Charles.
I tried it with ignore tags only and it works.
For example, I have three similar notes on mss B₁, B₂ and B₃. And I assigned the same xml:ids to these notes. On the apparatus of the the main edition I see them as three different additions:
image
But on the page of a transcribed ms, it collates with other ones.
image

However, there are some issues with the font:
image

@chchch
Copy link
Owner

chchch commented May 16, 2023

It looks like maybe you're missing an <l> or <lg> tag? If you let me know which file it is I can take a look.

@chakrabortydeepro
Copy link

Thanks for your response, Charles. I didn't use the <lg> tag here. But there is a <l> tag.

The example is from
berline.12433.txt
<l xml:id="BBP-1.1.1.1.10">

@chchch
Copy link
Owner

chchch commented May 16, 2023

Do you have a link to saktumiva.org?

@chchch
Copy link
Owner

chchch commented May 16, 2023

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.

@chakrabortydeepro
Copy link

chakrabortydeepro commented May 16, 2023 via email

@chchch
Copy link
Owner

chchch commented May 16, 2023

Hmm... that might be a bug in the program. Do you get the same problem if you remove the daṇḍa or the <caesura/>?

@chakrabortydeepro
Copy link

After removing the daṇḍa in the main edition, it works well.

@chchch
Copy link
Owner

chchch commented May 16, 2023

Ok let me take a look at the code... for now, maybe try |<caesura/> or <caesura/>dātuṃ or |<caesura/>dātuṃ in the edition to see if it fixes it temporarily.

@chakrabortydeepro
Copy link

Thanks, Charles. Yes, I tried |<caesura/>. It works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants