User:Aditya

From Apertium
Revision as of 22:27, 26 March 2018 by Aditya (talk | contribs)
Jump to navigation Jump to search

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?

        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 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 translations

  • Should give synonyms and alternative translations

    Story1

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

    Story2

    • FrontEnd:'
    • BackEnd:

    Phase-2

    Colour Grading according to the reliability'

  • Colour Grading according to the reliability:

    Story3

  • UI/UX upgrading to existing Apertium app:

    Story4

    • FrontEnd:'
    • BackEnd:

    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

    • FrontEnd:'
    • BackEnd:

    Work plan

    Phase-1,Weeks 1-4

    • Week 1:
    • Week 2:
    • Week 3:
    • Week 4:
    • Deliverable #1

    Phase-2,Weeks 5-8

    • Week 5:
    • Week 6:
    • Week 7:
    • Week 8:
    • Deliverable #2

    Phase-3,Weeks 9-12

    • Week 9:
    • Week 10:
    • Week 11:
    • Week 12:
    • Project completed


    Include time needed to think, to program, to document and to disseminate.

    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, ,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. 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.

    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.