Difference between revisions of "User:Hiten"
| Line 29: | Line 29: | ||
Reasons why Google and Apertium should sponsor it: |
Reasons why Google and Apertium should sponsor it: |
||
| − | * Marwari has about 22 million speakers from India and neighboring countries of India. Despite the popularity the major translation tools like Google Translate don't include it. |
+ | * Marwari has about 22 million speakers from India and neighboring countries of India. Despite the popularity the major translation tools like Google Translate don't include it. |
| − | * |
+ | * |
* a description of how and who it will benefit in society, |
* a description of how and who it will benefit in society, |
||
* and a detailed work plan (including, if possible, a schedule with milestones and deliverables). |
* and a detailed work plan (including, if possible, a schedule with milestones and deliverables). |
||
Revision as of 15:07, 12 March 2023
Contents
Contact Information
Name: Hiten Vidhani
Location: India
University: Birla Institute of Technology and Science Pilani
Email address: vidhani.hiten2001@gmail.com
IRC: @hi101:matrix.org
Timezone: GMT+5:30
Github: hitenvidhani
Why is it that you are interested in Apertium?
Which of the published tasks are you interested in? What do you plan to do?
I am interested in the task "Bring an unreleased translation pair to releasable quality". I plan to develop the Marwari-Hindi(MWR-HIN) pair.
Proposal
Deliverables:
- Creating the MWR-HIN bilingual dictionary.
- Creating the MWR monolingual dictionary
- Updating the HIN monolingual dictionary, if required.
- Building the transfer rules for the MWR-HIN pair.
- Creating a MWR-HIN translator.
Reasons why Google and Apertium should sponsor it:
* Marwari has about 22 million speakers from India and neighboring countries of India. Despite the popularity the major translation tools like Google Translate don't include it. * * a description of how and who it will benefit in society, * and a detailed work plan (including, if possible, a schedule with milestones and deliverables).
Work plan
- Week 1:
- Week 2:
- Week 3:
- Week 4:
- Deliverable #1
- Week 5:
- Week 6:
- Week 7:
- Week 8:
- Deliverable #2
- Week 9:
- Week 10:
- Week 11:
- Week 12:
- Project completed
Include time needed to think, to program, to document and to disseminate.
If you are intending to disseminate to a conference, which conference are you intending to submit to. Make sure to factor in time taken to run any experiments/evaluations and write them up in your work plan.
List your skills and give evidence of your qualifications. Tell us what is your current field of study, major, etc. Convince us that you can do the work.
List any non-Summer-of-Code plans you have for the Summer, especially employment, if you are applying for internships, and class-taking. Be specific about schedules and time commitments. we would like to be sure you have at least 30 free hours a week to develop for our project.
