We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
<L>27<pc>1,1<k1>aMSaBUta<k2>aMSa—BUta<e>3 <s>aMSa—BUta</s> ¦ <lex>mfn.</lex> forming part of.<info lex="m:f:n"/> <LEND> <L>27.1<pc>1308,1<k1>aMSarUpiRI<k2>aMSa-rUpiRI<e>3 <s>aMSa-rUpiRI</s> ¦ <lex>f.</lex> (with <s>Sakti</s>) a female personification of the divine energy, <ls>RTL. 187</ls>.<info n="sup"/><info lex="f"/> <LEND> <L>28<pc>1,1<k1>aMSavat<k2>aMSa—vat<e>3 <s>aMSa—vat</s> ¦ (for <s>aMSumat</s>?) <lex>m.</lex> a species of <s1 slp1="soma">Soma</s1> plant, <ls>Suśr.</ls><info lex="m"/> <LEND>
See — in aMSa—BUta and - in aMSa-rUpiRI
—
-
It should be consistent. @funderburkjim, is there any programmatic reason why this may have happenned?
The text was updated successfully, but these errors were encountered:
At some point in the past, I introduced the two types of hyphen in compounds. My current opinion is that either
In the particular case mentioned, aMSa-BUta is from the main text, and aMSa-rUpiRI from the supplement.
I would currently opt for changing the long-hyphen to a normal hyphen.
When interest is sufficient, there could be an attempt to devise a scheme for representing the parsed form of compounds.
Sorry, something went wrong.
In fact, my next issue is about this!!
It is flawed (implementation) in multiple ways and SHOULD be changed to a normal hyphen, when the full forms are 'made' in the digitised text.
I could make up some time today to post the intended issue at sanskrit-lexicon/mw-dev#23 (comment)
funderburkjim
No branches or pull requests
Data
Problem
See
—
in aMSa—BUtaand
-
in aMSa-rUpiRIIt should be consistent.
@funderburkjim, is there any programmatic reason why this may have happenned?
The text was updated successfully, but these errors were encountered: