User:Fantasticfears/GSoC 2014

Visual translation: Integration of page translation with VisualEditor

 * Public URL: https://www.mediawiki.org/wiki/User:Fantasticfears/GSoC_2014
 * Bugzilla report: 48891
 * 53974


 * Announcement: (link to the announcement of your proposal at the wikitech-l mailing list.

Name and contact information

 * Name: Erick Guan(User page)
 * Email: fantasticfears@undefinedgmail.com
 * IRC or IM networks/handle(s)
 * IRC: fantasticfears
 * Skype: fantasticfears@undefinedgmail.com
 * Gtalk: fantasticfears@undefinedgmail.com


 * Web Page / Blog / Microblog
 * Blog on DigitalOcean
 * Twitter

9am to 11am, 1pm to 9pm
 * Location:Shanghai, China (UTC+8)
 * Typical working hours:

Synopsis
Extension:Translate is a powerful tool to translate a page. It's widely used by Meta and MediaWiki.org for publishing news, notice and policy. And many other sites which used MediaWiki also take advantage of Extension:Translate. Now we try hard to make our VisualEditor with Parsoid work for millions of users without extra work to modify the wikitext. Nevertheless, Extension:Translate can not work well with VisualEditor because Parsoid have no idea about Extension:Translate special tags. This ["http://bug-attachment.wikimedia.org/attachment.cgi?id=12405 sreenshot] shows what's going on. It's worthwhile to supporting the Extension:Translate work with new sets of tools. Besides a perfect time we can adjust these special tag.


 * Possible mentors: general #VisualEditor plugins mentors + Niklas Laxström

Deliverables
Please describe the details and the timeline of the work you plan to accomplish on the project you are most interested in (discuss these first with the mentor of the project):

Participation

 * Regular report
 * I'd like post my progress under my proposal page every week and send a email to the wikitech-l, including related project mailing list if needed.


 * Source code
 * I'd like to make a feature branch on the Gerrit, including keeping all of these on the GitHub. And I expected a test instance for this, if not, I can use my own server in college.


 * Communication
 * Most MediaWiki hacker are living in IRC, it's the best choice to get help. But it would be nice to communicate by email, private and mailing list, because I can describe more thoroughly and think more deeper which would reduce the meaning less talk. Last but not least, the bugzilla is used for tracking bugs, any further problem and progress would be referenced there. I will follow the community development process and keep in touch with mentor for the project.

About you

 * Education completed or in progress:
 * 2nd year in the college, and 2 years left


 * How did you hear about this program?
 * Mailing list for this year program and RSS feed for GSoC one year ago


 * Will you have any other time commitments, such as school work, another job, planned vacation, etc., during the duration of the program?
 * I'd like to travel to Taiwan for 2 weeks on the summer vacation. If I can't keep track on the schedule, I would call it off.

start editing, translating and doing maintenance work. Therefore, I wonder what can I do for technical work to ease some unpleasure problem. I want to focus these:
 * Parsoid, especially language converter for enabling Visual Editor for Chinese wiki project.
 * Grid system, responsive design.
 * pajx loading, pushState.
 * More guidance on Visual Editor for better instruction.
 * Flow Extension
 * Easier and central control for commonly used template(e.g. Infobox, Navbox), creating more consistent ux and reduce copying, updating work for local template version.
 * Global module
 * More modern HTML5 feature.

Past experience

 * Please describe your experience with any other FOSS projects as a user and as a contributor:


 * Please describe any relevant projects that you have worked on previously and what knowledge you gained from working on them (include links):


 * What project(s) are you interested in (these can be in the same or different organizations)?