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

Inline dots in Kāvyamālā Commentary Canto 5 #154

Open
MAMMHOTH opened this issue Dec 22, 2021 · 3 comments
Open

Inline dots in Kāvyamālā Commentary Canto 5 #154

MAMMHOTH opened this issue Dec 22, 2021 · 3 comments

Comments

@MAMMHOTH
Copy link
Contributor

inline dots

How should we understand and encode those dots (p. 61)? Should they be <metamark/>ed (e.g. <metamark place="inline">......</metamark> although the dots are rather at the top of the line not at the bottom)?

@ppasedach
Copy link
Owner

I suppose the editors were not able to read their manuscript there, or maybe already their manuscript had a marked lacuna. I would not worry too much about the position of the dots. It seems, however, that in both cases we have two groups of three dots. Encoding them the way you did should be fine.

@MAMMHOTH
Copy link
Contributor Author

OK thanks a lot. I was also thinking that there were probably some problems with the source since there are also question marks popping up every now and then in the commentary:
question mark commentary

Would those also have to be encoded as <metamark/> or something else btw?

@ppasedach
Copy link
Owner

Oh, that's a reference to Yogasūtra 3.4, "trayam ekatra saṃyamaḥ," the three being dhāraṇā, dhyāna and samādhi, i.e. the upper three of the eight aṅgas, here in an odd order. Interesting. I'll have to see if there's more like that around there.

<metamark>(?)</metamark> should be okay, or, you could also transcribe it as it is. It apparently is an editorial insertion expressing doubt about their reading.

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

2 participants