Configure the Next Generation Translator Plugin
To view the configuration page for Next Generation Translator for Confluence, visit the Confluence General configuration page. In the left side bar, find the Translator category and select Configuration.
The configuration page allows you to:
configure which translation backend the plugin uses
view the set of languages supported by the configured translation backend
edit the subset of languages available to users
define regular expressions to exclude content from translation
add cached translations to the Confluence Search index
Configure which Translation Backend is Used
The Next Generation Translator plugin supports three kind of backend types:
DeepL (via the DeepL Api)
Google Translate (via the Google Translate Basic v2 Api)
Data-secure backend (via an instance of the Next Generation Translator Backend)
Which backend type is used is implicitly controlled by the selected Authentication Type.
Use a DeepL Backend
To use a DeepL backend, select
DeepL
from the Authentication Type drop-down menu. Select your DeepL Tier (free or paid) and enter your API key in the API Key field. You can get an API key at the DeepL website.
After entering these values, hit Save. Wait a few seconds for the notification shown underneath the save button to turn green to confirm that a connection to the backend has successfully been established.
Use the Google Translate Backend
To use the Google Translate backend, select
Google Cloud Translation (v2)
from the Authentication Type drop-down menu. Enter a valid Google API v2 key in the Google API Key field. The key needs to be authorized for calls against Google’s https://translation.googleapis.com/language/translate/v2 API (also called “Basic” API). Please see the documentation by Google for more details.
After entering these values, hit Save. Wait a few seconds for the notification shown underneath the save button to turn green to confirm that a connection to the backend has successfully been established.
Use a Data-Secure Backend
To use a Data-secure backend, select either of the remaining options
No Authentication
Basic Authentication
Bearer Token
AWS Cognito
OAuth2 Client Credentials
from the Authentication Type drop-down, depending on which authentication setup you have configured.
In either case, enter the server domain name or the IP address where the translation backend service is running in the Translation URL field.
With Basic Authentication selected, you will also be prompted to enter a username and password.
With Bearer Token selected, you will be prompted for a bearer token.
With AWS Cognito selected, you will be prompted for a username, password, cognito region and cognito client Id.
With OAuth2 Client Credentials selected, you will be prompted to enter a token URL, client Id and client secret.
After entering the requested values, hit Save. Wait a few seconds for the notification shown underneath the save button to turn green to confirm that a connection to the backend has successfully been established.
