-
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to handle multiple source and destination languages #45
Comments
Hi @michaelbaisch, this is a good point. I can see a use case to have multiple pairs. But given that I use this workflow primarily for one language pair, it never got important enough to prioritize it. How do you imagine triggering of a specific language pair? Would you think of a prefix before the text? Have a different keyword to invoke the workflow? Or do you have something else in mind? As a workaround, you could alter the workflow by following @ww7's suggestion here. It would create an extra step before actually looking for a translation, but it is an option. |
I'm just aware that others have solved this by using different keywords, like here. |
Hello,
I could imagine I'm not the only one who would like to translate between multiple language pairs. I think there is nothing about that in the documentation and probably it's also not possible within the workflow itself?
Greetings
The text was updated successfully, but these errors were encountered: