-
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
Next: 3.0 #78
Comments
Wow, judging by the list, there's a lot of work to be done 😃 |
New Translate Services:
New languages:
Other changes:
|
Added to the list ! |
Here is what is currently happening on the Brand new models have been implemented ! They now all include the Most of them support rich string representation, which can be generated through the By passing in the The brand new New dictionary, example methods and alternative methods have been added ! It natively handles bulk translations, transliterations, ... on everything ! Through the use of Moreover, the The iterable returned by bulk actions is a custom TRANSLATEPY_SCREEN_REC.mp4
Now I need to modify the actual translators implementations and re-implement |
Wow! @Animenosekai, Great job ✨ |
TODO: add logger (like loguru) |
TODO: Integrate fake-useragent |
TODO: avoid Flask warning:
|
This is fixed in the translate/translatepy/translate.py Line 28 in c6cce0f
|
The server is going to use See also: Nasse — Logging |
Great job! 🚀 |
TODO: Telegram bot 😀 |
Hmmmm I'm not sure if this should be done by this repo or in another repo |
Btw @ZhymabekRoman if you look at 5817dd6 I reorganized the CLI a bit (needs a bit more work) and I created a TUI using Textual |
Yeah, maybe in separated repo |
Wow! 😯 Great job @Animenosekai ! I like this! |
Reimplemented HTML translation |
Added the Papago translator from Naver |
|
|
|
version: 3.0
status: ALPHA
Next
This version provides general improvements over the whole project, bringing exciting new features.
New
website
6Fixes
Updates
dictionary
,example
methods 10alternative
method 10raw
attribute)Everything is detailed in the
README.md
fileA comparison from the previous release can be found here
v2.3...v3.0
A comparison from the current branch can be found here
v3.0...main
Footnotes
For single word translations ? ↩
Following Got another translator for you. #28 ↩
Following https://github.com/Animenosekai/translate/issues/78#issuecomment-1443529618 ↩
Following a suggest #54 ↩
An actual public website was planned but due to the end of Heroku's free service and a lack of resource for now, we are going to stick with the local website (I think?). However the idea is not abandonned and a way of ranking the different translators based on real results is expected in the future. ↩
The branch needs to be changed to fit the
main
branch (local website) and to have a CLI access ↩Following Bulk Translation support? #66 ↩
Following Consider adding the formality and glossary feature to DeepL #65 ↩
Following https://github.com/Animenosekai/translate/issues/28#issuecomment-918746811 ↩
Refer to https://github.com/Animenosekai/translate/discussions/62 ↩ ↩2
Following [New] Size limited LRU cache #58 ↩
We might use Textual for an interactive TUI. We should also default to the interactive TUI when running
translatepy
without any action specified. ↩This provides a way of choosing the translators to use from the CLI (Defining which translator to use from the CLI #53)
But this also allows choosing the translator from the web server and thus the website. ↩
https://www.deepl.com/en/blog/deepl-welcomes-turkish-and-indonesian ↩
The text was updated successfully, but these errors were encountered: