- Issue created by @jan kellermann
I think EC would be interested in making WEB-T more useful for majority of Drupal users. Do you suggest creating Translation service provider for TMGMT, so that WEB-T would only provide MT connection, and TMGMT would do the translation management? Before creating WEB-T Drupal module I explored options and TMGMT integration was one of them. But it seemed that translation with it was more of a semi-automatic process where I manually select items to include in asynchronous translation jobs. Would it still be possible to achieve current functionality using TMGMT API? Can you explain the workflow a bit more?
- 🇩🇪Germany jan kellermann
There a two large translation systems: TMGMT and AI.
TMGMT
For TMGMT we are working on the plugin module tmgmt_webt. We wrote our own service for API-requests. But I would prefer to have one centralized service from webt. If you make auto-translation optional or move to a sub-module we can go this way.
AI
At the moment the ai_translate only uses chat-based translations (see #3477180). The module ai_provider_webt is ready written using webt-service. Here we need your decision if you want to decouple service and auto-translation.
Technically it is only a config item and adding a if-clause in this line. We would write an update hook to enable per default for legacy.
Great to see WEB-T is useful for you and can be integrated with other modules! So for both of these systems it would help to have an option which disables WEB-T automatic translation on article save/page load? We can add setting option for that, it should be simple change. Would it work if by default the automatic translation is enabled?
An option to disable auto translation has been added to Translation provider -> Advanced settings. It is released in versions 1.1.x-dev and 1.1.0