Difference between revisions of "User:Eiji"

From Apertium
Jump to navigation Jump to search
Line 4: Line 4:
University: University of Manchester
University: University of Manchester
IRC:thelounge72
IRC:thelounge72
github:https://github.com/yypy22


*Why is it that you are interested in Apertium?
==Why is it that you are interested in Apertium?==


*Which of the published tasks are you interested in? What do you plan to do?
==Which of the published tasks are you interested in? What do you plan to do?==
*Tokenisation for spaceless orthographies in Japanese
*Tokenisation for spaceless orthographies in Japanese
Include a proposal, including
Include a proposal, including
Line 37: Line 38:


* '''Project completed'''
* '''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.

Revision as of 10:50, 9 March 2023

Contact Information

   Name:Eiji Miyamoto
   E-mail address:motopon57@gmail.com
   University: University of Manchester
   IRC:thelounge72
   github:https://github.com/yypy22

Why is it that you are interested in Apertium?

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

  • Tokenisation for spaceless orthographies in Japanese

Include a proposal, including

   * a title,
   * reasons why Google and Apertium should sponsor 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