-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
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
stem model f_A and declension #8
Comments
endings for f_A modelThe endings used for the f_A declension algorithm are:
|
Base for f_A modelWe assume that the stem (last pada of key2) already ends in 'A'. For example, the base for 'latA' is lat. |
f_A declension algorithmThe declension algorithm for feminine nouns ending in 'A' is procedurally the same as that for masculine Here is a summary of the procedure.
|
example rAmANote that nR sandhi applies for Genitive Plural
|
checks
These declensions are in decline_check, along with other declension checks. |
feminine nouns ending in 'A'
This list is derived from lexnorm-all2 by the simple filter:
a) key1 ends in long vowel 'A'
b) lexnorm is precisely 'f' or 'f#A'
Note: there are only a handful of cases with lexnorm 'f#A'. For a noun ending in A, this specification
of lexnorm is merely an alternate of 'f' .
As in #4, this excludes many adjectives and other nominals ending in 'a', namely those with more complex normalized lexnorm values, such as 'm:f:n'. As we will see when considering 'm:f:n' for
a citation Xa ending in 'a', the feminine stem is implied to be XA.
There are 17265 cases, listed in file nominals/inputs/f_a1.txt.
Note: The reason the file is named 'f_a1.txt' rather than 'f_A.txt' has to do with the fact that, in Windows
OS, filenames are case-insensitive -- i.e. f_a.txt is same as f_A.txt. To avoid problems arising from this
peculiarity, this system is using the convention of replacing an uppercase letter 'X' in a filename with
'x1', where 'x' is the lower-case form of 'X'. ---- It's annoying but necessary to introduce such
awkwardnesses when using Windows OS.
The text was updated successfully, but these errors were encountered: