Wikidocumentaries is multilingual. The user interface language can be changed to any available language on Wikimedia projects.
- 1 Translations
- 2 UI languages
- 3 Language fallback
- 4 Top language-related issues to fix
- 5 Navigation
- The item information comes from Wikidata, and the translations are managed there.
- The article comes from that language Wikipedia, and it is edited there.
- The UI is translated to any of the languages in TranslateWiki.
- The default user interface language is the browser language.
- The user may change the interface language of the site to another language, if it has been translated to that language.
- The language menu displays the available languages in alphabetical order. Later, custom language fallback order will be made possible.
- Even if the UI is not translated to a language, it is still possible to navigate using the language code in the site URL. For example https://wikidocumentaries-demo.wmflabs.org/Q32815?language=dag.
- The menu is created in UILanguageMenu.vue.
- English is used as the ultimate fallback option.
How to add a new user interface language to Wikidocumentaries?
- Navigate to TranslateWiki.
- Sign up.
- Select your language and start translating missing messages or checking existing ones.
- The UI language must have at least 25% translated messages to be imported to the project.
- TranslateWiki sends translated files to Wikidocumentaries twice a week. The json translation files are put together in wikidocumentaries-ui/src/store/messages.js. A new language is not automatically added to Wikidocumentaries. Please alert about new language translations by emailing firstname.lastname@example.org.
Wikidata language fallback is described here. Can that be utilized?
Language fallback mechanisms
Language fallback is handled differently in different cases. The MediaWiki API uses one mechanism and the SPARQL queries use another. Different components are based on different queries.
- Topic title and description
- Map labels
- Wikidata component values
These use SPARQL, and the fallback chain is declared in each query.
- The works, locations, related people and depicted in.
Fallback chain guideline
The desired display language is based on the following fallback chain.
- UI language (English default, user-defined.)
- Topic's original language (how?)
- Best option in the user-defined language fallback chain. The fallback chain is initially a hard-coded list of languages. Later on, the user may construct this list.
- Any language ordered by...
- The article is primarily displayed in the UI language
- If the article does not exist in the UI language
- a message to select another language is displayed.
- Alternatively, the article can be displayed in the best available language option of the language fallback chain.
- It is possible to create article generators that create stub articles from recorded facts.
- The article language menu displays a list of available article languages. The list is scrollable and displays all available languages in the following order.
- Available languages in the order of the user-defined language fallback chain. The fallback chain is initially a hard-coded list of languages. Later on, the user may construct this list.
- Any language ordered by...
- The menu is created in ArticleLanguageMenu.vue.
See also other search conditions in the Images page.
- The topic title is used to search for images
- Additional labels in different languages, properties and aliases may be used also
- Labels and aliases in primary languages
- Also use values of name properties if available.
- The primary language for the search term is chosen based on
- API service's preferred language(s)
- Topic's original language (how is this reasoned?)
- RTL support in the UI, T255530
|About||Technology||Design||Content modules||Tool pages||Projects|
|Setting up dev environment||
|Visual editor||Central Park Archives|