-
Notifications
You must be signed in to change notification settings - Fork 60
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
Consider adding the formality and glossary feature to DeepL #65
Comments
Thank you for reaching out and for this very detailed explanation ! I'm currently in vacation but I'll definitely look into it. Also, I think that we'll add a "raw" attribute to the result models for the raw response and that we will make specific models for different translators. |
Same thing, I won't be able to work on projects until September, if you need any help ping me. After rest we will start work on v3 😅 |
I might greatly progress into v3 in August, since I already made lots of changes in the |
Done in #95. Just pass formality keyword argument to function: from translatepy.translators.deepl import DeeplTranslateV2
dl = DeeplTranslateV2()
dl.translate("You are", "fr", formality="formal") |
This feature will come in the v3 (available now on the |
At first sight, it seems that it is only a matter of adding some formated fields to the JSONRPC request:
For formality:
For glossary (named dictionary in the json):
Notes:
The text was updated successfully, but these errors were encountered: