Skip to content
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

batch translation (needs to also 'translate' uids) #6

Closed
Tracked by #1
sargreal opened this issue Mar 21, 2022 · 6 comments · Fixed by #7 or #22
Closed
Tracked by #1

batch translation (needs to also 'translate' uids) #6

sargreal opened this issue Mar 21, 2022 · 6 comments · Fixed by #7 or #22
Labels
Milestone

Comments

@sargreal
Copy link
Member

sargreal commented Mar 21, 2022

Feature Description

Translate all or a specific list of entities of a content type to another locale.

Requirements:

  • Translation should happen in the background
  • Translation can be cancelled
  • Current status can be requested
  • Translation is paused on server shutdown and continued on start
  • A failure in translation should stop the translation and the reason is saved
  • Translation should not send too many requests to the DeepL-API
  • User can configure if translated entities should be published directly or saved as draft if draftPublish feature is enabled
This was referenced Mar 21, 2022
@sargreal sargreal added the enhancement New feature or request label Mar 22, 2022
@sargreal sargreal added this to the v0.4.0 milestone Mar 22, 2022
@tomh4
Copy link

tomh4 commented Apr 1, 2022

Hello,
we are receiving 413 errors for large items, if the exceed the maximum size per request.
Will that be solved by the batching? Or is it for something else :) ?

@sargreal
Copy link
Member Author

sargreal commented Apr 1, 2022

Hi @tomh4

we are receiving 413 errors for large items, if the exceed the maximum size per request.
Will that be solved by the batching? Or is it for something else :) ?

No that is a different topic, this issue will handle translating multiple entities. Please open a separate issue for that :)

@tomh4
Copy link

tomh4 commented Apr 1, 2022

Ah I see, sorry :)

@sargreal sargreal mentioned this issue Oct 26, 2022
Merged
@sargreal sargreal linked a pull request Oct 27, 2022 that will close this issue
Merged
@fekide-bot
Copy link

🎉 This issue has been resolved in version 1.0.0-next.1 🎉

The release is available on npm package (@next dist-tag)

Your semantic-release bot 📦🚀

@fekide-bot
Copy link

🎉 This issue has been resolved in version 1.0.0-next.1 🎉

The release is available on npm package (@next dist-tag)

Your semantic-release bot 📦🚀

@fekide-bot
Copy link

🎉 This issue has been resolved in version 1.0.0 🎉

The release is available on npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

Successfully merging a pull request may close this issue.

3 participants