Difference between revisions of "Kazakh and Tatar/TODO"

From Apertium
Jump to navigation Jump to search
Line 64: Line 64:
# <code>apertium-tat$ echo "^йөр<v><iv><gpr_impf>$" | hfst-proc -g tat.autogen.hfst</code> >> <code>йөрә торган</code>
# <code>apertium-tat$ echo "^йөр<v><iv><gpr_impf>$" | hfst-proc -g tat.autogen.hfst</code> >> <code>йөрә торган</code>


== Other ==
=== International vocabulary ===
=== International vocabulary ===



Revision as of 19:41, 21 January 2013

General TODO

See Kazakh and Tatar/Work_plan.

  1. Declination of Tatar nouns ending with -и.
  2. Set up bidix-with-context.sh script (see apertium-kaz-tat/dev/bidix; seems to be very useful, requires another script from spectie).
  3. Add some of the short wikipedia-article-like texts I have for evaluation into texts (should be ~200 words).
  4. Implement cont. class for compound/multiword nouns which already have possessive ending (<px3sp>), e.g. Қытай Халық Республикасы.
    1. This continuation class should link only to CASE (but consider that some of them can have plural form: ишегаллары).
  5. Add "ярты", "ярым" and "чирек" as numerals, but don't link them to common numerals cont. class.
  6. (Lexical selection rule): сондай-ақ > шулай-ук
  7. Fix roman numerals:
    1. add them to tat.lexc too;
    2. change LEXICON NUM-ROMAN to something like this: %<num%>%<ord%>: # ; .
  8. Add transfer rule(s) to handle instrumental case of all parts-of-speech which are subject to substantivation, not only of nouns (this is one of the things which make testvoc results look bad)
  9. A separate cont.class for verbs which have causative forms ending with -дыр/-дер
  10. A "location-cases" cont. classes for some of the postpositions and location adverbs (e.g. "бире")
  11. 'Natinfl cont. class in tat.lexc
  12. Fix "дыр<mod_ind>" thing (it doesn't pass bidix right now)
  13. Pronouns
    1. check cont. classes (note: if it looks like an overgeneration, and me is not sure about it, overgenerate in both lexc's)
    2. translate pronouns from kaz.lexc, add them to bidix and add equivalents into tat.lexc
    3. ^нигез/ни<prn><itg><px2pl><nom>
  14. Determiners
    1. "unify" cont. classes and tags
    2. add stems
  15. Adjectives
    1. personal clitics after adjectives are not implemented yet
  16. Translating between classes
  17. General stuff
    1. Copula suffixes: have for kazakh -ø = p3.sp, and for tatar -ø = p3.sp and -lAr = p3.pl. When translating kaz->tat there is no problem, when translating tat->kaz, pl->sp.

Phonology-related stuff

Might be twol, might not be, but JNW needs to go through this stuff and figure out the issues.

Kazakh

  1. Current: ^миллион<num><subst><dat>$ --> миллионге Should be: ^миллион<num><subst><dat>$ --> миллионға
  2. Current: ^сөйле<v><tv><coop><ger_past><loc>$ --> сөйлесгенде Should be: ^сөйле<v><tv><coop><ger_past><loc>$ --> сөйлескенде
  3. Kazakh: ^ойна<v><tv><ifi><p1><pl>$ --> ойнадык Should be: ойнадыҚ
  4. *жатқандығын
  5. безнекенеме (accusative case before clitics); безнекенгәме
  6. *журналистерді - *журналистеріне - *журналистерді
    • something like т:0 <=> :с/:0 _ %{L%}:/:0 (r40597)
  7. (kaz) *Назарбаевтың (r40594)
  8. АКШ-*тың НАТО-*ның
This is a problem with lexc, not twol —Firespeaker 06:15, 20 August 2012 (UTC)
  1. (kaz) *организмдер / организм<n><pl><nom> = организмдар (r40597)
  2. (kaz) процесс, процесі/процессі, процесінің/процессінің
  3. (kaz) автомобиль<n><attr>, *автомобильдер // автомобиль<n><pl><nom> = автомобильлер
As far as I can tell, автомобильдер is the most common form. The form автомобилдер also seems to be used, but doesn't look super formal, and автомобильлер seems to only be attested in "Kazakh" because Nissan seems to like to write in Noğay for its Kazakh-speaking audience. —Firespeaker 06:10, 20 August 2012 (UTC)
The thing is that the form we are generating is автомобильлер. - Francis Tyers 07:08, 20 August 2012 (UTC) (r40704)
  1. ^организмге/*организмге$ *организмнің *организмнен (r40705)
  2. *тарихынан *тарихы ... (≤r40705)

Tatar

  1. (tat) generates укыу
  2. (tat) generates айендә
  3. Deletion of soft sign "ь" before vowels in Tatar (see comments at the end of the apertium-tat/apertium-tat.tat.twol file)
  4. (tat) *аенда, generating музейе instead of correct музее
  5. apertium-tat$ echo "^йөр<v><iv><gpr_impf>$" | hfst-proc -g tat.autogen.hfst >> йөрә торган

Other

International vocabulary

*терроризмге  *массивіндегі  *террорлық *Факті  
*кодекстің *терроризмге  *Полицейлер *журналистерді  «*АНТИТЕРРОРЛЫҚ » 
*полицейлер  *антитеррорлық   *режим   *полицейлер   *журналистерді   
*автоматты  *автобустар   *полицейлер   *журналистеріне  *сайттың   

*технологиялар *компьютер  *мобильді *техникаларға *интернет *объектілерін 
*радиациялық   *сантехник *проблемасы *веб-*сайттар *позитивті *алгебра

*коалициялық 

*иммиграциялық *дипломатиялық *стратегиялық 

*станциясында 

Proper nouns


*Гонконгтан

Discuss first

  1. There is only one formal form (<frm>) in Tatar, which can be both sg and plural. But in Kazakh there are two forms. Should I pretend as if in Tatar it *were* the same and duplicate the same form with a different tag or should I handle it in transfer?
  2. Consider турындагы - should it still be tagged as postposition?
  3. How to handle verbs with inner inflection (sometimes a Kazakh verb is translated with a multiword and vice versa. E.g. әуреле > башын әйләндер)

Part-of-speech related TODO's and DONE's can be found here:

To run tests, use aq-regtest utility from Apertium-quality tools. E.g.

aq-regtest -d . kaz-tat http://wiki.apertium.org/wiki/Special:Export/Kazakh_and_Tatar/Postadvebs

Done

But keep an eye on this
  • Numerals
    • kaz <num><subst>(<px3>) in fractions[1] = tat <num><subst>(<px3>)
    • kaz <num><coll><advl> = tat <num><coll>
    • kaz <num><coll><subst> = tat <num><subst>

Notes

  1. Currently whether it is in fractions or not is not taken into account

See also