Grants:Project/Wikifab/Translate compatible with Page Form
Project idea edit
What is the problem you're trying to solve? edit
Page Forms (known until November 2016 as Semantic Forms) is a mediawiki extension allows users to add, edit and query data using forms. It allow users to create easily structured contents. However, it is not integrated with the Translate extension. We want to update Page Forms to be properly compatible with the Translate extension. So that every wiki page can be easily translated in many languages using a form.
This is a problem we are facing on the project wikifab.org
What is your solution to this problem? edit
Step 1. Understand the problem edit
To translate content of a page (using Extension:Translate so), we must edit the page, and add tags <translate>...</translate> to wrap the text to translate, save the page, then Click the "Mark this page for translation" link. This is quiet complicated.
Issue: The 'Translate' extension doesn't respect the PageForm fields.
Step 2. Automatically add 'translate' tags edit
- Currently, PageForms allow users to define the type of each properties. We will add the possibility to defined them as translatable.
- When a user will mark a page as ready to be translated, fields values of translatable properties will automatically be wrapped into a 'translate' tag
- Tags should not be visible on edition of page with forms.
Step 3. Improve translation forms edit
After adding tags, all pages could be translated. But the translate form is not very good : each text block must be translated one by one, and translators haven't a vision of the global page.
So we should create a translation form, which use a specific template, in the same way than we use form to create a semantic page.
Project goals edit
The goal is to allow and improve internationalization of all wiki projects using the SemanticMediawiki extension.
We plan to apply it on the wikifab.org project. Wikifab could with this feature enable people to share knowledges to the world.
Project impact edit
How will you know if you have met your goals? edit
We will consider this project complete when:
- The extension will be published on Gerrit, with all the documentation needed to install and use it on mediawiki
- The extension will be will be set up on wikifab.org, and start to have translators using it
After this project we will collect feedbacks, and will continue to use and maintain the extension.
We will consider it very successful when:
- 10% of the pages on wikifab.org will be translated in at least 2 languages
- This extension will be set up on some others popular mediawiki, and we'll have good feedback about it.
Do you have any goals around participation or content? edit
The Global metrics are not applicable here, because the project does not apply on wikipedia.org.
Project plan edit
Activities edit
We will spend our time to design and develop this extension. We will manages issues and feedbacks on the project using Phabricator.
Budget edit
| Description | months | amount € | amount USD (1 € = 1.06749 USD) |
|---|---|---|---|
| Software developer internship (incl. charges) | 6 | 8400 € | 8,966.93 USD |
Community engagement edit
First we will inform the authors of PageForms extension (we are collaborating with Yaron Koren)
Then we will targeting to the community using the wikifab project.
And of course, publish extension and document it on mediawiki.org.
Get involved edit
Participants edit
Clement Flipo (ClemFlip) and Pierre Boutet (Pyro853) are the fondators of the wikifab.org project. We are developing mediawiki extensions for 1 years to improve it. Our work is available mainly on github : https://github.com/wikifab
Clement is specialized in interface design and project management.
Pierre is specialized in backend development and technical architecture.
Community notification edit
Phabricator task : https://phabricator.wikimedia.org/T160348
Endorsements edit
Do you think this project should be selected for a Project Grant? Please add your name and rationale for endorsing this project below! (Other constructive feedback is welcome on the discussion page).