Difference between revisions of "User:Aditya"

From Apertium
Jump to navigation Jump to search
Line 10: Line 10:


<p>
<p>
As an organisation Apertium is currently working in areas that enthrals me like


</p>
</p>


Line 35: Line 39:
<p> Story2 </p>
<p> Story2 </p>


*'''Front-End:''' A check-Box or enable button under "Instant translation check box" if checked or enabled that allows to see synonyms to for translated word.These synonyms would be showed in div under the space in destination look-up.
*'''Front-End:''''
*'''Back-End:'''
*'''Back-End:'''


Line 55: Line 59:
<p> Story6 </p>
<p> Story6 </p>


*'''Front-End:''''
*'''Front-End:'''
<p>If user choose unlikely source language then a "red alert" or dialog box appears having "did you mean this" source language.
*'''Back-End:'''
</p>

*'''Back-End:''' Here in Back-End there are two modules to be developed
#<p>A module for integrating with front-End styling of "did you mean" is developed by checking alphabets matching Language pair sequentially </p>
== Work plan ==
== Work plan ==
===Phase-1,Weeks 1-4===
===Phase-1,Weeks 1-4===

Revision as of 07:55, 27 March 2018

Contact Information

Name: Aditya
E-mail address: adityaprayaga@gmail.com
Location: Hyderabad, India.
Phone Number: +91-8106805681
GitHub: https://github.com/aditya-369
IRC: aditya_369
Languages: Telugu(native), English, Hindi

Why is it that you are interested in Apertium?

As an organisation Apertium is currently working in areas that enthrals me like


        Apertium is a great organisation where machine translation of languages take place,not only the languages of prominent countries but also the regional languages of their states are also given importance. This is what makes Apertium unbiased, as any person can profusely use the platform. As there is no language barrier there is a healthy collaboration which builds good work atmosphere among the people in IRC. As above a healthy relationship is maintained between mentors and mentees which provokes the mentees to reciprocate it into their work, this enthrals me a lot to work with Apertium.

        Moreover, many existing machine translation systems are available at present which are mostly commercial or use proprietary technologies, which makes them very hard to adapt to new usages; furthermore, they use different technologies across language pairs, which makes it very difficult.But Apertium uses single uses a language-independent specification, to allow for the ease of contributing to Apertium, more efficient development, and enhancing the project's overall growth.

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

I am excited to work on the project Improving Apertium website which is listed as 1.8 idea under the published list of ideas.

Work Flow Details

Apertium has a pretty cool website already but,this is an opportunity that helps me in improving Apertium website and make it cooler than it is of now.So Coming to work flow details it is basically split into three phases as number of tasks listed in are also three i.e,

  • Phase-1: Dictionary Look-Up Mode for single-word translations
  • Phase-2: Colour Grading according to the reliability
  • Phase-3: Make language detection work properly and Suggestion styling if people choose an unlikely source language

    Phase-1

    Dictionary Look-Up Mode for single-word translations

    According to the task set of dictionary look-up for single-word translations, there needs to be a back-end module developed in python that would take language pairs and word as input parameters and these parameter are useful in morphological analyser phase as this phase segments the word and looks up in language dictionaries. This look up I also referred to previous ideas in github.

  • Dictionary Look-Up Mode should give synonyms and alternative translations

  • Dictionary Look-Up Mode should rank the translations by likelihood

    Story2

    • Front-End: A check-Box or enable button under "Instant translation check box" if checked or enabled that allows to see synonyms to for translated word.These synonyms would be showed in div under the space in destination look-up.
    • Back-End:

    Phase-2

    Colour Grading according to the reliability

  • Colour Grading according to the reliability:

    Colour Grading according to the reliability of translation is not as simple as it looks. There needs to be proper statistical method or probability distribution techinque(Baye's) that needs to be used as a reliability function in python which returns a number as this is a probability function so that this value helps in Colour grading in front-end development

    • Front-End:'
    • Back-End:

    Note:As this is a 4-week also would like to update existing bootstrap to bootstrap-v4 if time permits.

    Phase-3

    Make language detection work properly and Suggestion styling if people choose an unlikely source language

  • Styling if people choose an unlikely source language:

    story5

  • Make language detection work properly:

    Story6

    • Front-End:

    If user choose unlikely source language then a "red alert" or dialog box appears having "did you mean this" source language.

    • Back-End: Here in Back-End there are two modules to be developed
    1. A module for integrating with front-End styling of "did you mean" is developed by checking alphabets matching Language pair sequentially

    Work plan

    Phase-1,Weeks 1-4

    • Week 1: Front-End module for Dictionary Look-Up Mode with synonyms and alternative translations.
    • Week 2: Back-End module for Dictionary Look-Up Mode with synonyms and alternative translations.
    • Week 3: Back-End module for Dictionary Look-Up Mode ranks the translations by likelihood.
    • Week 4: Front-End module for Dictionary Look-Up Mode ranks the translations by likelihood
    • Deliverable #1: June 11-13

    Phase-2,Weeks 5-8

    • Week 5: Get to know various statistical methods and probability techniques and choose apt method to get reliability and start building a model.
    • Week 6: Back-End module for Colour Grading according to the reliability function(Probability functions to calculate reliability).
    • Week 7: Back-End module for Colour Grading according to the reliability function(Probability functions to calculate reliability).(Updating of Bootstrap-V4)
    • Week 8: Front-End module for Colour Grading according to the reliability
    • Deliverable #2: July 9-11

    Phase-3,Weeks 9-12

    • Week 9: Back-End module for styling("did you mean") if people choose an unlikely source language.
    • Week 10: Front-End module for styling("did you mean") if people choose an unlikely source language.
    • Week 11: Study Various methods to increase accuracy get the apt method and start building model.
    • Week 12: Back-End module for making language detection work properly by increasing the accuracy of detection.
    • Final Delivery: August 6 - 14
    • Project completed

      Apertium Website will finally,
      + has "dictionary lookup" mode for single-word translations
      + gives synonyms and alternative translations
      + ranks the translations by likelihood
      + has mode that colours the resulting translation depending on how reliable it is
      + makes language detection work properly
      + does "did you mean" style if people choose an unlikely source language.


    Above Week 5,Week 11 Would not be completely coding instead a specific time period is give so that to learn the required material as to optimise the performance of features in website.

    Education and Skills

    University Courses

  • Design and Analysis of Algorithms
  • Object Oriented Analysis and Design
  • Formal Languages and Automata Theory
  • Compiler Design
  • Data Structures
  • Data Base Management Systems
  • Math(Advanced Calculus,Ordinary Differential Equations and Laplace Transforms,Computational Methods,Probability, Statistics and Queuing Theory )
  • Web Technologies
  • Operating Systems
  • Linux Internals

    Special Courses

    Technical Skills

    Programming languages: C,C++,Python,Javascript, R, Java
    Web Technologies: HTML, CSS,Xml ,Angular, Bootstrap
    App Devlopment: Android Studio
    Frameworks: Django ,ExpressJs
    Databases: Oracle(My-SQL), Mongo-Db,SQlite

    Reasons why Google and Apertium should sponsor Improving of Apertium Website Project

    Apertium has a cool idea of machine translation of languages.But Website is their only gateway for the reflection of idea.So a good User experience would enable a large online crowd to use this site and be helpful in increasing knowledge on their required Language.

    As when societal aspect comes apertium core idea itself is a good advantage to society because where is no barrier for communication in specific language every one can express their thought in regional which is narrowed down by apertium.

    When it come to our project improving apertium website,there are feature like synonyms and also gives alternate traslations,colour grading according to the reliability,etc that would help User experience and intern help the growth of organisation.

    Description of how and who it will benefit in society

    As when societal aspect comes apertium core idea itself is a good advantage to society because where is no barrier for communication in specific language every one can express their thought in regional which is narrowed down by apertium.

    Non-Summer-of-Code plans you have for the Summer

  • I have my exam schedule during April 19-29.As per Gsoc Schedule results would be out on April-23.So I have 2 exams in-between the schedule although real coding would start at May-14 for which is lot of preparation gap for gsoc coding.

  • So except the for the exam day community bonding session i would work on weekly about 35-40 hrs.

    Coding Challenges

    1. Installed both apertium-html-tools and apertium-apy from their respective git repositories i.e, https://github.com/apertium/apertium-html-tools and https://github.com/apertium/apertium-apy.
    2. Tried To resolve issue #114 in apertium-html-tools(https://github.com/apertium/apertium-html-tools/issues) and sent pull request | #304
    3. The above is about Getting rid of inline styles in index.html.in file in apertium-html-tools file so the approach was basically remove styles in index.html.in file give them ids and refer these ids in external styling sheet, but in the due course of solving this issue I frequently interacted with my mentor Sushain and other organisaton members like Jonathan etc and finally got to a conclusion that apertium is slowly migrating to bootstrap-v4 so found some classes in bootstrap-v4 and placed these in general.css and remaining styles in translation.css.

    4. Started to work on issues related back-end in apertium-apy[ https://github.com/apertium/apertium-apy/pull/61 | #61]<\p>