-
Notifications
You must be signed in to change notification settings - Fork 9
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
consistent उदात्त svara notation #7
Comments
Also:
|
You want to have it not as per scan? |
Let us differentiate different types of changes, and discuss further. Type 1There is a typographical error. Change is made in digitized version to conform to printed text. All agree that it should be corrected. Type 2There is no change in content. Only display is to be changed. Glyph issue raised above falls in that category. There have been many such display changes adopted. No issues. Type 3Changes in encoding or transliteration standards. Every era has its preferred transliteration scheme. Over the years CDSL has been making such changes e.g. cp1252 to unicode. Anglicised Sanskrit to IAST. Sanskrit text from different dictionaries in different transliterations brought to SLP1. No issues. Type 4Changes where scholars differ, on principles. There has not been consensus about the accepted way of rendering accents across Sanskrit scholars. A Samaveda scholar may mark the same accent in a different way than Rigveda or Yajurveda. In such cases, a discussion is required to reach to a consensus. Some published papers or documentation would help. Otherwise, it may be decided based on what participants feel. Once consensus is reached, this can be taken up. Type 5Changes which are based on user’s preferences of user’s gut feeling. We should discourage such changes, because all users have different feelings or preferences. These changes also tend to create inconsistencies, because the user would submit only for the item he is interested in. There may be many such cases where such a change is not effected. |
Yes, but should we care?
Not sure. Or let's add more examples in each group. |
A more appropriate thread for discussing such types and generalities is sanskrit-lexicon/csl-orig#747 . So, I will not pursue it here.
You mean accents in devanAgarI script I presume, from the context. Ok.
Just in case you mean native experts - False. They understand, respect and follow each others conventions. No conflict. RV and YV don't mark udAtta-s at all.
Sure. I've made a proposal. Let's reach a consensus next. How will you go about it?
You should definitely bring this up in the more general thread. |
One way of doing this is to look at unicode documentations - pdfs linked in https://en.wikipedia.org/wiki/Devanagari_(Unicode_block) , https://en.wikipedia.org/wiki/Devanagari_Extended and https://en.wikipedia.org/wiki/Vedic_Extensions . They have been produced after long and detailed discussions among topic experts. If you have a better notation in mind from there - propose it. In any case, as you said:
So any changes we make here would be easily reversible in the future. |
Minor correction - They're not really three standards - as in three competing standards. Just 3 complementary code-point tables. Our choice for udAtta notation should necessarily come from them. |
Vedic accent and lexicography - https://zenodo.org/record/837826/files/Rau2017_vedic-accent-in-lexicography.pdf |
Good summary. Böhtlingk & Roth
Recipe for grand confusion (given #7 (comment) should use क꣡ and क᳡ respectively. (Creating a separate issue for the internal consistency and CSL encoding problems.) These are the mappings actually implemented in indic_transliteration_py anyway. MW
In devanAgarI - क꣡ and क᳡ respectively. Cappeller
Ditto. |
I guess the Samaveda svara notations (it being the one that is heavily depending on various svaras and glides to recite the Riks) could be adopted across all vedas and their associated works like Brahmanas, Aranyakas, ...), if a consistent 'common' notation is being considered (though it would differ with present published works-- not just the lexical ones being discussed here, sometimes slightly & manytimes to a major extent wrt each individual work). But I highly doubt if this would get any true appreciation from "non-techies"!! People are well accustomed to see different systems present in different works for ages now, and "no real complaint" seems to have comeup from any corner to make a "common framework"-- to the best of my knowledge. |
The above is false (as clarified below). Motivation is not some techie obsession but linguistic interest.
That's because very few people (esp. very few Indian veda memorizers) actually care to look at dictionaries for prakRti-svara-s . In fact, western sanskrit scholars routinely use and record those - not Indians (unfortunate but true). Those that actually care to do so (example- myself and a few friends) and use that information (esp in our speech and writing), would rather have some consistent notation across dictionaries and not have to memorize distinct dictionary conventions (not veda conventions)! |
Good to see your explanation; so you want only the digitised dictionaries to be with common svara notations across all cited vedic literature, even if by doing so they might not be matching with the corresp. vedic texts in print. Isn't better then that this be done in the 'stardict' (or babylon) branch of cdsl texts with a separate script in addition to format conversion (keeping the main cdsl texts as is, them being for a larger user group)? |
To clarify, my main concern is with headwords. That should have consistent notation. Users want to look up prakRti-svara in a jiffy. vedic citations should have internally consistent notation - whatever is right for the shAkhA being cited. Caveats
No - people who care to learn about svara-s from dictionaries don't always use stardict; and they will benefit from consistency. And consistent notation will anyway not bother those who don't care about svara-s. |
Yes, such inconsistencies (or errors in some cases) should definitely be corrected. But very few people have that knowledge or capacity (and mostly, interest) to do such corrections.
Learning svara-s through dictionaries? Sounds intesting; but a bad choice of 'proper sources', I'd say. |
I disagree with this prejudice (not to mention the unspecificity - most ignoramuses understand "learning svara-s" to mean learning to say veda-mantra-s in their neo-traditional intonations). I find the laxya, traditional padapATha-s (which I've dictified as well) and vyAkaraNa to be quite consistent with the efforts of these lexicographers (who have meticulously gone through and in some cases - cited their sources). |
@drdhaval2785 Can we please solve this just for headwords? It would be simple, if you agree on the devanAgarI notation suggested. We've begun practicing svaras ( https://groups.google.com/g/shabda-shAstram/c/1izIRQfA5b8 ), and consistency in the dicts we refer to would help much. |
Would it be common or the new common?
They are not. Keeping silent does not means it's fine. |
As far as devanAgarI is concerned, the image in #7 (comment) indicates that there was no "common" notation as far as the dicts were concerned (they were never intended to be used side by side). So, "new common". Btw, I messaged the below to @drdhaval2785 on whatsapp:
For our immediate purposes, it suffices if you leave aside point 4 and agree with points 1-3. Even there, point number 2 is critical (enough to cause one to change the devanAgarI headwords).
Besides, it is a matter of fact that most people are not "accustomed" to looking up svaras like this side-by-side : |
If you're jittery about changing the original, you can keep it, as well as add the headword in standard notation. For example: त꣡र्हि (Pr: त꣫र्हि). (I just needed to look up svara for उचित, and wasted time wondering what that diacritic over ta was supposed to mean. |
@funderburkjim guess it's a strong argument |
Just noticed that in capeller, we get the headword accented as शपथ्य^ - so the jAtya-svarita symbol is not being translated appropriately. Could be shown श॒प॒थ्य᳡ or more simply - शपथ्य᳡ |
Consider the below in the context of #6 (comment) -
It's best to settle on a consistent udAtta notation (꣡) for use in devanAgarI renderings.
The text was updated successfully, but these errors were encountered: