Help:Contributing/languages: Difference between revisions

From Wikibase
Jump to navigation Jump to search
Add languages bar to translatable page
The {{Languages}} bar is now included automatically on every content page (LanguageBar extension) — note it, don't add it by hand (via update-page on MediaWiki MCP Server)
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<languages/>
The knowledge base is multilingual on a best-effort basis: <code>en</code>, <code>fr</code>, <code>eo</code>. Multilingualism works in two places: inside entities — labels, descriptions and aliases — and on wiki pages, as static translated copies. Contribution is never blocked on translation: write in the language you know; translations are produced separately.


<translate>
== Entities and properties ==
<!--T:1-->
The knowledge base is multilingual by design: every item and property can carry <tvar name="label">labels</tvar>, <tvar name="desc">descriptions</tvar> and <tvar name="alias">aliases</tvar> in many languages, and wiki pages can be marked for translation. This page explains how the two mechanisms work and the house rules around them.
</translate>


== <translate><!--T:2--> Labels, descriptions and aliases (entity terms)</translate> ==
Items and properties are single entities: there is exactly one page per entity (for example [[Special:EntityPage/Q1]]), shown in the reader's interface language. The multilingual content lives <em>inside</em> the entity as per-language values.
 
<translate>
<!--T:3-->
Items and properties are single entities: there is exactly one page per entity (for example <tvar name="item">[[Special:EntityPage/Q1]]</tvar>), shown in the reader's interface language. The multilingual content lives <em>inside</em> the entity as per-language values.
</translate>


{| class="wikitable" style="width:100%"
{| class="wikitable" style="width:100%"
! Field !! What it is !! Example (property <code>P1</code>)
|-
|-
! <translate><!--T:4--> Field</translate> !! <translate><!--T:5--> What it is</translate> !! <translate><!--T:6--> Example (item Q1)</translate>
| Label || The short, human-readable name of the entity || instance of
|-
| <translate><!--T:7--> Label</translate> || <translate><!--T:8--> The short, human-readable name of the entity</translate> || <translate><!--T:9--> Instance of</translate>
|-
|-
| <translate><!--T:10--> Description</translate> || <translate><!--T:11--> A one-line clarification that disambiguates the entity</translate> || <translate><!--T:12--> that class of which this subject is a particular example and member</translate>
| Description || A one-line clarification that disambiguates the entity || that class of which this subject is a particular example and member
|-
|-
| <translate><!--T:13--> Aliases</translate> || <translate><!--T:14--> Alternative names or spellings that also resolve to the entity</translate> || <translate><!--T:15--> is a; belongs to class</translate>
| Aliases || Alternative names or spellings that also resolve to the entity || example of
|}
|}


<translate>
House rules:
<!--T:16-->
* A label and a description must be unique together <em>per language</em>: no two entities may share the same label + description pair in the same language.
To add or edit terms in another language, open the entity in edit mode and use the <tvar name="morelanguages">"In more languages"</tvar> section at the top of the page. Every field takes a <tvar name="lang">language code</tvar> (for example <code>en</code>, <code>fr</code>, <code>de</code>, <code>eo</code>) and the value for that language.
* Do not copy Wikidata property numbers — properties are mirrored and mapped via equivalence statements instead (see the ontology alignment decision).
</translate>
* Prefer the local, human-written value over a machine translation; if you use a machine translation, review it against the original before saving.


=== <translate><!--T:17--> House rules for entity terms</translate> ===
=== Workflow ===


* <translate><!--T:18--> A label and a description must be unique together <em>per language</em>: no two entities may share the same label + description pair in the same language.</translate>
To add or edit terms in another language:
* <translate><!--T:19--> Do not copy Wikidata property numbers — properties are mirrored and mapped via equivalence statements instead (see the ontology alignment decision).</translate>
<ol>
* <translate><!--T:20--> Prefer the local, human-written value over a machine translation; if you use a machine translation, review it against the original before saving.</translate>
<li>Open the entity (for example [[Special:EntityPage/P1]]) and enter edit mode.</li>
<li>Open the "In more languages" section at the top of the page.</li>
<li>Choose the language, type the value, save.</li>
</ol>
Every field takes a language code (for example <code>en</code>, <code>fr</code>, <code>eo</code>) and the value for that language.


== <translate><!--T:21--> Translating wiki pages</translate> ==
== Wiki pages ==


<translate><!--T:22--> Wiki pages (help pages, documentation, the main page) are translated with the <tvar name="translate-ext">[https://www.mediawiki.org/wiki/Extension:Translate Translate extension]</tvar>. A translation administrator marks a page for translation; translators then work through the translation interface.</translate>
Pages are written in English as plain wikitext — no translation markup. A translation is a separate static page at a language-suffixed title (<code>Page/fr</code>, <code>Page/eo</code>), maintained by hand with machine-translation assistance. A <code>{{Translation}}</code> banner at the top of a copy records which English revision it mirrors, and a <code>{{Languages}}</code> bar on the English page lists the available copies — the bar is included automatically on every content page, so you never add it by hand. The English original is always authoritative.


* <translate><!--T:23--> <tvar name="special-translate">[[Special:Translate|Special:Translate]]</tvar> the translation interface, listing untranslated units per page.</translate>
Copies are created only once a page has settled editorially translating a page that is still being restructured is wasted work. Browser machine translation complements, never replaces, the static copies: <code>fr</code> is covered in all browsers, <code>eo</code> only in Chrome.
* <translate><!--T:24--> Translated pages are served in the reader's interface language automatically; you can force a language with <code>?uselang=fr</code>.</translate>
* <translate><!--T:25--> Translation units are the <code>&lt;translate&gt;</code> blocks in the source wikitext — keep them self-contained, one sentence or short paragraph each.</translate>


=== <translate><!--T:26--> House rules for translated pages</translate> ===
=== Producing and maintaining translations ===


* <translate><!--T:27--> Machine translation is a starting point, not a final answer: always read and correct machine-translated units.</translate>
* [[Help:Contributing/languages/translator|Translator]] — how copies are produced, kept in sync and verified
* <translate><!--T:28--> Keep terminology consistent with the entity terms (labels/descriptions) used in the data layer.</translate>
* <translate><!--T:29--> Do not translate <tvar name="tvar">tvar</tvar> placeholders or markup — translate only the human-readable text.</translate>


== <translate><!--T:30--> See also</translate> ==
== See also ==


* [[Help:Contributing]] — contributing to this wiki
* [[Help:Contributing]] — contributing to this wiki
* [[Help:Contributing/code]] — code blocks and syntax highlighting
* [[Help:Contributing/code]] — code blocks and syntax highlighting
* [https://www.mediawiki.org/wiki/Help:Extension:Translate Translate extension help] (official)
* [[Help:Contributing/languages/translator]] — producing and maintaining translations

Latest revision as of 09:21, 10 September 2026

The knowledge base is multilingual on a best-effort basis: en, fr, eo. Multilingualism works in two places: inside entities — labels, descriptions and aliases — and on wiki pages, as static translated copies. Contribution is never blocked on translation: write in the language you know; translations are produced separately.

Entities and properties

Items and properties are single entities: there is exactly one page per entity (for example Special:EntityPage/Q1), shown in the reader's interface language. The multilingual content lives inside the entity as per-language values.

Field What it is Example (property P1)
Label The short, human-readable name of the entity instance of
Description A one-line clarification that disambiguates the entity that class of which this subject is a particular example and member
Aliases Alternative names or spellings that also resolve to the entity example of

House rules:

  • A label and a description must be unique together per language: no two entities may share the same label + description pair in the same language.
  • Do not copy Wikidata property numbers — properties are mirrored and mapped via equivalence statements instead (see the ontology alignment decision).
  • Prefer the local, human-written value over a machine translation; if you use a machine translation, review it against the original before saving.

Workflow

To add or edit terms in another language:

  1. Open the entity (for example Special:EntityPage/P1) and enter edit mode.
  2. Open the "In more languages" section at the top of the page.
  3. Choose the language, type the value, save.

Every field takes a language code (for example en, fr, eo) and the value for that language.

Wiki pages

Pages are written in English as plain wikitext — no translation markup. A translation is a separate static page at a language-suffixed title (Page/fr, Page/eo), maintained by hand with machine-translation assistance. A

This page is a translation (language ?). It mirrors the English original as of revision ?, dated ?. If it differs from the original, the original is authoritative.

banner at the top of a copy records which English revision it mirrors, and a

Languages: English · français · Esperanto

bar on the English page lists the available copies — the bar is included automatically on every content page, so you never add it by hand. The English original is always authoritative.

Copies are created only once a page has settled editorially — translating a page that is still being restructured is wasted work. Browser machine translation complements, never replaces, the static copies: fr is covered in all browsers, eo only in Chrome.

Producing and maintaining translations

  • Translator — how copies are produced, kept in sync and verified

See also