Difference between revisions of "Internationalisation"

From Wikifab Developers
Jump to: navigation, search
Line 1: Line 1:
 
=== Context ===
 
=== Context ===
  
Today wikifab has 2 websites :   
+
Wikifab use the mediawiki extension 'PageForm' https://www.mediawiki.org/wiki/Extension:Page_Forms (extensions previously called SemanticsForm ).
 +
 
 +
This enabled us to create forms templates in order that users create new pages with a predefined form.
 +
 
 +
 
 +
However, this extensions is not well integrated we the 'Translate' extension, which enable to have a multilingual website.
 +
 
 +
Today, wikifab has 2 websites :   
 
* http://beta.wikifab.org : the first version in french
 
* http://beta.wikifab.org : the first version in french
 
* http://en.wikifab.org : the english version
 
* http://en.wikifab.org : the english version
  
 
This requires that users create one account on each platform, and tutorials must be created separately on each site.
 
This requires that users create one account on each platform, and tutorials must be created separately on each site.
 
  
 
We want to have only one website, with translation features included. So that every tutorial can be easily translate to be available in many languages.
 
We want to have only one website, with translation features included. So that every tutorial can be easily translate to be available in many languages.
  
Mediawiki has an extension for this : Translate ( https://www.mediawiki.org/wiki/Extension:Translate ) this enable that each page of the wiki can be translated.
 
Wikifab use the PagesForm extension https://www.mediawiki.org/wiki/Extension:Page_Forms (extensions called previously SemanticsForm ). Unfortunately, this extension doesn't support page translation.
 
  
 +
So, we want to update the PageForm extension to be properly integrated with Translate extension.
  
===  state of the art ===
 
  
 
=== installation guide ===
 
=== installation guide ===
Line 24: Line 28:
 
Follow the tutorial here : https://github.com/Wikifab/wikifab-main
 
Follow the tutorial here : https://github.com/Wikifab/wikifab-main
  
Then install Mediawiki extension Translate, see instructions here : https://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle
+
Then install Mediawiki extension 'Translate', see instructions here : https://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle
  
 
==== Install empty mediawiki with extension Translate and PageForm ====
 
==== Install empty mediawiki with extension Translate and PageForm ====
Line 38: Line 42:
  
 
And install Mediawiki extension Translate : https://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle
 
And install Mediawiki extension Translate : https://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle
 +
 +
=== how Translate works ===
 +
 +
To translate content of a page, 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.
 +
 +
Then it show you the translation units, and here is the trouble for wikifab : it doesn't respect the PageForm fields.
 +
 +
After valid it, texts blocs to translate appear on the special page 'Translate'.
 +
  
 
=== To do ===
 
=== To do ===
  
* add link 'translate' to each page not translated
+
==== automatically add 'translate' tags ====
* change translate page to use forms. We may need to use specifics templates for translation.
+
 
 +
Tags should be added either at page creation, or on a click on a specific action button.
 +
 
 +
Tags should be added around each field to be translated.
 +
 
 +
==== improve translation forms ====
 +
 
 +
After adding tags, all pages could be translated. But the translate form is not very good : each text block must be translate one by one, and we havn'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 tutorial page.

Revision as of 16:44, 17 November 2016

Context

Wikifab use the mediawiki extension 'PageForm' https://www.mediawiki.org/wiki/Extension:Page_Forms (extensions previously called SemanticsForm ).

This enabled us to create forms templates in order that users create new pages with a predefined form.


However, this extensions is not well integrated we the 'Translate' extension, which enable to have a multilingual website.

Today, wikifab has 2 websites :

This requires that users create one account on each platform, and tutorials must be created separately on each site.

We want to have only one website, with translation features included. So that every tutorial can be easily translate to be available in many languages.


So, we want to update the PageForm extension to be properly integrated with Translate extension.


installation guide

To develops this feature, you can either install a wikifab wiki and add Translate extension, or just install a mediawiki with Translate and PageForm extensions :

Install wikifab site

Follow the tutorial here : https://github.com/Wikifab/wikifab-main

Then install Mediawiki extension 'Translate', see instructions here : https://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle

Install empty mediawiki with extension Translate and PageForm

Here are the commands to install ( proccess for ubuntu)

wget https://releases.wikimedia.org/mediawiki/1.27/mediawiki-1.27.1.tar.gz
tar -xzf mediawiki-1.27.1.tar.gz
mv mediawiki-1.27.1 translation.wikifab
cd translation.wikifab
cd extensions
git clone https://github.com/wikimedia/mediawiki-extensions-PageForms PageForms

And install Mediawiki extension Translate : https://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle

how Translate works

To translate content of a page, 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.

Then it show you the translation units, and here is the trouble for wikifab : it doesn't respect the PageForm fields.

After valid it, texts blocs to translate appear on the special page 'Translate'.


To do

automatically add 'translate' tags

Tags should be added either at page creation, or on a click on a specific action button.

Tags should be added around each field to be translated.

improve translation forms

After adding tags, all pages could be translated. But the translate form is not very good : each text block must be translate one by one, and we havn'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 tutorial page.