This is currently available as a beta feature. If you are interested in enabling LQA Suite for your account, please reach out to your Customer Success Manager.
General
Can I send content from any type of Smartling project?
Yes. You can send translations to an LQA job from any type of Smartling project, including GDN and API projects.
Is it possible to send content from different production projects to the same LQA project or job?
Yes. Content from multiple different production projects can be sent to the same LQA project, as long as they share the same source language. Content from different production projects can even be sent to the same LQA job within your LQA project, as long as the production projects use the same Linguistic Package at the time of the snapshot.
Can I send content from production projects with different source locales to the same LQA project?
Yes, but it depends. Production content with different source locales cannot be placed in the same LQA job, but they can be sent to the same LQA project, as long as the source language matches. This is the first set of letters in the locale ID; for example, fr-CA and fr-FR are different locales, but they are the same “fr” language.
You may configure an LQA project with a source locale (for example, en-US) and it will support submissions from any project with an en source locale (e.g., en-GB, en-CA, etc.) The LQA project source locale does not have to be the “international” version of the source locale you use most often (e.g., en, fr, de).
Do I have to add target locales to the LQA project first?
No. When you first create an LQA project at least one target locale is required, but any time you submit a request containing a new target locale (any locale not already configured in the LQA project), it will be automatically included with no additional effort required.
Note: If you wish to select a different workflow (separate from the standard/default LQA workflow) for a new target locale, you must add the target locale to the LQA project first. When locales are added automatically upon submission, they will always use the default LQA workflow which was selected upon project creation. Strings can be moved from the default LQA workflow into another LQA-enabled workflow if needed.
Can I create multiple LQA jobs with the same production content?
Yes. Because each submission takes a new snapshot of the selected content, you can submit the same content to the LQA project multiple times. This is useful if you have two evaluators for the same language, and you want them both to review a batch of translations concurrently (without seeing each other’s evaluation).
Translation Round-Trip Feature
Can I "Save & Update" in bulk?
In the CAT Tool, linguists must review each translation and make a choice between "Save & Update" and "Skip" at the individual string level.
An Account Owner or Project Manager can perform the "Save & Update" action in bulk by using the LQA Modified Translations tab in the LQA Project.
Can I "Skip" in bulk?
If you do not need the option to "Save & Update," an Account Owner can disable the translation Round-trip feature for your LQA workflow step so you are not prompted to choose "Save & Update" or "Skip."
I made the wrong selection. Can I "Save & Update" something I've already saved?
Each time you save an edit in an LQA job, you'll be prompted to make a choice if you want to "Save & Update" or "Skip" the translation.
If you "Skip" a translation, but decide later that the translation should be propagated to the original production project, an Account Owner or Project Manager can help. They can use the LQA Modified Translations Tab to send the updated translation to the production string.