→ discarded lessons AND / OR random writings and summaries
verb building machine
analyzing
building
how to build
how to build
how to build
analyzing
building
analyzing
building
analyzing
building
analyzing
building
analyzing
building
analyzing
building
analyzing
building
analyzing
building
analyzing
building
analyzing
building
analyzing
building
analyzing
how to analyze with hyderabad tools
building
analyzing
building
analyzing
building
building
analyzing
building
analyzing
building
Many of the
(1) choose a root and a tense, add the tense after the root
(2) replace the tense with one of the eighteen tiG affixes
(3) let the magic
Examples --
ad + laT →
nI + laT →
dviS + laG →
kR + liT →
bhU + liG → bhava +
In the first example,
In the second example
In the third example,
In the last example, bhU + jhi, some rules changed bhU into bhava, other rules changed jhi into
In theory, a person that has mastered the grammar and knows all rules can see a verb like
Until we get to that level, we have to cheat. While you're learning, if you have a good teacher, you can ask how to assemble or disassemble a verb. Without a teacher, we can use inria or hyderabad to disassemble and assemble.
In the following pages, I show some examples of how to use inria to disassemble a verb. This machine, most of the time, shows us the root, tense and tiG from which the verb was made, but does not show which grammar rules were used to make it. So I'll show those rules myself in the pages below.
Typing
pr means that the tense affix laT was added after the root
ac means that this laT was replaced with a flat affix
sg 1 means singular first person. Therefore the flat affix was mip.
The "[2]" thing means that rule [2] in page verb classes worked here, therefore none of the affixes in that page was added to the root.
Therefore inria is telling us that
(howtobuildadmiusingthe) (howbuilru)
One way of building a verb that means "I am eating" is using the
(1) choose a root that carries the meaning of "eating", like ad (there are many others, like
(2) add to it the tense laT, which, according to rule vartamAne laT, may be used to express that the action of eating is happening now.
(3) apply rule lasya and replace the laT with the affix mip, which, according to several rules, may be used to express that the doer of the action of eating is singular and first person. In less words, that the doer is "I". We know that mip is first person because rule tiGas trINi trINi says so, and we know that it is singular because of rule tAnyeka.
So far we have --
Now, mip is hard and expresses the doer of the action of the root, as it says who is eating. So we might think that kartarizap should work. However, it doesn't, because of the exception adi-prabhRtibhyaH zapaH, which says that after some roots, such as ad, rule kartarizap does not work and the root gets no affix.
As it happens, no other rules can apply at this point. So we are already done, and all that we have to do to get our verb is removing the label letter
ad + laT →
(as rule lasya works every single time we build a verb, I will write this, for short --
this " ad + laT mip" means that we add laT after ad and then replace the laT with mip. It does NOT mean that we first add laT and then we add mip.)
Now, if you try to build a verb in this way you will fail horribly, because to do this, you need to know all the rules. Otherwise, you don't know even WHEN to stop. We apply changes as long as some rule says we must, and we are done only when no more rules apply.
So even though using
(howtobuildadmiusinginr) (howbuila)
...
Beginners are strongly encouraged to learn to use the inria conjugation gadget to build their verbs.
Go to inria reader, and, at the bottom of the page, you will find a link called "grammar". Click it and go to the "conjugation" gadget, that is the verb maker.
Now we want the forms of the root ad that means "eat". Look up that root in a dictionary and the dictionary will tell you it is a class 2 root (see verb classes ). In the conjugation gadget, type
The top tables of that page, where it says "present", shows the laT forms.
The top left table of that page, where it says "active", shows the flat forms, that is, those for,ms made by replacing the laT affix with affixes tip tas jhi etc. These forms are shown as--
and carry the affixes --
respectively. Notice that the first person affixes are in the first line, second person in the second, third person in the third. So, as we want to say "I eat", we need the first person singular, and we'll find it in the first line. The verbs in all lines are singular dual plural, so the singular is the one in the left,
(howtobuildadmiusinghyd) (howbuilra)
The hyderabad tools are more accurate than the inria tools, but quite more inconvenient for the average European or American student. The problem is that as they have been made in an Indian university, they take for granted that you can read devanAgarI fluently. That is a very reasonably assumption to make if your students are all in India.
But MY students are mostly outside India and are the kind of lazy folks that won't learn devanAgarI until the last possible moment, so I tell them to compensate for their illiteracy by using a transliterator gadget, such as this one.
So how do we get
Go to the hyderabad tools page and choose "verb forms generator" from the menu. In the gadget, choose your alphabet, your root, and
The verb tables in hyderabad are written in the Indian order: third person affixes go at the top, second person in the middle and first person are last. So here for "I eat" you need the form that is at the bottom left of the laT table.
Writing
This means that the tense affix added was the present (a.k.a. laT) and it was replaced with the plural third person flat affix (a.k.a. jhi). So
and it is clear that some rule or rules changed jhi into
Most of the verbs that end in
The true answer to that question is quite long. But for now we can say that the list has jhi because some of the third person plural verbs end in
The rules that build
Rule jhontaH (literally, "
This rule will work on nearly all jhi, excepting only the ones that come after zlu and the ones that come after one the seven jakSi roots. In those cases, jhontaH does not work, because its exception adabhyastAt turns jhi into
Inria says --
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
This kartarizap rule says that we must add the affix
Therefore --
car + laT tip →
So, no special rules worked.
To make a verb that means "he is moving" --
take a root that means some kind of movement, such as car
add the present affix laT
replace laT with tip which is the singular third person flat affix
Now tip is a hard affix that means the doer, therefore rule kartarizap must work --
Now no further rules apply, so we just remove the labels and we are done --
(analyzingcaranti) (analyziran)
the "ac pl 3" (plural third person) means that we added jhi.
the [1] means that kartarizap worked, so
Apparently,
(buildingcaranti) (buildinran)
Now, the special rules. Rule jhontaH says that jhi must be replaced with anti''' most of the time (to be precise, jhi becomes
Now another special rule works: atoguNe. It says that when we have two
Summarizing --
Writing
The [1] there means that the rule [1] of the table verb classes worked and added the affix zap after the root. The root nI means to carry or lead, so, so far, we can say that
nI + laT tip →
as in
or
It's clear that some rule or rules turned
The rules that build
nI + laT tip →
Rule kartarizap teaches: "whenever a root is right in front of a hard affix that means the doer, add the affix
In this example, kartarizap works because
(1) tip is hard, because rule tiGzit says so.
(2) tip means the doer, because it expresses that the doer is third person and singular (he or she does the leading, not you or me)
(3) None of the dozen plus exception rules that stop kartarizap from working applies in this example. We'll worry about those rules later. For now, just remember that the class one roots (
Here you have some more examples of the root nI getting zap --
nI + laT sip →
nI + laG sip →
nI + loT sip →
nI + liG sip →
Now, in all these examples, nI plus zap turned into
Let's go back to explaining
nI + laT tip →
Now, rule hardsoft teaches, among other things,
"
In our example, zap is a root affix because it is hard, and it is hard because it has
nI + laT tip →
At this point rule ecoyavAyAvaH must work. This is not a verb building rule, but a letter rule that affects all of the
nI + laT tip →
so it looks like some rules changed
The rules that build
The jhi ending is almost always affected by jhontaH and turned into
Here atoguNe is not a verb construction rule, but a sandhi rule (a general rule about letter changes). Ordinarily, two
(analyzingdveSmi) (analyziveSm)
Inria shows --
which means
The [2] means that rule adipra worked, so no affix (such as zap) was added after dviS.
As we were expecting
(buildingdveSmi) (buildinveSm)
The rule that changed
"replace the nexttolast
Here no exception prevents puganta from working, so we say --
(analyzingdviSanti) (analyziS)
Inria shows --
which means
there was no change of
This time, puganta did not work. Why? Because of the exception kGitica, which teaches, among other things --
" puganta will not work before affixes that have
and it happens that jhi is such an affix.
In fact, jhi is just an abbreviation of
So, how do we know that jhi has
Because rule hard
The smart student will have now figured out that when we have laT after dviS, the dviS will only become
(1) puganta does not work before affixes with
(2) a hard that has no
Therefore, when a hard affix carries BOTH
(analyzingadveSam) (analyziveSa)
inria reader paints
Here the root is dviS, impft means that laG was added, [2] means that rule adipra worked, and " ac sg 1" is the mip affix,
So, Inria tells us that --
which means "I hated".
Here dviS plus
(buildingadveSam) (buildinveSa)
dviS + laG mip →
Incidentally, rule adipra worked and told us that rule kartarizap must not work after ad, dviS and other roots. This is why we did not add zap after the root like we did earlier in
The
"whenever the tense is laG luG or lRG, and the root starts with a consonant, add
(This rule applies to luG laG lRG only.)
Therefore, as
Now. When mip has replaced a Git tense, such as laG or liG or luG, rule tasthas always replaces the affix mip with the affix am'''.
Because of rule sthAnivad, this
(analyzingcakratus) (analyzirat)
Type
According to inria,
ac du 3 means the affix tas, so the verb was built this way --
kR + liT tas
Here kR became cakR before a liT affix, tas, and the liT affix tas turned into atus, and the two pieces
Notice that inria did not show a verb class, even though kR belongs to class [8]. That's because the rules mentioned in verb classes never add any affix to the root that is before a liT. Those rules only work before hard affixes, and the affix ( tip, tas, jhi...) that replaces liT is never hard, because rule liTca says so. So the liT verbs are always made the same way no matter the class of the root, and inria does not show the class number because doing that would not help you.
(buildingcakratus) (buildinrat)
There are many rules involved into making
kR + liT tas →
The first rule parasmaipadAnANNa replaces tip tas jhi... with Nal atus us... respectively. Here it replaced tas with atus.
The second rule liTidhA says that we must reduplicate most roots when they are before liT. The process of reduplication is quite complicated and it is described in ekAcodve and the rules that follow. In this case it is done in three steps:
ekAcodve turns
urat and another rule turn the first
kuhozcuH replaces that
So far we got --
and now rule ikoyaNaci turns
According to inria,
as " ac sg 3" means tip, here we had
This is the same thing as !"cakratus above, only that we added tip ( singular third person) instead of tas ( dual third person). Here kR turned into
There are many rules involved into making
kR + liT tip →
Here rule parasmaipadAnANNa replaces tip with Nal.
As Nal has
Next, rule liTidhA reduplicates the root
first ekAcodve turns
then hrasvaH turns the first
finally kuhozcuH replaces that
Then we add
The
(analyzingbhaveyus) (analyzivey)
Typing
An opt in inria means that the tense affix added was liG AND that rule liGAziSi was not applied, so the tiG that replaces the liG is hard. The [1] means that
The student will remember that
(buildingbhaveyus) (buildinvey)
When we must join a root and a liG replacer affix, like here --
there are between fifteen or twenty rules that must work, I lost count. So I will mention here only a few of them.
First, rules kartarizap, hardsoft and ecoya turn
Then rule jherjus works --
Now, usually, when a flat affix replaces liG, rule yAsuTp should work and add yAs in front of that affix. However, when the affix is right after an
Now the first
and the
Putting everything together --
inria reader paints
Here ac sg 3 means tip, whic is flat and shows that the doer is third person singular.
and means "he moved" (any kind of movement, such as walking, galloping, swimming, jumping or slithering).
As we were expecting that car + a + ti would make
See also how to analyze with hyderabad tools
(howtoanalyzewithhydera) (howan)
... half written
how to analyze
hyderabad tools do the same job inria does, but it is more inconvenient, particularly for the student that cannot read devanAgarI yet. The advantage is that it is more accurate -- it gets right some forms that inria gets wrong. So, I only use it when I suspect that inria is failing.
Go to hyderabat toolkit, and in the tools menu , select the morphological analyser. Set input ENcoding to KH, type
Here
car is the root
so
So this "
To form
To form
Rule itazca tells us that when tip, jhi, sip have replaced a Git tense, they lose their
(analyzingplavate) (analyziav)
In all the examples we have seen so far, the verb had one of the first nine affixes in list tiptas, and inria said ac to tell us had one of those affixes. When the verb has any of the other nine affixes, inria says either mo or ps. It says ps if yak was added after the root, mo otherwise.
To see an example, type
Here the root is plu, the tense is pr ( laT), and sg 3 means third person singular, like earlier. But here we have mo, not ac. mo and ps mean that one of the bent tiG affixes was added. Of those nine, only the affix ta is third person singular. As we do not have ps here, we know that yak was not added after the root, and as we have [1], we know that zap was added. So inria is saying that --
So, somehow
Writing
(A) the affix is bent (here it is ta)
(B) the affix does not mean the doer
(C) there is yak after the root
Now, as dRz is an objectful root, the affix ta must mean the object, and therefore the object of the root is third person and singular, so our
dRz + laT →
Notice that dRz is a zapclass root, but inria did not say [1]. That is because zap was not added. yak was added instead. And yak is added to all roots the same way, no matter their verb class.
To see why yak was added, see building
When we want to make a verb that means that one thing is being seen now, we do this --
Here we must use either ta or tip to mean that the object of the root (the thing that is seen) is third person and singular, and only ta and tip are third person and singular. Here, we must use ta because rule bhAvakarmaNoH says that when the affix does not mean the doer it must be bent. So ta is now an affix that means the object.
Being hard affix that does not mean the doer, this ta makes makes rule sArvadhAtukeyak work
and as ta is a bent affix that replace a
Putting everything together --
dRz + laT ta →
This verb can also be translated as "it is seen", but i added the "being" word because in English "it is seen" may mean either present time or past time, while in Sanskrit you use laT for present time and kta or laG or liT or luG for past time --
dRz + kta →
dRz + laG ta →
dRz + luG ta →
example sentences --
According to rule laHkarmaNi, we can add ta after
The rules that build
plu + laT ta →
Inria says --
The
As we know, ac sg 3 mans that this verb has tip, and pr means that laT was replaced with tip. The [3] means that this verb got the zlu affix by the rule [3] of page verb classes . Therefore the verb bibheti was formed this way --
So for some reason, when we added together
We want to join --
When we add the affix zlu after
Rule zlau says that
Rule pratyayasyaluk;zlu;lupaH says that we must erase the zlu --
Rule hrasvaH says that the first
Rule abhyAsecarca says that we must replace the first
Then rule hardsoft replaces
(analyzingbibhyati) (analyzih)
Inria says --
so this is almost like bibheti, only that it is " pl 3" instead of " sg 3". Therefore it means "they are afraid", and got jhi instead of tip.
So it looks like
We want to join --
Adding together
So far, all the examples we saw of laT jhi turned jhi into anti''' by rule jhontaH. But this rule has an exception -- adabhyastAt, which says that after a stammered, such as bibhI,
Here