Difference between revisions of "Anabaptistwiki:Language policy"

From Anabaptistwiki
(New page: {{Languages}} This page describes the current '''multi-lingual policy on MediaWiki.org'''. Languages == Help: namespace == Within the <code>Help:</...)
 
(Language Codes)
 
(66 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
{{Languages}}
 
{{Languages}}
This page describes the current '''multi-lingual policy on MediaWiki.org'''.
 
[[Image:Geographylogo.svg|right|150px|Languages]]
 
== Help: namespace ==
 
  
Within the <code>Help:</code> namespace we are building a set of [[Project:PD help|public domain help pages]].  The aim is to provide a basic set of help pages that may be imported into new wikis covering the basic editing and usage instructionsThese should be translated into as many languages as possible.
+
This page describes the current '''multi-lingual policy of the Global Anabaptist Wiki'''.  The Global Anabaptist Wiki is a set of encyclopedic pages about the global Anabaptist church in four languages (English, French, German, and Spanish) with the capacity to translate into ten other languagesHigh-level articles in the Global Anabaptist Wiki should be translated into these four languages while low-level articles need only include machine-translation code.  The following are guidelines for creating articles in multiple languages.
  
* English is the main reference language, and all root pages should be named and written in English.
+
==Organization==
* Other languages should be placed in an appropriately named sub-page of the English version. E.g. the French version of [[Help:Contents]] should be at [[Help:Contents/fr]] (not Help:Sommaire, Aide:Sommaire or Help:Sommaire/fr).
 
* Language sub-pages should be named using the appropriate language code for that language (see [[#Language codes|below]]).
 
* Sub-pages should ''only'' be used for translations into other languages, not for English content (e.g. you shouldn't use <code>Table editing/example</code> - use <code>Table editing example</code> or <code>Example of table editing</code> instead).
 
* If an international version of a page exists but an English version does not, then please create a stub article for the English version as this aids navigation.
 
* All pages in the help namespace should be tagged with the <code>{{[[template:Languages|Languages]]}}</code> template, which automatically creates links to all available translations.
 
  
This system will be compatible with the planned [[Automating help page export|automated import/export of Help pages]], but may need a bit of working around to export/import non-English pages in the interim.
+
Unlike [http://www.wikipedia.org/ Wikipedia] the Global Anabaptist Wikipedia is not comprised of distinct language encyclopedias that contain discrete bits of information.  Instead, the Global Anabaptist Wiki seeks to present the same content in multiple languages.
  
== The main page ==
+
There is, however, a balancing act that must be addressed when confronting language issues.  It comes down to human-translation, which is accurate but time consuming, vs. machine-translation, which is fairly inaccurate but labor-efficient.  Anabaptistwiki has struck a balance between these two methods of translation which has provided the best possible solution for language management.  Human-translation is organized under a system of root pages and sub pages which allows the Global Anabaptist Wiki to consolidate every translation of a particular article under one root name.  Machine-translation is structured to provide translation for any page in which Google Translate code is included.
  
The English version of our front page is located at [[MediaWiki]]Translated versions are located at MediaWiki/code, where code is the language code (e.g. [[MediaWiki/fr]]).  Please see [[Project:Main page templates]] for more details about creating or editing this content.
+
==Creating New High-Level Pages in Different Languages==
 +
High-level pages are highly accessed pages that are hubs for direction to other pages.  These pages include the main page, country pages, family tree pages etc. They are considered high-level pages because they rarely constitute the end result of a search and are critical to finding other informationIf these pages were to be haphazardly changed, they could potentially “orphan” other articles that are linked to them, meaning viewers couldn't find the article through a succession of link clicks.
  
Importantly, the rules about language codes (see [[#Language codes|below]]) should be followed here as well.
+
===English Root Articles===
 +
On high level pages, the English article is considered to be the "root article."  This means that the English article must be created before any other languages for that same article can be created.  In order to ensure that language templates on the Global Anabaptist Wiki work correctly, all root articles should be written in English.  Creating an English root article is as easy as creating a new article.
  
== Other namespaces ==
+
When creating another language variant of the article, a slightly different process must be utilized.
  
Apart from the Main Page, no policy has yet been decided about other namespacesFor the time being, if you would like to create translations for pages in other namespaces then please do so as described for the Help: namespace, however content may be moved or deleted depending on the policy that is eventually adopted.
+
===Creating Articles in Languages Other Than English===
 +
If you wish to write an article in a language other than English, first create the root article and then use the appropriate [[#Language Codes|language code]] to create the article in the language of your choice.  For example, if you want to create an article about the [[Iglesia Evangélica Menonita de Guatemala]] in Spanish, first create the English root pageOn that page insert the following [[:Template:stub|"stub" template]], to alert future editors to the fact that the English version is incomplete.  Next, create a new page for the Spanish translation by attaching the Spanish language code (/es) to the root page title.  For example if you used the "Iglesia Evangélica Menonita de Guatemala" format to create the root page you will use "Iglesia Evangélica Menonita de Guatemala/es" to create the Spanish translation page.  (To create links for the same article in other languages use the following format; French: "Iglesia Evangélica Menonita de Guatemala/fr", German: "Iglesia Evangélica Menonita de Guatemala/de".  Regardless of the fact that root articles are written in English, root article names are written in the native language of the specific congregation or group (In other words, the title for the [[Iglesia Evangélica Menonita de Guatemala]] article is "Iglesia Evangélica Menonita de Guatemala," not "Guatemalan Evangelical Mennonite Church").  To learn more about language codes, see the language code section [[#Language Codes|below]].
  
Discussion is ongoing at [[Project:Current issues#Localisation outside the Help: namespace|Project:Current issues]].
+
===Organizing Articles in Different Languages===
 +
When you start a new article, create new pages for several different translations.  For instance, when you create a French version of an article about Ethiopia ([[Ethiopia/fr]]) also create Spanish and German translations ([[Ethiopia/es]] and [[Ethiopia/de]]).  On these new pages attach the article stub template that corresponds to the appropriate languages.  For example, use the "stub" template on the root English page and the "stub/fr" template on the French page.  By inserting the stub template you will alert future editors to the fact that these versions of an article are incomplete.  To learn more about different stub templates read the [[Anabaptistwiki:Stubs|stub article]].
  
''Note that the rule that English content should not be placed in sub-pages does not apply to other namespaces.  This is one of the issues that needs resolving.''
+
At the top of each different article translation insert the "Languages" template.  This will create links to every other translation that exists for a given article.
  
== Language codes ==
+
Please note - when translating pages you need to change any categories to include the appropriate language code.  For example, if you translate a page from English to French (fr) and the page contains the "Category:Policy|Language policy" tag, you need to replace it with "Category:Policy/fr|Language policy".  Therefore, category pages will be separated by language.  For example, the "Paraguay" category will contain every English article that falls under the "Paraguay" category, while the "Paraguay/es" category will contain the Spanish translations of those same articles.
  
Throughout MediaWiki.org you should use the language codes specified by the MediaWiki software when creating language-specific content (see [http://svn.wikimedia.org/svnroot/mediawiki/trunk/phase3/languages/Names.php Names.php] for the full and up-to-date list).
+
==Creating New Low-Level Pages in Different Languages==
 +
Low level pages are articles that don’t have as high a risk to “orphan” other pages. If they are vandalized or haphazardly edited, very few pages will be affected and the damage can be contained. Low level pages usually include congregation pages, sources and stories. Unlike the relatively static high level pages, low level pages are pages that will continue to be created the longer the site is online.
  
Please also bear the following in mind:
+
Low-level pages are machine-translated by Google Translate.  Therefore, every time a new low-level page is created, the appropriate code needs to be added. This has been taken care of in an easy-to-use format when creating new articlesWhen first creating a page, there is a box that says "Select Boilerplate" above the editing pane with a drop-down menu of languagesAll that has to be done is select the language the article will be written in and the code for translating the article will be added to the editing pane. Its as easy as that.  Simply add the content for the article below the generated line of code.
* If the language code is not found in Names.php then we should not host help pages in that language.   
 
* If you want to add a language that is not present, first get it added to the software (by making a request at [[Bugzilla]]) and only add pages here once the changes have been accepted.
 
* If MediaWiki uses the 'incorrect' code for a language then you should also (for consistency) use that incorrect code hereIf you think a code is incorrect you should discuss it on [[Bugzilla]], and if this results in it being changed we will move the pages to match.
 
* Note that some language codes in Names.php are now deprecated (e.g. <tt>zh-yue</tt> has been replaced with <tt>yue</tt>)In these cases only the most recent code should be used.
 
  
==See also==
+
== Language Codes ==
*[[Project:Translation]]
+
 
 +
Throughout the Global Anabaptist Wiki you should use the language codes specified by the MediaWiki software when creating language-specific content (see [http://svn.wikimedia.org/svnroot/mediawiki/trunk/phase3/languages/Names.php Names.php] for the full and up-to-date list).
 +
 
 +
Following are the requisite language codes:
 +
 
 +
* English /en
 +
* French: /fr
 +
* German: /de
 +
* Spanish: /es
 +
* Indonesian: /id
 +
* Swahili: /sw
 +
* Korean: /ko
 +
* Dutch: /nl
 +
* Japanese: /ja
 +
* Chinese: /zh-cn
 +
 
 +
== Miscellaneous==
 +
If you do not like seeing the group name in English at the head of the page, the name can be removed by inserting the following code at the top of the page:  double-underline + NOTITLE + double-underline.
  
 
[[Category:Policy|Language]]
 
[[Category:Policy|Language]]

Latest revision as of 11:14, 22 July 2010

This page describes the current multi-lingual policy of the Global Anabaptist Wiki. The Global Anabaptist Wiki is a set of encyclopedic pages about the global Anabaptist church in four languages (English, French, German, and Spanish) with the capacity to translate into ten other languages. High-level articles in the Global Anabaptist Wiki should be translated into these four languages while low-level articles need only include machine-translation code. The following are guidelines for creating articles in multiple languages.

Organization

Unlike Wikipedia the Global Anabaptist Wikipedia is not comprised of distinct language encyclopedias that contain discrete bits of information. Instead, the Global Anabaptist Wiki seeks to present the same content in multiple languages.

There is, however, a balancing act that must be addressed when confronting language issues. It comes down to human-translation, which is accurate but time consuming, vs. machine-translation, which is fairly inaccurate but labor-efficient. Anabaptistwiki has struck a balance between these two methods of translation which has provided the best possible solution for language management. Human-translation is organized under a system of root pages and sub pages which allows the Global Anabaptist Wiki to consolidate every translation of a particular article under one root name. Machine-translation is structured to provide translation for any page in which Google Translate code is included.

Creating New High-Level Pages in Different Languages

High-level pages are highly accessed pages that are hubs for direction to other pages. These pages include the main page, country pages, family tree pages etc. They are considered high-level pages because they rarely constitute the end result of a search and are critical to finding other information. If these pages were to be haphazardly changed, they could potentially “orphan” other articles that are linked to them, meaning viewers couldn't find the article through a succession of link clicks.

English Root Articles

On high level pages, the English article is considered to be the "root article." This means that the English article must be created before any other languages for that same article can be created. In order to ensure that language templates on the Global Anabaptist Wiki work correctly, all root articles should be written in English. Creating an English root article is as easy as creating a new article.

When creating another language variant of the article, a slightly different process must be utilized.

Creating Articles in Languages Other Than English

If you wish to write an article in a language other than English, first create the root article and then use the appropriate language code to create the article in the language of your choice. For example, if you want to create an article about the Iglesia Evangélica Menonita de Guatemala in Spanish, first create the English root page. On that page insert the following "stub" template, to alert future editors to the fact that the English version is incomplete. Next, create a new page for the Spanish translation by attaching the Spanish language code (/es) to the root page title. For example if you used the "Iglesia Evangélica Menonita de Guatemala" format to create the root page you will use "Iglesia Evangélica Menonita de Guatemala/es" to create the Spanish translation page. (To create links for the same article in other languages use the following format; French: "Iglesia Evangélica Menonita de Guatemala/fr", German: "Iglesia Evangélica Menonita de Guatemala/de". Regardless of the fact that root articles are written in English, root article names are written in the native language of the specific congregation or group (In other words, the title for the Iglesia Evangélica Menonita de Guatemala article is "Iglesia Evangélica Menonita de Guatemala," not "Guatemalan Evangelical Mennonite Church"). To learn more about language codes, see the language code section below.

Organizing Articles in Different Languages

When you start a new article, create new pages for several different translations. For instance, when you create a French version of an article about Ethiopia (Ethiopia/fr) also create Spanish and German translations (Ethiopia/es and Ethiopia/de). On these new pages attach the article stub template that corresponds to the appropriate languages. For example, use the "stub" template on the root English page and the "stub/fr" template on the French page. By inserting the stub template you will alert future editors to the fact that these versions of an article are incomplete. To learn more about different stub templates read the stub article.

At the top of each different article translation insert the "Languages" template. This will create links to every other translation that exists for a given article.

Please note - when translating pages you need to change any categories to include the appropriate language code. For example, if you translate a page from English to French (fr) and the page contains the "Category:Policy|Language policy" tag, you need to replace it with "Category:Policy/fr|Language policy". Therefore, category pages will be separated by language. For example, the "Paraguay" category will contain every English article that falls under the "Paraguay" category, while the "Paraguay/es" category will contain the Spanish translations of those same articles.

Creating New Low-Level Pages in Different Languages

Low level pages are articles that don’t have as high a risk to “orphan” other pages. If they are vandalized or haphazardly edited, very few pages will be affected and the damage can be contained. Low level pages usually include congregation pages, sources and stories. Unlike the relatively static high level pages, low level pages are pages that will continue to be created the longer the site is online.

Low-level pages are machine-translated by Google Translate. Therefore, every time a new low-level page is created, the appropriate code needs to be added. This has been taken care of in an easy-to-use format when creating new articles. When first creating a page, there is a box that says "Select Boilerplate" above the editing pane with a drop-down menu of languages. All that has to be done is select the language the article will be written in and the code for translating the article will be added to the editing pane. Its as easy as that. Simply add the content for the article below the generated line of code.

Language Codes

Throughout the Global Anabaptist Wiki you should use the language codes specified by the MediaWiki software when creating language-specific content (see Names.php for the full and up-to-date list).

Following are the requisite language codes:

  • English /en
  • French: /fr
  • German: /de
  • Spanish: /es
  • Indonesian: /id
  • Swahili: /sw
  • Korean: /ko
  • Dutch: /nl
  • Japanese: /ja
  • Chinese: /zh-cn

Miscellaneous

If you do not like seeing the group name in English at the head of the page, the name can be removed by inserting the following code at the top of the page: double-underline + NOTITLE + double-underline.