Before You Begin
Complete the following steps before using the Smartling integration in Knak.
1. Set Up the Smartling Integration
You must connect Smartling to your Knak instance before submitting translations.
Follow the Smartling Integration Setup Guide.
2. Add Target Languages in Smartling
You must add your target languages inside Smartling before selecting them in Knak.
Smartling controls which languages are available for translation.
Knak only displays languages already added to your Smartling project.
If you do not see a language in the Choose Languages step, add it in Smartling first.
Refer to Smartling’s documentation:
https://help.smartling.com/hc/en-us/articles/7115748265115-How-to-Add-a-Language-to-a-Project
Demo Video
Submit an Asset for Translation
Follow these steps to send your asset to Smartling.
Important: If your asset includes module variations that are not locked, all variations will be translated. This includes variations toggled off.
1. Open the Translation Menu
Open your asset.
Click Translate in the top menu bar, then click the Translate Now button.
2. Select the Smartling Integration
Choose your Smartling integration from the list.
3. Choose Project and Workflow
Select your Smartling Project.
Select your Workflow.
Choose one of the following:
Create New Job
Add to Existing Job
Enter a Custom Job Name if needed.
4. Language Selection
Select the target languages for translation. Only languages configured in Smartling will appear.
Learn how to set this up through Smartling's help documentation.
5. Select the Campaign
Choose the campaign where the translated asset will live.
Configure optional settings:
Add Notes for translators
Apply custom field data from the base asset to translated variants
Select a Due date
Note: If you do not see the option to select a due date, your admin may have hidden this setting in the Smartling integration configuration in Knak.
Click Submit Request.
How Translations Appear in Knak
Your translated assets display differently depending on campaign selection.
If Assigned to the Same Campaign
The translation appears as a collapsible card under the original asset from the Studio View.
Click View Translations to expand the list.
If Assigned to a Different Campaign
The translation appears as a separate asset from the Studio View.
It displays inside the selected campaign.
Best Practices for Smooth Translations
Follow these rules to avoid issues:
Do not delete content in base assets after translation.
Do not delete content in translated assets.
Do not delete content in modules that are in use.
These actions may cause sync issues with Smartling.
Troubleshooting
Update Out of Date Variants
Use Update Out of Date Variants when your base asset changes.
This button will:
Update edited elements
Add new elements
Remove deleted elements
If you delete a text element and add a new one, you must resubmit the asset for translation. The translated variants will reflect the changes after updating.
Exception: Custom HTML Blocks
If you update a Custom HTML block, the button updates it automatically. You do not need to resubmit the asset for translation.
Resubmit an Asset for Translation
If a translation request is not marked Completed or Failed, delete the original request before resubmitting.
Open the Translate tab.
Click the three-dot menu next to the language.
Delete the existing request.
Submit a new translation request.
Translation Stuck in Translation Requested
Smartling shows the job as Completed, but the language in Knak still shows Translation Requested. The translation never imports into Knak.
Why This Happens
Knak imports a language only when every string in it is translated and authorized. A string is one piece of text from your asset, like a headline or a button label. Authorizing a string means approving it for translation in Smartling.
Smartling can mark a job as Completed even when some strings in the file were never authorized. This can happen if only some strings were authorized before the asset was approved in Knak. Knak keeps waiting for the missing strings.
How to Fix It
Open your project in Smartling.
Open the file view for the asset.
Check the authorization status of each string.
Add any unauthorized strings to the job.
Authorize those strings.
Wait for all strings to finish translation.
Knak imports the translation automatically once every string is complete.
Important: Do not delete or resubmit the request in Knak. The import works as long as the language still shows Translation Requested.
For help finding and authorizing strings in Smartling, see Smartling’s guide to troubleshooting untranslated content.
Merge Tags Translated in Smartling
If Smartling translates your merge tags, check the Custom Placeholder Format in your Smartling integration settings. This setting tells Smartling which placeholders to exclude from translation.
See How to set up the Smartling integration for setup instructions.
Need more help? Contact support via live chat within Knak using the chat bubble in the bottom right corner or email support@knak.com.