-
Notifications
You must be signed in to change notification settings - Fork 61
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
Is the DeepL split text correct? #82
Comments
Thanks for reporting this issue ! Seems like #83 closed it. Let me know if you want to reopen 👍 |
@Animenosekai Thanks! On a new note, I think the regex is not being used, as it's return is not being stored in any variable, nor it's being used as a function return: translate/translatepy/translators/deepl.py Line 122 in 11650ca
|
Oh that's right, I should look into it ! |
I believe that deepl split text should splits the text into an array of text lines.
Currently it appears that the regex doesn't splits by line, and the regex usage doesn't change the
text
variable.But I'm not sure if I'm confusing the calls to
LMT_split_into_sentences
vsLMT_split_text
(I noticed that using deepl in the browser, it appears to use the later).I made a test in the browser, translating "こんにちは世界" and "こんにちは" in two separated lines, and in case it helps, it made the calls:
An option and then a post request to
https://www2.deepl.com/jsonrpc?method=LMT_split_text
:With the response:
Then an option and then a post request to
https://www2.deepl.com/jsonrpc?method=LMT_handle_jobs
:With the response:
(for some reason it incorrectly translated both lines to Hello World, but it gave a beam for each line)
I hope this helps in case there is something missing! (I would make more tests but I'm getting "Too Many Requests" error, so I guess my IP was banned for trying invalid requests).
The text was updated successfully, but these errors were encountered: