Why not just use deep-translator?

[nidhaloff]

Hi, I stumbled across this library by chance and I can't help but notice that the code (or at least a good part of it) under wordhoard/utilities/deep_translator.py is clearly copy-pasted from the deep-translator library. Like even the name of the file is the name of the library. Most of the code is exactly the same as in deep-translator, even variable names. Why not just use the library? it is open source anyway

Like, I understand that you added some extra stuff to it, but it would have been cool to just use the library as it is (as a dependency) or for example to give credit in your README or docs.

I think as open source developers, it would be really great if we support each other and the bare minimum in this case would be just to mention or give credits to someone for their work, because most of the time it is taken for granted.

Congratulation on your library/work. Keep up the good work.
IMHO, It would be cool if you just use deep-translator as a third party lib because you will get the last updates, so more features, definitely bug fixes and most importantly support.

[johnbumgarner]

All the translator modules are names after the source.

• wordhoard/utilities/deep_translator.py
• wordhoard/utilities/mymemory_translator.py
• wordhoard/utilities/google_translator.py

Also my code uses the DeepL Python Library and not your library. I also noted that your library also calls the DeepL service.

I wrote the deep_translator module code back on September 24, 2021. Please let me know where you think I plagiarized your library in my code?