feature request: set the level of formality for the translations

[markusmilkereit]

DeepL knows a couple of different "formality" levels, and modern branding voices are not always following the default "formal" setting.

Applied to the API call it looks like this, just don't know where you would want the setting to come from, maybe the Contao backend "settings"? Or the config.yml?

\contao-deepl\src\Api\DeepLApi.php line 36:
$this->translator = new Translator($this->apiKey, [TranslateTextOptions::FORMALITY => 'less']);

All formality options here: https://developers.deepl.com/docs/api-reference/translate
Can provide a PR with the change, just wanted to agree on where the setting should be :)

[bennyborn]

Sounds like a nice feature 😊

Since Contao is already shifting more and more settings from the backend to the config.yml I guess we should go the same route.

[markusmilkereit]

@bennyborn I went through a couple of usability scenarios, and from testing the extension I would say the "formality" would be nicer if a) it's a setting that the editors have access too, and b) if it's a setting that can be also set per page (optionally). So more like the date or time formats are handled - in tl_settings / tl_page. Any thoughts?

[bennyborn]

I fear that if you leave it up to the editors, especially if there are multiple editors, it might become too inconsistent. Defining it on the root page isn’t a bad idea at all, but I think I would also appreciate the option to set it globally via .env - kind of as a default 😊