Difference between revisions of "Kazakh and Tatar/TODO"

From Apertium
Jump to navigation Jump to search
Line 23: Line 23:
* <code>көр%<v%>%<tv%>%<imp%>%<p2%>%<sg%>:гөр # ; ! "" Dir/LR</code> get's trimmed
* <code>көр%<v%>%<tv%>%<imp%>%<p2%>%<sg%>:гөр # ; ! "" Dir/LR</code> get's trimmed
* ма не - мыни thing
* ма не - мыни thing
* Handle the sentences from the paper in transfer, not in CG


== Phonology-related stuff ==
== Phonology-related stuff ==

Revision as of 19:06, 1 July 2013

General TODO

See Kazakh and Tatar/Work_plan and Kazakh and Tatar/Remaining unanalysed forms

  • 0 itself and numbers containing it aren't analyzed (in both directions)
    • This is only true for the transducers in apertium-kaz-tat, apertium-kaz and apertium-tat ones work fine.
  • A number with a following . is analyzed incorrectly and therefore not generated:
    • When apertium (not hfst-proc) is used, this is the case for any number at the end of the line, because deformatter puts a "." at the end of the sentence automatically.
/apertium-kaz$ echo "21." | hfst-proc kaz.automorf.hfst 
^21./21.<num>$
  • Make instrumental case to a clitical postposition, leaving only 6 cases which are the same both in Tatar and Kazakh (see [[1]] and the log from 12.03.2013 for reference)
    • update the t1x files accordingly (i.e. get rid of the rules for handling instrumental case)
  • Revise continuations of gerunds
  • жігіт% %{М%}ен
  • Declination of Tatar nouns ending with -и.
  • A separate cont.class for verbs which have causative forms ending with -дыр/-дер
    • Isn't this the default for <v><iv> ?
  • A "location-cases" cont. classes for some of the postpositions and location adverbs (e.g. "бире")
    • What do you mean? —Firespeaker 16:20, 6 February 2013 (UTC)
  • Better disambiguation
  • көр%<v%>%<tv%>%<imp%>%<p2%>%<sg%>:гөр # ; ! "" Dir/LR get's trimmed
  • ма не - мыни thing
  • Handle the sentences from the paper in transfer, not in CG

Phonology-related stuff

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

Kazakh

Currently generated incorrect form(s) Unanalyzed correct form(s) Comments
^жатқандықын/жат<v><iv><ger_perf><px3sp><acc>/жат<vaux><ger_perf><px3sp><acc>$ 200 *жатқандығын 
%<ger_perf%>:%>%{G%}%{A%}н%>%{L%}%{I%}%{K%} GER-INFL ;

/apertium-kaz$ echo "^біз<prn><pers><p1><pl><px><nom>+ма<qst>$" | hfst-proc -g kaz.autogen.hfst
біздікін бе

/apertium-kaz$ echo "біздікі бе" | hfst-proc kaz.automorf.hfst
^біздікі/біз<prn><pers><p1><pl><px><nom>/біз<prn><pers><p1><pl><px><nom>+е<cop><p3><pl>/біз<prn><pers><p1><pl><px><nom>+е<cop><p3><sg>$ ^бе/ма<qst>$

/apertium-kaz$ echo "біздікін бе?" | hfst-proc kaz.automorf.hfst
^біздікін бе/біз<prn><pers><p1><pl><px><nom>+е<cop><p3><pl>+ма<qst>/біз<prn><pers><p1><pl><px><nom>+е<cop><p3><sg>+ма<qst>/біз<prn><pers><p1><pl><px><nom>+ма<qst>$^?/?<sent>$

/apertium-kaz$ echo "біздікін" | hfst-proc kaz.automorf.hfst
^біздікін/біз<prn><pers><p1><pl><px><acc>$

/apertium-kaz$ echo "^біз<prn><pers><p1><pl><px><acc>+ма<qst>$" | hfst-proc -g kaz.autogen.hfst
біздікіні ме

Has something to do with %{n%} archiphoneme realisation before clitics

done (but keep an eye on)

  • Current: ^миллион<num><subst><dat>$ --> миллионге Should be: ^миллион<num><subst><dat>$ --> миллионға
  • Current: ^сөйле<v><tv><coop><ger_past><loc>$ --> сөйлесгенде Should be: ^сөйле<v><tv><coop><ger_past><loc>$ --> сөйлескенде
  • Kazakh: ^ойна<v><tv><ifi><p1><pl>$ --> ойнадык Should be: ойнадыҚ
  • *журналистерді - *журналистеріне - *журналистерді
    • something like т:0 <=> :с/:0 _ %{L%}:/:0 (r40597)
  • (kaz) *Назарбаевтың (r40594)
  • АКШ-*тың НАТО-*ның
This is a problem with lexc, not twol —Firespeaker 06:15, 20 August 2012 (UTC)
  • words with "[back vowel]...и[(cons)]" (i.e., borrowings) dealt with via %{☭%}
    • (kaz) *организмдер / организм<n><pl><nom> = организмдар (r40597)
    • Currently: ^Исраил<np><ant><m><gen>/Исраилдың$ and ^Исраил<np><ant><m><dat>/Исраилға$ Correct forms are Исраилдің and Исраилге respectively
    • Currently: ^Иерусалим<np><top><dat>/Иерусалимға$, Иерусалимдағы and Иерусалимның. Correct forms are Иерусалимге, Иерусалимдегі and Иерусалимнең respectively. In short, make them take front vowel affixes!
  • (kaz) процесс, процесі/процессі, процесінің/процессінің
  • (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)
  • ^организмге/*организмге$ *организмнің *организмнен (r40705)
  • *тарихынан *тарихы ... (≤r40705)
Currently generated incorrect form(s) Unanalyzed correct form(s) Comments
^қаубы/қауіп<n><px3sp><nom> 294 *қаупі 
қауіп:қау%{y%}п N1 ; ! "danger"
қауіп:қауіп N1 ; ! "danger" Dir/LR
.gc қаупі=10,500 .gc қауіпі=1,560 .gc қаупы=27 .gc қауыпы=10 .gc қәуіп=11
^құғы/құқ<n><px3sp><nom>$ 284 *құқы Final consonant remains voiceles in intervocalic position.
^жойу/жой<v><tv><ger><nom>$ 215 *жою
и phonology
^жиіліп/жи<v><tv><pass><gna_perf>/жи<v><tv><pass><prc_perf>$ 35 *жиылып Added in lexc as жи:жи V-TV ; ! "". Tried to change it to жи:жи%{й%} V-TV ; ! "" — makes жиып work, but doesn't affect the gerund form. Not quite the right thing.
жиіп/жи<v><tv><gna_perf>/жи<v><tv><prc_perf>$ 58 *жиып
^жиу/жи<v><tv><ger><nom>$ жию

—r42636 and previous

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 >> йөрә торган
  6. ^хокукын/*хокукын$ <-- ^хокукын<n><px3sp><acc>$ See ^құқын/*құқын$ issue above.
Currently generated incorrect form(s) Unanalyzed correct form(s) Comments
^безнекенеме/без<prn><pers><p1><pl><px><acc>+мы<qst>$ ^безнекенме/*безнекенме$ See "біздікі" above

Other

International vocabulary

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

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

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

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

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

Proper nouns


*Гонконгтан

Other

  • Some nouns in Tatar (and Kazakh) lexc seem to be in NLEX and NLEX-RUS. This is fine for analysis, but which form is generated? There should be some ! Dir/.. filtering somewhere in there.

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

Retrieved from "https://wiki.apertium.org/w/index.php?title=Kazakh_and_Tatar/TODO&oldid=42457"