[ai_translate] more flexibility

Created on 10 September 2024, 11 days ago
Updated 18 September 2024, 3 days ago

Problem/Motivation

Interesting features (some requested by customer).
1. Allow customer to alter the prompt via interface for specific jargon (admin interface)
2. Allow different prompt per language
3. Allow different LLM per language
4. have the flexibility to enable the above only if needed.
5. allow developers to override (hook_).

Proposed resolution

Ad admin form for ai_translate with 3 options
- Take default LLM model (ai module settings)
- Different model per language

User interface changes

- Add admin form with settings
- translate button might also change a little (translate using Mistral) for one lang and (translate using openai ) for another.

API changes

Might add a hook for extension.

Data model changes

None

Feature request
Status

Needs review

Version

1.0

Component

Other Submodules

Created by

🇧🇪Belgium wouters_f Leuven

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

Comments & Activities

  • Issue created by @wouters_f
  • 🇧🇪Belgium wouters_f Leuven

    now we show the actual model used to translate:

    Here you can now configure different prompts per language and diffferent model per language:

  • Issue was unassigned.
  • Status changed to Needs review 10 days ago
  • @wouters_f opened merge request.
  • 🇧🇪Belgium wouters_f Leuven

    Added some code so the module now also supports not selecting a model (and falling back to the one selected in the AI default settings).

  • 🇧🇪Belgium wouters_f Leuven

  • 🇧🇪Belgium wouters_f Leuven

    1 Rebased and checked all merge conflicts.
    2 Re-tested (with openai and Mistral
    Tested the following
    - settings screen (als entity reference settings as the form is now TREE structure which resulted in that setting not working)
    - actual translation (which now uses batch)
    tested with
    - openai
    - mistral

Production build 0.71.5 2024