Manual:Extension/BlueSpiceTranslationTransfer

Prerequisites

The translation mechanism requires at least one source and one target wiki. The configuration of the translation must be prepared accordingly by a server administrator (see requirements on the reference page of the TranslationTransfer extension).

Translation workflows

Translation of a page

Once the wikis have been configured, pages can be translated from the source wiki and created in another language wiki instance.

To translate a page:

1. Click on the Translate link in the toolbar on the source page. A dialogue opens.
2. Select the desired target language.
3. Click Translate to start the translation.
4. Check the suggested page name in the target wiki and change it if necessary. This dialogue box only appears for the first translation of the page.
5. Click Translate again to save the page name. The translation is displayed.
6. Click Save to save the translated page in the target wiki. You can now go directly to the page in the target wiki, translate it into another language (if configured) or close the dialogue box without taking any further action.

• 
  Translation button
• 
  Language selection dialogue
• 
  Customise page title
• 
  Page translation display and confirmation
• 
  Link between the language versions

Merge page content

If a page has already been translated, subsequent translations overwrite the previous page.

However, it is possible to configure in the server configuration whether the pages first land in a specific draft namespace and have to be checked and released manually.

If this is configured, the corresponding documentation is available on the manual page of the MergeArticles extension.

Additional information about the translation

The translated content during the translation process includes:

• Content of the page
• Display title (and optional real title)
• Categories (however, the category pages are not created, only the category link is transferred)
• Internal links
  • Links to other internal pages are also adjusted to point to the correct translated page.
  • Example: If the German page A links to the German page B, the English translation page A will link to the English translation page B.
• The embedded files/images on the source page are transferred to the target page without being translated or renamed.
• Templates and template calls in the wikitext are not translated, but are transferred with their original names. The templates can then be adapted manually or translated if necessary.
• Transcluded pages are also transferred without translation
• Code blocks are not translated.
• Translations are linked in the language changer (link to the same page in the other language wikis)
• Limitation: If a page is too long / large, the DeepL API cannot translate it. The best option is to divide the page into smaller subpages

Exclude file from translation

A tag can be inserted on the source page to exclude the file transfer for a specific page from the translation process.

In this way, the changes made in the target system are not overwritten during the next translation.

To do this, the user must insert the tag on the source page that contains the files to be excluded from the translation process.

Steps to exclude files from translation:

1. Add the tag in the source code of the source page
2. Add the files to the source page
3. Translate the page into the target language
4. The placeholder from the file is transferred, but the file is not. The file is therefore shown as ‘incorrect’ on the page. This allows users to see that files are missing and may need to be replaced.

Not-transferred file

​Note: If the file already exists on EN Wiki, the file will be displayed correctly.

Translation overview

An overview of all translations is available under Special:TranslationsOverview.

Translation overview

Translation Dictionary

The dictionary with all page titles and links can be viewed under Special:TranslationDictionary.

If the title of a target page needs to be adapted after the first translation, this can be done on this special page.

Translation Dictionary

If a source page is renamed, the titles are automatically retranslated and the title translations are updated in the database and in the wiki.

The different translation versions are still linked correctly. The redirect selected on the source page is also set up on the corresponding target pages.

Translation glossary

Glossary entries for the translation can be maintained on the Special:TranslationsGlossary page. This ensures that certain terms from the source language are always translated with a specific term from the target language. This applies to both the page title and the normal page content.

The maintained wiki glossary is transferred to the DeepL glossary and used in the translation.

Please note: DeepL glossary has restrictions for supported languages (see DeepL documentation)

Translation glossary

Additional information

Configuration of wiki structure and namespaces

• The translation processes (i.e. which wiki/language can be translated into which wiki/language) must be configured.
• The farm may contain some wiki instances that do not use translation workflows.
• Caution: DeepL translation is not available in all existing languages.

The links between the source and target namespaces must be maintained under Special:BlueSpiceConfigManager and BlueSpiceTranslationTransfer extension.

For example, the pages from the DE source namespace ‘Finanzen’ must be translated into the EN target namespace ‘Finance’.

Namespace configuration

If the pages must first be created in the draft namespace after translation, this must also be configured in the backend.

Configuration DeepL API

The DeepL API key must be created under Special:BlueSpiceConfigManager and DeepL extension.

The configuration is required in the source wiki.

DeepL API Key Configuration

Ad-hoc Translation

The AdhocTranslation extension translates a wiki page directly into the user's language.

If users have set a language other than the installation language of the wiki as the user language in their settings, the link Translate to my language appears in the toolbar of the page.

‘Translate to my language’ in the toolbar

After clicking on the link, the page content is displayed translated. After reloading the page, the actual content of the page is displayed again.

ExportThe PDF export does not take the ad-hoc translation into account. Export is only available in the original source language.

Configuration

The DeepL API key must be set up under Special:BlueSpiceConfigManager and DeepL Extension.

The configuration is required in each relevant instance.

DeepL API Key Configuration

Related info

• Manual:Extension/ContentTransfer
• Manual:Extension/MergeArticles

Technical Reference: BlueSpiceTranslationTransfer

---

To submit feedback about this documentation, visit our community forum.