sandhi tables ←

chunk 79: verb building machine

→ discarded lessons AND / OR random writings and summaries

verb building machine
building adveSam
unbuilding adveSam with inria
building carati
building caranti
building the verb plavate




(verbbuildingmachine) (verbb)

verb building machinemmmmmmmmm glosses glosses ^ C- 1512

A verb is any word that can be built by the following process --

(1) add a tense after a root

(2) replace the tense with one of the eighteen tiptasjhi affixes

(3) let the magic pANini rules do their work and change things

Example 1.

Suppose we wnt to make a verb that means "I am eating", usimg the root ad "eat". Rule vartamAnelaT says we can add laT after all roots to mean that the action of the root is happening, so we join --

ad + laT

Now rule lasya says that we must replace the laT affix which one of the eighteen tiptas affixes. which one of the eighteen? In this case, other rules say that we may use the affix mip, which is singular and first person. So we replace laT with mip --

ad + mip

After this, none of the automatic rules work, so our verb will be

admi "I am eating"

the p disappears because it is a label.

Example 2.

We want a verb meaning "he eats" or "she eats". We do the step (1) as in admi above,

ad + laT

Now, in step (2), instead of using the first person affix mip we use the third person singular affix tip --

ad + tipadti

Now for step (3), we must use rule kharica, which teaches that dt must be always replaced with tt --

adti kharica atti

This verb can be used in sentences like

atti kapiH "monkey is eating"

kapir atti "monkey is eating"

Besides kharica, there are lots and lots of rules that can work on step (3). Fortunately, you are not expected to memorize all rules BEFORE you can make your own verbs. The important part is understanding how the general process works, and after that, you start to get used to the small rules by seeing a lot of examples of each.

In fact building verbs up is not important. The beginner student will usually spend more time unbuilding verbs. For instance, seeing a verb like admi or admas, it is important that you learn to recognize that these have the affixes mip and mas, and therefore mean "I eat" and "we eat".

The following lessons illustrate some of the more common rules used when building verbs.

building adveSam

1514 letters. -- 28200verbbuildingmachine.bse 3 -- popularity 2

3 next pages for chris

1467 word building overview




(buildingadveSam) (buildinv)

building adveSammmmmmmmmm glosses glosses ^ C- 1513

adveSam means "I hated". this verb is built from the root dviS "hate", with laG added. Rule anadyatanelaG tells us when we can add the laG affix. Then, some other rules say that when laG is after dviS, the laG can be replaced with either mip or iT'. Let's use mip this time.

dviS + laGdviS + mip

After we havedecided that we use mip, not iT', a lot of rules work automatically --

dviS became dveS because of rule puganta

dveS + mi

dveS gets a in front because of rule luGlaG

adveS + mi

mip turns into am''' because of rule tasthas

adveSam "I hated"

Summarizing --

dviS + laG mip puganta dveS + mi luGlaG adveS + mi tasthas adveSam "I hated"

If instead of using mip we use iT', rule puganta does not work, by a complicated reason I'll explain later, and rule tasthas cannot work because there is no mip, so we get --

dviS + laG iT'dviS + i luGlaG adviSi "I hated"

adveSam and adviSi means exactly the same thing. We can only choose between two affixes this way after a few special roots such as dviS, krI, kR and rudh. Of course there are rules that teach which roots are these.

Now. You can see that if you knew all the rules, you might be able to turn dviS + laG into adveSam by following the rules. But if you do not know the rules, guessing that adveSam comes from dviS + mip is very hard. For that you need to know that mip sometimes turns into am and dviS sometimes turns into dveS. But do not panic. Using the inria reader gadget, you can easily find out that adveSam comes from dviS + mip

unbuilding adveSam with inria

*unbuilding adveSam with hyderabad

1178 letters. -- 28200verbbuildingmachine.bse 30 -- popularity 1

1512 verb building machine




(unbuildingadveSamwithi) (un)

unbuilding adveSam with inriammmmmmmmm glosses glosses ^ C- 1514

Go to inria reader, set it to HK, and lookup adveSam. It will paint adveSam isn a red color. The red color means that adveSam might be a verb. Clicking the red word, inria tells you this --

adveSam = dviS_1 impft [2] ac sg 1

Translated, this means that adveSam comes from the root dviS, that first got he tense laG added to it, and then the laG turned into mip. So the word was built this way --

dviS + laGdviS + mip → .. → adveSam

inria just tells us that we started at dviS + laG mip and then we ended up at adveSam, but it does not tell us what rules did the other changes. Yet knowing where we started can help us imagine that that some rules turned mi into am, dviS into dveS, and added a in front of the root.

Inria also said [2]. This means that dviS is a second class root, and that therefore the second rule in the page verb classes worked here. That rule says that after certain roots, such as ad, we do not add anything right after the root.

Lets look nmow at an example of a verb where something was added after the root.

building carati

796 letters. -- 28200verbbuildingmachine.bse 50 -- popularity 1

1513 building !adveSam




(buildingcarati) (buildinar)

building caratimmmmmmmmm glosses glosses ^ C- 1515

When we write carati into inria, it says --

car pr. [1] ac. sg. 3

So the root is car. The pr means that we added laT after the root, and the "ac. sg. 3" means that we replaced laT with tip.

Here the [1] means that car is an class one root, and that rule kartarizap worked (thats rule number [1] in page verb classes ). This kartarizap rule says that we must add the affix (z)a(p) right after the root whenever the root is in front of ac or a mo. Here tip is an ac, so we add zap.

So the steps used to build carati are these --

car + laT

car + tip

car + zap + tip

carati "he moves"

here no special rules worked.

436 letters. -- 28200verbbuildingmachine.bse 60 -- popularity 1

1514 unbuilding !adveSam with @inria




(buildingcaranti) (buildinr)

building carantimmmmmmmmm glosses glosses ^ C- 1516

caranti means they move, and this word is made by adding the plural affix jhi. Inria says --

car pr. [1] ac pl 3

the "ac pl 3" (plural third person) means that we added jhi.

car + laT

car + jhi

the [1] means that kartarizap worked

car + zap + jhicara + jhi

Now, the special rules. Rule jhontaH says that jhi must be replaced with anti''' most of the time (to be precise, jhi becomes anti after anything that is not a stammered, and cara is not a stammered). So we get --

car + zap + anti

Now another special rule works: atoguNe. It says that when we have two a touching inside a word, we erase the first one. So our verb is --

car + a + anticaranti "they move"

Summarizing --

car + laT jhi kartarizap car + zap + jhi jhontaH car + zap + anti''' atoguNe caranti "they move "

538 letters. -- 28200verbbuildingmachine.bse 80 -- popularity none




(buildingtheverbplavate) (buildinav)

building the verb plavatemmmmmmmmm glosses glosses ^ C- 1517

In all the examples we have seen so far, except adviSi, we used one of the first nine affixes in list tiptas. When do we use the other nine?

Of course, we use those when some rules tell us that we may or must use them. For instance, the first nine affixes are forbidden after the roots plu and labh. These only use the last nine affixes.

When we type plavate into inria, we get a red, and the hovertext of that red says --

[plu]pr. [1] mo. sg. 3

Here we have something new, mo instead of ac. What does this mean?

When instead of ac inria says either mo or ps, that means that one of the last nine affixes was used. So here we used affix ta (third person singular) instead of the usual tip (third person singular).

If it says mo, then one of the rules in verb classes was used. If it says ps, then yak was used. Here it says [1], so we know that rule kartarizap worked and added zap after plu . So inria says that the verb started like this --

plu + laT taplu + zap + ta

Now the automatic rules of step (3) --

because of rule hardsoft, the letter u turns into o whenever it is before zap or some other affixes --

plo + zap + ta

because of rule ecoya, the o that is not wordfinal becomes av before all vowels, here before a (ignore the z, it is a label) --

Because of hardsoft and ecoya, plu + zap adds up to plava --

plava + ta

And then rule Tita turns ta into te --

plavate "he jumps"

1028 letters. -- 28200verbbuildingmachine.bse 100 -- popularity none
















sandhi tables ←

chunk 79: verb building machine

→ discarded lessons AND / OR random writings and summaries