Settings

Important

Set Access level of this plugin to something more restrictive than 'Public' (like 'Special' or 'Super Users'). Otherwise anyone could use you API key to translate his content, which could lead to excessive expenses.

Basic settings

Source language detection

Select how the source language for the translation should be detected. Note, that translation engine could ignore this setting, if it detects different language on translated text.

If the source language is same as requested translation language, warning will appear, and no translation will be performed.

If you want to bypass this behavior, just select "Automatic detection by translation engine" here.

Additional translation fields

Here you can specify additional fields for displaying translation button. Currently only Text and TextArea fields are supported.

You need to specify Form ID (also known as context), where value of * means "Any form". Second, you need to specify the field name itself. When working with subfields, you can specify here the field group using dots.

Some examples of fieldnames:

  • Article "Meta Description" field - metadesc with form set to com_content.article
  • Article "Note" field - note with form set to com_content.article
  • Article custom field with name (name, not title) "whatever" - com_fields.whatever with form set to com_content.article
  • Article "Intro image description" field - images.image_intro_alt with form set to com_content.article

Note on cutom fields

When using custom fields, you need to make sure, that "System - Fields" plugin is published before the "n3t Translate" plugin. Otherwise, custom fields will not be available to n3t Translate.

Translation engine settings

Translation engine

Select which translation engine to use. Currently DeepL and OpenAI is supported.

DeepL settings

DeepL API key

Insert DeepL API key. You can get one by registering at https://www.deepl.com/cs/pro-api.

Preserve formatting

Sets whether the translation engine should respect the original formatting, even if it would usually correct some aspects.

Formality

Sets whether the translated text should lean towards formal or informal language. This feature is only available for certain target languages. Setting this parameter with a target language that does not support formality will fallback to default formality.

Context

Additional context that can influence a translation but is not translated itself. This context will be used for all translations, so it should be something related to all your site, for example "Rock music magazine", "Cars, trucks, automotive" etc...

OpenAI settings

These settings are used for translations, if OpenAI is selected as translation engine, and Post Process actions, when any defined and OpenAi is used as engine.

OpenAI API key

Insert OpenAI API key. You can get one by registering at https://platform.openai.com. You should need to purchase some bolling plan to enable API access.

Model

Select AI model to use for translation.

Max. tokens

Maximal number of tokens in response. Tokens are chunks of text that can represent individual characters or words. Zero means no limit.

Temperature

Controls model output randomness. High (0.8-1.0) for diverse, creative responses. Low (0.2-0.5) for focused, deterministic output.

Formality

Ask OpenAI to change formality of the text. Make it less or more formal, or keep it same as in translates text (default).

Prompt

Any additional instructions for OpenAi to translate the text.

MS Azure settings

These settings are used for translations, if MS Azure is selected as translation engine.

MS Azure API key

Insert MS Azure API key. You can get one by registering at https://azure.microsoft.com.

MS Azure Region

Insert MS Azure Region. Fill according to settings of your MS Azure container.

Profanity action

Specifies how profanities should be treated in translations. 'No Action' will keep it, 'Marked' will replace it with asterisks and 'Delete' will remove it.

Google Cloud settings

These settings are used for translations, if Google Cloud is selected as translation engine.

Google Cloud API key

Insert Google Cloud API key. You can get one by registering at https://cloud.google.com/translate.

Post Process settings

Post process operations

Since version 5.1.0 n3t Translate supports Post Process actions. This means, that translated text is being processed using AI to get more relevant result.

Engine

Select which post process engine to use. Currently only OpenAI is supported.

Prompt

Enter instruction what to do with translated text. Be as specific as possible.

Only in HTML fields

Use this post process step only in HTML fields. For short texts AI could be confused, and produce unexpected results.