Support translation direction

[sigito]

Using source= query parameter a translation direction can be specified. E.g., source=english would look for translations from English.

Add an abilitiy to force the translation direction.

[ww7]

Why translation direction still not supported?

[sigito]

Hi @ww7, unfortunately I did not have much time to finish this. If time allows, I might do it this or next week.

[sigito]

Hi @ww7, could you explain a use case you have in mind with the forced translation direction? Is it to only ever tranlate from one language to another? Or is it to be set per query?

[ww7]

@sigito for ability to have separate Script Filter for different translation directions, to translate from/to another language.

Some way to change source_language and destination_language variables with Script Filter.
(For Hotkey we can change variable with Arg and Vars)

You already asked:
https://www.alfredforum.com/topic/15755-set-an-environment-variable-for-script-filter/

[ww7]

It works with Keyword (press Enter) → Arg and Vars → Script Filter

Issue can be closed.
Thank you for great Workflow!
Hope Linguee will add Ukrainian someday!

[sigito]

@ww7, cool, thanks for confirming there is a solution. Though, this bug was more about forcing the translation direction. Currently, the workflow would attempt to translation from both languages that it is configured with. E.g., for an English-German pair, searching for "Bus" would give results for both en→de and de→en. And when a direction is force, the translation should only happen from the source language (or destination if the feature would support that).

Hope Linguee will add Ukrainian someday!

They have recently added Ukrainian to DeepL, so there is a pretty high chance of having it on Linguee too 🤞 .