|In other languages:||Português|
Important note - Before you add or edit a translation of this page or any other page in this wiki, please read the following instructions carefully. Please, DO NOT edit this page if you are not REALLY sure about what you are doing.
This documents defines the translation policy for the LibrePlanet wiki.
Terminology used in this document:
- original [page]
- master page
- - both refer to the original page (written in the language used by the author) from which the translations are made;
- translation [page]
- - refers to a page containing a translation of a original page.
Naming of translation pages
A translation page should be named using the following format:
- is the name of the master page;
- is the 2-digits lowercase code (ISO 639-1) of the language used by the translation.
So, the rule is: the translation page keeps the same (untranslated) name of the original page, plus a dot character followed by the 2-digits lowercase code (ISO 639-1) of the language used by the translation.
This will result in better searches findings, less confusion and more consistency of the wiki.
Example: The Italian translation of the Main_Page of this wiki should be named as Main_Page.it.
Language bar ('Languages' template)
When some translation of a master page exist in the wiki, then either the master page or each of its translation pages should display (at their top) a language bar linking to all the available translations.
To do this, the master page and all its translation pages should call (at their top) the Template:Languages.
The Template:Languages should be called in the following format:
- is the name of the master page;
- is the 2-digits lowercase code (ISO 639-1) of the language used for the content of the page from which the template itself is being called (no matter if it is the master page or one of its translations).
The Main_Page of this wiki has been written in English, so it should include at top:
and its Italian translation page should include at top:
Please, note that in both cases the template is called referring to the same master page (this keep them all related each other!), but for the page in English it is used the language code 'en' while for the page in Italian it is used the language code 'it'.
Semantic language properties
When using the Template:Languages, both the Semantic MediaWiki properties 'Language code' and 'Content language' for the calling page are set to the <LangCode> parameter value. These properties could then be used in semantic queries and searches.
In other words, following the example above, when including in a page:
it not only will display the language bar, but it also will assign the 'it' value to both the semantic properties 'Language code' and 'Content language' for that page. This means that this page will be matched when searching/querying the Semantic MediaWiki for those pages having the 'Language code' or the 'Content language' properties set to 'it'.
Renaming/moving a master page
In order to keep the
working as expected when renaming/moving a master page, then the "old" master page should NOT be deleted and a redirection to the "new" master page should be set. This is needed because the translation pages including the Template:Languages still refer to the "old" master page name after it has been renamed/moved.
Only if all the references to the "old" master page in its translation pages were updated with the "new" master page name, then the redirection of the "old" master page is not required.
Example: To rename the Group:LibrePlanetTest\FooPage master page in Group:LibrePlanetTest\FooPageNew keeping at the same time the language bar correctly displaying its translation pages, the 'FooPage' should NOT deleted and its content should be replaced with:
Aligning existing translation pages to this policy
If a master page has one or more translations, then they should be checked in order to be aligned to this policy.
To do this:
- the names of all the translation pages should be aligned to the naming format described above:
- create a new page for the translation, giving it the "right" name accordingly with the <MasterPage>.<LangCode> format;
- cut 'n paste ALL the content from the "old" translation page (that with the "wrong" name) to the "new" page just created (that with the "right" name);
- redirect the "old" translation page to the "new" one;
- either the master page and all its translation pages should be checked in order to add a call to the Template:Languages (using the calling format described above) if such a call it is missing or wrong.