deriv SD cv ashtadhyayi.com hei.de LSK ETT STT a 6.1.84 ALPH OLDHOMEPAGE NEWHOMEPAGE

ekaH pUrva-parayoH

एकः पूर्वॱपरयोः ONPANINI 61084

(The following rules replace) both previous and following with the same one.

NDEVANAGARI

This is an /adhikAra, valid from here 61086 Satvatukor... >> down to 61111 Rta::ut. These rules are called the /ekAdeza rules (replace-two-with-one rules).

Those rules do a special kind of replacing called a merge (or /ekAdeza substitution).

Example. When we join azva- अश्वॱ and ina इन, rule AdguNaH >>> appears to tell us "replace after a before i with e ", which is sort of nonsensical. But ekaHpUrva एकःपूर्व explains what AdguNaH >>> means:

  1. We have to replace azva अश्व with e getting azve अश्वे
  2. We replace ina इन with e getting ena एन
  3. Both e are ONE AND THE SAME e , so we get azvena अश्वेन, not azveena.

**azva- अश्वॱ + ina इन
→ **azvena अश्वेन

So, rule AdguNaH >>> does NOT replace a::i अ‌इ with e . It replaces a with e , and it replaces i with the same e .

Why would that be relevant? We'd get **azvena अश्वेन either way.

Two reasons.

First, for brevity. If this ekaHpUrva एकःपूर्व rule did not exist, rule AdguNaH >>> would have to be replaced with some other rule meaning "replace a with e before i and delete the i ", and that rule would be longer. To save space, /pANini gathered in this section of the grammar many rules that replace two things with one. See pANini's razor.

Second, to trigger other rules. When AdguNaH >>> applies to mahA- महाॱ + RSi- ऋषिॱ, it replaces A with a and it replaces R with the same a . The replacing of R with a triggers uraNraparaH automatically and we get **maharSi- महर्षिॱ. If rule AdguNaH >>> were instead replacing a::R अ‌ऋ with a , there would be no uraNraparaH, because uraNraparaH triggers when you replace a vowel, not when you replace two.

dhAtos tan-nimittasy... <<<< 61084 ekaH pUrva-parayoH > antAdivacca