Closed moonlight-komorebi closed 2 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be automatically closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it was a stale issue that had no recent activity. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be automatically closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be automatically closed if no further activity occurs. Thank you for your contributions.
I followed up with @jmiraNR on this question
we can use this existing project, the only concern @jmiraNR was how we actually go about testing this, we don't want to send the entire site over in our test as we have limits to consider.
For a round trip test, we can send 10 docs and pretend that they are 1500. That is totally safe.
I said 10, but if it can be 5 or even 2 or 1, that's even better. ;)
Background
We will want to create a new project in Smartling with a machine translation workflow, as this will likely be easier to work with than a dynamic workflow. We simply point our scripts to use this project when doing machine translations using an environment variable (current implementation), and that should be the only change needed in our interaction with Smartling.
Acceptance Criteria
New Relic - Tech docs MT production
If we need to create a new project & workflow for machine translation in Smartling pair with Julien on thatUseful links
Relates to: #2341