Managing the Translation Process

Strings View (Project)

The Strings View is available for Account Owners and Project Managers who have access to our new user experience. It is also available in beta for customers in Classic and is used in the Jobs dashboard for all customers. To learn how to search for strings in the Classic Experience, go to Search within a Project.

Agency Account Owners and Translation Resource Managers have access to their own Strings View, as well as Translation Resources. This means that if you have a filtered strings view that you need to discuss with your vendor, you can simply share the URL with them, and they can access the same view.  There are two ways users who have vendor roles can access this strings view. See below for more details about link sharing between roles and a new experience called "Read Only".

Requesters can access the strings view via Jobs.

This new Strings View replaces and builds on the classic "List View" (Content > Translations).  Providing more powerful, broader views of content, more bulk actions, and some new actions not previously available.

This article covers the following details of the Strings View:

Access Strings View via Job Details

Go to Jobs and click on a Job - Under Job Summary, click View Strings

Access Strings View via Projects

Go to a Project and click on the Strings tab

Screenshot_2020-06-19_at_14.46.51.png

Strings View Layout

The Strings View contains the following columns of detail:

  • Source String: The string in the project's source language. This also contains strings namespace and variant metadata.
  • Translation: The translation of source string (if available)
  • File/URL: The file name or URL containing the source content. This also lists the context file and string key metadata
  • Language: The target language in which the source string will be translated
  • Job: The Job name in which the string will be translated. Strings can be translated outside a Job; therefore, a Job name may not always be present. If there is a Job name listed, this will be hyperlinked to bring you directly to the Job when clicked.
  • Status: The status the string is in, as well as the workflow name.
  • Actions: This ellipse contains two functions - Strings Details and accessing the CAT Tool.

String Details

For information on the metadata gathered on each string, read String Details documentation.

Methods of Viewing Strings

There are two primary views for the new strings interface; Source and Translations. By default, you will enter the Translations view. To enter the Source view, check "Show source language only" under the Languages filter.

The Source view is only available to content owners, not linguists/vendors.

Additionally, you can customize the strings view.

Translation Strings View

Reviewing and managing strings in the translation view will allow you to carry out bulk actions across multiple languages, as well as;

  1. Viewing strings that are Awaiting Authorization, In Progress, and Excluded at the same time.
  2. Applying any filter listed on the left-hand panel.

Source Strings View

Reviewing and managing your strings in the source view can be more efficient, as it removes any translations from your view and allows you to focus on the source content. You can apply many actions to the source string, which will be applied to your target language translations. 

When viewing by source language, we show the source string and its source metadata (File/URL name) as well as a summary of its status.  Status is calculated based on the status for all the language pairs.

Custom Strings View

You can customize the columns and re-arrange their order to suit your preference. To find out more, read our documentation on customizing your Strings View.

Filtering Strings

For information on how to search and filter for strings, read our documentation on Strings View Search & Filters.

Strings View Actions

For information on actions you can make on a string in Smartling, read String View Actions.

Quick Edit

If you need to modify translated content quickly, Account Owners and Project Managers can do so directly from the Strings View via Quick Edits.

Strings View for Linguists

In the new Strings View linguists will have a new experience for seeing content in the projects where they have been given access to work on specific workflow steps and languages. Linguists can now see translations in all steps of a workflow, before or after the steps that they have been assigned to (for the languages that have access to).

Strings in these steps, they will be labeled "Read Only".  Linguists cannot edit the strings/translation when they are in Read Only steps. This gives linguists more visibility into content that might be in the steps before or after the step where they will be working.  

The workflow filter will include a shortcut to filter the Strings View for just the steps they need to work on.  In the Workflows filter click "My Steps Only" to quickly view just the strings you need to work. If a workflow is configured to use "assignment" but the translation has not yet been assigned, it will simply show with an "unassigned" label. The translation will not be editable until it is assigned to a linguist. If it's not assigned to the linguist viewing, it will simply show who is assigned and be un-editable.

Filters and Actions

The filters and available actions depend on your role.  Content owners see all the filters and actions available for the Strings View and linguists see a subset of them.  Similarly, the results of a filter may differ slightly between roles because of other permission differences. The application will retain the filters that can be applied for the linguist, but omit any which are not available to the linguist. Therefore, if a content owner shares a link with a linguist, they might see different results.

Examples of reasons why the linguist will see different results than a content owner for a given filter:

  1. Workflow (Awaiting Authorization)
    1. Linguists do not see content that has not been authorized. Any filter that includes awaiting authorization can result in different results when viewed by a content owner vs a linguist.
  2. Workflow + language permissions
    1. Linguists are given access to specific workflow steps in specific languages.  If a content owner shares a URL for a language that the linguist has no permissions to then they will not see any strings/translations.

Was this article helpful?