No edit summary Tag: 2017 source edit |
(Created page with "A wiki can be set up to include different language versions of a wiki content. Wiki administrators have to make some decisions regarding how they want to support their wiki us...") |
||
| Line 1: | Line 1: | ||
A wiki can be set up to include different language versions of a wiki content. Wiki administrators have to make some decisions regarding how they want to support their wiki users' language in addition to simply providing translated content. | |||
The following considerations refer to a single-wiki scenario and don't apply if the language versions are maintained in multiple wikis. | |||
== | == Concepts == | ||
To make a wiki multilingual, different aspects have to be considered: | |||
# Content language and location of translated pages | |||
# Linking translated pages | |||
# User language (set in the user's preferences) | |||
# Multilingual navigation | |||
# Multilingual templates | |||
# Content organization (categories, portal pages) | |||
The following information gives some suggestions how to organise a wiki around its multilingual content. It does not consider using the MediaWiki extension Translate which is often installed in multlingual wikis to faciliate a section-by-section translation of wiki pages. | |||
== Content language and location of translated pages == | |||
Usually, language versions of a page are maintained as subpages. For this to work well, we need to know the actual content language of the wiki, which will always act as the "parent" of the other language versions. To find out the content language of your wiki installation, you can place the variable <code><nowiki>{{CONTENTLANG}}</nowiki></code> on a wiki page and look at its output, which corresponds to the language's [[wikipedia:List_of_ISO_639-1_codes|ISO 639-1 language code]], a double-digit abbreviation. For an English wiki installation, it would be <code>en</code>. | |||
'''Subpages:''' The language versions of a page would then live under its English parent page and use its language code as the subpage name: MyPage/de, MyPage/fr and so on. The pages can automatically be associated through a language template that relies on this subpage structure to "detect" the different language versions. | |||
'''Namespaces:''' This setup assumes that you always have the same main language as a starting point for your translation. If this is not the case, you can also think about using namespaces for your different language versions. This makes sense when you have content in different languages, but the content in these languages is not necessarily always related. You could create namespaces for your languages as you see fit, e.g. <code>DE:</code> , <code>FR:</code> or <code>IT-de:</code>, <code>IT-fr:</code> and so on. If there are related pages between languages, they can be connected through [[Manual:Extension/BlueSpiceInterWikiLinks|interwikilinks]]. | |||
== Linking translated pages == | |||
[[ | === Language switcher === | ||
=== Interwikilinks === | |||
Revision as of 14:01, 22 March 2022
A wiki can be set up to include different language versions of a wiki content. Wiki administrators have to make some decisions regarding how they want to support their wiki users' language in addition to simply providing translated content.
The following considerations refer to a single-wiki scenario and don't apply if the language versions are maintained in multiple wikis.
Concepts
To make a wiki multilingual, different aspects have to be considered:
- Content language and location of translated pages
- Linking translated pages
- User language (set in the user's preferences)
- Multilingual navigation
- Multilingual templates
- Content organization (categories, portal pages)
The following information gives some suggestions how to organise a wiki around its multilingual content. It does not consider using the MediaWiki extension Translate which is often installed in multlingual wikis to faciliate a section-by-section translation of wiki pages.
Content language and location of translated pages
Usually, language versions of a page are maintained as subpages. For this to work well, we need to know the actual content language of the wiki, which will always act as the "parent" of the other language versions. To find out the content language of your wiki installation, you can place the variable {{CONTENTLANG}} on a wiki page and look at its output, which corresponds to the language's ISO 639-1 language code, a double-digit abbreviation. For an English wiki installation, it would be en.
Subpages: The language versions of a page would then live under its English parent page and use its language code as the subpage name: MyPage/de, MyPage/fr and so on. The pages can automatically be associated through a language template that relies on this subpage structure to "detect" the different language versions.
Namespaces: This setup assumes that you always have the same main language as a starting point for your translation. If this is not the case, you can also think about using namespaces for your different language versions. This makes sense when you have content in different languages, but the content in these languages is not necessarily always related. You could create namespaces for your languages as you see fit, e.g. DE: , FR: or IT-de:, IT-fr: and so on. If there are related pages between languages, they can be connected through interwikilinks.
Discussions