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

Support for submitting additional languages for translation #28

Open
stevejalim opened this issue Sep 17, 2024 · 2 comments
Open

Support for submitting additional languages for translation #28

stevejalim opened this issue Sep 17, 2024 · 2 comments

Comments

@stevejalim
Copy link
Collaborator

I've come across a use-case that doesn't appear to be supported (yet), based on the idea of someone sending a page for translation in a subset of available locales and then trying to add more locales to the original job before it's come back (eg someone realises they forgot a language).

Step to reproduce

  1. Have at least three locales enabled (localeA, localeB, localeC,)
  2. Translate a test page from en-US to localeA, submitting to Smartling
  3. ./manage.py sync_smartling
  4. Confirm job has landed in Smartling with localeA
  5. Go back to the test page and hit Translate this page a second time
  6. Note that (correctly IMO) localeA is not in the list of langs to translate
  7. Select a new language (localeB) to translate and tag that for sending to Smartling
  8. ./manage.py sync_smartling
  9. Check whether the job has been updated in Smartling to include localeB

What I expected

That either
a) the Job was expanded to include both locales, IF the job was pending authorization (or in some other state where adding to it makes sense)
or
b) a separate Job for localeB was created, whcih can be done in parallel with localeA

And that the page for LocaleB shows that its translations, too, are being managed by smartling

What happened

The job didn't change at all, and the page for LocaleB does not show the message about the page's translations being managed in Smartling

@stevejalim
Copy link
Collaborator Author

I appreciate this is a complex flow of stuff here. I think as long as there's a reliable way to handle this situation - even if it's a manual-worfklow case of waiting for the completion Job 1 (LocaleA) and holding off sending LocaleB to make Job2 until Job 1 lands.

@zerolab
Copy link
Collaborator

zerolab commented Sep 17, 2024

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

No branches or pull requests

2 participants