Help:Contributing/languages: Difference between revisions

From Wikibase
Jump to navigation Jump to search
Fix example table to property P1; show the In more languages workflow (via update-page on MediaWiki MCP Server)
Restructure: general principles (en/fr/eo), entities and properties, classic wiki pages with role subpages (via update-page on MediaWiki MCP Server)
Line 3: Line 3:
<translate>
<translate>
<!--T:1-->
<!--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.
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, through the Translate extension. Contribution is never blocked on translation: write in the language you know; translators cover the others.
</translate>
</translate>


== <translate><!--T:2--> Labels, descriptions and aliases (entity terms)</translate> ==
== <translate><!--T:2--> Entities and properties</translate> ==


<translate>
<translate>
Line 25: Line 25:


<translate>
<translate>
<!--T:31-->
<!--T:16-->
House rules:
* 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.
* 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.
</translate>
 
=== <translate><!--T:17--> Workflow</translate> ===
 
<translate>
<!--T:18-->
To add or edit terms in another language:
To add or edit terms in another language:
<ol>
<ol>
Line 32: Line 42:
<li>Choose the language, type the value, save.</li>
<li>Choose the language, type the value, save.</li>
</ol>
</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>
</translate>
== <translate><!--T:19--> Classic wiki pages</translate> ==


<translate>
<translate>
<!--T:35-->
<!--T:20-->
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.
Wiki pages are translated with the Translate extension, which separates two roles:
* The translation administrator marks pages for translation and manages their units.
* The translator translates units through the translation interface.
</translate>
</translate>


=== <translate><!--T:17--> House rules for entity terms</translate> ===
=== <translate><!--T:21--> Workflow per role</translate> ===
 
* <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>
* <translate><!--T:19--> Do not copy Wikidata property numbers — properties are mirrored and mapped via equivalence statements instead (see the ontology alignment decision).</translate>
* <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>
 
== <translate><!--T:21--> Translating wiki pages</translate> ==


<translate>
<translate>
<!--T:22-->
<!--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.
Follow the page for what you do:
* <tvar name="admin">[[Help:Contributing/languages/translationAdmin]]</tvar> — marking and managing pages
* <tvar name="translator">[[Help:Contributing/languages/translator]]</tvar> — translating units
</translate>
</translate>


* <translate><!--T:23--> <tvar name="special-translate">[[Special:Translate|Special:Translate]]</tvar> — the translation interface, listing untranslated units per page.</translate>
== <translate><!--T:23--> See also</translate> ==
* <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> ===
 
* <translate><!--T:27--> Machine translation is a starting point, not a final answer: always read and correct machine-translated units.</translate>
* <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> ==


* [[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)
* [https://www.mediawiki.org/wiki/Help:Extension:Translate Translate extension help] (official)

Revision as of 07:57, 19 August 2026

Languages: English · français · Esperanto


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, through the Translate extension. Contribution is never blocked on translation: write in the language you know; translators cover the others.

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 — (P1 has no aliases yet)

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.

Classic wiki pages

Wiki pages are translated with the Translate extension, which separates two roles:

  • The translation administrator marks pages for translation and manages their units.
  • The translator translates units through the translation interface.

Workflow per role

Follow the page for what you do:

See also