This plugin is still a work in progress

Requirements

This plugin requires the following, in order to work correctly:

• Strapi v4 (this plugin is not compatible with v3)
• The plugin i18n installed and enabled (@strapi/plugin-i18n [npm])
• The content type to have internationalization enabled (advanced settings in the content type builder)
• In the internationalization settings at least two locales
• In the config an apiKey defined (see Configuration)

Unless you have the previous set up, the field on the right where you can translate will not show up. Also it will not show up when editing the currently only available translation of an entry.

Installation

1# with npm
2$ npm install @shawnvogt/strapi-plugin-google-translate
3# or with yarn
4$ yarn add @shawnvogt/strapi-plugin-google-translate

After successful installation you have to build a fresh package that includes plugin UI:

1# with npm
2$ npm run build && npm run develop
3# or with yarn
4$ yarn build && yarn develop

Configuration

Configuration is currently only possible using the plugin config file config[/env]/plugins.js or environment variables

1module.exports = {
2  // ...
3  deepl: {
4    enabled: true,
5    config: {
6      // your Google Cloud Translation API key
7      apiKey: 'key',
8      // Which field types are translated (default string, text, richtext, components and dynamiczones)
9      translatedFieldTypes: [
10        'string',
11        'text',
12        'richtext',
13        'component',
14        'dynamiczone',
15      ],
16      // If relations should be translated (default true)
17      translateRelations: true,
18    },
19  },
20  // ...
21}

or using the default environment variables:

• GOOGLE_TRANSLATE_KEY - default null

Features

• Fill in and translate any locale from another already defined locale
• Translation is restricted by permissions to avoid misuse of api quota
• Configure which field types are translated
  • standard text fields and nested components by default
  • uid fields are not translated by default because they might not result in the same translation as the attached field
    -> saving is prevented in the conent manager anyway until you change the slug again
• Fields that are marked as not translated in the content-type settings will not be translated
• Translation of relations by the followig schema:
  (The related objects are not translated directly, only the relation itself is translated)
  • the related content type is localized:
    • if a localization of the relation with the targetLocale exists
      -> it is used
    • else the relation is removed
  • the related content type is not localized:
    • the relation goes both ways and would be removed from another object or localization if it was used (the case with oneToOne or oneToMany)
      -> it is removed
    • otherwise the relation is kept

(Current) Limitations:

• Only the google translate supported languages can be translated
• Currently supports the basic google cloud translate api
• Only super admins can translate. This is currently the case, since permissions were added to the translate endpoint. Probably you can change the permissions with an enterprise subscription but I am not sure. If you know how to do that also in the community edition please tell me or open a merge request!
• Relations that do not have a translation of the desired locale will not be translated. To keep the relation you will need to translate both in succession (Behaviour for multi-relations has not yet been analyzed) a