Send sanskrit mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://mailman.cs.utah.edu/mailman/listinfo/sanskrit
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of sanskrit digest..."
Today's Topics:
1. Re: sa chchhAdakaH (Jay Vaidya)
2. sandhi after sandhi (Jay Vaidya)
----------------------------------------------------------------------
Message: 1
Date: Tue, 1 Feb 2005 17:03:30 -0800 (PST)
From: Jay Vaidya <[EMAIL PROTECTED]>
Subject: Re: [Sanskrit] sa chchhAdakaH
To: Ambujam Raman <[EMAIL PROTECTED]>, [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
--- Ambujam Raman <[EMAIL PROTECTED]> wrote:
> Jay:
> "etat-tadoH sulopo-.akor-anaJN-samAse hali |
> 6.1.132"
>
> By the above rule it willbe:
> asashchhAdakaH
> (It is not he who is concealed)
>
> Am I right?
>
> rAmaH
>
I am going by Toke's original pre-sandhi words as
"saH chhAdakaH"
The quoted sUtra causes the "su" -> "H" = visarga
termination of 'etad' or 'tad' to be dropped (su-lopa)
if followed by a consonant (hali), except for the
forms containing 'k' (namely, 'eshhakaH' and 'sakaH',
an endearment for 'eshhaH' and 'saH'), and excepting
the naJN-samAsa forms (e.g., not-he shiva = someone
other than him who is shiva = asaH shivaH -> asaH
shivaH/asash-shivaH). The sUtra does not CAUSE a naJN
samAsa to occur where none existed before, but tells
you the special exception for it.
= "sa(H dropped) + chhAdakaH"
= "sa chhAdakaH"
Srini's quotation from Coulson that saH/sa are two
alternative forms of conjugation (an not sandhi) is an
imaginative way of putting it, but not the traditional
way.
This 'short vowel' + followed by 'chha' triggers the
inclusion of 't' between the two, which, in torturous
ways comes to be a 'ch'
sa+t+chhAdakaH = sad+d+chhAdakaH = sa+j+chhAdakaH
= sa+ch+chhAdakaH = sa-chchhAdakaH
Such a chain of sequentially applied sandhi rules
makes it important not to go under the blanket
assumption of "no sandhi after sandhi".
If you had a whole new case:
Someone other than him (=not-he) is the concealer
(na+tad, masc sing prathamA) + chhAdakaH
asaH + chhAdakaH
(deletion rule exception)
asashchhAdakaH
as you say above.
dhana.njayaH
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
------------------------------
Message: 2
Date: Wed, 2 Feb 2005 08:35:27 -0800 (PST)
From: Jay Vaidya <[EMAIL PROTECTED]>
Subject: [Sanskrit] sandhi after sandhi
To: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
Here is a more pedestrian example for one sandhi rule
used after another:
(1) Rule 1:
'aH' -> -> 'o' in certain circumstances
e.g. rAmaH + gataH = rAmo gataH (rAma [is] gone)
(2) Rule 2:
'o' + 'a' -> 'o'
e.g., go + ashva = goshva (dual) -> goshvau (an ox and
a horse)
(3) How about "rAmaH + ashvArUDhaH"
First use rule 1: rAmo + ashvArUDhaH
Next use rule 2: rAmoshvArUDhaH (rAma [is] mounted on
a horse)
It may be possible to create a "rule" for every
combination of rules (e.g., 'aH' + 'a' -> 'o', as a
rule by itself), but that would not be an efficient
system.
Again, there are certain (but not all) sandhi rules
that do not allow for re-evaluation by other rules.
dhana.njayaH
__________________________________
Do you Yahoo!?
Yahoo! Mail - Easier than ever with enhanced search. Learn more.
http://info.mail.yahoo.com/mail_250
------------------------------
_______________________________________________
sanskrit mailing list
[email protected]
http://mailman.cs.utah.edu/mailman/listinfo/sanskrit
End of sanskrit Digest, Vol 23, Issue 2
***************************************
