Apertium has moved from SourceForge to GitHub.
If you have any questions, please come and talk to us on #apertium on irc.freenode.net or contact the GitHub migration team.

Narimann/GSOC 2019 proposal: Kazakh-Turkish and Turkish-Kazakh

From Apertium
(Difference between revisions)
Jump to: navigation, search
(Title)
(Why Google and Apertium should sponsor it? How and who it will benefit in society?)
Line 84: Line 84:
   
 
Turkish-Kazakh & Tatar-Kazakh pairs work stably, but only in one direction. So making them work in both direction will make these pairs more valuable and will lead to further development of Turkic languages in machine translation. In addition, it will help people to communicate with each other or at least translate the texts needed.
 
Turkish-Kazakh & Tatar-Kazakh pairs work stably, but only in one direction. So making them work in both direction will make these pairs more valuable and will lead to further development of Turkic languages in machine translation. In addition, it will help people to communicate with each other or at least translate the texts needed.
  +
  +
{{comment|"Turkish-Kazakh & Tatar-Kazakh pairs work stably," — usually "Turkish-Kazakh" means "Turkish-to-Kazakh", whereas "Kazakh-Turkish" means "Kazakh-to-Turkish". Because of this, what you wrote above is a little unclear. Also, one major use of these pairs will be not just to try to make sense of text in the other language, but to translate material from one of them to another which needs little post-editing/cleaning to be a useful text. —[[User:Firespeaker|Firespeaker]] ([[User talk:Firespeaker|talk]]) 23:47, 4 April 2019 (CEST)}}
   
 
===Work Plan===
 
===Work Plan===

Revision as of 23:47, 4 April 2019

Contents

Contact Information

Name: Daniyar Nariman

Location: Kazan, Tatarstan

E-mail: n.daniyar@innopolis.ru, nariman9119@gmail.com

IRC: nariman

Github: https://github.com/nariman9119

Gitlab: https://gitlab.com/users/nariman9119

Telegram: nariman9119

Timezone: GMT+3, GMT+6

Skills

I am a third-year undergraduate student at Innopolis University(Tatarstan, Russia).

Major: Computer Science

Track: Data Science

Programming Skills: Python, Java, C, C++, XML

Languages

Kazakh - upper-intermediate

Russian - fluent

English - upper-intermediate(IELTS 6.0 - 2015)

Turkish - intermediate(5 years of studying in Kazakh-Turkish school)


NLP Related Projects

Word Sense Disambiguation for WordNet corpora

LSTM for Text classification

Russian-Tatar text classification

Tweet analysis on different preprocessing approaches

Keyboard layout and associated misspellings analysis

Dynamic Language Interpreter implementation



My current field of study is more related to Natural Language Processing. For the last 3 months, I worked on a company by developing an AutoLabeller system, which can process the text and collect only the information needed.

Since I will graduate from University next year, I am planning to take the topic related to machine translation for my diploma, and this internship will help me a lot for deeper and more detailed study of how RBMT works.

Why is it that you are interested in Apertium?

I am studying Computer Science at my university, Data Science track. I am very interested in machine translation and other stuff related to the NLP.

I am interested in Apertium because it pays attention not only to common languages which have a lot of speakers around the world but also to these minority of languages which are not so popular and sometimes do not even have enough data to build a valuable translator.

Nowadays statistical machine translation(SMT) is very popular around the globe comparing with rule-based machine translation(RBMT). But the problem is that SMT requires a lot of data in the form of parallel languages corpora, since they very addicted to data, and many languages cannot afford it. While RBMT does not require so much data but requires a lot of effort to put in. From this point, we can conclude that Apertium is a good approach for machine translation purposes of small languages. Another point is that with a good and full implementation of a specific pair Apertium can reach accuracy comparable to big giants in this field such as Google or Yandex.

Which of the published tasks are you interested in? What do you plan to do?

Turkish to Kazakh and Tatar to Kazakh MT.

As we discussed in the Apertium-stuff mailing list, I will make these two pairs work stably in that direction, given my linguistic knowledge. Choosing from the given tasks, this task is more related to 1.2 and 1.4.

Proposal

Title

Turkish-Kazakh(Tatar-Kazakh) MT

How about "Turkish and Tatar to Kazakh MT" or "tur-kaz & tat-kaz" (what the mentors will probably call it)? —Firespeaker (talk) 23:44, 4 April 2019 (CEST)

Why Google and Apertium should sponsor it? How and who it will benefit in society?

There are a lot of people who speak these languages: Kazakh(around 11 million), Turkish(75 million), Tatar(5 million).

Turkish-Kazakh & Tatar-Kazakh pairs work stably, but only in one direction. So making them work in both direction will make these pairs more valuable and will lead to further development of Turkic languages in machine translation. In addition, it will help people to communicate with each other or at least translate the texts needed.

"Turkish-Kazakh & Tatar-Kazakh pairs work stably," — usually "Turkish-Kazakh" means "Turkish-to-Kazakh", whereas "Kazakh-Turkish" means "Kazakh-to-Turkish". Because of this, what you wrote above is a little unclear. Also, one major use of these pairs will be not just to try to make sense of text in the other language, but to translate material from one of them to another which needs little post-editing/cleaning to be a useful text. —Firespeaker (talk) 23:47, 4 April 2019 (CEST)

Work Plan

Turkish-Kazakh & Tatar-Kazakh

  • Add at least 1000 bidix stems each week
  • Write new transfer rules
  • Write constraint-based lexical selection
Week Dates Goals Bidix WER / PER Coverage
Post-application period 9 April - 27 May
  • Identification of morphological and syntax differences
  • Begin fixing broken bidix entries
kaz-tur: ~8000, kaz-tat: ~10000
1 27 May - 3 June
  • Expand bilingual dictionary(nouns)
  • Write transfer rules (Turkish > Kazakh)
  • Write lexical selection rules (Turkish > Kazakh)
2 4 June - 11 June
  • Expand bilingual dictionary(verbs)
  • Write transfer rules (Turkish > Kazakh)
  • Write lexical selection rules (Turkish > Kazakh)
3 12 June - 19 June
  • Expand bilingual dictionary(adj)
  • Write transfer rules (Turkish > Kazakh)
  • Write lexical selection rules (Turkish > Kazakh)
4 20 June - 27 June
  • Expand bilingual dictionary
  • Write transfer rules (Turkish > Kazakh)
  • Write lexical selection rules (Turkish > Kazakh)
  • Documentation

First evaluation

5 28 June - 4 July
  • Expand bilingual dictionary(nouns)
  • Write transfer rules (Tatar > Kazakh)
  • Write lexical selection rules (Tatar > Kazakh)
6 4 July - 11 July
  • Expand bilingual dictionary(verbs)
  • Write transfer rules (Tatar > Kazakh)
  • Write lexical selection rules (Tatar > Kazakh)
7 12 July - 19 July
  • Expand bilingual dictionary(adj)
  • Write transfer rules (Tatar > Kazakh)
  • Write lexical selection rules (Tatar > Kazakh)
8 20 July - 27 July
  • Expand bilingual dictionary
  • Write transfer rules (Tatar > Kazakh)
  • Write lexical selection rules (Tatar > Kazakh)
  • Documentation

Second evaluation

9 28 July - 3 August
  • Testing, Evaluation, Correction, Documentation
10 4 August - 11 August
  • Testing, Evaluation, Correction, Documentation
11 12 August - 19 August
  • Testing, Evaluation, Correction, Documentation
12 20 August - 27 August
  • Testing, Evaluation, Correction, Documentation

Final evaluation

Coding Challenge

To be updated

List any non-Summer-of-Code plans you have for the Summer

I consider GSoC as a full-time job and I will not have other commitments during this time. Also, I am planning to start work on the project during the community bonding period to get acquainted with all aspects of these pairs as far as possible(20 hours a week).

I am planning to visit my parents in Kazakhstan in the period between 1-10 August. In this period I will be able to work at least 30 hours a week. During this time I will change timezone from GMT+3 to GMT+6.

Personal tools