Smartling FAQs

This article is for Account Owners and Project Managers.

Glossaries are used to define unique words or phrases that are important to your company. Industry lingo, brand names, andhomonyms are all examples of common glossary entries. These help identify the tone, voice, and definition you want your Translation Resources to convey in the translations.

By design, a glossary is meant to be a "living" document that changes as your content matures and evolves. Therefore, updating terms is encouraged.

Update a Glossary Term (New Experience)

Go to Account Settings > Linguistic Assets.

Under Assets, click Glossaries.

Click the name of the glossary to update. You'll default to the glossary that applies to your source language but you can toggle to the language of your choice.

Find the glossary term to update and click the pencil icon. The Edit Glossary Term dialog appears.

Edit the glossary term and then click Save Changes.

You can also work in a .xls, .csv, or .tbx file when editing glossary terms, which enables you to export those file types with target languages.

To edit a glossary from a file:

In the top right area, go to More > Export Terms.

Make updates to the file and then go to More > Update Terms From File.

Choose the file and clickUpload.

Update a Glossary Term (Classic)

Go to Assets > Glossaries.

Click the name of the glossary for which you'd like to add a term. You'll default to the glossary that applies to your source language (the language your content originates in) but you can toggle to the language of your choice.

Find the glossary term you want to update and click the pencil icon to edit the term. The Edit Glossary Term dialog box will appear.

Make any necessary changes then click Save Changes.

If you prefer to work in a .xls, .csv, or .tbx file when editing your glossary terms, instead of clicking the pencilicon on your glossary page:

Click the Moredrop down arrow near the top right of the page and select Export. This will allow you to export in any of the above mentioned file types, and optionally include target languages.

Once updates have been made to the exported file, click the More drop down arrow near the top right of the page and selectUpdate From File. Provide the appropriate file path and clickUpload.

This article is for Translators and Editors.

While working in the CAT tool, you can add or edit glossary terms.

Add a Glossary Term

If you come across a term that you feel should be added to the glossary, you can add it with this default keyboard shortcut: Ctrl + Shift + G. (Alternatively, you can customize your keyboard shortcuts from within the CAT tool by going to Settings > Keyboard Preferences.)

Edit a Glossary Term

Account Owners and Translation Resource Managers also have the ability to Edit Glossary Terms in the CAT Tool. You will see a pop up with the Glossary Term > Definition > Name of Glossary.

At the top right corner of the pop up, click the pencil icon to edit.

The Edit Glossary term box will appear:

The GitHub Connector is not compatible with self hosted GitHub (GitHub Enterprise) repositories. For options, consult the Options for Automation With Source Repositories article.

If your localization resource files are in a GitHub repository, the Smartling GitHub connector may be the ideal option for automating the process of sending source files to Smartling, and getting translations into your repository, where you need them. The Smartling hosted GitHub connector is designed to work well with standard development practices. Its important to understand how and when files will move between the repository and your Smartling project.

We rely on your team, using pull requests, to start this process. The Smartling GitHub connector:

Acts like a phantom developer focused on getting your resource files translated.

Monitors all pull requests. Based on your configuration, if a pull request has files that require translation, it will jump into action, and flag that pull request.

Uploads the original language files that require translation to your Smartling project, packaged as a job. They're uploaded to the Smartling project using a URI that includes the branch name they are being uploaded from.

Will commit the translated versions of the files into a new branch in your repository when this translation job is complete in Smartling.

Will make a pull request so that you can review and properly merge these changes.

Create a GitHub User

We recommend that you create a GitHub user specifically for use with Smartling. This user will be used to authenticate Smartlings access to your repo when configuring the Smartling project, and will provide access to the repository. It will also be the user who is associated with the branches, commits, and pull requests that are made in your repository. (If you feel that this process may not be compatible with your development process, see Options for Automation with Source Repositories for an overview of other options.)

Additional Authorization

Once you allow Smartling to access your GitHub account, via the OAuth flow, there may be an additional authorization required by your GitHub admin. For example, your GitHub account may have been set up by a third-party application where authorization must be performed by an "owner".

If this is the case:

Go to your GitHub Settings > Applications > Authorized OAuth Apps.

Select Smartling GitHub Connector and then select request access. Until an owner grants access, the status will show as "Access request pending". During this time, the connector will fail to connect.

Flow for Resource File Translation with Smartling GitHub Connector

Create branches to work on changes to your source code. In those branches, make edits to the original source language versions of your repositories localization resource files. This includes adding new files or modifying existing files.

Make pull requests to merge the changes to your main (master) branch.

If there are changes in the pull request to the resource files that require localization, the Smartling GitHub Connector will flag it.

The Smartling GitHub Connector will create a job in your Smartling project. This job will be configured with the original language resource files, which will be uploaded using their branchs name in the Smartling file URI.

Translation happens according to your Smartling translation workflow which will include:

The Job is Authorized for translation. (By default, automatically authorizing a job is disabled. To enable the feature, log in to Smartling and go to Project Settings > GitHub Settings then select Automatically Authorize All Jobs. This feature is only available for Enterprise customers.)

The translation work is performed using workflows that can contain multiple steps.

When all translations in the job have been published, the job is automatically updated to the completed state.

The Smartling GitHub Connector will create a new localization branch from the branch where the pull request originated.

The Smartling GitHub Connector will download the translated versions of the files from Smartling, and commit them to the localization branch, one commit per file, per language (locale).

A pull request is made by the Smartling GitHub Connector for the localization branch that includes just the translated versions of the localization resource files.

The location and file names of these translated files will depend on your configuration.

Review, accept, and merge the localization branch pull request.

The original branch is now fully translated.

The original branchs pull request is unflagged.

The original branchs pull request can now be accepted and merged with the master.

This article is for Account Owners, Project Managers, and Translation Resources

Once Review Mode has been enabled, you can begin to use this tool to quickly and easily proofread translations without being distracted by advanced CAT tool features.

visual context capture

To launch Review Mode, it must be enabled for an account and the strings to review must be in the Review workflow step.

Launch Review Mode (New Experience)

From the Jobs page, click the linked words in the Words column. On the page that opens, hover over the strings you want to review and click Edit Translation.

Launch Review Mode (Classic)

From the Strings View page, click the three dots and select Edit in CAT Tool.

Translations Panel

The translations panel appears below the visual context panel in the Review Mode interface. It shows a text view of the currently selected string, including showing tags and placeholders.

Approve or Reject Content

You can choose to approve a string or reject it. There are a few different ways to do this.

Click the Reject or Approve button in the translation list

Hovering over an active string in context will show a Rejectbutton

Pressing Enterwill approve a string, pressing Deletewill reject it

Edit strings

You can edit strings by clicking on a translation in the translation panel. This will open an edit view showing the source and translation side by side. Any quality check errors will be shown below the editing box. Click Save when you're finished and ready to save your edits.

Keyboard Shortcuts

Tab key will move to the next string

"Up/Down" keys will move up and down the translation list

Enter key approves a string

"Delete" key rejects a string

Submit a Document

To finish the reviewing task, press the Submit Document button. Any strings that have not yet been rejected or approved will be approved and submitted when you press the submit button. After clicking Submit Document youll see a confirmation modal outlining how many strings have already been rejected or approved and how many have had no action taken.

Toggle between bilingual and monolingual

You can view the string list as either bilingual or monolingual. Click the toggle next to Translations to switch between the two options.

Move between Documents

Some jobs will have multiple documents or pages, which are shown in the left sidebar. A document is divided depending on what type of content is in the job. For example, if there were two files in a job, each file would be its own document. For a GDN project, two different URLs would be two documents. To switch between documents, click on the image in the sidebar.

Switch to CAT Tool

Users who need some of the features offered in the CAT tool, but not available in Review Mode can switch to the CAT tool by clicking the Switch to CAT Tool button in the header.

After moving to the CAT tool, to switch back to Review Mode, click Settings and select Open in Review Mode.

Some strings are associated with visual context, butcan'tbe viewed in context. For example, a title tag for a webpage, or text in a hidden panel. These strings will be shown in the translations panel with a May Not Be Visible indicator.

Not seeing Visual Context in the context panel of Review Mode? You may need to integrate with one of our tools.

This article is for Account Owners and Project Managers. Project Managers also have access to all translation memories for all projects, and not just the projects to which they are assigned.

Smartling facilitates the creation of new TMs and the management of existing ones. Smartling's Translation Memory Management (TMM) provides powerful search capabilities within a TM, the ability to move content between TMs, delete content, export content, as well as insight into the history of a string within a TM.

To access all of Smartling's Translation Memory Management features, log in to Smartling and go to Assets > Translation Memory.There are several actions you'll be able to take, such as:

Create a Translation Memory

Import a TMX File

View TM Details

Rename a TM

Search

Move, Export, Delete Content

Editing

Find and Replace

Delete a TM

View History of a String

Create a Translation Memory

Within Smartling, you can create a completely new translation memory or import a TMX file into an existing translation memory. (To apply a TM to a leverage configuration, see Configure Translation Memory Leverage.)

Import a TMX File (New Experience)

A Translation Memory Exchange (TMX) file is a format used for exchanging translation memory data created by a CAT tool. TMX files are useful when you're migrating from another tool or process to Smartling.

To import a TMX into a translation memory, under Actions, click the three dots and select Import TMX File. For more information on TMX files, see Upload a Translation Memory.

Translation Cache

Import a TMX File (Classic)

A Translation Memory Exchange (TMX) file is a format used for exchanging translation memory data created by a CAT tool. TMX files are useful when you're migrating from another tool or process to Smartling.

To import a TMX into a translation memory, under Actions, click the three dots and select Import TMX File. For more information on TMX files, see Upload a Translation Memory.

For subsequent imports of the same TMX file, with the same naming convention, the previous TMX import will be overwritten.

View TM Details

To view the details of your translation, click the more icon and select Details. You'll be able to view details about the following:

Created By

Created On

Last Modified By

Last Modified On

Active Package (linguistic package with a direct to it)

Leverage Configuration (with a direct link to it)

Target Language (and the number of strings/words associated with it)

Strings

Words

Rename a TM

To rename a translation memory, click the more icon and select Rename. Enter a new name and click Confirm.

Search

Search Within a TM (New Experience)

Search is based on keyword search and not fuzzy matching, as Smartling uses a different algorithm for that.

Click on the name of a TM. There are several ways you can search or filter for a string:

Keywords: Source or target keyword

Languages: Target language

Project: Project name

Translation Activity: Authorizer, Date Authorized, Translator, Date Translated

String Metadata: Variant, Key, Hashcode

Content Sources: File, URL, TMX File

Search Within a TM (Classic)

Search is based on keyword search and not fuzzy matching, as Smartling uses a different algorithm for that.

Click on the name of a TM. There are several ways you can search or filter for a string:

Keywords: Source or target keyword

Languages: Target language

Linguist Action: Name of the user who last saved or authorized the string

Dates: Date lastauthorized or date that the translation was saved

Project: Project name

String Metadata: Variant, Key

Content Sources: File, URL

Search Multiple TMs At Once

You can search multiple translation memories at once. When you select a TM, you'll see on the left hand side of the page that there's a Translation Memories drop down menu where you can select all TMs or just certain ones from which to search.

If there are TMs containing different source languages that are being searched, the Move and Export actions will not work. For example, if you're attempting to move or export strings from an English (USA) TM to an English (UK) TM. Of course, if all TMs have the same source language, then Move and Export are possible.

Move, Export, or Delete Content (New Experience)

You can move content to another TM, export content from a TM, and delete content within a TM.If the same string is stored in multiple TMs, you will need to move, delete, or edit in multiple TMs.

To move, export, or delete content, go to your list of translation memories (Account Settings >Linguistic Assets> Translation Memory), and click the name of the relevant TM to display the Actions menu in the top left area.

Move Content to Another TM

Search or filter for strings that you want to move to another TM with the same source language, then select the strings and click Actions >Move. You'll be prompted to select the appropriate translation memory.

Export Content From a TM

Search for strings that you want to export from the TM, then select them and click Actions >Export. You can export an entire translation memory or only export a portion of a TM based on specific search criteria. For example, you might search for only content that was translated in the last six months, and export that as a TMX file.

To export an entire translation memory, without having to click on each individual string, go to your full list of TMs. Click the more icon and select Export TM. All strings within that TM will be exported. An email will be sent to your email address with a link to download the generated TMX file.

Delete Content Within a TM

Occasionally, you may want to pare down your translation memory to ensure that only the most appropriate content is in it. Search or filter for strings that you wish to delete from the TM, and click Actions >Delete. You'll be prompted to confirm the action.

Deleting individual strings is permanent, and will affect all projects leveraging the TM. (If you think you may want to recover this content in the future, as a workaround, you could create a TM, name it something like "Deleted Content", and then move the unwanted content to this TM.) In the future, if the same translation appears again, and is saved, it will be added back to the TM.

Move, Export, or Delete Content (Classic)

You can move content to another TM, export content from a TM, and delete content within a TM.If the same string is stored in multiple TMs, you will need to move, delete, or edit in multiple TMs.

To move, export, or delete content, go to your list of translation memories (Assets > Translation Memory), and click the name of the relevant TM. You'll then see the Move, Export, and Delete buttons.

Move Content to Another TM

Search or filter for strings that you wish to move to another TM with the same source language, then select the strings and click Move. You'll then be prompted to select the appropriate translation memory.

Export Content From a TM

Search for strings that you wish to export from the TM, then select the strings and click Export. You can essentially export an entire translation memory or only export a portion of a TM based on specific search criteria. For example, you might search for only content that was translated in the last 6-months, and wish to export that as a TMX file.

To export an entire translation memory, without having to click on each individual string, go to your full list of TMs. Click the more icon and select Export TM. All strings within that TM will be exported. An email will be sent to your email address with a link to download the generated TMX file.

Delete Content Within a TM

Occasionally, you may want to pare down your translation memory to ensure that only the most appropriate content is in it. Search or filter for strings that you wish to delete from the TM, and click Delete. You'll be prompted to confirm the action.

Deleting individual strings is permanent, and will affect all projects leveraging the TM. (If you think you may want to recover this content in the future, as a workaround, you could create a TM, name it something like "Deleted Content", and then move the unwanted content to this TM.) In the future, if the same translation appears again, and is saved, it will be added back to the TM.

Editing

When hovering over a TM string, youll see a link to Edit Translation. Clicking this link allows you to edit one string at at time.

This feature allows you to edit one string at a time.

There are no quality checks that are performed here like there are when editing in the CAT tool.

You can:

Save: This updates the translation of the string within the Translation Memory only. Fuzzy matches and SmartMatches in the future will use this new translation.

Save & Update Projects: This updates the translation of your string within the Translation Memoryandwill propagate to strings within your project that have used the same translation.

Cancel: To cancel any changes that may have been made, and exit editing.

Save & Update Projects The propagate function can cause updates to your published or pre-published translations. This can trigger downstream behaviors like notifications, refresh, or file download, depending on your integration setup. This option may not be available. This can be because the translation is not currently active any projects. This can be because it was imported from a TMX; or because a change was already made and saved, but not propagated.

Update Project Strings

Update project strings is an important feature that's available in both single string edit, and Find and Replace. Choosing this option will update the translation of your string within the Translation Memory, and will update strings within projects that have used the same translation. The project strings will be updated in whatever step they're currently in, whether that's a translation step or a published step.

To illustrate how this works, imagine a string in a project called "Business Docs" is translated and saved to the TM. Later, the exact same source string appears in a different project, "Email Marketing". This repetition gets Smartmatched from the translation that was already in the TM. If the TM translation is updated and Update Project Strings is selected, the strings in both "Business Docs" and "Email Marketing" projects will be automatically updated.

Find and Replace

Find and Replace is a powerful feature allowing you to change large numbers of translation memory strings at once.

To use Find and Replace:

Search for the word youd like to replace by first doing a Target Keyword search.

Select the strings youd like to replace.

Click on the Actions button and choose Find and Replace.

In the resulting modal that pops up, fill in the replacement wording in the Replacement Text field.

You may optionally choose to update project strings.

Click Replace.

Note that if many strings are selected it may take some time to calculate the number of strings that will be replaced. This is because Find and Replace is more precise in choosing text than the standard Target Keyword search, and does its own search through all selected strings to ensure only the exact characters are replaced.

Bulk Replace

To do a bulk replace, select all strings on the page, then click Select all strings matching current filter.

Delete a TM

Deleting an entire TM is permanent and will affect all projects leveraging the TM. (If you think you may want to recover this content in the future, as a workaround, you could create a TM, name it something like "Deleted Content", and then move the unwanted content to this TM.)

Find the TM that you wish to delete. Click the more icon and select Delete TM.

The Delete Translation Memory dialog will appear. In this example, the TM is still being used by a linguistic package.

If the TM is not being used by a linguistic package, you'll be prompted to confirm the deletion.

View History of a String (Classic)

To view the history of a string (such as the Translator's name, completion date, project name, and the person who authorized the content), click the clock icon within the History column.

For project specific string history, use the History feature by going to Content > Translations (also referred to as the "List View").

Who can use this feature? Requestors can use this feature. Account Owners and Project Managers should read this article. Available in the Enterprise plan.

Requesters can upload files for translation, check the status of their requests, and download completed translations.

Create a Job

Click the Jobs menu.

ClickRequest Translation.

Add/enter the following:

Files that you want translated

Job Name

Due Date

Reference Number

Description

Target Languages

Click Create.

Get a Cost Estimate (New Experience)

From the Jobs Dashboard, click the name of the job. On the left panel, view the cost estimate.

Get a Cost Estimate (Classic)

While the status is Awaiting Authorization, you can generate a cost estimate for the job.

Go to Jobs.

Find the job for which you wish to run an estimate. Click the name of the job, then select the Estimate tab to create an estimate.

Select the workflows to be used for the estimate and click Estimate. Estimates are available for 60 days.

Check the Status of a Job (New Experience)

With a job, you can group and prioritize content for translation. You can check the status of a job you submitted in Smartling by clicking the link from within your email notification, or by logging in to Smartling.

In Smartling, click Projects and select your job.

Under Progress, hover over the progress bar to display the status of yourrequest by workflow step.

Check the Status of a Job (Classic)

A job allows you to group and prioritize content for translation. You can check the status of a job you submitted in Smartling by clicking the link from within your email notification, or by logging in to Smartling.

Go to Projects Dashboard.

Mouse over the project. Click View Project.

Click the name of the job to view the overall status of your request.

Hover over the progress bar to display the status of yourrequest by workflow step.

Download Completed Translations (New Experience)

In Smartling, click Projects and select your job.

Click the name of your job.

Click theFilestab > Download Files.

Select how you'd like your translated files to be downloaded.

Subfolders for languages: Downloads a .zip file containing one folder per language for translated files. No language code will be added to the translated file name.

Languages in file names: Downloads a .zip file containing one file per language for each file in your translation job. The language code will be added to the translated file name.

Subfolders for languages and languages in file names: Downloadsa .zip file containing one folder per language for translated files with the language code in the file name.

ClickDownload.

Download Completed Translations (Classic)

You can download completed translations.

Go to Project Dashboard. Select the project.

Click Jobs (or click the link from within your email notification).

Click More >Download Files.

Select how you'd like your translated files to be downloaded.

Subfolders for languages: Downloads a .zip file containing one folder per language for translated files. No language code will be added to the translated file name.

Languages in file names: Downloads a .zip file containing one file per language for each file in your translation job. The language code will be added to the translated file name.

Subfolders for languages and languages in file names: Downloadsa .zip file containing one folder per language for translated files with the language code in the file name.

ClickDownload.

Enable project notifications to be notified when translation requests are complete.

This article is for Account Owners and Project Managers.

Idle strings are strings that have remained in a workflow step for longer than intended and are blocking the translation process. Idle string rules are a component of dynamic workflows that prevent idle strings (and workflow steps) from becoming a bottleneck.

They do this by:

Sending a reminder email to users that strings are idle.

Submitting strings to the next workflow step after a specified number of days.

Sending a confirmation email after submitting the strings.

Working with idle stringsSince moving strings back to a previous workflow step can be labor-intensive, Smartling recommends setting up procedures to ensure that only idle strings which should be moved forward are affected. Consider configuring your rules to send email reminders to Account Owners and Project Managers before strings are submitted.

Add an Idle String Rule

On a supported workflow step (Edit, Review, or Post-Machine Revision), click the down arrow and select Manage Step.

In the dialog that appears, turn on Idle Strings.

(Optional) Select Only count weekdays.

Click Add New Rule.

In the menu, select the Language(s) for which you want to create the rule.

In the menus, specify when to Send Reminder Email before the string is moved and when to Move String to the next step.

Under Reminder Recipients, add the email addresses of the users you want to remind. Optionally, select Send emails to Linguists assigned to step.

Click Save.

Delete an Idle String Rule

On a workflow step with an idle string rule, click the down arrow and select Manage Step.

In the dialog that appears, under Idle Strings, do one of the following:

To delete all idle string rules, turn off Idle Strings.

To delete a single rule, click the trash can icon.

Click Save.

Integrations with Smartling are most effectively accomplished by using standard resource files. See the complete list of supported file types. Assuming that Smartling doesn't have a connector for your platform, the best practice for API integrations is to choose the "natural" resource file format for your platform or tech stack.

For example, for Android applications (the Android XML resource files) and for iOS strings, the (.strings or .xliff file formats) are supported by those platforms.

For web applications, developers should use, if available, standard localization features that are built into the part of the stack that is being localized. For example, Java supports standard localization with Java property resource files. Alternatively, developers can choose a localization library that meets their needs. For example, localizing your React front-end with React INTL.

In the rare exception that no standard localized resource format is available, then we recommend choosing to serialize the content in JSON or XML, which are flexible and easily map to databases if your content happens to be stored in a custom database. CSV and Excel are never recommended because they are the least suited to localization and translation (even though they are commonly used for that purpose).

Upload Content

Here's a simple example of uploading your file to Smartling:

curl -X POST -H "Authorization: Bearer {token}" -F "[email protected];type=text/plain" -F "fileUri=file.properties"-F "fileType=javaProperties" 'https://api.smartling.com/files-api/v2/projects/{projectId}/file'

The above example will upload your Java properties file directly into the Smartling project identified by the {projectId}. Smartling will ingest this file, parse out the keys and texts as strings for translation. At this point, content is ready for translation.

There are several different options that can be used when uploading content into Smartling.

Want to translate specific placeholders?See JSON - Default Placeholder Format.Only want certain paths of your XML file translated? See Custom XML - Specifying Paths.Are you using ICU Message Format?See ICU Message Format.

For a full spec on file upload, consult the Files API.

File Type

If you're just starting to work with Smartling, we recommend that you review the documentation for the file type that you plan to use in order to better understand how that file is handled, by default. Then, upload some example files and review them in the Smartling Dashboard to confirm that the strings were created as you expected. Some items to keep in mind:

The correct number of strings were extracted.

Placeholders were correctly recognized.

Other metadata is reflected the way that you wanted (such as string instructions, keys, and special cases, such as plural strings).

Try downloading the "pseudo translation" of the files to see what they might look like once they've gone through the translation process.

If the file doesn't capture and deliver the way that you thought it would, review the documentation for that file type to see which Smartling directives are available. These directives can change how your file is processed and the translated version is delivered. There are two ways to implement directives:

Directly in the file (inline) -OR-

As options (parameters) to your API call.

The syntax of a directive to get a specific result might be slightly different when they are set as API parameters versus inline, inside of the file, due to requirements of escaping in the different contexts.

Download Content

Here's an example for downloading your translated file, using the Smartling Download File API.

curl -H "Authorization: Bearer {token}" "https://api.smartling.com/files-api/v2/projects/{projectId}/locales/{localeId}/file?fileUri={your-file-Uri}"

The above example will download your translated file for a locale of your choice. You can request your translated file at any time.

Typically, customers upload their file with a callbackUrl, and Smartling will make a call out to that callbackUrl when your file is 100% translated, or, they poll and check the file progress before downloading their file. Find out more about callbacks and of your file.

Ready to use the Files API?Click here.

2019 December

Dashboard

Idle String Rules - You can now build workflow rules that remind users about idle strings and move them to the next step after a specified period of time.

CAT Tool

Plural Quality Check : A new quality check notifies you in the CAT tool when any of the forms of a plural translation are the same as another form. The quality check does not run if the target language requires only one form.

2019 November

Dashboard

Job Automation : You can now schedule automated jobs to run every two or three weeks.

CAT Tool

Improved Dynamic Workflow Notifications: We now provide more useful notification emails about idle strings by including links to the project or job, as well as links to the string in the CAT tool.

Connectors

Sitecore Connector : You can now submit the children of children of a new data source with our Sitecore connector, which allows you to ensure that all related content is included in a translation request.

AEM Touch Connector : You can now translate multiple content fragments simultaneously.

File Types

DITA : We now support the .ditamap file type.

Developers

New Java SDK: Build your Java integration with Smartling through a new Java SDK that includes APIs for Authentication, Jobs, Jobs Batches, Issues, and Locales. You will temporarily need to use the prior SDK in addition to the new one to access Files.

2019 October

Dashboard

Itemized Repetitions - String repetitions are now itemized in cost estimates and word count reports.

Unique Job IDs - All Smartling jobs are now labeled with a unique ID that can be filtered for on the Jobs page.

Changes to Jobs:We will no longer add previously published content to any new job that you create. In addition, we will no longer remove content from a job when you close it.

CAT Tool

MT/TM Pre-population Threshold - You can now set a fuzzy match threshold in the CAT tool, below which machine translations are pre-populated and above which translation memory matches are pre-populated. This feature is configured in the translation workflow step and overrides linguist-specific preferences.

Developer

Issue Webhooks - Customers can now specify a callback URL to which Smartling will send all issue events. Information sent includes the project ID, event type, issue ID, string hash code and other issue data.

2019 September

Dashboard

Filter Strings by Assigned User: Filter for assigned or assignable users on the string level.

Clickable Links in Job Descriptions : Add clickable links to job descriptions on the Job Details page.

Delete Cancelled Jobs: You can now delete cancelled jobs from the Jobs Dashboard or the Job Details page.

Get Short URLs: In the "Help" menu, Click Get Short URL for this page to copy a short URL from Smartling to your clipboard.

Add a Watcher to an Issue via Email : Add a watcher to an issue from the To: or CC: sections of an issue email.

Issue Type Filter in Strings View : Choose between Source and Translation issues with the new Issue type filter in the Strings View.

Assign Issues: Assign an issue to a resource with the new Assign to drop-down menu. In the Issues Report, filter for assigned issues with the new Issue Assigned To filter. These features are available to Account Owners and Project Managers.

Language-Specific Glossaries: Glossaries can now be tied to individual target languages.

Case Sensitivity in Glossaries: Glossaries now support case-sensitive text matching.

CAT Tool

New Issue Keyboard Shortcut: Open new issues for any string with a custom keyboard shortcut that you set.

2019 August

Dashboard

Respond to Issues via Email: Comment on issues and send file attachments directly within your email client.

QA Report by Job: Run a QA report across an entire job.

Blacklist Term Management: Filter your blacklisted glossary terms by text and locale, and create and delete blacklisted terms as needed. Export and import your blacklist as well.

Strings View: An improved user experience to confirm your bulk actions.

Cost Estimates: Generate accurate cost calculations for non-Published types of SmartMatch.

Connectors

Contentful Connector: When you request translations, you are now asked to specify a (new) job to package that content. Once your job is created, you can review and authorize the job.

2019 July

Dashboard

New Experience Updates:

Strings View - Easily identify and manage unauthorized strings by showing source strings only

Added support for Eloqua and Salesforce Marketing Cloud

Job Custom Fields: Add additional data to your translation jobs, such as department name or description.

Translation Memory Management: Find and Replace - Keep your translation memory clean by finding and replacing strings in your TM in bulk.

CAT Tool

Increase CAT Tool search speed by 3x.

Find and resolve open issues with enhanced filters. Filter by save status and issue status.

Plugins

Sketch Plugin: Original Sketch file is attached to the Job for troubleshooting or desktop publishing

Smartling Draft (NEW!): Standardize source content by repurposing words and phrases from your linguistic assets. Available as a Google Docs extension.

2019 June

Dashboard

New Experience: Unified design and code refresh for faster, more scalable, and more flexible navigation and API-driven actions.

Dynamic Workflows: Automatically direct content to a step in one workflow path or another, based on pre-set conditions.

Roles and Permissions: Grant permissions to linguists and agencies to add, edit, delete, export, and manage various linguistic assets.

2019 May

Connectors

Contentful Rich Text Format : Retain rich-text formatting from Contentful source content when creating translations.

2019 April

Dashboard

Quality Check Severity Warnings at the Segment Level: Now easier to see which sentences need users attention

2019 March

Dashboard

Markdown : We now support GitHub flavored markdown files.

Quality Checks : New quality check that verifies whether or not the source string punctuation is consistent with what's in the target.

Enhanced Quality Checks: Added support for glossary compliance

Developer

Vendors API: Enables LSPs to easily view the list of open jobs in your account

Reports API: Enables users to pull translator word count analytics for invoicing and tracking purposes

Connectors

HubSpot Blog: API-key integration to easily submit and retrieve translations for blog content

2019 February

CAT Tool

CAT Tool Overview : Added the ability to autocomplete glossary terms, tags, and placeholders when working in the target field of the CAT tool.

Dashboard

Quality Checks : Added a new quality check that sees whether the capitalization in the source is consistent with what's in the target.

Strings View : (BETA) Access strings via Projects and Jobs.

2019 January

CAT Tool

CAT Tool Overview :Added ability to pop out the context view into a separate window, as well as ability to reposition the context view options (gear wheel) to a different area within the context view.

Customize CAT Tool Behavior :

In your CAT tool preferences, you can:

Set your translation options to auto-propagate updates across all pages (instead of just the current page), provided that your content is in a job.

Pre-populate machine translations if there's no TM match available over 100%.

CAT Tool Overview :Smartling does a glossary match of different forms of a word (such as run, ran, running). For example, in the source, the term "currency" will match against "Currencies" in the glossary.

Dashboard

Request Translations Using Jobs : You can now gain insight into events that occurred within your job(s), via the History tab.

Jobs Dashboard for Agencies : Jobs are automatically updated every 3-hours, however, you now have the ability to refresh the data when needed. The Expand Languages feature has also been implemented allowing you to see each language for each job, along with its associated word count.

Quality Checks : Added a new quality check that verifies whether legal symbols in the source were used in the target.

Screenshots : Ability to add context (JPG and PNG files) to your string(s).

Plugins

Sketch : Added ability to preview strings when submitting content, and the ability to select multiple languages when retrieving translations. In addition, you can authorize content from within Sketch (for all languages only). For specific languages, authorization is performed in the Smartling dashboard.

2018 December

CAT Tool

CAT Tool Overview : Added mobile responsive context for translation resources to be able to view what context would look like on a mobile phone or tablet.

Search Translation Memory : Updated design for the external TM search window.

Insert, Remove, or Move Tags and Placeholders : Added ability to insert formatting tags in the target.

Dashboard

Screenshots : For context, you can now upload multiple images (up to 100 images) at once. Each file cannot exceed 10MB.

QA Translations : Added the Glossary Compliance check.When a source string contains a glossary term, this quality check will check if a glossary translation was or was not used.

Choose a Translation Method : Added a new third-party provider: Amazon Translate.

String Changes Report :The String Changes Report allows you to view and download the history of changes that were made to a translated string.

Fuzzy Match : Unedited fuzzy matching is shown with a lighter, italicized font.

2018 November

CAT Tool

Search Translation Memory (Concordance Search) : Added ability to pop-out Search TM to perform a concordance search and view context at the same time. Useful if you're using an external monitor.

Dashboard

Capture Content : For Global Delivery Network projects,all content that passes through the proxy will appear pseudo-localized, allowing you to simulate a translated website before any real translation is done.

Manage Issues Via Slack : This integration enables you to send Smartling translation issues to a Slack channel and take action on them from within Slack.

Exclude Content From Translation and Restore : "Unexclude" strings by restoring and authorizing them.

Developer

Callbacks : Callbacks for pre-published strings and files.

2018 October

Dashboard

Manage Issues : Ability to add an attachment to an issue.

Customize CAT Tool Behavior : Added setting to automatically save auto-propagated strings.

Search Translation Memory (Concordance Search) : Added Exact Match setting in concordance search.

2018 September

Connectors

AEM Touch Configuration for Version 5.0 : There are new AEM Touch configuration procedures if you are planning on migrating to AEM 6.4.

Developer

JSON : New file directive: character_limits

CAT Tool

CAT Tool Overview :

Added the ability to export bilingual translations for third-party review. ( QA Export )

Added keyboard shortcut for Submit All and Submit Saved Translations. ( Submit Translations )

Dashboard

View Translation History : Added a new "Revised in Publish" filter which allows you to find content that was edited while in the Publish step.

Jobs Dashboard for Translators and Editors : Added ability to export content and import translations.

Insert, Remove, or Move Tags and Placeholders : Added ability to automatically place tags from source to target, in its correct position. (Currently only available for French translations.)

2018 August

Developer

Automatically Create a Job Upon File Upload : When using certain parameters for uploading files, your content goes into the translation queue upon file upload, and strings from the file will automatically be added to a job.

CAT Tool

Save and Submit Translations / Proofread Translations : Translators, Editors, and Reviewers can now save certain strings at once. For Editors and Reviewers, the "Confirm" button has now been renamed to "Save".

CAT Tool Overview : Ability to automatically replace standard straight quotes with smart quotes - German and French only.

Dashboard

Translation Memory Management : You can now search across multiple translation memories.

View Translation History :Allows you to find content that was edited while in the Publish step.

2018 July

CAT Tool

Save and Submit Translations : Ability to save/submit certain strings at once.

Dashboard

Jobs Dashboard for Translators and Editors : Enables you to view all of your tasks in one place, and easily find those which have a higher priority.

Export Content to CSV : Export and download translations as a CSV file to easily sort and view content in spreadsheet format.

Configure Quality Checks : Added a new quality check - insertable consistency - which checks for the presence of break tags, non-breaking spaces, newline characters, word joiners, and zero-width characters.

Jobs Dashboard for Agencies :At any point in time, you can run a fuzzy estimate and download it as a CSV file.

Request Translations Using Jobs : Ability to view strings from within a job.

2018 June

CAT Tool

Customize CAT Tool Behavior : Ability to auto-propagate all matching drafts and saved translations when a 100% repetition is updated.

CAT Tool Overview : Toggle between uppercase, lowercase, and the capitalization of the first letter of each word.

Dashboard

Respond to Questions from Linguists : Ability to add email watchers to "watch" when an issue is opened, commented on, or closed.

Translation Memory Management : Ability to search within a TM, move content between TMs, export or delete content, and insight into the history of a string.

Manage Issues : Any email address can be added as a watcher to receive notifications about an issue being opened, commented on, or closed.

Context Crawler : Allows you to easily grab visual context from your website by simply entering the URL of a website, and the crawler will then find the pages to visit on its own.

Application Files and Business Documents : When uploading files and requesting translation, you will be required to add your content to an existing job, or a new job, before authorizing the content.

Translate Glossary Terms : When glossary terms are authorized for translation, they're packaged into a job.

Request Translations Using Jobs : Run a "refresh estimate" on jobs in progress to show the cost for all content within a job.

2018 May

Dashboard

Jobs Dashboard for Agencies : Easily see all jobs from your customers, across all accounts.

Connectors

Sitecore release 1.7.1 : See Downloads for the latest version.

Developer

GitHub Connector : Added ability to automatically authorize all jobs. (For Enterprise customers only.)

2018 April

Dashboard

Quality Confidence Score : A fundamentally new approach to Quality Management.

CAT Tool Find and Replace : Quickly find and replace translations within a specific workflow step.

Configure a Workflow Step :When making an edit to either the Editing or Internal Review step, you have the option to skip either step.

Insert Tags or Placeholders : New shortcut to insert next tag or placeholder.

2018 March

Dashboard

Inactive Strings : Better defining how inactive strings are handled.

Jobs : New UI for the Jobs feature for Account Owners and Project Managers.

Connectors

The following connectors now support adding content to a new or existing job: Drupal 8 TMGMT Connector, Drupal 7 Classic Connector, and the WordPress Connector.

Developer

XML : Added two new directives: character_limits_paths and instruction_paths.

2018 February

CAT Tool

Missing Tags : Tags that have not been placed in the translation field will be shown in red in the source.

Special Characters : You now have the ability to quickly insert special characters in the target field of the CAT tool.

Dashboard

Sketch Plugin : New version of the Sketch plugin. Fixed issues with applying styles and new line characters.

Manage Issues : In addition to downloading the Issues Details Report, you can now view and manage all issues from within the Smartling Dashboard.

Connectors

Contentful Connector : The Contentful platform lets you create, manage, and distribute content to any platform. Contentful customers are interested in a seamless approach to translating their content and media asset types. The Smartling Contentful Connector facilitates the translation process.

Sitecore Connector : Upgrade to version 1.6.0

Developer:

XML : Added new supported format (block) to string_format_paths directive.

2018 January

CAT Tool

Added percentage to fuzzy match score.

Fixed an issue where fixing a QA error for a segment removed the QA status for the whole string.

Moved string instructions to the editor.

You can now jump to a particular page by typing the starting page number.

Reorganized keyboard shortcut menu.

Resolved issues are now shown more visibly on a string.

Machine translation now has a dedicated shortcut.

It is now possible to drag placeholders and special characters.

Dashboard

Emergency Contact Info : You can add an email address in Smartling in order to receive notifications about important system status and maintenance.

Filter by String Properties- SEO Content :Allows you to easily find and handle SEO content.

File Versioning (For Essential, Basic, Pro, Business): Smartling automatically versions your file uploads.

Developer

GitHub Connector :If your localization resource files are in a GitHub repository, the Smartling GitHub connector may be the ideal option for automating the process of sending source files to Smartling, and getting translations into your repository, where you need them.

HTML File Variants Support :HTML files uploaded via our API supports thedata-sl-variantattribute, similar to our Global Delivery Network (GDN).

2017 December

CAT Tool

Fixed an issue in FireFox where the cursor jumped to the end whenever selecting a segment that was inactive.

Added a filter for unresolved issues.

We now show the number of comments pertaining to an issue.

We rearranged the comment box in Issues so that comments are more noticeable.

Fixed an issue where adjusting the height of the side panel in one browser window unset changes made in another browser window

Implemented a number of improvements for editing speed on large strings.

Added a user preference to stop the string list from automatically scrolling.

Added a user preference for font size.

Dashboard

ICU Message Format :Smartling supports standard arguments (a.k.a. placeholders), as well as 'select' and 'plural' arguments. The following items will not be supported: 'selectordinal', nested 'select' and 'plural', and plural strings with multiple plurals. If you are currently using MessageFormat or considering using it, contact your Smartling Customer Success Manager to review your files and ensure compatibility.

Offline Work for Jobs : To enable taking jobs offline, Account Owners can contact their Customer Success Manager. Once the feature is enabled, Translations Resources will be able to export a job to work offline, and then import the translations back to Smartling.

2017 November

CAT Tool

Keyboard Shortcut :Added keyboard shortcut to close pop-up window: Tab key + Enter.

Bulk Save : Continuous improvements to bulk save.

Dashboard

Video Context :Media projects now support translation using YouTube videos as context.

Chrome Browser Extension for Capturing Context:Now has a standard Smartling login form.Therefore, it supports sign in with Google and also better handles difficulties with logging in (for example, a forgotten password).

2017 October

CAT Tool

Tags : Click and drag tags in a segment without breaking HTML code.

Dashboard

CLI :For API v2, replacing the command lineBASH scripts with a CLI tool. (Alpha)

AEM Classic Connector :Changes to original content won't affect locked translated sections.

2017 September

CAT Tool

Quality Check Severity Errors: Improved experience of Medium Severity Errors. As part of our continuing work to improve how bulk save works, medium severity errors now have new buttons: Fix Later and Save Anyway. Selecting either button will let you immediately move on to the next string instead of stopping the the queue of strings to save.

TM Matches: Fixed an issue where TM matches were sometimes not repopulating on page load.

Plurals:Fixed an issue with plurals where the string status (check mark) was not getting updated when a user was editing other forms.

Dashboard

N/A

2017 August

CAT Tool

Personal Dictionary : Add words that you know are correctly spelled.

DQF : Evaluate, track, and benchmark translation quality within the CAT tool.

Resize Panels: You can now resize the height of panels. For example, the height of a panel (such as the Language Resources panel) can be modified by clicking and dragging the top or bottom edge of the panel.

Severity Errors: All high severity errors are batched together for bulk save. Theyll be shown at the end of the save process after all other strings have been saved.

Drafts: Improved how we handle empty drafts.

Save and Submit: Save All and Submit buttons are split into two separate ones to make those actions clearer.

Glossary: Fixed an issue that was preventing glossary terms created in character-based languages from being highlighted.

Unconfirmed Strings: Fixed an issue around the number of unconfirmed strings being shown in the CAT tool.

Badges: Number of badges in the sidebar is only shown if the number is greater than 0.

Spellcheck: Fixed some usability issues with the add to dictionary/spellcheck popup.

Copy Only Tags: Fixed a bug around copy only tags. If you press the copy only tags shortcut, and there are no tags in the target, we no longer delete the translation in the target.

100% Matching: Fixed an issue with 100% matching when comparing strings with different segmentation but matching content.

Pre-Populate: Pre-populate TM matches used to only be available for 100% matches. Now, Translators can set any Fuzzy Match threshold they want to populate TM matches.

Dashboard

Predictive Typing :Allows you to see in real-time next word alternatives.

MT :Improve the quality of machine translations through an approach that combines human translations with machine learning (adaptive machine translation).

Jobs : New navigation and feature enhancements to Jobs. For now, this is being rolled out to new enterprise clients.

Search and Replace : Content search and replace allows you to perform a "find and replace" on your translated strings.

String Search: Search for a string by the date it was added/uploaded.

Content Velocity Reports : The Content Velocity by Workflow Report (data is grouped by workflow) and the Content Velocity by Locale Report (data is grouped by locale) provide insight into the average amount of time that a word or a string spends in a particular workflow step from content authorization to publishing.

Content Changes Reports : The Content Changes by Workflow Report (data is grouped by workflow) and the Content Changes by Locale Report (data is grouped by locale) provide insight into how much content is actually changing in each step of a workflow.

Badges: Only red number badges are shown in the resources panel if there are more than 0 items.

Fixed usability issues with the spellcheck suggestion/add to dictionary pop up.

Fixed a bug around strings getting a lower TM match than it should have.

2017 July

CAT Tool

Quality Checks:

All error" tab in Quality Check report is now the same color as the highest severity level in report.

Quality Check Report tabs are now sorted by severity level.

Quality Check Report tabs with 0 errors are now hidden.

Korean Language: Fixed an issue with Korean language translation.

Pre-population: Fixed an issue with pre-population of 100% matches (edited).

Adding Glossary Terms: Glossary terms can now be added with a new button in addition to the keyboard shortcut. Highlighting text in the source will now reveal an Add to Glossary button.

Dashboard

Wordpress: Added UI to control logging - on/off and to pick the folder where logs are stored.

2017 June

CAT Tool

Adding Glossary Terms: Glossary terms can now be added directly in the CAT tool.

Filtering: It's now possible to filter the CAT tool. Available filters include: workflow, job, translation status, files URI, tags, and keyword.

Quality Checks Panel: Added a Quality Checks panel to show translation errors per segment.

Speed: Improved speed of the CAT tool on big strings.

Bulk Save: Fixed a bug with bulk save.

MT: Added the option to hide machine translations.

Font: Updated the CAT tool font to Google Noto Sans and gave users the ability to change the font in their editor.

Dashboard

Video Context : Videos can now be adding as context (with SRT file).

Reference Code : Reference Code field added to Jobs.

Dynamic Quality Framework (DQF) : Support for TAUS' DQF - a quality framework.

Reconnection: Added reconnection when connector is disconnected from CMS Gateway, in order to not have missing context for some pages.

Locale Mappings: Extended default locale mappings for non-standard locale `es_la=> es-LA`.

Launch Title: Fixed issue with automatically generated launch title being too long. AEM has restriction on length of launch title. During launch title creation, unique data is added at the end of the title and is cut according to AEM rules. If page title is too long, we had an issue with creating the same launch title during the creation of the following launch title.

JSON: Added JSON Properties HTML Decoder component in order to fix broken value of JSON properties.

Job Name: You can now show the Job Name in the Content/Translations List by clicking on the gear icon and selecting "Show Job Name."

Issues: Issue Details Report allows for a download of all issues data.

Marketo: Marketo Programs are now available for translation along with other types of assets.

2017 May

CAT Tool

Offline CAT: Available for agency owners and translation resource managers. Previously, this was only available for translation resources.

Edit Glossary: Ability for user to Add/ Edit glossary term.

Added user-defined character limit to quality checks.

Added ability to turn on check for no emojis in quality check settings.

Fixed spellcheck for capitalized words in German.

Improved CAT tool performance with large glossary load.

Fixed glossary popup getting obscured by other parts of CAT tool.

Improved experience for selecting and dragging words in editor.

Fixed copying source to target only inserting last segment in multi-segment strings.

Fixed issues with launching CAT tool after selecting Do not show this message again.

Fixed HTML entries not showing in autocomplete.

Fixed constant repositioning of scrollbar during bulk save.

Fixed poor performance of Next Tag keyboard shortcut.

Fixing resetting of custom keyboard shortcut profile on switching projects.

Updated TM fuzzy scores to be consistent with old CAT tool experience.

Fixed bulk save order to be consistent with string order.

Fixed false empty string detection when segment has only tags.

Fixed copy source to target when segments have been merged.

Improved page load performance.

Fixed HTML tags being counted in string length.

Fixed full width question mark being treated as emoji in ZH-TW.

Fixed autocomplete suggestions for tags/ placeholders overriding save and next string shortcut.

Fixed HTML rendering of styleguide and special instructions.

Fixed discrepancy in total spelling errors shown in the editor and the QA report.

Fixed QA error being displayed spelling errors surrounding tags.

Added string-level check for character count limit.

Fixed character counts to be based on plural forms.

Fixed certain Polish characters not being recognized in CAT tool.

Fixed CAT tool not scrolling to active string selected in List View.

Fixed strings not loading for certain old content.

Corrected ability to use standard shortcuts (Cmd C/V) to copy-paste source into target.

Updated in-line quality errors for double spaces to single spaces for character based languages.

Added string hashcodes to additional information.

Fixed spellcheck popover requiring two clicks to open, when cursor is not at end of segment.

Improved UI for leading/ trailing space errors.

Fixed tag order not being saved correctly on submission.

Fixed editor not focusing on current string, when user clicks on padding in the input segment.

Improved offline recovery/ messaging.

Resolved some tags not inserting via keyboard shortcut.

Standardized formatting of all dates in CAT tool.

Dashboard

New SmartMatch setting added to leverage translations that aren't fully published. Useful for translations that were deleted while In Progress and not fully Published.

GDN: JSON parsing directives can now be passed as HTTP headers - in addition to directly in JSON.

2017 April

CAT Tool

100% TM match pre-population enabled.

Enabled new CAT tool for admin approval step.

Fixed performance issues for Microsoft Edge.

Fixed Issue count bubble not changing when using the Issue resolved toggle.

Resolved translators getting errors when fetching workflow data for a string outside their workflow step.

Fixed adjacent placeholders/ tags not being tokenized appropriately.

Fixed translators not being able to insert characters D and M.

Added keyboard shortcut hover-over for Restore Segmentation command.

Autoscroll jitter for Video translation fixed.

Quality Check Tools allow for management of quality errors in the CAT tool.

Quality check settings improved for business documents.

Fixed progress bar to show correct progress for Edit/ Proofread step.

Decoupled Reject action from Confirm action across all workflow steps.

Restricted Confirm action to only be available in post-translation and admin approval steps.

Fixed error thrown when glossary shortcut is used when no glossary exists for linguistic package.

Fixed non-functioning Custom status for string filters.

Improved memory management for context.

Formatted TM results to be the same as Glossary search results.

Reviewer can submit content, even if it is locked from editing.

Fixed incorrect focus on string on page load, if CAT tool loaded from any point other than list view.

Fixed context not loading when user clicks on source.

Resolved spellcheck not functioning for multiple languages, including Hungarian.

Fixed merge functionality for document translation.

Fixed only saved strings to be submitted on Submit action (previously also Submitting Draft strings).

Improved tag insertion/ resolved tag inconsistency error performance.

Improved quality check warning to show the highest severity associated with a string.

Dashboard

First release of design tool plugins: Sketch, Adobe Photoshop, and Adobe Illustrator. Sketch has some additional functionality to be able to automatically submit content and context to Smartling using your Smartling account. Adobe Photoshop and Illustrator will have this functionality in a forthcoming release; for now, source content is exported as a file and translated content is imported back in as JSON. All three plugins support pseudo translation.

Powerpoint files uploaded to the Dashboard now have options for selecting slides, master slides, and notes.

Exporting translation memory now has the ability to select multiple languages for download.

Character limits can now be specified in iOS and Android resource files. The specific values from the files will be set on the string. Example for iOS Strings:

/*This is an instruction*//*smartling.character_limit=25*/"thisis.a.key" = "This is a string";

2017 March

CAT Tool

Launched shortcut for Save and Next String.

Enabled full emoji support in new CAT tool.

Made language resources insert shortcuts customizable.

Introduced messaging for possible slow performance when list contains large strings.

Improved shortcut hover-overs: Now show if shortcut is not set and needs to be updated.

Improved double-spaced false positive errors in certain connector projects.

Fixed TM source showing No source specified.

Renamed double-space quality check to whitespace check, to account for Asian languages.

Fixed broken context when image tag appears in source in word documents.

Corrected in-editor spacing errors to account for target locale.

Corrected validation for issue type presence on issue create: fixed Creating Issue message.

Improved string loading behavior in the presence of large glossary updates.

Fixed problem inserting << due to conflict with keyboard shortcuts.

Fixed incorrect missing tags error message, even when tags inserted properly.

Made string order in CAT tool consistent with string order in List View.

Fixed tag insertion order when source HTML is broken.

Improved handling of `</br>` as a special character.

Added source content display to glossary in language resources.

Fixed video replay restart when video does not start at 00::00::00.

Improved background display of progress with bulk save/ submit.

Limited number of language resources available via keyboard shortcut to 10.

Corrected keyboard shortcut actions to use i18n.

Fixed default keyboard shortcut inconsistencies between classic and new CAT tool.

Added tooltip hints for copy tags to target.

Improved loading of history and issues panels.

Dashboard

Assign All button has been added to make it easier to assign all content to a single resource.

Word Count Report to view by translation resource in addition to Language and Job.

iOS Files: The `includeOriginalStrings` parameter has been added to support iOS .stringsdict and .strings files.

An addition to the Eloqua connector to allow for automatically rewriting content as it moves from Smartling to Eloqua. The primary use case is to replace phone numbers, email addresses, and other blocks of content to localize it for a particular market.

Build rules to automate how content is packaged into a job through Job Automation. Rules can include or exclude files or URLs, be built for specific languages, and more.

Wordpress: New 1.4.4 release which brings the new way how to register custom post types for localization- no custom code has to be written - just describe what should be localized in the custom post type and the rest will happen automatically. Also extended integration for Wordpress "shortcodes." This was done for upcoming release of Divi Builder localization. In addition, improved memory and CPU usage. Wordpress Connector works only when content editor submits content from Wordpress Admin UI so loading of connector's code by Wordpress when page is rendered for site visitors has been removed.

2017 February

Dashboard

TM Leverage Report: See how much content has benefited from leverage of Translation Memory.

Mobile Context Library easily takes screenshots of app screens in iOS and Android.

Demandware: Addresses issue in applying translations when Demandware does other concurrent updates of products in background (backup; replication stg prod). Background tasks (for uploading and downloading content) were switched to a new Demandware platform version. Continue refactoring which is required to switch on FAPI v2. Also added Test Connection button in Smartling settings.

Repository: Improvements in SVN flow - it's more robust in case when workspace is in broken state (previous operation failed because of network; security; etc). For Git flow, added validation that workspace is in consistent state. Can be useful for troubleshooting. Also updated validation pattern for client locale code. So now a customer can use any string as client locale code (length: 1 to 50).

Sitecore: Introduced presentation layout customization per language. It means that content editor can adjust presentation (add personalization and so on) for every language without involving developers. We added native support for this feature. Also added the new Sitecore WF step which allows a customer to submit an item to all configured locales. So if client uses WF then upload to Smartling can be just a part of his WF and no need to send content to Smartling explicit. Every new content, or updates in content will be submitted to Smartling automatically.

Wordpress: Released an additional plugin for Wordpress. The core plugin supports translation of built-in WP types including simple customizations, but almost every website uses additional 20-30 plugins which extend WP functionality. And some of these plugins use custom storage for content. The new plugin, Smartling ACF Localization, allows a customer to translate content created by popular ACF plugin (1M+ installations).

2017January

Dashboard

GDN:sl_path_notranslateJSON directive was implemented. It enables XPath for notranslate functionality in JSON.

Word Count: Word Count Report broken down by job.

Content Changes by Workflow Report: Shows how workflow could be optimized by removing steps where few changes are made.

Content Velocity Report:Identifies bottlenecks to optimize workflow.

AEM Classic Connector: New URL Rewriter: Covers more cases and default behavior. Rewrites everything that is possible and exclusions can be configured. Simplified Integration: For those who built automation on top of Classic connector we simplified integration. Now required input parameters are more straightforward.

Eloqua: Added ability to translate 2 new asset types: emails and landing pages.

This article is for Account Owners and Project Managers.

Once you have created a project in Smartling, you can always add more languages when necessary.

Add a Language to a Project (New Experience)

From within a project, click the gear icon on the right side and select Project Settings.

Click Add Languageto display the Add Languages dialog.

Select a language from the list.

Select a Default Translation Workflow.

To learn more about changing translation workflows, go to Change a default workflow.

Select a Translation Authorizationas follows:

Authorize all active strings

I'll decide later

Synchronize with a language

Click Add.

Add a Language to a Project (Classic)

Go toProjects > Content > Summary. In the Summary view, you'll see a list of all languages that are currently part of the project.

To add a new language to the project, click +Add Languages within the Languages section.

After you've added a new language, keep these next steps in mind:

Make sure that you have translation resources assigned to the new language. Contact your Smartling Customer Success Manager (or your third-party translation vendor) to ensure they are ready to assign resources for a new language.

Choose the correct default workflow for the new language.

Assign a style guide for the new language.

Customize the leverage configuration and SmartMatch settings for the new language as needed.

Translate your glossary terms into the new language.

Enter the per word or per hour rates for your new language in order to run accurate cost estimates.

Request translations for your new language.

Extension

.xml

Smartling Identifier

xml

Example File

customxml.xml

Resources

XML Standards

Smartling supports XML 1.0 files by processing text within specified tags and attributes. You must specify the tags and attributes you want translated using the translate_paths directive.

Keys-Variants

Key and Variant metadata must be enabled and configured using the source_key_paths and variants_enabled directives.

Specifying Paths

Some directives require you to specify a path or set of paths to keys or strings in the file. A path is a slash-separated string which uses an Xpath-like syntax (although not all features of Xpath are supported). The node separator is always / (slash).

Wildcards are not allowed in path definitions.

To specify an attribute, use dot notation: node.attribute.

To specify paths based on an attribute value, use the syntax /node[@attribute="value"].

For the translate_paths directive, ending the path with a trailing / (slash) will also translate all child nodes.

For example, in the following file:

XML<data> <string name="home-button">Smartling Hotels</string> <string name="back-button">Back</string> <localize name="navigation"> <string>Browse Hotels</string> <string>About Us</string> <string>Site Map</string> </localize> <localize name="description"><string>An excellent budget hotel in New York City</string> </localize> <images> <img src="/img/0156849.png" title="Bedroom - Basic Suite"/> <img src="/img/0156849.png" title="Bathroom - Basic Suite"/> </images></data>

data/localize/string - will match Browse Hotels, About Us, Site Map and An excellent budget hotel in New York City.

data/images/img.title - will match Bedroom - Basic Suite and Bathroom - Basic Suite.

data/localize[@name="description"]/string - will match An excellent budget hotel in New York City.

HTML-like Files

Some XML files closely resemble HTML files and are more effectively translated by parsing them as HTML files. Smartling allows you to specify HTML as the file type when uploading an XML file in the dashboard to cope with this type of XML files. If uploading via API, give html as the Smartling identifier for the file.

Managing Untranslated Strings

If using File API to download Custom XML files from Smartling, the parameter includeOriginalStrings=false can be set to return an empty string if no translation is available. By default (includeOriginalStrings=true) Smartling returns the original string.

Standard Placeholder Format

See Placeholders in Resource Files for more on placeholders.

Directives

Format

<!-- smartling.[directive_name] = [value] -->

entity_escaping

Exact delivery depends on file type.

Values

auto (default)true (or yes)false (or no)

Description

Can control whether or not characters will be "escaped" into entities when delivering translations. This can be set universally for the whole file via API, or by setting the directive at the top/start of the file. The directive can also be placed inline to control the behavior of specific strings.

Examples

To use inline:<!-- smartling.entity_escaping = false -->

String:<!-- smartling.entity_escaping = auto -->

For example, your translation might look like this:Smartling HTML escaping < > & " example string4

By default, using the "auto" setting, we would assume this is HTML from the <hr> tag and it would be converted to:Smartling HTML escaping < > & " example string4

Using smartling.entity_escaping = false would allow Smartling HTML escaping < > & " example string4 to appear as it should.

variants_enabled

Values

true|TRUE|on|ON OR false|FALSE|off|OFF

Description

When enabled, Smartling will make strings unique using variant metadata. Must be used in conjunction with the source_key_paths directive, which provides the information needed to generate variant metadata.

If you have previously uploaded a file with variants turned off, and reupload the file with variants on, Smartling will capture all content as new strings. You can configure Smartmatch to automatically match the existing translations.

Examples

<!-- smartling.variants_enabled = TRUE -->

translate_paths

Values

A comma-separated list of paths to be captured as strings for translation.

Description

When included in this list, all plain text within the specified tag will be considered a translatable string. Optionally, you can append a . and a relevant attribute name to the path to translate tag attributes with the file. You can end the path with a trailing slash, / and it will treat all child nodes as translatable (content must still be text within a tag).

Examples

<!-- smartling.translate_paths = data/localize/string, data/localize.title, data/localize/root/ -->

Smartling will translate content in the data/localize/string & data/localize/root nodes. The title attribute of the data/localize node will also be translated.

string_format_paths

Values

The value of this directive is expressed as [format]:[paths].

Description

Specifies the format of strings for the specified paths and can enable HTML inside another file format.

Currently supported formats are:

HTML - string value will be parsed as HTML@default - (note the leading at-sign) string value will be treated as simple text.TXT - string value will be parsed as plain text with strings separated by new lines.block - passes all elements within the block as a single Smartling string.Separate multiple formats by commas.

You may specify a single path for a format or a comma-separated list of paths enclosed in square brackets. The list may be empty.

Examples

<!-- smartling.string_format_paths = -->

Disables the effect of the previous string_format_paths instruction.

<!-- smartling.string_format_paths = html: /product/description -->

Enables HTML in /product/description only.

<!-- smartling.string_format_paths = html: /product/description/ -->

Enables HTML in /product/description and all its child nodes.

<!-- smartling.string_format_paths = html: /product/description/, html: /product/title -->

Enables HTML in /product/description and all its child nodes, and the product/title node.

<!-- smartling.string_format_paths = block: /product/description -->

Enables block and everything inside of root to be one string.

placeholder_format_custom

Values

1) Custom Perl compatible regular expression.2) NONE - disables any current custom placeholders

Description

Specifies a custom placeholder format. Any text in your file matching the regular expression you provide will be captured as a placeholder.

Examples

<!-- smartling.placeholder_format_custom = \[.+?\] -->

Any characters surrounded by square brackets will be treated as a placeholder.

placeholder_format

Values

NONE; C; IOS; PYTHON; JAVA; YAML; QT, RESX

Description

Used to specify a standard placeholder format.

Examples

<!-- smartling.placeholder_format = IOS -->

Specifies iOS-style placeholders for the file.

sltrans

Values

translate OR notranslate

Description

Use this directive to enable or disable processing of translation strings in the file. You must turn translation back on after the strings you want to exclude.

Examples

<!-- smartling.sltrans = notranslate -->

Strings after this directive will be captured as strings but excluded from translation. (It is the entire string that is excluded, not just a portion of the string.)

<!-- smartling.sltrans = translate -->

Strings after this directive will be translated.

source_key_paths

Values

A comma separated list of paths to use create keys for strings on translate_paths.

The key will be a space separated string of all the keys leading to the source string. For example: string, group1 string.

Description

Used to define the schema for capturing a key for each source string. Keys are required:

If you want to import pre-existing translations from a file with the same structureIf you want to create variants of strings that would otherwise be duplicates (By default Smartling does not create duplicate strings.)Creating or updating variants for previously uploaded strings cause new strings to be created that will not have translations. The SmartMatch feature can be configured to automatically apply the existing translations, or translators can use the 100% match from the Translation to manually apply the translation.

Specify the full path to the value, then indicate which part of the path should be used as the key using {} notation.

Examples

<!-- smartling.source_key_paths = data/item/{string.name} -->

Smartling will capture the name atribute of the data/item/string node as the key.

<!-- smartling.source_key_paths = data/item/{string_name} -->

Smartling will capture the content of the string_name node as the key.

pseudo_inflation

Values

Integer - Accepted values are 0 - 100

Description

Sets the percentage by which original strings are inflated when downloading pseudo translations. If this directive is not set, pseudo translations are 30 percent longer than the original strings.

Examples

<!-- smartling.pseudo_inflation = 80 -->

Downloaded pseudo translations will increase the length of original strings by 80 percent.

instruction_paths

Values

Instruction text

Description

Instructions from XML file. Order is important. The element with the instruction must be a sibling of the corresponding element with the translation (as specified by translate_paths), and it must appear before the translation in the file.

Examples

<!-- smartling.instruction_paths = data/unit/instruction -->

(See code sample below.)

instruction_paths code example:

<data> <unit> <instruction>instruction text</instruction> <string>translation text</string> </unit></data>

character_limit_paths

Values

Integer - Values such as 10, 20, etc.

Description

Source string level instructions for character length. character_limit_paths point to elements that define character limits.

Order is important. The element with the limit must be a sibling of the corresponding element with the translation (as specified by translate_paths), and it must appear before the translation in the file.

Examples

<!-- smartling.character_limit_paths = data/unit/limit, data/sub-level/unit/limit, data/item/limit -->

(See code sample below)

character_limit_paths code example:

<data> <unit> <string id="id1">data 0</string> </unit> <unit> <limit>10</limit> <string id="id2">data 1</string> </unit> <sub-level> <unit> <limit>20</limit> <string id="id3">data 2</string> </unit> </sub-level> <unit> <limit>30</limit> <string id="id4">data 3</string> <string id="id5">data 4</string> </unit> <unit> <limit>40</limit> <string id="id6">data 5</string> <limit>50</limit> <string id="id7">data 6</string> </unit> <unit> <limit>60</limit> <string id="id8">data 7</string> <limit>NONE</limit> <string id="id9">data 8</string> <string id="id10">data 9</string> </unit> <item> <limit>100</limit> <text name="name1">data 10</text> </item></data>

smartling.force_inline_for_tags

Values

Tags such as: <ol>, <li>, <strong>, <icon>

Description

This directive allows for specified tags to be treated as inline tags (visible and moveable for translators and editors) versus block-level tags (creates a new string and are not visible).

Examples

<!-- smartling.force_inline_for_tags = icon, tooltip -->

Resource files often use placeholders in strings to allow dynamic information to be inserted into a string. For example: "Welcome %{username}, you have $%{balance} in your account". Smartling will recognize these placeholders and protect them from being translated, while still allowing the translator to position them as needed in the translated string. Placeholders are also known as formatting strings, format specifiers or just specifiers.

We recognize standard placeholders by default. Exactly what is captured as a placeholder depends on the file format. In most cases you don not need to customize this behavior if you are using standard placholders. If you are using a custom file format, have custom placeholder syntax or use non-standard placeholders, you can integrate to get the behavior you want. Integration can be performed either in the file or via the API. So-called file inline integration gives you extra customization options - for example, you may be able to change placeholder behavior throughout the file - but requires you to customize the file for Smartling. API-based integration allows you to avoid adding Smartling specific code to your file but will affect all the strings in the file.

Smartling offers two directives to identify the types of placeholders that are used in your files:

The placeholder_format directive lets you specify that your placeholders adhere to a common standard. Options are C, IOS, PYTHON, JAVA, YAML, QT, or RESX.

The placeholder_format_custom directive lets you specify custom placeholders using a regular expression. Any group of characters matching the regular expression will be captured as a placeholder.

Positional Information

For some standard placeholder formats, Smartling automatically adds positional information, so that if a translator needs to switch the order of placeholders, they will still work correctly. For example, if you upload the string A room at %s is reserved for %s., Smartling will capture A room at %1$s is reserved for %2$s.. Note that this will not be done for custom placeholder formats, so if you have more than one custom placeholder in a string, make sure that a translator can tell them apart. For example: A room at [hotel] has been reserved for [user]. is safer than A room at [var] has been reserved for [var].

Specifying Standard and Custom Formats

These two directives work in tandem. For example if you were specifying placeholder behavior inside of a custom XML file you could specify both:

<!-- smartling.placeholder_format = PYTHON -->

and

<!-- smartling.placeholder_format_custom = \[\[.+?\]\] -->

Both the standard Python style placeholders, and a custom placeholder will be recognized when found in a string. In this example the custom placeholder is delineated by having two open and closed square bracket characters with text in between them: [[firstName]].

Verify Placeholders

To check that your placeholders are being captured as expected, check the string in the List View in the Smartling Dashboard. Correctly captured placeholders will be highlighted:

Escaping

When defining the regular expression for a custom placeholder you may need to escape characters that are part of the expression to account for the environment (file or shell). After escaping is accounted for the expression will be evaluated as a Perl compatible regular expression (PCRE).

So, in the above example, because brackets have special meaning for PCRE they must be escaped with a backslash ()for the regular expression engine. However, in another context the backslash itself may need to be escaped.

The most common example is seen in JSON where the backslash character in the value of name/value pair already has special meaning for JSON, and so must be escaped to be valid a character in JSON. Also note when defining a custom placeholder inline of a JSON file we require the expressions to be listed in an array. So the above directives modified to be inside of a JSON file would be:

JSON

"smartling": {"placeholder_format" : "PYTHON", "placeholder_format_custom" : ["\\[\\[.*?\\]\\]"]}

Not Specifying Placeholder Formats

If your file has non-standard placeholders and you do not integrate to define them Smartling will capture the string with the placeholder as plain text; they will typically be counted as words for translation, translators will have to manually enter the placeholder using the correct syntax, and the Smartling CAT tool will not be able to warn the translators about missing placeholders or incorrect syntax.

This article is for Account Owners and Project Managers.

Strings View is a New Experience feature. To learn how to search for strings in the Classic Experience, go to Search within a Project.

In the Strings View, with a robust set of filters, you can quickly search across a large number of strings in a project to identify the ones you need. You can search in Translation Mode, which enables all filters, or in Source Mode, which enables only filters related to source strings and hides translation-related columns.

You can open the strings view from multiple places in Smartling with the correct view already loaded:

From a project Click the Strings tab.

From a job Under Job Summary, click View Strings.

For a job language In the Languages tab and Total Words column, click the View Strings icon.

For strings not in a job From the Project View, next to words not in job, click View Strings.

Strings View Filters

Search for strings with the filters on the left area. Reset your search with the link at the top.

Filter

Options / Definition

Status

Select and search by the following options:

Awaiting Authorization Strings are not yet authorized for translation.

In Progress Strings are authorized for translation but not published.

Published Strings are published.

Excluded Strings have been excluded from translation.

Mixed Strings are in different statuses for different languages. This option is only shown in Source Mode.

Languages

Select and search by the languages configured for the project.

Selecting Show source language only switches the Strings View from Translation mode to Source mode.

Source Keyword

Search for a word or phrase in the Source Strings column.

Translation Keyword

Search for a word or phrase in the Translations column.

Key/Variant

Search for string variants by looking up translations based on key or variant metadata.

File

Search for file names from the File/URL column. Optionally, select Exact Match.

Issues

Search by the following options:

Any Issues Strings that have or have had had open issues.

Any Unresolved Issues Strings with an unresolved issue.

Any Resolved Issues Strings with a resolved issue.

No Issues Strings with no issue.

Issue type

Search by the following options:

Source Strings that have an issue with the source.

Translation Strings that have an issue with one of the translation languages.

Context

Search by the following options:

Context Strings that have visual context.

No Context Strings that do not have visual context.

Context Name

Search by the name of the visual context, optionally with an Exact Match.

Hashcode

Search by a strings unique hash code.

Domains

In a GDN project, select and search for domains in the URL/Domain column.

Assignment

Search by the following options:

Pending Assignment Strings have not yet been assigned to a resource, such as a translator, editor, or proofreader.

Assigned Strings have been assigned to a resource.

Assigned To

Select and search for which resource(s) strings have been assigned to.

Translations

Search by the following options:

Has translation Strings have at least one translation.

Does not have translation Stringsdon'thave any translations.

Translation same as source String translations match the source copy.

Prepublish

Search by the following options:

Available to prepublish Strings are available to prepublish.

Currently prepublished Strings have been prepublished.

Workflow

Search by one or more project or account-level workflow steps. Click a step to select it.

History

Search by the Action taken, the Date range selected, and the User who performed the action; for example, all content excluded in the past seven days by a certain user.

Tags

Select and search by one or more content tags. Alternately, select and search by No tags.

Job

If in a project, search by the job the strings are located in. Optionally, select Not in A Job.

This article is for Account Owners and Project Managers.

In this guide, you will learn how to use the Smartling platform to translate files. You will create an account, add a linguistic package (which includes a glossary, a style guide, translation leverage, and quality checks), set up a workflowand then translate and download your files.

Table of Contents

Step 1: Register for Smartling Step 2: Add a Files Project Step 3: Create a Glossary Step 4: Create a Style Guide (Optional) Step 5: Upload a TMX File Step 6: Configure Leverage Step 7: Configure a Workflow Step 8: Set Up Quality Checks Step 9: Upload Files Step 10: Create a Job Step 11: Translate Content Step 12: Download Translations

Step 1: Register for Smartling

In your Smartling registration email, click the link to open the registration screen. Add your name and a password and click Register. The Smartling Account Dashboard appears.

Request Translations Using Jobs

Step 2: Add a Files Project

A project in Smartling is a translation environment with a collection of settings that change infrequently, such as the configuration of your linguistic package and the technology solution you will use to translate content.

To create a new project, click the Create New Project button and select Files. Choose Business Documents and click Next. Then, enter a project name.

To add a linguistic package to your project, click Create New Package. Select a Source Language and Target Languages that you will translate to. Click Create Project to finish.

For more information, see Create a Project.

Step 3: Create a Glossary

In Smartling, a glossary is a collection of words with rules for each to ensure translation consistency. Glossary terms are highlighted in the Computer-assisted Translation (CAT) tool.

To create a glossary, click Account Settings in the top navigation bar and select Linguistic Assets. Then, on the left side of the screen that appears, click Glossaries and click Create Glossary to open a dialog.

Add a Name, choose the same Source Language and Target Languages you chose in Step 2, and click Create Glossary. Click the glossary name and then click Add Term to add terms to the glossary.

For more information, see Create a New Glossary.

Step 4: Create a Style Guide

A style guide is a collection of rules for content formatting, punctuation, and writing tone to ensure that your customers have a consistent experience across all languages.

To create a style guide for your project, on the left, click Style Guides and then click Create Style Guide. Select Use a Smartling Template, change any options within, and click Save Changes.

For more information, see Create a Style Guide.

(Optional) Step 5: Upload a TMX File

A Translation Memory Exchange (TMX) file is a file format used for exchanging translation memory data created by a CAT tool. It is useful if youre migrating from another translation platform to Smartling.

To upload a TMX file, click Translation Memory. Next to the translation memory for your project, click the three dots and select Import TMX File. Click Continue, select the TMX file from your computer, and click Open.

For more information, see Upload a Translation Memory.

Step 6: Configure Leverage

Translation memory leverage controls which completed translations are available to a project or set of projects, and how those translations can be applied. Put another way, leverage sets the business rules that govern translation memory use.

To configure translation memory leverage, click Leverage and then click the name of your project. Click Enabled to configure Smartmatch settings and then set the leverage penalty, which defines the percentage by which all matches with your translation memory source will be reduced.

Step 7: Configure a Workflow

In Smartling, a workflow intelligently routes content based on parameters you choose. For example, you might use a workflow to add an edit step for your attorneys to review legal content.

To configure a workflow, from the top navigation bar, click Projects and then search for and select your project. Click the gear icon on the right side and select Workflows.

Click Create Workflow and select Add Project-Level Workflow. Enter a Name and select a Content Type and Target Languages. Click Create.

For more information, see Configure a Workflow.

Step 8: Set Up Quality Checks

Smartlings quality checks improve translation consistency by sending a customizable warning to the translator based on rules you configure. For example, you could warn a translator that a number from a source string is missing from the translated string.

To configure quality checks, click Quality Checks. Choose options and set their severity from the Translation Consistency, Spacing, and Other menu items in the top right area.

For more information, see Quality Checks.

Step 9: Upload Files

In this guide, you will upload business documents to translate. You can choose from Microsoft Word, Microsoft Excel, Microsoft Powerpoint, or Adobe InDesign files.

From the top navigation bar, click Projects and then search for and select your project. Click the Files tab and drag and drop your source files to upload them.

Step 10: Create a Job

Now you will create a job to translate your files from. In Smartling, a job is a task that allows you to prioritize and group content for translation.

To translate content with a job, from the Files tab, click Request Translation. Add a Job Name, select Languages, and click Confirm. The Jobs view is displayed.

Click Authorize to authorize all strings for translation. In the dialog that appears, select the workflow you created in Step 8 and click Confirm. The job status changes to In Progress.

For more information, see .

Step 11: Translate Content

There are many ways to translate content in Smartling. In this guide, you will use machine translation.

To do this, to the right of each target language, click the three dots and select Edit in CAT Tool.

For each translatable string, click the target column and then, under Language Resources, click Insert MT. When all strings are translated, click Save All and then click Submit.

Step 12: Download Translations

To download your completed translations, click the Smartling logo in the top left corner. Then, from the top navigation bar, click Projects. Search for and select your project.

Click the Files tab and then click Download Files (select Subfolders for languages). A .zip file with two folders and files that contain translated copy is downloaded.

This article is for Account Owners and Project Managers.

Workflows can be created for individual projects or at the account level, and are available for all projects under that account. Only an Account Owner can create workflows at the account level.

Create a Workflow (New Experience)

In a project, click the gear icon and select Project Settings.

On the left side, click Workflows.

Click Create Workflow and select either Add Project Workflow or Add Account Workflow. The Add New Workflow dialog appears.

Add a Name and select an appropriateContent Typefrom the menu.

Do one of the following:

For a Project workflow, select all languages set up in the project that this workflow will apply to.

For an Account workflow, select both aSource Languageand aTarget Language, then clickAdd Source Language. Add as many language pairs as you require.

Click Save.

Create a Workflow (Classic)

Go to Projects (select a project) >Project Settings > Translation Workflows.

Click the plus signand selectAdd Project WorkfloworAdd Account Workflow. The Add New Workflow dialog box will appear.

Enter a name for your workflow. If you have several workflows based on different workflow steps or different content, it's helpful to briefly include this information in the workflow name.

From theContent Typedrop down, select the type that best describes the content that will be processed through this workflow.

In theTarget Languagesbox, do one of the following:

For a project workflow, select all languages that this workflow will apply to. The list includes only languages that have been set up in the project. If more languages are added to the project in the future, you will be able to add them to the workflow at that time.

For an account workflow, select both aSource Languageand aTarget Language, then clickAdd Pair. Add as many source and target language pairs as you require.

Click Save.

This article is for Account Owners and Project Managers.

Adding a user to a workflow step allows them to access the content available in that step. This will be useful for you to ensure that your Translators, Editors, Reviewers, or other team members have the right access to content they are responsible for within your account.

There are two places in Smartling where you can add users to workflow steps. This can take place on either the resource's profile or under the translation workflow settings. Using the resource's profile is an easy way to add a user to multiple steps or multiple languages, while the translation workflow settings are a quick way to add a user to one step for one language.

Using Resource Profile

Do one of the following:

In the New Experience, go to Account Settings > Team > People. (Go to Account Settings >Team > Agenciesif you're assigning an agency to a workflow step, provided that you have already added an agency. If you haven't, see Add an Agency.)

In the Classic Experience, go toTeam>People. (Go toTeam > Agenciesif you're assigning an agency to a workflow step, provided that you have already added an agency. If you haven't, see Add an Agency.)

Select the resource whose access you would like to edit by clicking on their profile.

ClickAdd Assignment.

Select the languages, workflow, and step you would like to have this user access.

ClickAdd Assignment.

ClickSave Changes.

Using Workflow Settings (New Experience)

In a project, click the gear icon and select Project Settings.

Click Workflows.

Next to the step that you would like to add the user to, click the down arrow and select Manage People.

Select the appropriate target language and user name.

Using Workflow Settings (Classic)

Go to Projects (select a project) >Project Settings.

In Translation Workflow, click the drop down arrow next to the step that you would like to add the user to.

ClickManage People.

Select the appropriate target language and user name.

When assigning users, you will only see those who are available to work in the step. A user is considered available if they have been invited to the project and are set up to translate the selected language. Agency translators will not be displayed. To add a new user or manage a particular users access to languages and workflow steps in detail, use the Team page. See Manage Users and Agencies for more information.

This article is for Account Owners and Project Managers.

The Job Automation feature allows you to schedule content to automatically be batched into a job, based on a set of rules. You can also choose to automatically authorize the job for translation.

Automating a job is only compatible for cases where content is not automatically authorized for translation, for example, by using a connector or API integration. Global Delivery Network (GDN) projects are an ideal candidate for Job Automation.

To set up Job Automation:

Do one of the following:

In the New Experience, from a project, click Jobs,then click the gear icon and select Jobs Automation.

In the Classic Experience, select a project and then go toProject Settings > Jobs Automation.

Click Create Rule. You'll be prompted to fill out the following:

Job Name (required): Smartling will use your preferred job naming convention each time a new job is created.

Job Description: Give your job a meaningful description for Translators.

Schedule (required): Decide when you want the job to be created, and the frequency.

Content: Toggle ON if you want to include/exclude a particular file name (if it's a Files Project) or URL (if it's a GDN Project). If this is left to OFF, Smartling will capture all new content into the job.

You can use wildcard symbols to specify what should not be included in the job. For example, a"?" can be used to denote a single character wildcard (any 1-character matches), or an "*" can be used to denote a multiple character wildcard.

Languages: Select the languages to be captured into the job.Only content that is not authorized across all of the selected locales will be captured.

Authorize for Translation: Set to ON if you want to automatically authorize the job for translation.

Due Date: Decide on the due date for your job according to content volume. You should keep in mind your translation providers standard turnaround times for translation.

Notifications: Enter the email address for anyone that needs to receive a notification when a job is created. Recipients do not need to have a Smartling account.

Click Save. This will enable your rule.

If you wish to run Job Automation prior to the scheduled time, click the play icon from within theActions column. You canalso edit or deletethe rule at any time. If you wish to temporarily disable the rule, toggle OFF from within the Status column.

Each time the rule runs, the most recent time is captured in the Last Run column.

Job Automation rules will not apply to partially authorized content unless the automation rule is set up to run on only the languages that are partially authorized.

This article is for Account Owners and Project Managers. If you are using the New Experience Beta, jump to this section.

Translation Workflow Step

Every workflow consists of at least one translation step (during which the initial act of transforming the source locale into the target locale is undertaken) and exactly one published step, which indicates that translations are ready for use.

Add a Workflow Step (Classic)

Go to Projects (select a project) > Project Settings > Translation Workflow.

Click +to add a new step. The Add Step dialog box will appear. Workflow Branches and Dynamic Workflows

Select a step type, enter a name, and set its properties.

Content Assignment:If set to ON, each string must be assigned to a specific translation resource. If set to OFF, any resource with access to this step can work on any string.

Primary Action:For revision steps, the primary action is either edit (or review). This can be used for invoicing and also affects where SmartMatchedstrings enter the workflow.

Skip this step if the string's TM match is: This property is applicable for the Editing or Internal Review steps, allowing you to skip either of these steps in the workflow.

Resources can revise content:If checked, translation resources can edit the translation. CheckingAutomatically submit edits by resourceswill cause strings to proceed to the next workflow step when a translation resource saves an edit.

Resources can reject content to:If set, translation resources on revision steps will be able to return content to a previous step.

Resources can Reject and Edit Published Content:If checked, translation resources assigned to this step will also be able to edit or reject published strings from this workflow.

Pre-publish all translation:You can choose to pre-publishtranslations when translations are submitted to the next workflow step, or when translations are saved.

Click Save.

Pre-translation steps and Workflow Holds are special steps that pause the flow of content. Strings are held in the step until an Account Owner or Project Manager moves them forward. For example, you may want to use a pre-translation step if you know that you want to translate the content, but want to estimate costs before moving all strings into translation. A Workflow Hold can be useful before the publishing step if you want to wait until all your content is translated, and publish everything at once.

Reorder Workflow Steps (Classic)

Your current workflow might look something like this: Translation > Edit > Internal Review > Published

However, you might want to rearrange the order to: Translation > Internal Review > Edit > Published

To reorder workflow steps:

Go to Projects (select the project) > Project Settings > Translation Workflow.

Click and drag the circle to move the step to the correct position in the workflow.

You cannot move the Translation or Published steps, or a pre-translation Hold step. As well, when you reorder a workflow step, it's always best to inform all translation resources of the changes made.

Edit or Remove a Workflow Step (Classic)

Go to Projects (select a project) > Project Settings > Translation Workflow.

Click the drop-down arrow and select Edit or Remove. See Step 3 of Add a Workflow Step for more information about the step's properties. When making an edit to either the Editing or Internal Review step, you have the option to skip either step. For example, if both the Editing and Internal Review steps are skipped, translations will go directly to the published step. Skipping an Editing or Internal Review step should only be done if the original fuzzy match score in the Translation step is high enough, for example, 99-100%. However, you have the ability to select a lower match score. 3. Click Save.

Reject Published Strings in a Workflow Step (Classic)

To allow translation resources to reject published strings:

Go to Projects (select a project) > Project Settings > Translation Workflow.

Click Published > Edit.

CheckResources can reject content toand select the workflow step that you want the rejected content to be returned to. Only resources assigned to a step with the Resources can reject and edit published content option enabled will be able to reject published content.

Adding a Workflow Step (New Experience)

Go to Projects (select a project) > Gear Icon > Project Settings > Workflows

Scroll to the workflow youd like to configure, then click Add Steps. Click on any of the icons to add a step

Select a step type and enter a name for the new step. If you clicked on a + anywhere before a Translation step, you will see the following options:

Decision: automatically routes content to different workflow steps, based on user-defined rules. Learn more about Decision steps here.

Pre-Translation: Pauses the flow of content before translation. Useful for reviewing costs before submitting to translation. If you clicked on a plus sign anywhere after a Translation step, you will see the following step types: Edit: Allows Translation Resources to make revisions to translated content. Review: Allows Translation Resources to review translated/edited content for quality. Post-Machine Revision: Allows Translation Resources to revise machine-translated content. Workflow Hold: Pauses the flow of content after translation. Useful before the publishing step if you want to wait until all your content is translated, and publish everything at once. Note:Edit, Post-Machine Revision, and Review all have similar settings, but have different rates and affect where SmartMatched strings enter the workflow.

Configure the settings on the step:

Enable Content Assignment: If set to ON, each string must be assigned to a specific translation resource. If set to OFF, any resource with access to this step can work on any string.

Skip this step if the string's TM match is: This property is applicable for the Editing or Internal Review steps, allowing you to skip either of these steps in the workflow.

Resources can revise content: If checked, translation resources can edit the translation. Checking Automatically submit edits by resources will cause strings to proceed to the next workflow step when a translation resource saves an edit.

Resources can reject content to: If set, translation resources will be able to return content to a previous step.

Resources can Reject and Edit Published Content: If checked, translation resources assigned to this step will also be able to edit or reject published strings from this workflow.

Pre-publish all translation: You can choose to pre-publish translations when translations are submitted to the next workflow step, or when translations are saved.

Click Save

When you are done adding steps to the workflow, click on Done on the workflow toolbar.

Pre-translation steps and Workflow Holds are special steps that pause the flow of content. Strings are held in the step until an Account Owner or Project Manager moves them forward. For example, you may want to use a pre-translation step if you know that you want to translate the content, but want to estimate costs before moving all strings into translation. A Workflow Hold can be useful before the publishing step if you want to wait until all your content is translated, and publish everything at once.

Edit a Workflow Step (New Experience)

Go to Projects (select a project) > Gear Icon > Project Settings > Workflows.

On a workflow step, Click the drop-down arrow and select Edit Step. See here for more information about the step's properties. When making an edit to either the Editing or Internal Review step, you have the option to skip either step. For example, if both the Editing and Internal Review steps are skipped, translations will go directly to the published step. Skipping an Editing or Internal Review step should only be done if the original fuzzy match score in the Translation step is high enough, for example, 99-100%. However, you have the ability to select a lower match score.

Click Save

Reject Published Strings in a Workflow Step (New Experience)

To allow translation resources to reject published strings back into the workflow:

Go to Projects (select a project) > Gear Icon > Project Settings > Workflows.

Click Published > Edit Step.

Check Resources can reject content to and select the workflow step that you want the rejected content to be returned to. Only resources assigned to a step with the Resources can reject and edit published content option enabled will be able to reject published content.

Deleting a Workflow Step (New Experience)

Workflow steps can only be deleted under the following conditions:

There are no strings in the step.

There are no users, agencies, or MT configurations assigned to the step.

If the selected step is the only Translation step in the workflow, it cannot be deleted.

If the selected step is a Translation step on a workflow branch, the other steps on the branch must be deleted first. Learn more about .

Go to Projects (select a project) > Gear Icon > Project Settings > Workflows.

On a workflow step, click the drop-down arrow and select Delete Step.All users, agencies, and MT configurations will be unassigned from the step. If there are still strings in the step, they will be submitted to the next step

This article is for Account Owners and Project Managers.

Default workflows allow you to set a workflow for each locale that is most commonly used for those translations. When strings are authorized, content is assigned to each language's default workflow, unless you select otherwise.

As an Account Owner or Project Manager, you can customize the default workflow for each language assigned to a project.

Change Your Default Workflow (New Experience)

In a project, click the gear icon and select Project Settings.

Under Project Languages, in the Default Workflow column, click the workflow you want to change.

In the dialog that appears, select a new default workflow.

Change Your Default Workflow (Classic)

To set your default workflow:

Go to Projects(select a project) >Project Settings > Translation Workflow.

Select the Default Workflows tab near the top right of the page.

Select the default workflow from the drop down for each language listed.

When adding a new language to a project from theContent > Summary page, you can set the default workflow for the new language at the time it is added.

This article is for Account Owners and Project Managers.

Translations can be pre-published. When a string is pre-published, allpost-publication eventsimmediately take place, but the string remains in the translation workflow.

Pre-publishing is useful if you value time to market and can correct mistakes quickly and easily after publication, as is the case when using the Global Delivery Network. On the other hand, pre-publishing is not recommended when there is little or no opportunity to correct mistakes after publication, for example, with marketing emails.

Based on SmartMatch

Account Owners and Project Managers can customize SmartMatch behavior to pre-publish strings.

Based on Workflow Step

Account Owners and Project Managers can configure a workflow step to pre-publish strings.

This article is for Account Owners and Project Managers.

You can customize the translation step for each workflow.

Customize a Translation Step (New Experience)

Within a project, click the gear icon and select Project Settings.

On the left side, click Workflows.

Next to the translation step to customize, click the down arrow and select Edit Step.

In the Edit Step dialog box, select a translation method under Select Translation Provider.

Customize your translation provider options depending on the option you selected by following the instructions below for Human Translators or Third Party Providers.

Click Save.

Customize a Translation Step (Classic)

Within a project, go toProject Settings >Translation Workflow.

Next to the translation step of the relevant workflow, click the drop down arrow and select Edit. article

In the Edit Step dialog box, select a translation method.

Depending on the selected translation method, additional fields may appear. Follow the instructions below to complete them before continuing.

ClickSave to customize the translation step orCancel to exit.

Human Translators

You can control how human translators interact with content authorized into the workflow.

Assign strings to specific resources: If checked, an Account Owner, Project Manager, or Translation Resource Manager needs to assign each string to a specific Translation Resource. If not checked, any Translation Resource can work on any string.

Allow resources to claim jobs: If checked, Translation Resources can claim available jobs. If not checked, an Account Owner, Project Manager, or Translation Resource Manager needs to assign jobs to Translation Resources.

Allow resources to translate outside of Smartling: If Allow Offline Work is checked, Translation Resources can choose to export work assigned to them to be completed outside of Smartling, for example, using a third-party CAT tool.

Allow resources to edit or reject published strings: If checked, Translation Resources assigned to the translation step can edit or reject strings that have been published under the workflow.

Automatically submit to the next workflow step on save: If checked, strings will automatically be submitted to the next workflow step when they're saved.

There are a number of disadvantages to allowing resources to translate outside of Smartling. Resources don't have visual context, which may negatively impact translation quality. New translations aren't immediately available for leveraging by other resources, which may increase costs. Finally, Smartling cannot capture and report on certain important data points.

You can also control when translations will be pre-published.

Only if SmartMatch is set to pre-publish: Strings will be pre-published only if they match an enabledSmartMatch rule, and SmartMatch has been customized to pre-publish translations.

When submitted to the next workflow step: Strings will be pre-published when they're submitted to the next workflow step.

When saved:Strings will be pre-published when they're saved.

Copy Source to Target

This translation method copies the source text to the translation field and is useful formaking source content available for adaptation for a different locale,for example, American English source content for British English translations.

Third-Party Providers

Smartling provides built-in integrations with the following third-party providers of translation:

Amazon Translate

CrossLang

DeepL

Google Translate

Microsoft Translator

Unbabel

Watson Language Translator

An account with the third-party is required in order to use each integration. Contact each provider directly to create an account, or if you need credentials for an existing account.

When a third-party provider is selected as the translation method, Smartling will send content authorized into the workflow to the third-party. When the third-party returns translations to Smartling, they will be advanced to the next step in the workflow.

Also consult this for more information about integrating with a Smartling third-party provider..

This article is for Account Owners and Project Managers.

When creating a copy of a workflow, the newly created workflow will have the same configuration and resource assignments as the original workflow.

Copy a Workflow (New Experience)

In a project, click the gear icon and select Project Settings.

Click Workflows.

Next to the name of the workflow, click the gear icon and select Copy Workflow.

In the dialog that appears, enter a name for the new workflow.

Click Save.

Copy a Workflow (Classic)

Within a project, go toProject Settings >Translation Workflow.

Next to the workflow you wish to copy, click Copy.

Enter aname for the copy of the workflow.

Click Save to create a copy of the workflow or Cancel to exit.

The newly created workflow will have the same scope as the original workflow. For example, a copy of an account workflow will also be an account workflow, except if the user creating the copy is a Project Manager, in which case the newly created workflow will be a project workflow.

Creating a copy of a workflow is one way to have variations with different steps (for example, translation and editing versus translation, editing, and review) or for different translation resources. Other approaches may be easier to maintain depending on your organization's needs. Contact your Customer Success Manager for personalized guidance.

This article is for Account Owners and Project Managers.

You can delete a workflow if the following criteria have been met:

It is not the first workflow listed in a project, and it is not configured as a default workflow

No strings are in progress in the workflow (in any project, language, or state (i.e. active or inactive))

No resources are assigned to any of the workflow steps

All steps except "Translation" have been deleted from the workflow

If a workflow step uses copy-source-to-target method, it must be switched to human translation method

Delete a Workflow (New Experience)

In a project, click the gear icon and selectProject Settings.

ClickWorkflows.

Next to the name of the workflow, click the gear icon and selectDelete Workflow.

ClickConfirm.

Delete a Workflow (Classic)

Within a project, go toProject Settings >Translation Workflow.

Next to the workflow you wish to delete, click Delete.

Click Confirm to delete the workflow or Cancel to exit.

Only Account Owners can delete an Account Level workflow.

Submit a help ticket if you encounter difficulty deleting a workflow.

This article is for anyone using the Smartling Files API.

Do not confuse automatically creating a job upon file upload and authorization with Automate Job Creation (which allows you to schedule content to automatically be batched into a job, based on a set of rules).

If you're using the following parameters when uploading your files, your content goes into the translation queue upon file upload, and strings from the file will automatically be added to a job.

Parameters:

authorize=true

localeIdsToAuthorize[]

How the Job is Created

The job is created on the first upload-and-authorize, and all subsequent file upload-and-authorize actions will add more content to the same job until there are no other file uploads for the next hour, or if 4-hours have passed since the first time content was added to the job.

How the Job is Named

An automatically created job name will look something like this:"Daily upload YYYY-MM-DD (batchNumber)"

Within the Smartling Jobs Dashboard, it will appear like this:

How Due Dates are Set

Due dates are not automatically set. You can set them manually as needed. The job name (which contains a creation date) is indicative of priority.

How Content is Moved to A New Job (New Experience)

Automatically creating a job upon file upload and authorization can be turned off on a per project basis. Contact your Customer Success Manager if you prefer to have this setting turned off.

To move content from one job to another, do the following:

From a project, click the Strings tab.

Select the checkbox next to the string(s) you want to move.

Click Actions > Change Job.

In the dialog that appears, select New Job or Existing job.

For New Job, enter a Job Name and optionally a Reference Number, Due Date, and Description.

For Existing Job, select the job.

Click Confirm.

How Content is Moved to A New Job (Classic)

Automatically creating a job upon file upload and authorization can be turned off on a per project basis. Contact your Customer Success Manager if you prefer to have this setting turned off.Content can also be moved to another job via the Smartling Dashboard: Content > Translations > Add/Move to a Jobor via API queries. Cancelling a job will also unauthorize content.

This article is for Account Owners and Project Managers on the New Experience - Beta.

Dynamic Workflows are designed to help you achieve translation cost savings and faster time to market by intelligently routing your content based on parameters you choose.

Make your workflow dynamic by configuring Decision Steps and Workflow Branches.

Decision Steps and Workflow Branches

The Decision step is a new workflow step type that evaluates a strings properties and automatically chooses between multiple steps to send them to. Decision steps are different from other workflow steps in that:

Can point to multiple steps: other workflow steps can only be followed by one workflow step. Decision steps can be followed by several parallel workflow steps

Fully automated: users do not need to submit strings from a Decision step

here

Once a Decision step is defined, you can create multiple workflow branches from it. A workflow branch can consist of multiple workflow steps. This effectively allows you to have a single workflow that has the functionality of multiple workflows. Each branch can be configured to best translate the content that moves through it. Decision steps can be used to support complex translation needs effortlessly and within the same workflow. Some examples:

Send strings with high fuzzy scores to human translators (to leverage TM and SmartMatch) and strings with low fuzzy scores to machine translation (for cost savings and velocity).

Split content by File URI to different agencies, then have all translated content reviewed together in an Internal Review step.

Combine multiple different workflows for different locales into a single workflow.

Currently, only one Decision step is allowed in a dynamic workflow and it must be in pre-translation. However, you can create as many workflow branches as youd like.

Creating a Dynamic Workflow

Go to Projects (select a project) > Gear Icon > Project Settings > Workflows

Scroll to the workflow youd like to configure, then click Add Steps. Click on the + icon before a Translation step

Select the Decision (New Branch) step type, then click Next. Enter a name for the step, then click Create

The new Decision step will show up in the workflow as. Now you can create a second workflow branch to send strings to. Click on the + icon to begin building the second branch

Choose the Workflow step type, and choose a step for this workflow branch to merge back into.

Define your new Translation step. You can read for more information on step settings. Click Create when you are done configuring the step

Repeat steps 4-6 to create as many workflow branches as you need

Now you have to define the rules to route content to your workflow branches. Click on the Decision step to configure your rules.

Decision steps contain the rules for sending strings to different workflow branches. A Decision step always has a default rule, which automatically sends strings to the first Translation step if no other rules apply. ClickAdd New Rule to define a new rule

A rule consists of an action (where the string should go) and a condition (why it should go there). Choose a branch to send strings to, then choose a condition and define the value for it. The following conditions are currently supported:

Fuzzy score is greater than or equal to X%

Fuzzy score is less than X%

String word count is greater than or equal to X

String word count is less than X

File URI contains X

File URI does not contain X

Target language is in the list X,Y,Z (must use locale IDs, like fr-FR and pt-BR)

Target language is not in the list X,Y,Z (must use locale IDs, like fr-FR and pt-BR)

String key contains X

String key does not contain X

Has string tags X

Does not have string tags X

Repeat steps 9-10 to define all your rules

Click Save when you are done defining rules

When you are done adding steps to the workflow, clickDone on the workflow toolbar

To ensure that content is translated correctly, all possible paths through a workflow must have exactly one Translation step and end at the same Published step. A workflow branch does not have to merge back to the Published step, but it must merge with a step that will eventually lead it to Published.

This article is for Account Owners and Project Managers who are using one of the following self-service plans: Essential, Basic, Pro, or Business.

Once the file has been translated, you can download the translated version.

Go to Projects (select a project) >Recent Files> View All Files.

Click the source file name. You'll then be able to see all of the translated version(s).

ClickDownload.

(The example below shows the target language, but the translated version has not yet been completed.)

Some events in Smartling can trigger callbacks to a specified URL after a webhook has been configured. Callbacks notify you when an action is completed. For example, a file or string is translated in a particular locale or a translation job is complete.

Our callback service offers the option to sign requests to ensure that the payload of the request was not tampered with and was actually sent by Smartling.

Callbacks are issued from IP 184.73.255.141. To make sure you receive callbacks, you should whitelist this IP address. If a callback fails, Smartling will make multiple attempts to reach the designated URL. However, we do not keep retrying a failed callback indefinitely. Try to make sure your callback URL is as stable as possible and be aware that callbacks are not a 100% reliable way of being notified that a file is published. If the upload has begun but is taking more than a minute to complete, it responds with a 202 status.

String is translated for a locale: This callback is sent to the URL provided in the Create strings request. It can be sent as a GET or POST request. However, only the POST request includes translations.

The POST request looks like this:

{ "projectId": "51df0cf05", "hashcode": "3325fc569a651bef02a93732e48701b4", "localeId": "fr-FR", "type": "string.localeCompleted", "translations": [ { "translation": "Bonjour!", "pluralForm": null, "modifiedDate": "2016-12-01T14:18:00Z" } ]}

The GET request includes the same information - with the exception of the translations object as query string parameters: ?projectID=9db9036e6 etc.

Callback Types

The following table describes the types of callbacks Smartling offers: jobs, strings, files, and issues.To receive callbacks for pre-published strings or files, contact your Customer Success Manager to have them enabled at a site level.

Callback Type

Event

Description

Job

Job Completed

A job is completed, or completed for a locale.

Job Cancelled

A job has been cancelled

String

String Prepublished

A string has been prepublished for a locale. For more information on prepublishing, see Prepublish Translations.

String Published

A string has been published for a locale.

File

File Prepublished

A file has been prepublished for a locale.

File Published

A file has been published for a locale.

Issue

Issue Created

An issue has been created.

Issue Deleted

An issue has been deleted.

Issue State Changed

An issue has been opened or resolved.

Issue Answered

An issue has been answered.

Issue Severity Level Changed

An issues severity level has been changed to Low, Medium, or High.

Issue Comment Added

A comment has been added to an issue. Includes the comment body, creation date, and commenter.

Issue Watcher Added

A watcher has been added to an issue.

Set Up Sign Requests

You can enable sign requests as a way of ensuring that the request is actually coming directly from Smartling, and hasn't been intercepted or tampered in any way.

To enable this option, Smartling needs a 'secretKey' from you. Contact our support team. There will be a single secretKey key per account. Smartling will store this key, along with the accountUid, in the callback service.

Signing Procedure

Smartling allows GET and POST methods for requesting a callback. The request body (or URL) is the message to be signed by your secretKey via HMAC-SHA1, and then base64 encoded. This signature is then added to a request header called X-Smartling-Signature for you to validate. The specifics are outlined below.

For all signed requests, a timestamp parameter (ts) is added to all requests. It will be milliseconds from epoch (January 1st, 1970 at UTC).

GET:When using a GET request, all parameters will be appended to the callback URL. The callback URL is the message to be signed.

Example: callback URL: https://www.callback.com/event| secretKey: SECRET-KEY

A jobs callback will have translationJobUid and localeId as parameters. The callback that will be sent to you will be:

https://www.callback.com/event?translationJobUid=1qazxsw23edc&localeId=es-ES&ts=436363636332.

Smartling takes this URL and signs it via HMAC-SHA1 using your secretKey. For example:

signature = base64.encode(hmac("SHA1", "https://www.callback.com/event?translationJobUid=1qazxsw23edc&localeId=es-ES&ts=436363636332",SECRET-KEY)); ... request.addHeader("X-Smartling-Signature",signature); // end

From your end, you can perform the same procedure and compare results with the value in the X-Smartling-Signature header. If they are the same, then this is a valid request.

POST When using POST, we will create a request body (JSON) with the custom parameters sent in the request. We will append all parameters (in alphabetical order) with a pipe delimiter ("|") to create the message to be signed, for example:

callback URL: https://www.callback.com/event secretKey: SECRET-KEY

A jobs callback will have translationJobUid and localeId as parameters.

The callback that will be sent to the client will be: https://www.callback.com/event with a JSON request body such as:

{ "translationJobUid":"1qazxsw23edc", "localeId": "es-ES", "ts": 436363636332}

Secret Creation

Smartling will alphabetize the parameter names and concatenate them (with a pipe delimiter) to create a string as our message. It will look something like this:

localeId=es-ES|translationJobUid=1qazxsw23edc|ts=436363636332

In pseudo-code:

signature = base64.encode(hmac("SHA1", "localeId=es-ES|translationJobUid=1qazxsw23edc|ts=436363636332",SECRET-KEY)); ... request.addHeader("X-Smartling-Signature",signature); // end

From your end, you will follow the same procedure and compare your signature to the value of X-Smartling-Signature. If they are the same, then this is a valid request.

Nested Objects

For nested objects, we will flatten the structure and follow the same procedure as above.

Example response:

{ "projectId":"abcdef", "hashcode":"abcdefghijkl", "localeId":"fr-FR", "translations":[{ "translation":"some translation", "pluralForm":"OTHER", "modifiedDate":"2015-11-21T01:51:17Z" }], "type":"string.localeCompleted"}

The parameters to create the signature will be as follows:

projectId=abcdef

hashcode=abcdefghijkl

localeId=fr-FR

translations[0].translation=some translation

translations[0].pluralForm=OTHER

translations[0].modifiedDate=2015-11-21T01:51:17Z

type=string.localeCompleted

Once we've flattened the object, we will add the timestamp (ts) parameter and proceed with the general Secret Creation as documented above.

Ready to use the Smartling APIs?Click here.

This article is for Account Owners and Project Managers.

SmartMatch allows you to bypass workflow steps automatically for certain types of matches. SmartMatch behavior can be customized for eachtranslation memory source within a leverage configuration.

SmartMatch Rules

SmartMatch has different levels of precision which are evaluated in the below order.

Use Case

Example

Rule to Use

1.

Do you want to recover and SmartMatch unpublished translations for canceled jobs and deleted files?

Content will become available for SmartMatch even if it has not been published. For example, a string can be SmartMatched against a previous translation that has only been saved by a linguist, but has not gone through the entire workflow. (For SmartMatching, a date is not a field or parameter that is looked for to SmartMatch against. The date would only be used to indicate the location of the string.)

Restore translation: Exact match for previously removed unpublished translations (Recommended Setting- First Revision Step: Edit, Review, or Holding)

2.

Would you like strings with the same text and order of inline tags and placeholders to SmartMatch?

Strings will match if the sources are identical sequences of non-tag characters, and the number and position of inline tags are identical (the tags themselves can be different).

For example,

Open <span>box</span>Open <a>box</a>

Text ignore markup: Text exact match and ignore markup

3.

Would you like strings with the same text, inline tags, and placeholders to SmartMatch ignoring variant ?

Unlike "text exact", character sequence exact does not take into account variants, but would respect same text, inline tags, and placeholders.

Text without variant: Text exact match regardless of variant

4.

Would you like strings with the same text, variant, inline tags, and placeholders to SmartMatch?

String will match if the sources are identical sequences of characters, including inline tags, and the variants for the source strings are also identical.

Text with variant: Text exact match and variant exact match

5.

Would you like the text to SmartMatch ignoring both case and whitespace ? (Only the source whitespace will be maintained in the translation.)

For example,

"Open box"

"open box"

Match any: Any combination of ignore whitespace, markup, or case

6.

If the strings have identical sequences of characters, including inline tags and placeholders, would you like them to SmartMatch regardless of differences in whitespace? (Smartling will apply the SmartMatched translation while maintaining the whitespace from the source.)

For example,

"Open box"

"Open box "

Text ignoring whitespace: Text exact match and ignore all whitespaces

7.

Would you like the text to SmartMatch ignoring case? (Smartling will not maintain the case of the source characters in the translation.)

For example,

"Open box"

"open box"

However, if the source is lower-case, but is matched against a capitalized string, the translated string will also be capitalized.

Text ignore case: Text exact match and ignore uppercase and lowercase characters

SmartMatch runs continuously but is not guaranteed to be instantaneous. Therefore, matching strings may appear in the translation step briefly.

If enabling theRestore translation: Exact match for previously removed unpublished translationsrule, consider selecting theFirst Revision Step (Edit, Review or Holding) result to minimize the probability of an incorrect translation being copied to multiple strings.

SmartMatch Results

Each SmartMatch rule can be disabled or enabled with one of four results.

Published:Matching strings will bypass all workflow steps and immediately be published.

First Revision Step (Review):Matching strings will jump to the first revision workflow step with primary action "review," bypassing all previous workflow steps. If there is no such workflow step, matching strings will bypass all workflow steps and immediately be published.

First Revision Step (Edit):Matching strings will jump to the first revision workflow step with primary action "edit," bypassing the translation workflow step. If there is no such workflow step, matching strings will bypass all workflow steps and immediately be published.

First Revision Step (Edit, Review, or Holding):Matching strings will bypass the translation workflow step. If there are no other workflow steps, matching strings will immediately be published.

Enable or Disable Rules

Account Owners and Project Managers can customize SmartMatch behavior for each translation memory source within a leverage configuration.

Do one of the following:

In the New Experience, go to Account Settings > Linguistic Assets.

In the Classic Experience, go toAssets >Leverage.

Click the name of the leverage configuration you want to customize.

In the list of translation memory sources, under SmartMatch, clickEnabledorDisabled.

Select a result for each SmartMatch rule. If you chooseFirst Revision Step, you have the additional option of selecting or deselecting Enable Pre-Publish.

ClickSave Changes to put the customizations into effect orCancel to exit.

The link text (Enabled or Disabled) indicates whether at least one SmartMatch rule is currently enabled for the translation memory source.

Set all SmartMatch rules toPublished to maximize cost savings and time-to-market benefit. SelectingFirst Revision Step andEnable Pre-Publish also maximizes time-to-market benefit.

This article is for Translators, Editors, and Reviewers.

The Smartling CAT (computer-aided translation) tool is where you, as a Translator or Editor, will be translating, editing, and submitting content.Within each section of this article, you'll see a detailed view of each feature. See Working Within Smartling on how to access the CAT tool.

Save a String (for Translators) Confirm a String (for Editors) Reject Translations Submit Translations Keyboard Shortcuts Strings and Segments Tags Fuzzy Match Insertables Draft Mode and Internet Connection Issues Filters Panels Run Quality Assurance QA Export Search Glossary Glossary Terms Autocomplete Search Translation Memory String Level Matches Toggle Case Special Characters Preferences Personal Dictionary Visual Context View Mobile Responsive Context

Save a String

For Translators, when you save a string, you can continue to make further updates (and re-save) it provided that you haven't already submitted the string.

To save a string, click the checkmark for the designated segment. The checkmark will then appear next to the segment. Remember that if a string contains multiple segments, you'll need to translate and save all segments before being able to submit the string.

Video Translation Overview

Instead of saving strings individually, you can also click Save All to perform a bulk save.

The bulk save functionality will save the strings for the page you're currently on. Each page has a limit of 100 strings. If you have more than 100 strings that need to be bulk saved, you'll need to click to the next page. (Basically, we start paginating after 100 strings, so the bulk save will save up to 100 strings at a time.)

You can use the default keyboard shortcut:Command + S(Mac) orControl + S(Windows) to save your work. See Configure CAT Tool Settings and Keyboard Shortcuts for more information.

For information, see Save and Submit Translations.

Confirm a String

For Editors, when you confirm a string, you can continue to make further edits (and re-save) it provided that you haven't already submitted the string.

To confirm a string, click the checkmark for the designated segment. The checkmark will then appear next to the segment. Remember that if a string contains multiple segments, you'll need to translate and confirm all segments before being able to submit the string.

For more information, see Save and Submit Translations.

Reject Translations

You can reject an individual string or reject all strings at once.

To reject an individual string, click the X for a specific segment.

To reject all strings at once, click Reject Translations.

For more information, see Proofread Translations.

Submit Translations

When submitting your translations, you'll be given two options:

Submit saved translations: This submits all previously saved/confirmed translated strings.

Submit all translations: If you haven't previously saved/confirmed your translated strings, this saves and submits them in one action.

Remember to click Submit. Keep in mind that once you submit your strings, you'll no longer be able to modify them.

You can also create a keyboard shortcut for each action above. Go to Settings > KeyboardPreferences. Add your shortcut to Submit Saved Translationsand/or Submit All Translationsand click Save.

The submit functionality will submit the strings for the page you're currently on. Each page has a limit of 100 strings. If you have more than 100 strings that need to be submitted, you'll need to click to the next page. (Basically, we start paginating after 100 strings, therefore up to 100 strings will be submitted at one time.)

For more information, see Save and Submit Translations.

Keyboard Shortcuts

Mouse over the following keyboard shortcuts to reveal functionality and keystrokes.

To change keyboard shortcuts or select a preset profile, go to Settings > Keyboard Preferences.

Change any keyboard shortcut or select a Keyboard Shortcut Profile.

Click Save Changes.

If a keyboard shortcut you're familiar with isn't working, make sure to check your settings so that it doesn't conflict with your preset shortcut.

For more information on this topic, see Customize CAT Tool Behavior.

Strings and Segments

When content is ingested into Smartling, it gets broken down into strings. Each string could consist of an entire paragraph, a phrase, or simply a word.

The green vertical bar indicates an entire string. In this example, this one string is broken into three segments. When translating this type of string, each segment would need to be translated before the string can be saved.

For more information on this topic, see Content Parsing.

Tags

For tags, you can toggle between the HTML code view or simplified view, denoted by numbers (1,2,3, etc.).

To copy a tag to your segment, click the tag in the source. This will copy the source tag to the segment.

To move the placement of a tag within a segment, click and drag the tag to anywhere that is highlighted in green. This prevents HTML code from breaking. If you're dragging a pair of tags to another spot, move the opening or closing tag first (depending on the direction you need to move the tags). For more information on tags, see Insert, Remove, or Move Tags and Placeholders.

Fuzzy Match

When Smartling uses an existing translation memory to match source content with existing translations in the translation memory, it will often find word matches that are less than 100% identical. These type of matches are what we refer to as a fuzzy match. They're represented by a percentage on how the words match, typically somewhere between 50-99% (but a 100% exact match is also possible).

For more information on this topic, see Get a Fuzzy Estimate.

Unedited Fuzzy Matches

For unedited fuzzy matches, such as the example shown in the screenshot below, the font is lighter and italicized. The two occurrences when this could happen are:

From auto-population of fuzzy matches -OR-

From inserting matches from the Language Resources panel

Once you make any edit to the text, it will return to its normal state.

Unedited fuzzy matching is not persistent across page loads, therefore, if you refresh your browser, the unedited fuzzy matches will become normal strings.

Insertables

If a translated string requires different formatting than the source, click on a formatting option in the insertables toolbar or use the keyboard shortcut that's displayed on hover over.This will insert the tag where your cursor is placed in the translation field.

All are unicode characters, and not tags (with the exception of "BR"). Unlike tags, these unicode characters do not necessarily have to be added. However, for tags, you can't add a tag that wasn't in the source.

For more information on tags, see Insert, Remove, or Move Tags and Placeholders.

"Draft Mode" and Internet Connection Issues

The CAT tool automatically backs up your translations in your local browser as you type. Even if you lose internet connection or close your browser, they will remain available until you're ready to save them.

Draft translations can't be retained if you were browsing privately or if you clear your browser cache.Translations are saved in your browser's local storage. Therefore, if you were using one browser (Chrome) and then opened another browser (Firefox), translations in draft mode would not be retained. As well, if you were using Chrome on one computer, and opened your translations in Chrome on another computer, the translations would be not be retained.

Filters

While the generalSearch source and translationsfield is still available to you, strings can also be found by using Filters.

The workflow and job filters will change the display of content available for translation in the CAT tool.

Workflow (workflow step)

Job

Tag

Keywords

Current Status

All

Not Saved

Saved

Unresolved Issues

Files URI

Panels

Additional Details: From this section, you can access your glossary and style guide.

Language Resources: You'll find suggestions of records in the translation memory that match closely with the strings you're translating. You'll also find machine translation suggestions, both of which can be entered into your segment. (The languages supported by machine translation are a combination of Google Translate and Bing Translator.)

Quality Checks: This panel is configured by your customer, and shows any errors that are found within your segments.

Issues: If you need to address anything that might need clarification from your customer, you can open an issue.

History: If thestring was previously translated, you can see the history of it in this panel.

Run Quality Assurance

At any time, you can run a quality check on your translated strings. The Quality Check feature checks for translation consistency, spacing consistency, proper spelling, etc. Keep in mind that it will only check what's on the specific page that you're on, and will only load up to 100 strings at a time.

In the CAT tool, select the Quality Assurancetab to run quality checks on all translations currently on your screen. (This creates a report of all errors detected in your translations. A string with a translation error will show a warning icon next to it. The color of the warning icon depends on the severity of the error.)

Click on a quality check to bring you directly to the string that needs attention.The report updates itself in real time. Once you are certain that you have fixed all quality errors, you are ready to submit your translations.

In the Quality Assurancepanel, you can see a list of errors found within your translations, at a segment level, informing you of the number of errors along with what they are.

For more information on quality assurance, see Quality Checks.

QA Export

As a Translator, you have the option to export a bilingual CSV or DOCX file of all saved translations in the current job. This does not include drafts. Exporting translations is commonly done when a third-party is used to run quality assurance. For example, you may specifically want to run a Microsoft Word spell check.

QA Export is only available when the CAT tool is filtered by job. If it's not filtered by a job, click Filter and select a job from within the dropdown menu.

To export your translations, click the QA Export menu and select either:

Export Job as CSV-or-

Export Job as DOCX

(Any tags that appear in the source/target translations in the CAT tool will be removed upon export.)

Note: There is no import option.

Search Glossary

To search the glossary, click Search Glossary. If you have access to multiple projects, you select the project from the drop down menu.

Glossary Terms

Glossary terms are underlined with a dotted black line.

To edit the glossary term, hover over it to reveal the modal dialog. Click the pencil icon.

To insert a glossary term in the target segment, hover over it to reveal the modal dialog. Click the appropriate glossary term.

Smartling also does a glossary match of different forms of a word (such as run, ran, running). For example, in the source, the term "currency" will match against "Currencies" in the glossary. Likewise, "Ran for food" will match against "run for food". This only applies to English source terms.

For more information on this topic, see Add or Edit a Glossary Term.

Autocomplete

Glossary Terms, Tags, and Placholders

When you start to type a glossary term, tag, or placeholder in the target field, you'll be presented with options which you can select from. If there are multiple items, you can use the arrow keys to go up or down.

If you're using the Smartling keyboard profile, use "Enter" to insert the item. For Trados and MemoQ, use the "Tab" key. (If not already configured, it can be done from within the Keyboard Shortcuts menu.)

Search Translation Memory

To search the translation memory, click Search TM. You can toggle between languages in the drop down menu.

For more information, see Search and Use Translation Memory.

String Level Matches

String level matches are TM matches that correspond to an entire string, and not to each segment within a string. When inserted, they will be inserted into the first segment of a string.

String level matches areindicated by diagonal stripes. Also note that string level matches will not be auto-populated by the pre-populate feature. Therefore, it's possible for a segment to have only a string level match and not be auto-populated.

Smartling doesn't allow for string level matches to auto-populate as a way of preventing all of the text from being added to the first segment.

Toggle Case

Improve translation speed by using the toggle case feature. Options include:

Change all text to lowercase (ex.: morning)

Change all text to uppercase (ex.: MORNING)

Capitalize the first letter of each word (ex.: Good Morning)

Highlight the text you'd like to change and click the Aa button or use the default keyboard shortcut Shift + F3 to cycle through the different options.

(If you would like to customize the toggle case keyboard shortcut, go to Settings > Keyboard Shortcuts > Miscellaneous.)

Not all languages have the concept of upper/lower case. Supported languages include all languages using the Latin alphabet, Cryllic alphabet, Greek, and Armenian.

Special Characters

You can easily insert special characters into the target field by opening the Special Character Menu and selecting the one that you need.

Preferences

In your settings, you can adjust the following:

Translation Options:

Pre-populate 100% translation memory matches: If this is enabled, you can adjust the range in order to see a lower score match.

Overwrite all matching drafts and saved translations when a 100% repetition is updated (current page only).

Notify before overwriting saved repetitions.

Replace straight quotes with smart quotes - German and French only. When enabled, a pair of straight quotes (" ") will automatically be converted into language specific quotes:

For French:

For German: You can also set up a keyboard shortcut for smart quotes, or use the smart quotes toggle on the segment.Note: Once the feature is turned ON, the only way to insert a standard straight quote (") via the keyboard is to toggle the feature off (either by keyboard shortcut or through the toolbar).

Display Options:

Tag values: Enabling this feature will show HTML tags in strings and segments.

Spaces between words: Enabling this feature creates a dot in the place of a space.

Editor Settings:

To change your preferences, go to Settings > Preferences.

For more information on this topic, see Customize CAT Tool Behavior.

Personal Dictionary

Sometimes you'll see words are underlined in the CAT tool, suggesting that there's a spelling error, when in fact, there isn't. The personal dictionary feature allows you to add words to a dictionary that only applies to you. (You can also remove words.) Once this is done, these words will no longer be marked as containing spelling errors.

To access your personal dictionary, go to Settings > Personal Dictionary.

For more information on this topic, see Customize CAT Tool Behavior.

Visual Context View

Visual context gives you insight into what you're translating.You can see in real-time how your translated string will appear. (When you click a segment, the relevant text will be highlighted in the context view.)

To pop out the context view into a new window, click the gear wheel and select New Window. This is useful for when you'd like to have the TM search open on one screen, with the context view on an external monitor. You can also click and drag the gear wheel to another area within the context view.

To resize the context view, click and drag (up or down) the window.

To collapse the context view, click the arrows.

For more information on Visual Context, see Screenshots.

Mobile Responsive Context

To view what your context would look like on a mobile phone or tablet, click the gear wheel at the bottom left of your context window and select from the following:

Desktop

Mobile

Tablet

Looking for information about video context? See the article.

This article is for Account Owners and Project Managers.

Smartling API tokens are used to authenticate into the Smartling platform via API or the connector. This article describes how to generate API tokens. API documentation can be found here.

To generate API v2 tokens:

Do one of the following:

In the New Experience, click Account Settings > API.

In the Classic Experience, from the top menu, clickAPI.

Select thev2.0 tab.

Click Create Token.

If creating a Project token, select the project you wish to connect to from the menu.

Enter a token name.

Click Create.

Make note of your token secret.

You will not be able to access your token secret after dismissing the prompt.

To generate API v1 keys:

Do one of the following:

In the New Experience, click Account Settings > API.

In the Classic Experience, from the top menu, clickAPI.

Select thev1.0 tab.

Select the project you wish to connect to from the drop down list.

Click Generate new API key.

Click Confirm to generate a new API key.

If you click Confirm, your current API key will stop working and you will have to update your API integration code or connector configuration.

This article is for Account Owners, Project Managers, Translators, and Editors.

You can manage Quality Checks and decide what level of translation consistency is appropriate for your content.

Enable or Disable Quality Checks

Do one of the following:

In the New Experience, go toAccount Settings > Linguistic Assets and then click Quality Checks.

In the Classic Experience, go toAssets > Quality Checks.

QualityChecks Settings

Each quality check has one of the following severity settings:

Disabled: The quality check is completely disabled, and no errors associated with the quality check will be shown to the Translator in the CAT tool.

Low Priority: The quality check is enabled, and any errors associated with the quality check will be shown to the translator in the CAT tool. However, these errors will not prevent the Translator from saving/submitting work.

Medium Priority: The quality check is enabled, and any errors associated with the quality check will be shown to the Translator in the CAT tool. In addition, these errors will result in a warning to the Translator during saving/submitting a string. Using this setting will obligate the Translator to fix or accept error before saving or submitting the content.

High Priority: The quality check is enabled, and any errors associated with the quality check will be shown to the Translator in the CAT tool. In addition, these errors will prevent the Translator from saving/submitting a string until all errors are resolved.

For eachqualitycheck, you can add a language specific setting, or disable it.

these languages

It may take up to 15-minutes for changes made in the quality checks settings to apply and get updated in the CAT tool.

Errors Captured Through Quality Checks

At the moment, we support the following quality checks:Translation Consistency,Spacing, and Other.

Translation Consistency

Placeholder

A placeholder in the source is causing an error. (Default severity: medium)

Incorrect spacing around placeholders: The spacing around placeholders in the source differs from what's in the target.

Placeholder added: There's a placeholder in the target that wasn't in the source.

Placeholder deleted: There's a missing placeholder in the target that was originally in the source.

Number Consistency

A numerical discrepancy between source string and translated string. (Default severity: low)

Incorrect number format conversion: Takes into account how numbers are localized. For example, French uses a comma for a dollar value instead of a period.

Number added: A number was added in the target that's not in the source.

Number missing: A number is missing in the target that was originally in the source.

Tag Consistency

A tag in the source is causing an error. (Default severity: high)

Spaces around tags: Checks to see if spacing around source tags is the same as what's in the target.

Tag added

Tag deleted

Tag order changed: For example, the source has a word in bold, followed by a word in italics, but the target has that order reversed.

Insertable Consistency

By default, the Insertable Consistency quality check is disabled. You have the option to enableInsertable deleted or Insertable added. The insertable consistency check tracks the presence of the following characters:

Break tag (<br>)

Non-breaking space (A space character that prevents an automatic line break at its position.)

New line character

Word joiner (A code point in Unicode indicating that a word separation shouldn't occur at a position when using scripts doesn't explicitly specify spacing.)

Zero width (Invisible, "non-printing" characters that aren't displayed by the majority of applications.)

Emoji Consistency

An emoji in the source is causing an error. (Default severity: low)

Emoji added

Emoji deleted

Do not allow emoji in translation

Segment Completeness

Checks to see if the target is of similar length to the source. If the target is 50% shorter or 250% longer than the source, a warning will get created.

Translation is too long compared to source

Translation is too short compared to source

Glossary Compliance

When a source string contains a glossary term, this quality check will check if a glossary translation was or was not used. The check will only run if the term has a translation, or is a "do not translate" term. If it's a "do not translate" term, the check will see if the glossary source term was used in the target.

There are two possible settings:

Exact Match: Sees whether or not the exact translation for the glossary term was used. If it's not used, an error will be shown.

Match by Percentage: This allows for some word variation that you may have used. By default, the check is set to match the first 50%. This means that the check will look at the first 50% of the glossary translation and see if that series of characters appears in the target.

For example, let's say there's a glossary term for "drive", with a French Translation of "conduire". The first 50% of that word is "cond". If there is, for example, a conjugation of that verb in the target, such as "conduit", this would be marked as a match since the first characters of "conduit" contain "cond".

Match percentages can be set to 25%, 50%, or 75%. (Words under 6 characters must always use the Exact Match setting instead of Match by Percentage to help prevent false positives.) As a Translator or Editor, you will only see Glossary Compliance checks if you click the Quality Check tab to run quality checks on all strings on the page, or when you're saving a string.

Punctuation Consistency

Checks to see if ending punctuation in the target matches the ending punctuation in the source. For example, if the source string ends with a question mark, it will check to make sure that the target string also ends with a question mark.

Also checks that the number of brackets and parentheses are consistent between source and target; includes [ ], ( ), and { }.

Global Capitalization Consistency

Checks to see if capital letters in the source were used consistently in the target. For example, a warning will appear if "ATTENTION" was translated to "Achtung" instead of "ACHTUNG".

By default, this quality check is low severity.

Legal Symbol Consistency

Checks to see if legal symbols in the source were also used in the target. The list includes:

Trademark:

Copyright:

Service mark:

Registered:

Spacing and Target Length Limit Errors

Spacing and target length limit can be adjusted in the spacing quality check.

Leading or Trailing Spaces

There is an extra space at the beginning or end of a segment. (Default severity: low)

Check that spacing at the beginning/end of the translation is consistent with the source.

Spacing Error

There is an extra space within the segment. (Default severity: low)

Checks that translation is within the word count limit: In Smartling, there's the option to give strings a character limit. This check occurs if that feature is enabled. (Tags are not counted toward character limit.)

Target Length Limit

The number of characters in the target exceeds the limit that was set up on a per string basis. (Default severity: high)

Other

Spell Check

A word is misspelled in the target language. Spell check is provided for.(Default severity: low)

Skip if word starts with a capital letter.

Skip if word appears in source string.

Skip if word is valid in source locale.

Run spell check for hyphenated words.

Source string is the same as translated string

(Default severity: low)

Checks to see if the source string is exactly the same as the target. i.e. source is "Hello world" and the translation is also "Hello world".

Repeated Word

Words repeat in succession. (Default severity: low)

Checks to see if a word is repeated multiple times in a row, in a translation. For example, "A word is repeated repeated."

Target in the Wrong Language

Words in the target are in a different language from what should be translated. (Default severity: low)

Checks that the translated string is in the target language: For example, if your source is in English, and the target should be French, but a segment has been translated into Spanish.

Source in the Wrong Language

Words in the source are in a different language from what needs to be translated. (Default severity: low)

Checks that the source string is in the source language: For example, the source should be in English, but a source string or segment is in Spanish.

Plural Form Is the Same as Another Form

(Default severity: medium)

In a target language, plural translation forms are the same even though they are different in the source language. This check does not run if the target language requires only one form.

When this check is triggered, review the CAT tool for information about the plural source string and required translation forms. Check the Additional Details panel for Plural Forms in Source Language as well as the language-specific plural instructions in the yellow bar above the translation entry field.

This article is for Translators, Editors, and Reviewers.

Smartling, a cloud-based translation technology and services company, makes it quick and easy for translation teams to deliver localized content with high quality. Below are some key concepts to help you get started with navigating Smartling.

Your User Role

End-to-End-Workflow

Content Hierarchy

Key Concepts

Your User Role

At Smartling, linguists are comprised of Translators and Editors. Reviewers take care of proofreading translations and ensuring brand alignment before publishing content. (We use the term "Translation Resources" to refer to Translators, Editors, and Reviewers.)

Depending on your Smartling user role (Translator, Editor, or Reviewer), you will have different user permissions, and therefore, a slightly different user interface from your Translation Resource Manager, Agency Account Owner, Project Manager, or Account Owner.

User Role

Description

Translator (Linguist)

In your role, you are responsible for translating content. You'll receive an email notification that there's content ready for you to translate. After you save and submit your strings, if the workflow was set up by an Account Owner or Project Manager, such that the content goes through an editing process, the Editor will then receive a notification that there's content ready for editing. Your translated content will then be locked in the CAT tool (and you won't be able to make any changes while it's in the editing step).

Editor (Linguist)

In your role, you are the second pair of eyes ensuring that the content has been translated accurately.You have the option to edit, submit, or reject strings. If content needs to be reworked, you can reject content, which will be sent back to the Translator along with any comments you may have. If the content is fine, you can submit it to the next step in the workflow, which is likely an internal Reviewer of the client. The Reviewer will receive a notification that there's content ready for review.

Reviewer (Proofreader)

In your role, you're the last set of eyes before the content goes live in its localized version. Your role is to focus on the translated content for consistency, quality, and brand alignment. You have the option to edit, submit, reject, or publish strings. If you reject a string, it will be sent back to the person in the previous workflow step.

End-to-End Workflow

At a high level, this is how Smartling works: Once content from a file or website is added to Smartling, the Account Owner, Project Manager, or Agency Account Owner assigns content for translation. This essentially triggers the translation process that is performed by a Translator. Depending on how the workflow is set up, the translated content may also go through an editing and internal review process before the content is published.

Content Hierarchy

The content that you will be translating, editing, or reviewing is set up with the following hierarchy:

Accounts: This is the Smartling customer whose content you are translating.

Projects:An account may contain one or more projects that house certain types of content such as a website, business documents, emails, etc.

Jobs:Within a project, content is organized (and prioritized by due dates) into Jobs.

Strings:When content is initially ingested into Smartling, it's broken down or parsed into strings. Strings can consist of an entire paragraph of content, a sentence, a phrase, or a word.

Segments:A string is broken down further, into a segment. If you have a string that contains more than one segment, each segment must be translated before your work can be saved, and before the string can be sent to the next step in the workflow.

Key Concepts

SmartMatch

SmartMatching refers to a string that perfectly matches a string in the translation memory, including any tags, placeholders, etc. SmartMatch compares new strings against existing translations in your leverage configuration to automatically apply translations to strings you've translated before.

Fuzzy Match

When Smartling uses an existing Translation Memory (TM) to match source content with existing translations in the TM, it will often find word matches that are less than 100% identical. These are called "fuzzy matches" and are represented by the percentage to which they match (typical fuzzy match percentages are 50-99%). Translators can see these fuzzy matches in the CAT tool and choose to edit them instead of translating from scratch.

See our terminology page for more on general localization terms as well as those specific to Smartling.

Consult the Working Within Smartling article to better understand how to log in to Smartling, access the CAT tool, and view all the features available to you to get your work done.

This article is for Account Owners and Project Managers using the Global Delivery Network.

By default, the Smartling Global Delivery Network (GDN) is setup tocapture all pages on your source domain, and rewrites links within pages that point to your source site. In some cases, you may want to make exceptions to this default behavior. To do this, Smartling offers a set of tools within your Smartling GDN project that allow you to control some capture and translation behaviors of your GDN site. This interface is one of the 3 methods for controlling GDN behavior.

Capture behavior can be controlled at two levels in this inferface:

Website page level

HTML element level

Class Names

IDs

If you need to control behavior by language, you may need to consider a different method.

To Create a Translation Rule

Do one of the following:

In the New Experience, from your GDN project,click the gear icon > Project Settings > Rules.

In the Classic Experience, from within your Global Delivery Network project, clickGlobal Delivery Network > Configuration > Rules

Click Add a New Rule

Enter your rule parameter

URL rules: Enter full URL path of the page to apply the rule. NOTE: Rules will execute on partial matches. For example, if you enter rule text "/products", your rule will apply to any page that contains /products in its' URL.

HTML Class or ID rules: Enter an HTML class or ID to apply the rule against. NOTE: If the HTML class or ID is not unique, your rule will be applied to every instance of the HTML element on your site.

Select your rule type from the dropdown

Click Save to create your rule or Cancel to start over

Conditions

Requests that Match URLs- Any URL matching the URL regular expression entered will have the selected features applied.

HTML Elements with Class Names- Any CSS class matching the class name you enter will have the selected features applied.

HTML Elements with IDs- Any HTML element matching the id value you enter will have the selected features applied.

Rule Types

Do Not Translate:Content will not be captured, translations will not be served, links will be rewritten.

Do Not Localize URLs:links will not be rewritten, content will be captured and translations will be served.

Do Not Translate or Localize URLs:Content will not be captured, translations will not be served, links will not be rewritten.

Do Not Capture Content:Content will not continue to be captured after enabling this rule. Any existing translations for a page will continue to be served.

Remove Content from Page:Only applicable to HTML Class or ID rules. The element will be hidden from the localized page.

Translation Rules apply across all domains in a given Global Delivery Network project. If you need to configure translation behavior for individual domains, or need more advanced control over translation behavior, consult our GDN Integration Tag Library.

This article is for Account Owners Project Managers using the Global Delivery Network.

Smartling's Debug mode (?smartling_editmode=3) is a preview mode that can be used on Global Delivery Network (GDN) sites to allows users to view information about content capture, translation, and link rewriting behavior on a page. This mode is most readable when applied to the source code view of a translated page or response, but can also be applied to the front-end page.

This article covers how to use Debug mode to troubleshoot the following common issues:

Content Capture & Translation

Patterns

Link Rewriting

Javascript and JSON Parsing

Content Capture and Translation

There are two ways in which debug mode can help you understand how content is being captured and translated: at the page level and string level.

Page Level

The first line in the source code will be a comment indicating the capture ("parsing") and translation status of the page:

<!-- HTML PARSING BEGIN -->

Content is being captured, and translations are being served for HTML content on the page.

<!-- NO INGESTION BEGIN -->

New content will not be captured for translation on this page. Existing translations will continue to be served.

<!-- NOTRANSLATE MODE BEGIN -->

Content will not be captured, and translations will not be served on this page.

If you see an unexpected capture mode or translation status, check your page level capture rules defined in one of the following locations:

In the New Experience, go to the gear icon > Project Settings > Rules.

In the Classic Experience, Global Delivery Network > Configuration > Rules.

String Level

If the first line displays<!-- HTML PARSING BEGIN -->,debug mode will apply comments to individual strings within a page with their capture and translation status. Search for a particular string within a page to see the status:

<!-- STRING TRANSLATE BEGIN HASH:XXXXXXXXXXXXXXXXXXXXXXXXXXXX -->

The string has been ingested and is in one of the translation workflow steps.

Try checking the Awaiting Authorization and Excluded queues first. If the string isn't there, it's possible the string is currently in translation (In progress queue) or completed without a translation (Completed).

<!-- STRING TRANSLATE BEGIN[NO INGESTION] -->

The string will display translated, but will not ingest or translate if there are any edits.

<!-- NOTRANSLATE MODE BEGIN -->

This will appear before a string that will not be ingested or translated by Smartling. Check your source code for any "notranslate" classes that may appear.

Patterns

If a pattern is being applied to content on a page, debug mode will display the pattern and ID.

<!-- STRING TRANSLATE BEGIN HASH:XXXXXXXXXXXXXXXXXXXXXXXXXXXXPATTERN[ID:########]:~^{pattern}$ -->

In some cases, a pattern may be too general ("greedy"), and prevent you from capturing content you want translated. If this happens, locate thepattern inContent > Patterns, and try making your pattern more specific by using additional parameters.

Removing a pattern will cause the original patterned version of the string to revert to English. Re-capture that string and apply a new pattern.

Link Rewriting

In most cases, the GDN will automatically rewrite both relative and absolute links of the source domain on translated sites. You can see this behavior in more detail in debug mode, which can be helpful when you observe a link that is not rewriting on a translated site as expected:

<!-- NOREWRITE MODE BEGIN -->

Links will not be rewritten, so all links will stay on your source domain. Checkfor the presence of any "Do Not Localize URLs" rules or your source code of the sl_opaque/notranslate class.

<!-- ABSOLUTIZE URI BEGIN -->

The relative link will be rewritten.

<!-- LINK SUBSTITUTION BEGIN -->

The absolute link will be rewritten.

Javascript and JSON Parsing

Javascript and JSON strings are not captured by default, and require integration in order to be captured. In the absence of the Smartling markup, the debug mode will not display comments in front of the string, which is a sign that the content is not being detected by the GDN parser.

<!-- JS PARSING BEGIN -->

Indication that Javascript is being recognized by the GDN parser and will ingest any applicable content for translation.

<!-- JSON PARSING BEGIN -->

Content, specified by keys, is being parsed as JSON for translation.

If this comment does not appear, Smartling markup will have to be added for the JSON strings.

This article is for users participating in the beta release of the new Smartling experience. This document is intended to help you locate all of your existing features in the new experience. It also covers 3 new features only available in the new experience. Comprehensive updates to our documentation in the Help Center will be done at general availability.

Viewing the New Experience

If you are part of the closed beta, you will see the new experience upon login. You'll be able to try out the new experience while still having the opportunity to revert back to the classic view.No data will be lost if you switch between experiences during the beta release.

To switch between experiences, click on your profile icon in the upper right-hand corner of your screen and select Profile. On your profile page, toggle New Experience setting ON/OFF.

During your beta, we encourage you to submit any comments or questions through this form.

New Features

All features that were available to you in the classic experience, are available in the new experience. 3 new features are available only in the new experience. They are described below:

Strings ViewThe Strings View is designed to enable you to see all content across workflow states more easily compared to the List View in the classic experience. For example, "Excluded", "Authorized", and "Awaiting Authorization" states can be seen all at once - without having to toggle between different pages. With robust filter features, you can manage your content with fewer clicks.Learn more about the Strings View.

GDN PagesThis new view in GDN projects enables you to easily find the content you need to translate, review, publish, or exclude at a page level. Content is presented in a "files"-like grid view, organized by your site's URLs. Learn more about GDN Pages.

Dynamic WorkflowsAutomatically direct content to a step in one workflow path or another based on set conditions. Learn more about Dynamic Workflows.

New Navigation Experience

We've changed our interface to simplify the user experience and increase focus on key functions that are needed to perform common daily tasks. As a best practice, the use of jobs is encouraged, so that you can take advantage of the jobs dashboard and associated features.

Key changes to highlight include:

Top navigation: This has been simplified to the areas that you need to manage, track and report on your translation requests. Account level settings and configurations are still available, accessed from within the new Account Settings menu.

Project Summary: The project summary page has a new look and feel, and is now more actionable. It provides information on jobs, open issues, and deeper insight into the progress across languages

Project Settings:Click on the gear icon on the top right of the project summary to view and manage key project settings such as active languages, workflow, and linguistic packages.

Locating Features (Classic vs. New Experience)

Account Dashboard

API Keys

Team

Project Settings

Content

GDN

Connectors

Reports

Account Dashboard

CLASSIC:Click the Smartling logo to access the Account Dashboard.

NEW: Click the Smartling logo to access the Account Dashboard.

Strings View

API Keys

CLASSIC:Click the API menu.

NEW: Click the Account Settings dropdown arrow and select API.

Team

CLASSIC:Team > People/Agencies

NEW: Click the Account Settings dropdown arrow and select Team.

Project Settings

Languages (NEW)

This is a new page. You can add or remove a language, and configure a style guide for a project using this page.

NEW: Projects > Select a project > Gear Icon > Project Settings > Languages

Workflows

CLASSIC:Projects > Select a project > Project Settings > Translation Workflow

NEW: Projects > Select a project > Gear Icon > Project Settings > Workflow

New! Learn about Dynamic Workflows here

Content

Files

Upload a File:

CLASSIC:Projects > Select a project > Content > Files > Upload Files

NEW:Projects > Select a project > Upload Files

Request a Translation:

CLASSIC:Projects > Select a project > Content > Files > Select the files > Request Translation

NEW:Projects > Select the files > Request Translation

Translations (List View)

CLASSIC:Projects > Select a project > Content > Translations ("list view")

NEW: Projects > Select a project > Gear Icon > Workflow Summary > Click a word counter

Strings View (NEW)

Learn more about the

NEW: Project > Select a project > Click a file > Click a language link

Image Context

This is for uploading an image, such as a JPG or PNG file, for context.

CLASSIC:Projects > Select a project > Content > Image Context > Upload Files

NEW: Projects > Select a files project > Context tab > Upload Files

GDN

GDN Pages (NEW)

This is a new page that has no equivalent in the classic experience.

NEW: Projects > Select a GDN project > Pages

GDN Settings

CLASSIC:Projects > Select a GDN project > Global Delivery Network > Domains

NEW: Projects > Select a project > Gear Icon > Project Settings

GDN Capture Domain (NEW)

All new GDN projects now have an automatically configured "capture domain" for each domain that is added to that project. This is a localized domain that can capture content, but uses "pseudo localization" to show all strings rather than the actual translations. In other words, all content that passes through the proxy will appear pseudo-localized.

This is useful because:

It's a great way to see what is or isn't getting captured by the GDN, or rather, what is or isn't passing through the proxy.

It is an alternative to arbitrarily picking one target language and browsing the site in its translated state (if available).

It's easy for the user to read the content and identify what has or hasn't been captured.

edit_mode URL parameters are not supported.

NEW:Projects > Select a GDN project > Pages > Capture Domain

Connector Settings

Zendesk, Contentful, Marketo, Salesforce, Hubspot, etc.

CLASSIC: Projects > Select a connector project > Project Settings > Connector Settings

NEW: Projects > Select a connector project > Gear Icon > Project Settings > Connector Settings

Reports

All reports are now available account-wide and access from the top navigation "Reports" menu.

This article is for Translators, Editors, or Reviewers.

Smartling allows Translators to translate SubRip (SRT) files with video context, for more accurate translations. While largely the same as our CAT tool interface for text, there are a few key customizations for video translation. Consult the CAT Tool Overview page for general info about Smartling's CAT tool.

Play/Pause

Like any standard media player, you can toggle the video on or off using the play/pause button. You may click on the video itself or the play/pause button on the far left of the media controls panel.

Replay

Replay will repeat the segment that is currently active, i.e. whatever segmentyou'veclicked into. The segment will repeat once every time replay is clicked.

Loop

The loop command will keep a segment looping indefinitely. While loop is enabled (the icon will turn blue if its enabled), clicking into any segment will automatically start playing that segment and keep it looping. Pressing the pause button will pause the loop.

Autoscroll

Autoscroll plays through the entire video; its particularly useful for reviewing translations.

Playback Rate

Playback rate controls the speed the video is playing. Its set to 1x by default. Click on this option to slow down or speed up the video.

Insert a New Line in a Subtitle

Use the insert new line command.

Change Keyboard Shortcuts

Hover over any command to show its keyboard shortcut. If youd like to change the shortcut, you can do that by selectSettingsin the top right of the screen, then selectingKeyboard Preferences.

Timestamps

SRT files are divided into segments with timestamps. You can see the timestamps of whatever segment is currently active in the additional details panel in the top right underVariant.

It is not currently possible to edit an SRT files timestamps.

This article is for Account Owners and Project Managers using the Global Delivery Network.

When a user requests pages on your localized site, the Global Delivery Network (GDN) will add additional headers when retrieving content from your source site. These headers are useful for identifying traffic on your localized site and serving custom content.

To learn how to use headers, see Display Language-Specific Content.

View Headers

To view all headers that are sent from the Global Delivery Network to your source site, you can append /__smartling/api/headers.htm to the end of any URL on your localized site (i.e http://localized-domain.com/__smartling/api/headers.htm). The resulting page will show you all headers that are sent to the source domain.

For information on additional preview modes, see Global Delivery Network Preview Modes.

X-Language-Locale

The X-Language-Locale is a custom request header added by the GDN. This header specifies the language being requested. You can use a web server configuration (i.e Apache, Nginx) or server side logic (i.e PHP, Node.js) to detect this header and its value.

Format of the header:

X-Language-Locale: [language_code]-[COUNTRY_CODE]

For example:

French (France): X-Language-Locale: fr-FR

French (Canada): X-Language-Locale: fr-CA

English (United Kingdom): X-Language-Locale: en-GB

Spanish (International): X-Language-Locale: es

Russian: X-Language-Locale: ru-RU

To find out the value of your custom header:

Do one of the following:

In the New Experience, from your GDN project, click the gear icon >Project Settings>Domains, then click the globe icon.

In the Classic Experience, from within the Smartling Dashboard, selectGlobal Delivery Network > Domains then click the globe icon.

Click the localized domain. Then click on the Arrow next to the language and choose Edit Localized Domain. The value next toX-Language-Locale displays the value that the GDN will send for the X-Language-Locale header. To change this value to use underscore instead of dash, click on the drop down down to make your change, then click Save.

Other Headers

X-Forwarded-For

The X-Forwarded-For request header will identify the originating IP address of the request. Since your source site will only see the Global Deliver Network IP addresses, this header is useful for identifying the IP address of your end user.

For more information visit https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For

X-Forwarded-Proto

The X-Forwarded-Proto request header will identify the HTTP protocol (http or https) of the end user making the request. Smartling will not automatically redirect to https and will retain the protocol used by the end user. This header will have a value of http or https.

For more information visit https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-Proto

X-Forwarded-Port

TheX-Forwarded-Portrequest is the port that the end user used to access your site. This will usually be 80 for HTTP and and 443 for HTTPs.

X-Amzn-Trace-Id

TheX-Amzn-Trace-Id request header is added by our load balancer for troubleshooting purposes.

If you would like to send any other custom headers on your localized site, please contact your Smartling Customer Success Manager or use an Advanced GDN Rule.

The file types below are currently supported by Smartling. Click into each file type to learn how to integrate your content with Smartling:

File Type

Extension

File Size Limit

Android XML

.xml

10MB

Comma Separated Values

.csv

10MB

DITA

.dita

10MB

Gettext

.pot (or .po but orignal source should be .pot)

10MB

HTML

.html

10MB

InDesign

.idml

100MB

iOS Strings

.strings, .stringsdict

10MB

iOS Plurals Localization Library

.stringsdict

10MB

Java Property Files

.properties

10MB

JSON

.json

10MB

MadCap Lingo ZIP Package

.zip (containing .xliff)

20MB

Markdown

.md, .markdown

10MB

Microsoft - Word

.docx

20MB

Microsoft - Excel

.xlsx

10MB

Microsoft - PowerPoint

.pptx

50MB

Plain Text

.txt

10MB

Qt Linguist

.ts

10MB

RESX

.resx, .resw

10MB

SubRip

.srt

10MB

TMX **

.tmx

1GB

XLIFF

.xlf, .xliff, .xml

10MB

XML

.xml

10MB

YAML

.yaml, .yml

10MB

PDF *

.pdf

Not Supported

*You cannot upload PDF files. It's best to acquire the file in its original format, such as one of the supported file types above (most commonly, InDesign or Microsoft Word), and translate that file.** TMX files can be uploaded by managers with sufficient permissions using the Translation Memory Import flow.

This article is for Account Owners and Project Managers.

To download the Smartling logs:

Open the Sitecore Log Viewer application.

Retrieve the most recent file with the SitecoreLocalization prefix. Open the file and download it.

If you have direct access to the server with Sitecore, you can find the log file in the Data\log subfolder.

This article is for Account Owners, Project Managers, Requesters, and Translation Resources. If you're an Agency Account Owner, a Smartling Customer Success Manager will email you credentials. Available in all plans.

Complete Registration Process

When your account is set up, you'll receive an email notification.

Click on the link from within the email to complete your registration process.

You'll be prompted to fill out your details, add your location, and the languages that you're capable of translating.

You'll then gain access to the Smartling dashboard. (If you're experiencingissues accessing the dashboard, try clearing out your cache.)

If you're a Translation Resource and unable to see the dashboard, it's likely because you haven't been assigned to any content yet, and you should contact your customer or translation agency to have you added to a project and workflow.

Access the Smartling Dashboard

At any time, you can access the Smartling Dashboard by going to dashboard.smartling.com where you'll be prompted to enter your credentials.

Forgot your password? See Reset Password.

This article is for Account Owners and Project Managers.

Smartling offers six roles in the platform with different permissions:

Account Owner: The role with the highest level of permissions, typically manages the translation process from capture to delivery, including all account and project setting administration, as well as all users across all projects under the account.

Project Manager:Manages the translation process from capture to delivery within a particular project, including settings and users. The PM needs to be given access to specific projects to be able to see and modify anything in that project. Account Owners can add Project Managers. Project Managers can add additional Project Managers to the projects they have access to.

Agency Account Owner:An Agency Account Owner manages content and resources they are given access to.

Translation Resource Manager (TRM): Assigns translation resources to workflow steps and languages to which they themselves have access. A Translation Resource Manager may be part of the client's project team or a translation agency. Agency Translation Resource Managers can only manage translation resources from their agency. Both can also perform work themselves.

Translation Resource (TR): Translates, edits, or reviews content. Only has visibility into workflow steps and languages they have been given access to. When revising content, it will be categorized as either "Edit" work or "Review" work depending on how the workflow step is configured. Workflow configuration also determines if content may be available to all resources without assignment, require assignment to specific resources, or be available for claiming (self-assignment) by resources.

Requester:Can upload files and request translations in any of the languages available in the project that they have been given access to. Monitors jobs after they have been authorized, using a limited view of the Smartling dashboard. To add Requesters, the Requester Portal feature must be enabled for your account. Contact your Smartling Customer Success Manager or Account Manager for more information.

The grid below defines the default permissions of each user role. Some permissions can be configured. Read ahead to learn more about Configurable permissions.

Account Owner

Project Manager

Agency Owner

TRM

TR

Requester

Global Search

x

x

Clone a project

x

x

Archive a project

x

x

Rename a project

x

x

Create a project

x

Watch a project

x

x

Add a language

x

x

Disable a language

x

x

Upload files

x

x

Update files

x

x

Delete files

x

x

Add file instructions

x

x

Upload image context

x

x

Create a job

x

x

x

Edit due dates

x

x

x

x

Download job activity report

x

x

Close a job

x

x

Cost estimate for a job

x

x

x

x

x

x

Download job files

x

x

x

Download job estimates

x

x

x

x

Manage style guide

x

x

Manage glossary

x

x

Manage translation memory and leverage

x

x

Export glossary

x

x

x

x

Search glossary

x

x

x

x

x

Import glossary

x

x

Manage quality checks

x

x

Add glossary terms

x

x

x

x

x

x

Manage linguistic packages

x

x

Add users

x

x

x

x

Remove users

x

x, but only PM, TR or TRM

x, but only TR and TRM

Manage workflow assignments for agency

x

x

Create API token

x

x

Authorize/exclude/delete content

x

x

Tag content

x

x

x

x

Remove content from a job

x

x

Move content between workflows

x

x

Assign content

x

x

x

x

View content history

x

x

x

x

x

Managing issues

x

x

x

x

x

Enter/edit translations

x

x

x

x

x

Submit content to next step

x

x

x

x

x

Search and filter content

x

x

x

x

x

x

Create job automation rules

x

x

Customize workflow

x

Create workflow

x

x

Copy workflow

x

x

Edit default workflow

x

x

Manage Google API key

x

x

Site traffic*

x

x

Tracked URLs*

x

x

Processed words

x

x

Issues

x

x

Smartmatch leverage

x

x

Word counts

x

x

x

x

Words under Management

x

x

Content velocity

x

x

Content changes

x

x

Translation Memory leverage

x

x

Configurable Permissions

Account Owners and Project Managers can configure access to Linguistic Assets for Agency Account Owners (AAO), Translation Resource Managers (TRM), and Translation Resources (TR) from the Permissions tab in the User's Detail page.

If you are working with a Language Service Provider/Vendor, it is recommended that you grant your Agency Account Owners access to an added permission, and then have them grant the same access to their Translation Resources.

ahead

There are four types of Linguistic Asset permissions:

Glossary : For the management of glossaries and glossary content.

Style Guide : For the management of Style Guides.

Leverage : For the management of leverage configurations.

Translation Memory : For the management of Translation Memories and content in a TM.

Skip to learn more about permission details.

Add Permissions

To add a permission:

Click on Account Settings > Team

Click on a User Tile

Click on the Permissions Tab

Click Add Permission

From the dialogue box, choose a Permission Type from the drop-down

Choose the assets the user should have added permissions to

Choose permissions from the Available Permissions section to grant to a user by using the checkboxes

Click Add

The permission will be added to the User's Permission page.

Delete Permissions

To delete a permission:

Click on Account Settings > Team

Click on a User Tile

Click on the Permissions Tab

Select the checkbox next to the permission on the Permissions page you wish to remove. Use the checkbox at the top left of the table to select all permissions.

Click Remove Permission

The permission(s) will be removed from the user's profile.

Permission Details

Glossary Permissions

Create and Edit Terms: Add/Edit/Remove terms in a glossary.

Export Glossary: Export a glossary to file.

Update existing Glossary from file: Import a file to update an existing glossary

Style Guide Permissions

Edit Style Guide content: Edit the contents of a Style Guide

Leverage Permissions

Edit Leverage: Edit all the details of a leverage configuration.

Edit Leverage source: Edit the details of each leverage entry, but cannot add/remove actual leverage entries.

Translation Memory Permissions

Export a Translation Memory: Export a TM to a file

Edit translations: Edit the content of a TM

Browse a Translation Memory: See the content of a TM.

Import translations: Import a TMX file into an existing TM.

Delete strings: Delete content from a TM.

Move strings: Move content to a new TM (if the user has access to another TM).

This article is for Translators and Editors.

In addition to viewing previous translations for similar strings (fuzzy matches) in the Language Resources panel of the CAT tool, you can search all of the available translation memory to see past translations for any string, in any target language.

You can perform different types of searches, for example:

A phrase search such as: hello world

Case sensitive versus case insensitive search

Search Translation Memory

From the CAT tool, click Search TM.

Select a target language from the drop down menu. You also have the options to include:

Search Target: By default, the search is on words in the source, however, if "Search Target" is enabled, then the search will be on the words in the translation.

Published Only: The search will only return results of strings that have been published.

Match Case: The search will take case into account. Therefore, searching for "LOGIN" would not return "Login".

Exact Match: If this is selected, the search result has to exactly match the query, character for character.

Enter keywords in the search field and press Enter.

From within theSearch TM tab click New window to keep it open in its own separate window. This is particularly useful if you're using an external monitor. It allows you to perform a concordance search and view context at the same time.

Display String Details

The TM search results display details about the translated string, such as:

Source

Target

The name of the Translator along with the respective TM

The date that the TM was last modified

Whether or not the string has been published

Insert TM Search Result

Clicking the down arrow beside a string in the TM search results will insert the translation into the target segment for the string you are working on.

Machine Translation

Smartling also displays a machine translation (MT) for each string in the Language Resources panel. Click on the MT string to insert it into the translation column of the string you are working on.

This article is for Account Owners and Project Managers.

As an Account Owner or Project Manager, it may be necessary to find and replace translations within a project or account to ensure translation consistency. Through theContent Search feature, you are able to search for content or translations across your account, regardless of workflow state. This is particularly useful if you need to change a product name, a proper noun, or correct a widespread error.

Keep in mind the following:

Content search and replace may not update all translations in the translation memory. For example, TMX files can be used for translation memory leverage i.e. SmartMatch and TM suggestions in the CAT tool, but content search and replace does not cover TMX files, only translations that appear in Smartling projects.

You can't perform a content search and replace on tags and placeholders.

Access Content Search

Do one of the following:

In the New Experience, click Search in the top bar.

In the Classic Experience, click the Smartling logo > Content Search.

Search and Replace

From theProjectsdrop down menu, select a project (or multiple projects). This will activate the other fields.

In this example, theLanguagefilter is set to "Spanish", and theSource Stringis "teas". ClickingSearchwill show a list of source strings that contain "teas", and all of the Spanish translated strings that contain "ts".

Turn onReplace mode. This allows you to enter the translated word(s) with the word(s) you wish to replace it with. In this example, "ts", the Spanish word for "teas", will be replaced by "cafs" (coffees). Entering "ts" in theTranslation to Replacefield automatically highlights every Spanish string that contains "ts".

Enter a word in the Replace Translation With field. In this example, we're using "cafs".

Select the strings for the words you wish to replace. (You need to have filled out theReplace Translation Withfield and selected your string(s) forMatch Whole WordandCase Sensitiveto become active.)

Click Replace.

If you've selected all source strings, instead of manually selecting individual strings, note the following:

Match Whole Word:

Turn this ON so that an exact match of the word(s) will be replaced. In this example, only an exact match for the word, "ts", will be replaced.

If this setting is OFF, the letters "ts" could appear within a word, and be mistakenly replaced.

Case Sensitive:

Turn this setting ON for an exact case sensitivity match when replacing words.

Turn this setting OFF if case sensitivity is not an issue when replacing words.

This article is for Account Owners and Project Managers.

The Smartling Adobe Experience Manager (AEM) Touch connector allows you to translate AEM content with context. Translations are requested from within AEM, and translated content is automatically sent back to your environment.

The connector supports translation of pages, i18n dictionaries, and tags via AEM Translation Projects.

Request Translations

Once you have installed and configured the AEM Touch connector, you can begin submitting content to Smartling for translation.

In the AEM Touch Page Editor, the Smartling: Translate as Jobmenu item will allow you to submit the current page and child pages for translation.

Translate Pages

From the Sites view, open the page for translation in the AEM Touch Page Editor by selecting it and clicking Edit.

Select Smartling: Translate as Job from the Page Information menu to bring up the Smartling - Translatewindow.

Type in a Job Name for this submission and select a Due Datefor translation, if applicable, or select an existing job to add this submission from the Add to Job tab.

Check Authorize Job if you'd like to authorize the content for translation automatically.

Check Include all Sub-pages to include all of the current pages' sub-pages in the submission.

CheckForce resubmission (Required if page is unchanged).

Select the languages to translate in this submission.

Translate Content in Bulk

The Include all Sub-pages option in the Smartling - Translate window allows bulk submission of a page and all of its sub-pages.

Not seeing all of your page content available for translation in Smartling? Check that all of the relevant Properties are included for translation in Tools > General > Translation Configuration for the context path being submitted in AEM.

Resubmit Options

The Force resubmission (Required if page is unchanged)option in the Smartling - Translate window allows you to submit an original page to Smartling even if there are no changes after the last submission. By default, AEM doesn't submit such pages, but if for some reason you need to resubmit an original page, you can enable this option and the Smartling connector will make AEM think that the original page was modified, and should be submitted for translation.

Include Visual Context with your Translation Request

A Visual Context capture tool is built into the AEM Touch connector, helping linguists get your translations right the first time - reducing translation cost and time to market.

If Visual Context is not displaying properly in Smartling, your AEM Administrator should check the Smartling settings in AEM's Web Console Configuration page, or enable a Proxy Connection in Smartling - Network Settings.

Check the Status of Translations

The Smartling Connector creates a smartling-auto Project folder in AEM, with subfolders for each date content is submitted. To check the status of a Job, go to the corresponding folder within the smartling-auto Project and open the Translation Project. Click the ... icon on the Job to view the contents and State of each page in the Job. For more detailed translation progress information, check the Job status in the Smartling Dashboard.

Check Translation Status More Frequently

By default, the AEM Touch connector checks checks translation progress once per day, but you can set it to do so more often.

To set the AEM Touch connector to check translation progress every four hours:

Open the AEM Web Console (/system/console/configMgr)

Scroll down to Translation Platform Configuration.

Next to Scheduler Cron, enter the new cron expression: "0 0 0/4 1/1 * ? *"

Save your changes.

Download Translations

AEM will download translations automatically after all of the content in the Translation Project is published. There may be a delay after content has been translated as the download process runs once per day. The AEM Touch interface does not allow for manual download of translations from Smartling.

Handle Updates to AEM Content

The AEM Connector does not automatically resubmit pages with updates. To resubmit a page with updates, use Smartling: Translate as Jobonce again to submit the page and create a new job. Only new strings that were not previously submitted will be created and added to the new job.

Request Translations by References Panel

Smartling does not recommend using the default AEM submission flow via the References panel, nor manually creating translation projects.

When you submit pages via the References panel, the Smartling connector will do the following:

Create a Smartling job with a name that consists of the current date, page path, and unique identifier.

Attach uploaded file to the job above.

Job will not be authorized automatically. You can can decide when to authorize the job as needed.

Additional notes:

A Smartling job is created for every AEM project. For example, you might submit a page for three languages. AEM will then create three translation projects (one per language), and in turn, the Smartling connector will create three jobs.

All pages that are added to the same AEM project will be attached to the same Smartling job. For example, if you submitted "pageA" for "French", it will be added to the Smartling job "2018-01-01 - pageA - 1". Later on, if you submitted "pageB" also for "French", and used the existing AEM translation project, then "pageB" will be attached to the Smartling job "2018-01-01 - pageA - 1"

Smartling jobs are not authorized automatically.

This article is for Account Owners and Project Managers.

The Smartling Zendesk connector allows you to translate Zendesk content with context. Translations are requested from within the Smartling platform, and translated content is automatically sent to your Zendesk instance.

The connector supports translation of categories, sections, articles,and dynamic content.

Request Translations (New Experience)

Once you have linked your Zendesk account, your content will be displayed in Smartling. From here, you can choose which content to translate:

From your Zendesk project, click theZendesktab.

UnderAsset Type, select the type you want to translate.

Select the items to translate.

ClickActionsand selectRequest Translation.

In the dialog that appears, select theLanguagesyou want to translate to.

Click Authorize.Your content will be automatically authorized for translation into the Default Workflow set in your project.

Both draft and published content will be displayed in Smartling for translation. You can request translation of draft content, however context is only available for published content.

Request Translations (Classic)

Once you have linked your Zendesk account, your Zendesk content will be displayed in Smartling. From here, you can choose which content to translate:

From within your Smartling Zendesk Project, click on Zendesk > Translate Content.

Toggle between Article, Category, Section, and Dynamic Contentusing the buttons in the upper right-hand corner of the screen to locate the content you want to translate.

Once in your desired Zendesk content area, select the items you want to translate. Select individual items using the checkbox next to the item name. Select all items from the content area by using the checkbox next to Request Translation.

Click Request Translations.

Choose the languages you'd like to translate to, or use the Select All checkbox to translate to all languages available in your project.

Click Request Translations.

Your content will be automatically authorized for translation into the Default Workflow set in your project.

Both draft and published content will be displayed in Smartling for translation. You can request translation of draft content, however context is only available for published content.

Check TranslationStatus (New Experience)

To check the status of your translations, from your Zendesk project, click the cog wheel and selectZendesk Progress. Translation progress is indicated with a progress bar next to each asset.

Check TranslationStatus (Classic)

Status of your Zendesk translation requests can be tracked in the Translation Progress tab.

From within your Smartling Zendesk Project, click on Zendesk > Translation Progress.

Translation completion is indicated as a percent in the Percent column next to each article.

Download Translations to Zendesk (New Experience)

As translations are completed, they are automatically sent to your Zendesk instance every three hours.

To perform a manual download of translated content to Zendesk:

From your Zendesk project, click theZendesktab.

Select the translated assets to download.

ClickActionsand selectExport Translation.

For content lower in the Zendesk content tree to appear in your translated Help Center, the parent areas must first be translated. For example, a translated article will not appear until its corresponding section and category are translated and published.

Download Translations to Zendesk (Classic)

Once translation is completed for a given asset, the translations are automatically sent to your Zendesk instance every 3 hours.

To initiate a manual download of translated content to Zendesk:

From within your Smartling Zendesk Project, click on Zendesk > Translation Progress.

Select individual items using the checkbox next to the item name. Select all items from the list by using the checkbox next to the Title field.

Click Export to Zendesk.

The parent content areas must be translated in order for content lower in the Zendesk content tree to appear in your translated Help Center. For example, a translated article will not appear until its corresponding Section and Category are translated and published.

Handling Updates to Zendesk Content

Your Smartling Administrator can configure the connector behavior for handling updates to your source articles.

If your connector is set to Auto mode, changes to your source content will be automatically submitted to Smartling for translation every 3 hours. The connector will not automatically submit new articles, only updates to articles that have been submitted for translation in the past.

If your connector is set to Manual or Disable mode, or if you have created new content in Zendesk, you will need to request translations using the method described above.

This article is for Account Owners and Project Managers.

Aleverage configuration controls which completed translations are available to a given project or set of projects, and how these translations can be applied.

Create a Leverage Configuration

Account Owners and Project Managers can create a new leverage configuration.

Do one of the following:

In the New Experience, go to Account Settings > Linguistic Assets and click Leverage.

In the Classic Experience,go toAssets >Leverage.

ClickCreate Configuration.

Enter aname for the new leverage configuration.

Select a source language.

Enter a description.

ClickCreate Configuration to create the new leverage configuration orCancel to exit.

Pick aname that will distinguish the leverage configuration from all others. This might be the type of content (general purpose, legal, etc.), a brand name (Best Soft Drink, Diet Soft Drink, etc.), or any other unique characteristic of the content.

Add a Translation Memory Source

Account Owners and Project Managers can add a translation memory, translation memory group, or translation memory exchange (TMX) file to a leverage configuration. Doing so makes completed translations from that source available to projects using the leverage configuration.

ClickAdd Source.

Select a translation memory source.

ClickAdd Source to continue orCancel to exit.

Your selection will appear in the list of translation memory sources.

UnderLanguage(s):

Select All Available to make the source available for every locale for which it contains completed translations.

Select a single locale to make the source available for only one locale.

UnderPenalty, select a percentage by which all matches against this translation memory source should be reduced. For example, selecting1% will reduce matches to 98% from 99%, 84% from 85%, and so on.

ClickSave to add the source to the leverage configuration or X to exit.

You can make translations for one locale available for a different locale, for example, Argentinian Spanish for Chilean Spanish. See enable cross-locale leverage for more information.

Penalize a translation memory source only if you want linguists to be more cautious when re-using its translations, for example, if you distrust or are uncertain of their quality.

Penalizing a translation memory source doesn't affect SmartMatch. If you want linguists to evaluate these matches, customize SmartMatch behavior toFirst Revision Step orDisabled.

Customize SmartMatch Behavior

SmartMatch allows you to bypass workflow steps automatically for certain types of matches. See customize SmartMatch behavior for more information.

Prioritize Translation Memory Sources

If a leverage configuration contains more than one translation memory source, Account Owners and Project Managers can set the order in which they'll be evaluated.

linguistic packages

To reposition a translation memory source, click and drag theorder iconuntil the translation memory source appears in the correct place; then release your mouse.

Matches are ranked based on a number of factors, one of which is the relative priority of the translation memory source.

Remove a Translation Memory Source

Account Owners and Project Managers can remove a translation memory source from a leverage configuration.

UnderActions, clickX and thenConfirm to remove a translation memory source. Removing a translation memory source doesn't affect completed translations.

Rename a Leverage Configuration

Account Owners and Project Managers can rename a leverage configuration or change its description.

When viewing the list of leverage configurations, underActions, click the pencil icon. If viewing a specific leverage configuration, clickEdit Details.

Delete a Leverage Configuration

Account Owners and Project Managers can delete a leverage configuration.

If viewing the list of leverage configurations, underActions, click the trash icon. If viewing a specific leverage configuration, clickDelete.Deleting a leverage configuration doesn't affect completed translations.

If the leverage configuration is being used by one or more, you will be prompted to select a replacement leverage configuration before confirming deletion.

Version 5.1.3

New Features

You can now translate multiple content fragments simultaneously.

Version 5.1.1

New Features

You can now submit content fragments through the new Translate menu item.

Version 5.0.2

Bug Fixes

Fixed issue where a Smartling job was authorized even when not all AEM translation jobs were created. The translation workflow's polling of uploaded files is only for 20 minutes. After that, the job will be authorized for successfully uploaded files.

For how translation projects in 6.4 are created, we delegate the creation of AEM multi-language translation projects to translate content instead of doing it programmatically. Projects that were created via the "Translate as a Job" Smartling pop-up is now the same as those created through the AEM Reference panel. One project includes one-per-language job translation.

Changed automated launch promotion feature to disable by default.AEM in 6.4 provides a built-in automated promotion. The same Smartling functionality is disabled by default.

Version 5.0.1

Bug Fixes

Fixed context issue. Context connection(s) was not automatically established due to the issue with getting a list of Smartling configurations.

Version 5.0.0

The AEM Touch Connector version 5.0x will only work with AEM 6.4 and above. (AEM Touch Connector version 4.0x will only work with AEM 6.3 and below.)

Bug Fixes

Fixed getting Smartling configuration by page path.

Fixed Smartling UI styles: Translate as Job menu item

Added the new security group:projects-smartling-default-project-translationreviewer

Version 4.1.2 and 4.1.3

Bug Fixes

Fixed locale format check provided by Smartling using locale mapping.

Fixed removal of live relationships on the target translation resource.

Version 4.1.1

Improvements

Added property mappings for translated properties, which allows you to specify how Smartling should parse each propertys content.

The Test connectionbutton now checks the context connection, which simplifies troubleshooting by letting you know when context is not configured.

We now prevent a stuck page in the workflow if one of the workflow steps has a validation error, or if no AEM translation project was created.

Bug Fixes

Resolved an issue where the connector was unable to upload all requested languages.

Version 4.0.15

Improvements

Added capability to configure Custom Placeholder.

Version 4.0.14

Improvements

Improved the behavior for when something went wrong while creating jobs for translation via AEM. Now, the connector waits 20 minutes for the new job, and if all AEM translation jobs aren't created, then an error is written to the log summarizing what was and wasn't created.

Bug Fixes

Fixed the behavior of theForce resubmission (Required if page is unchanged) option when Include all Sub-pages is also checked.

Version 4.0.13

Bug Fixes

You'll need to reset your browser's cache to ensure that the new Smartling Javascript version will load. (Reset cache by selecting the "Cached images and files" option.)

Fixed page submission in Smartling popup. (Previously, the page could be submitted regardless of validator status. Now, the connector allows page submission only if all validators have no errors.)

Fixed resetting validation errors icon on the Smartling popup when it's opened multiple times. Validation error icons are cleared when the Smartling popup is reopened, or when a user switches between the Create Job and Add to Job tabs.

Sync a label text on the submit button when user switches between Create Job and Add to Job tabs.

Version 4.0.12

Bug Fixes

Fixed issue with Smartling namespaces for Content Fragments. When you update original content and resubmit it to Smartling, AEM generates unique file names. The connector uses the same namespace in order to share strings of the same asset in different files.

Fixed length of auto-generated Smartling job name (when you submit pages via References panel instead of Smartling popup). Previously, it could be too long and was rejected by Smartling.

Version 4.0.11

Improvements

Reset the cache of your browser (select the "Cached images and files" option) to make sure that the new version of Smartling java-script will be loaded.

Added the new validator to the Smartling pop up that validates that the checkbox Auto-execute is set in the Translation Integration configuration.

Implemented a workaround for the inconsistency bug in AEM. You may notice this bug when you submit a brand new page for translation, but sometimes it doesn't appear in Smartling. If you check your AEM projects, then you may see that a submitted page is present in a randomly generated translation project instead of a project that was passed to an AEM translation framework. In a nutshell, the Touch connector creates non-existing language copies before asking AEM to translate pages. It's done by the new step in the Smartling workflow. If you want to revert this improvement, then you can just remove the workflow step.

After this release, you should no longer see files in Smartling jobs with auto-generated names. As well, messages in logs such as this, should be removed:

Translation object in project path="/content/projects/smartling-auto/2018/08/03/user_-_italian-22-20-56-707" is not committed for translation yet

Version 4.0.10

Improvements and Fixes

Improved package installation behavior for customized language mapping. Previously, if you installed a new version of the AEM Touch Connector, it would overwrite your custom language mapping. With this new version, the connector will try to merge your custom language mapping with the default language mapping.

Added workaround for the issue when AEM tried to re-execute a completed translation workflow instance, more specifically when components such as ExternalProcessJob* are restarted. For unknown reasons, AEM took all instances of the workflow steps that implement WorkflowExternalProcess interface and tried to re-execute them. As a result, the Smartling workflow steps tried to resubmit pages. The connector now tries to detect multiple incorrect executions and do nothing with adding them into the log. Example: wfStep="Send Page for Translation" has been already executed.

Version 4.0.9

Improvements and Fixes

You can now you can use https in context configuration.

Added a new option which allows resubmission of original page to Smartling, even if it was not modified. By default, the AEM translations framework does not allow this.

Attach files to Smartling jobs when submitting pages from the References panel. It's not recommended to use the References panel, but if you have to submit pages, then the Touch connector will take care of it, and will create a Smartling job with the attached files.

Version 4.0.8

Improvements and Fixes

Improved stability of Automated Launch Promotion. (Previously, it would try to promote the same launch twice when it received multiple concurrent events from AEM.)

Restored functionality of notifying user as soon as upload is completed or failed. The connector creates task in the inbox.

Version 4.0.6

Improvements and Fixes

Connector now always uses TLS1.2 for HTTPS connections regardless of Java version. (It was TLS1.0 for Java 7.)

Improved error handling edge case when AEM translation project is created and configured but then the Smartling configuration gets deleted.

Version 4.0.5

If version 4.0.4 has been installed to AEM, Adobe Consulting Services should be deleted from packages, manually.

Improvements and Fixes

Removed Adobe Consulting Services as it brings several dependencies that can't be satisfied in a variety of AEM instances.

Fixed validation for target locales. Previously, target locale validation was case sensitive, so if a page was submitted for 'de_DE locale' and language mapping was configured for 'de_de locale', validation would fail.

Added possibility for providing callback URI.

Enabled Launch Promotion by default.

Extended parse JSON configuration by providing possibility to add fields that will be sent to Smartling along with 'smartling.translate_paths' directive.

Added test connection button, so the user can test whether the provided credentials are suitable for configuration.

Added validation within the submitting page, so now the error is shown right after the submission.

Version 4.04

Improvements and Fixes

Added inbox notifications. From now on, you will receive an email notification when a request is completed. The notification will either contain a link to a Smartling job, or a reason as to why the submission request failed. For example, if all locales are filtered in the initial step due to the fact that the appropriate language copies are up to date, or missing language mapping configurations, then you will see an error. In screenshot below, the results of three submissions are shown: one successful, and two with errors (see from bottom to top).

Fixed issue with missing folder title. When you a submit page for translation, the Touch connector creates folders for storing AEM translation projects. Before, these folders didn't have a title.

Fixed issue with how connector detects that the translated page is up to date and should not be submitted to Smartling. Fixed comparison source page, last modified date, and language copy last modified dates.

Version 4.0.3

Improvements and Fixes

Modernized flow in order not to create AEM translation project for up to date language copies. If nothing has changed in a source page, content shouldn't be submitted and project shouldn't be created for those locales, for which content has been sent.

Version 4.0.2

Improvements and Fixes:

Extended String Duplicates processor in order to allow user to configure name space that is sent along with the file. When Use legacy namespaces is checked, strings will be shared across files on the same page, otherwise, content for each language will be uploaded as a unique string.

Version 4.0.1

Improvements and Fixes

Fixed NPE for Automated Launch Promotion feature.Fixed issues with locale mapping. AEM locale code was used for Jobs API calls (instead of Smartling locale code).Improved logging:Added more logging for jobs related operations.Removed sensitive information from logs (Smartling refresh and access tokens).Better handling of error case when pages were submitted to job but no new strings were added.Updated log messages when asset doesn't have translatable strings or asset format is not supported (examples: PNG, PDF).

Version 4.0.0

Important: This release contains 2 major changes.

Use our new version of Jobs:Smartling account must be switched to the new version of Jobs before using this version. Please contact your Smartling Account Manager.

String sharing:Changed behavior of string sharing: We used to share strings across all locales of the same page. Now, strings that belong to the same page, but with different locales, are interpreted as different strings. For example, you submitted a page for two locales, and as a result, AEM uploaded two files to Smartling. Strings in these two files are shared, and each string is authorized for two locales. If you upload a page for two locales with the new version of the connector, then the two files will upload, but this time, the strings from the first file will be authorized for one locale, and strings for the second file will be authorized for another locale.

Important: This will affect your existing translations. If you changed a page that was previously translated, and submitted it to Smartling, all strings will then be ingested as "new", and translations will need to be reapplied from the translation memory.

Improvements and Fixes:

Integration was migrated from Jobs API v2 to v3.Pages now can be attached to existing job in any state (Awaiting Authorization, In Progress, Completed).

Job may contain files that are authorized for different locales.

Version 3.3.2

Improvements and Fixes:

Authorize job checkbox in the New Job dialog is now unchecked by default.

Version 3.3.1

Improvements and Fixes:

Translation Job Support: Allows submitting of pages even if they were not modified after the last translation.

Automation: Fixed an issue that caused pages to be deleted when a launch is promoted.

Got rid of the deprecated API usage: All background operations are performed on behalf of smartling-touch-connector user instead of admin. To achieve this, a new service user is created with ID smartling-touch-connector. This user is granted Read-Write access to /content and Read access to /etc (as well as, Read-Write access to the connector's internal folders, under /apps and /etc).

Version 3.1.1

Improvements and Fixes

Fixed issues with HTTP proxy support

Fixed issue with submitting content when the target locale is disabled in Smartling.

Version 3.1.0

Improvements and Fixes

The connector now uses Smartling API v2 and is not backwards compatible with earlier versions. After installing you must create v2 credentials and add them to each Cloud Configuration.

Improved context capture performance.

Fixed issue with missing context on some configurations of AEM.

A separate log file smartling.touch.log has been created to capture all the log messages coming from the Connector.

Improvements and Fixes

Improved performance of the connector under heavy loads.

Version 3.0.0

Improvements and Fixes

Support for AEM 6.2 with the following limitations:

Due date on a translation job is not supported even if set on the AEM side.

Reject translation from AEM is not fully supported: once translation is rejected in AEM, the only option is to cancel all the translation job manually, wait until translation is corrected and request translation once again as a new job in AEM.

Version 2.2.0

Improvements and Fixes

Added the ability to configure an HTTP proxy in a single place to be used by the connector - via Felix OSGi Console, Smartling - Network Settings configuration entry.

Support anonymous proxy configuration via Java System properties.

Fixes to translation context to improve quality and make troubleshooting easier.

Version 2.1.0

Improvements and Fixes

Improved string sharing behavior for the case where multiple versions of the same page are being translated at the same time. As of the version 2.0.0 strings have been shared within a page, but if the page was copied into one or more launches then strings in these copies were considered completely different. As of 2.1.0, strings are shared among the page and all its versions in different launches.

The connector package has been renamed from Smartling Translation Connector to the Smartling-Translation-Connector. We recommend to manually remove the old package after installation.

Version 2.0.0

Improvements and Fixes

The string sharing behavior in Smartling TMS has been significantly changed in this release:

Identical strings on different pages are treated as unique strings in Smartling.

If a page was submitted more than once as part of different Jobs, Smartling continues to share translations along all copies of the page.

Users can now control how Smartling should treat identical strings on the same page. Duplicates can be ingested as a single string or as unique strings. This feature is disabled by default but can be enabled from the Configuration Console.

This article is for Translators, Editors, and Reviewers.

Overview

Content in Smartling is generally organized and prioritized in the following way:

Claim

A Smartling project (such as a mobile, web, files, or connector project) may contain one or more jobs. You may have multiple projects, each containing multiple jobs. The Jobs feature allows Account Owners, Project Managers, and Agency Account Owners to group and prioritize content for translation by due date, as well as monitor the progress throughout completion. Each job contains strings, consisting of words or phrases. When using the CAT tool, those strings are broken down into segments. For more information on strings and segments, see Content Parsing.

Jobs Dashboard

As a Translator, Editor, or Reviewer, you can see the jobs that have been assigned to you by your Account Owner, Project Manager, Agency Account Owner, or Translation Resource Manager. The Jobs Dashboard enables you to view all of your tasks in one place, and easily find those which have a higher priority.

Your typical workflow would be to view all of your jobs in the Jobs Dashboard with approaching due dates, and then generate fuzzy estimates to better understand the effort required to complete the job. Once your work is saved and submitted via the CAT tool, the job that is completed will no longer appear in the Jobs Dashboard list.

Login to Smartling to see the Projects Dashboard and Jobs Dashboard. The Jobs Dashboard shows the following columns:

Job: Job name

Project: Project name with a link that brings you directly to your specific project (and subsequently, your list of translations: Content > Translations).

Language: The source and target language. There is a separate row for each language and workflow step combination, therefore the same job name may appear multiple times.

Strings: The number of strings in the job. In other words, if the job is in your list of "Current Work", this is what was assigned to you or claimed by you.

Words: The number of words in the job. In other words, if the job is in your list of "Current Work", this is what was assigned to you or claimed by you.

Task: Translating or editing.

Issues: Number of issues. Click on the number to address the issues.

Task Due Date: The due date for your specific task. For example, you may only be completing a portion of the job, not the entire job.

Job Due Date: The due date for the entire job.

Actions: If you're translating, click Open to launch the CAT tool or click the "more" icon to create a fuzzy match estimate. If you're editing, simply click Open.

A fuzzy match estimate is only available for translation tasks and not editing tasks.

Filter for Jobs

You'll be able to quickly filter on:

Current Work: If you've selected Current Work, you'll have the options to Export Content or Import Translations. Click the More (...) button under Actions and select one of those options.(If the "Offline work" feature is not enabled in the workflow step, Export Content and Import Translations will be greyed out and you won't be able to select either of them.)

Export Content:When using Export Content, Smartling prepares the following files for you:

Content (to translate) - XLIFF file

Glossary - TBX file

Translation Memory - TMX file (50%+ matches for the content of the job)

Import Translations:When using Import Translations, you should upload the same XLIFF file with translations filled in. Once translations are uploaded, they have to be submitted to the next step (either from the CAT tool or from Content > Translations).

Available to Claim:If you've selected Available to Claim, click to add work to your queue.

Upcoming: If there's a Job that contains strings in a workflow step that directly precedes you, then the Job will be displayed in the "Upcoming" tab of your dashboard

Work Not In Job: This allows you to see any translation/editing work in your queue that was not packaged into a job. It shows a breakdown by project, language, and workflow step. You can:

Filter by Account and/or Project.

Launch the CAT tool by clicking Open.

View content in Project > Translation by clicking on the string or word link.

This glossary provides definitions of terms related to the localization industry, and more specifically, Smartling. It is divided into two sections: General and Global Delivery Network.

General

100% Match

When the text of a string matches the text of a string in the translation memory. It's considered a 100% match even if there are discrepancies with tags, placeholders, key values, etc. (This is not to be confused with a SmartMatch.)

Agency

Smartling's label for a Language Service Provider (LSP).

CAT Tool

Computer assisted translation tool. This is where all of the translating, editing, and reviewing takes place.

ccTLD

Acronym for Country Code Top Level Domain, and correspond to a country, territory, or other geographic location. For example, .de (Germany), .uk (United Kingdom), .ca (Canada).

CDN

Acronym for Content Delivery Network (aka Content Distribution Network), a geographically distributed network of servers with the purpose of delivering content to users much faster.

Fuzzy Match

When Smartling uses an existing Translation Memory (TM) to match source content with existing translations in the TM, it will often find word matches that are less than 100% identical. These are called "fuzzy matches" and are represented by the percentage to which they match (typical fuzzy match percentages are 50-99%). Translators can see these fuzzy matches in the CAT tool and choose to edit them instead of translating from scratch.

GDN

See the Global Delivery Network section of this page for more related terms.

Inactive Strings

Inactive strings refer to strings that have been removed from your source/original file. Inactive strings become unauthorized and are removed from the job. If a string is inactive and has no published translations, it will be deleted from the system entirely. However, published translations will remain in the Published queue, and will not be removed, simply marked as inactive. Basically, a string only becomes inactive when it's no longer part of any file in Smartling, and thus, Smartling assumes it should no longer be made available for translation.

If content becomes inactive and removed from the system, Translation Resources will still receive credit for their work.

LSP

Acronym for Language Service Provider.A group, usually operated as a business, who provides professional translation services including translation, editing, review, and proofreading. An LSP typically has a roster of individual professional translators (linguists) who can be assigned to work for specific clients. Also referred to as "Vendors".

Original File

This is an exact copy of the file as it was uploaded to Smartling. Contains the source strings.

Pseudo Translations

The original strings with added characters, to increase the length of each string (by 30 percent or more). Useful when testing your UIs tolerance for longer strings without having to wait for the translation to be completed.

Repetition

When the text in a string is identical to another string in the same set of content, such as a Job. A repetition is not drawn from translation memory, so it is different than a 100% Match or a SmartMatch. However, a repetition is invoiced at the same rate as a 100% Match.

Segments

The primary unit of translation. A segment can be a single word, short phrase, or sentence(s). The translation memory is segment based.

SmartMatch

A string that perfectly matches a string in the translation memory, including any tags, placeholders, etc. SmartMatch compares new strings against existing translations in your leverage configuration to automatically apply translations to strings you've translated before.

Source Words

The total number of words in the original source language, regardless of any fuzzy matches, SmartMatches, or repetitions.

Strings

Piece of translation. Based on the source, strings can be parsed differently. A string is then broken down further, into one or more segments.

Translation Memory

The database of your translated strings and segments. The translation memory is used (leveraged) by translators and automation tools in Smartling to translate new strings and segments faster and consistently. In Smartling the Translation Memory is live in the cloud so it's always up-to-date with the latest translations.

Transcreation

The process of adapting content from one language to another without losing consistency in tone, intent, and style. Unlike translation, where words or phrases are converted from one language into another, transcreation is based on the conversion of the essence of a message from one language to another, rather than verbatim.

Variants

Metadata, such as a version number, date, or URL path indicating the location of a source string.

Weighted Words

An approach to estimating the cost and effort required to translate a job that accounts for Translation Memory Leverage and Repetitions. Calculated by multiplying each word with the corresponding fuzzy match rate.

For example, lets assume your job has ten source words, and that for words with an 85-94.9% fuzzy match, you will pay 60% of the per-word-rate. If all ten words fall into this fuzzy tier, there are six weighted words in the job. The reason is that 10 x 0.60 = 6.

Whitespace

Any unused/blank/negative space separating paragraphs, characters, or graphics within a document.

Global Delivery Network

CDN

See CDN above.

DNS

Acronym for Domain Name Service. A DNS is an internet service from which an IP address is obtained and associated with the name of its server.

Editmode

A parameter appended to the localized URL. Editmode tells the GDN to display different parts of your translated site. They are also referred to as Preview Modes.

GDN

Acronym for Global Delivery Network. It is a Smartling translation proxy tool that enables you to translate your website and web applications without the need to internationalize your site or host, and manage translated content within your systems.

Proxy Server

A dedicated software running on a computer system that acts as an intermediary between your web browser and a server from which you are making a request. The GDN is an example of a proxy server that facilitates the localization of your website.

Pseudo Translation

See pseudo translation above.

Source Site

This is a Smartling term used to refer to the website for which your translated sites reference to capture and translate content. It is also sometimes referred to as your Origin.

Web Crawler

Also referred to as a "web spider". It is a program or automated script that methodically visits web sites and reads their pages to create entries for a search engine index and/or to provide up-to-date data.

This article is for Account Owners, Project Managers, Agency Account Owners, Translators, Editors, and Reviewers.

Whenever Smartling captures content from your file, app, or website, the system parses or breaks it down into small, discrete entities. This makes it easier to re-order a translation, whether for formatting or linguistic reasons. There are two levels of parsing: strings and segments.

Strings

Smartling extracts strings from the captured content based on the paragraph markers found in your content. Those markers vary depending on the content or file type. For example, for HTML, everything in a< div >tag may be considered one string.

Segments

Strings are parsed into segments, defined by end of sentence punctuation markers, i.e. periods, semicolons, interrogation points.

Strings and Segments in the CAT Tool

In the CAT tool, strings are parsed into segments, with each segment needing to be individually translated. The following example shows an entire string (denoted with a green vertical bar) that has been parsed or broken down into two segments. A Translator, Editor, or Reviewer will then be able to translate or edit each of the corresponding segments.

Merge Segments

If you're translating a string with multiple segments, you have the option to merge segments. Mouse over the Merge segment into nexticon. Alternatively, you can use the short cut that you've set in your keyboard settings.