Skip to content

DeepL: Setting needed to choose language model ("Classic" vs "Next gen") #71

Closed as not planned
Closed as not planned
DeepL: Setting needed to choose language model ("Classic" vs "Next gen")#71

Description

@MartinSchmid2409
MartinSchmid2409
opened on Nov 19, 2025

Currently DeepL lets you choose between two language models: "Classic" and "Next gen".

Your choice here affects translation quality and style significantly.

So it would be very handy and cool if you add this feature to the DeepL settings of Multi Translator.

Thanks!

Activity

  1. MartinSchmid2409
    closed this as not plannedon Nov 19, 2025

  2. JanEbbing commented on Nov 19, 2025

    @JanEbbing
    JanEbbing
    on Nov 19, 2025
    Contributor

    We have this in the TextTranslationOptions :) https://github.com/DeepLcom/deepl-php?tab=readme-ov-file#text-translation-options

  3. MartinSchmid2409 commented on Nov 19, 2025

    @MartinSchmid2409
    MartinSchmid2409
    on Nov 19, 2025
    Author

    Yes, I wanted to make this suggestion for improvement for the Craft CMS plugin "Multi Translator" which seems to rely on your API.

    Posted this issue for the wrong project. Sry :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions