AI Translate should be able to use the TranslateText operation type

Created on 27 September 2024, 7 months ago

Problem/Motivation

We are getting the TranslateText operation type, it would be good to have those as a choice in the AI Translate.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task
Status

Active

Version

1.0

Component

Other Submodules

Created by

🇩🇪Germany marcus_johansson

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @marcus_johansson
  • 🇩🇪Germany jan kellermann

    As I understood it, the AI-Translate module is supposed to deliver a provider for “translate_text” that works with LLMs and chat.

    My impression is that AI-Translate works past “translate_text”. I cannot select the set Deepl provider at any point.

    Was this the goal? What is the sense of “translate_text” then? How can I use ai_provider_deepl with AI-Translation module?

  • 🇧🇬Bulgaria alexrayu

    Confirmed. With the recent changes from #3480861, The whole translate-text branch of providers fell off. DeepL is no longer accessible. The code now enforces the use of "chat" provider type.

  • 🇬🇧United Kingdom scott_euser

    I'm not sure the plan here myself, but maybe a separate issue should be raised in ai_provider_deepl. It seems like converting it to chat would lose the source/target language though so I don't think this issue should be closed. Maybe AI Translate instead needs to check for providers that provide both chat and/or translate_text, and if translate_text is found in a provider, use that, otherwise fall back to chat.

Production build 0.71.5 2024