Skip to main content

Strings View Search & Filters (Project)

The Strings View can display a large amount of content when you open the tab. To quickly find what you need, use the filters described below.

Filters

Search for strings with the filters on the left area. Reset your search with the link at the top. You can also save your string searches for the future.

The available filters will change depending on the view you are using. The following translation-related filters are not available when using the Source view: Languages, Translation keyword, Issues, Assignment, Translations and Workflow.

Tip: The Key/Variant and Hashcode filters accept multiple values directly (see their rows below). For multi-value searches across Source Keyword, Translation Keyword, Namespace, or File/URL, use Advanced Bulk Action.

Filter

Options / Definition

Job

Filter strings by an existing job name or choose to view strings outside a Job by selecting Not In A Job. Filter supports searching by job number.

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 – Translation is completed and 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, so you only see the source content.

Source Keyword

Search for a word or phrase in the Source Strings column. Select a match mode to control how results are matched:

  • Contains (default): Returns strings where the source text includes the keyword anywhere, even as part of a longer word. For example, searching for "cat" also returns strings containing "category" or "concatenate."

  • Whole Word: Returns strings where the keyword appears as a standalone word, not as part of another word. For example, "cat" returns "the cat sat" but not "category."

  • Exact Match: Returns only strings where the entire source text matches the keyword exactly. For example, "cat" returns only a string whose full text is "cat" and nothing else.

  • Starts With: Returns strings where the text begins with the keyword as a complete word. For example, searching for "cat" returns "cat sat on the mat" but not "category" or "the cat sat."

Translation Keyword

Search for a word or phrase in the Translations column. Supports the same three match modes as Source Keyword (Contains, Whole Word, Exact Match, and Starts With). Use together with "Replace Text" under Actions to find & replace translations.

Plurals & Placeholders

Find strings with plurals or placeholders, or both.

Key/Variant

Search for string variants by looking up translations based on key or variant metadata. To enter multiple key or variant values at once, paste or type each value on its own line (using Shift + Enter on your keyboard). The field expands to show up to 10 values, then scrolls. The limit is 50 values.

Because key and variant values can contain commas, newline is the only supported separator. Make sure none of your values themselves contain a newline character.

To apply your search, click outside the field or press Enter.

Optionally, select Exact Match to return the exact set of characters.
​
Select No Key/Variant to search for strings without keys or variants.

File / URL

Search for file names from the File field (files or Connector projects) or URL's from the URL field (GDN projects).

Optionally, select Exact Match to return the exact set of characters.

Issues

Search by the following options:

  • Any Issues – Strings that have or have 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.

LQA
​

Search by the following options in relation to Linguistic Quality Assurance:

  • LQA Reviewed - Has Errors – Strings that have been recorded as having LQA errors.

  • LQA Reviewed - No Errors – Strings that have been recorded as not having LQA errors. Note that strings that have been submitted without recorded errors (i.e. submitted or skipped) are recorded as strings with "No Errors" by default.

  • Not LQA Reviewed - Strings that have not been reviewed under LQA.

Language Quality Estimation

Search by Language Quality Estimation status:

  • Not Estimated

  • High

  • Medium

  • Low

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.

Ingestion Warnings

String ingestion warnings are flags raised when Smartling ingests a string that appears to have a possible problem. The string will still be ingested into Smartling.

This filter allows you to view strings that might require further attention.

See String Ingestion Warnings Explained for further detail on each warning.

String Instructions Type

Filter for strings that have

  • No instruction - all strings without translator instructions

  • String has an instruction - all strings with translator instructions

  • Instruction from file - strings with translator instructions given in the source file (e.g.: using the #smartling.string_instructions_paths directive)

  • Manually added instruction - strings with translator instructions applied manually by selecting the string in Smartling > Actions > Edit Translator Instructions

String Instructions Text

Search for strings with specific text, e.g., "Do not translate...".

You must choose one of the options in the above filter first.

Hashcode

Search by a string’s unique hashcode. You can find a string's hashcode from the String Details or Additional Details panel in the CAT Tool.

Enter multiple hashcodes at once by separating them with a newline (Shift + Enter) or a comma. The field expands to show up to 10 values, then scrolls. To apply your search, click outside the field or press Enter.

Namespace

Search by a string’s unique namespace.

SEO Content

In a GDN project, filter for SEO or non-SEO content from the dropdown.

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 – Strings don’t have 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 Action, Date range, and the User who performed the action. For example, filter for content excluded in the past seven days by a specific user.
​Available actions:

  • Content Created, Content Assigned, Content Authorized, Content Excluded, Content Moved, Content SmartMatched, Content Unauthorized, Translation Last Modified Date, Translation Submitted, Edit Submitted, Review Submitted, Post-Edit Submitted, AI Review Submitted, Light-Post-Edit Submitted, Revised in Published

Tags

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

State

By default, all active strings will be shown. You can choose to filter by:

  • inactive strings

  • both active and inactive

Search by multiple filter values (Advanced Bulk Action)

The sidebar filters for Source Keyword, Translation Keyword, Namespace, and File/URL accept only one value at a time. To search for strings that match many values at once across these filters (for example, a list of dozens of keywords or file paths), use Advanced Bulk Action.

With Advanced Bulk Action, you paste or type up to 50 values for one or more of these filters, then tag the matching strings so you can find and work with them using the Tags filter afterward.

Search

When searching for text-based fields, you can use the * character as a wildcard to match anything. This is especially useful for the following use cases:

  1. To find a string that includes a placeholder. Although Smartling will show the placeholder in the string, the only way to find the string including the placeholder is to use a wildcard.

    1. Example: Hello, *

    2. Will match Hello, ${firstName}

    3. Will not match Why, hello there!

  2. To find multiple strings that are similar in the form they start with or end with.

    1. Example: Good *!

    2. Will match: Good morning!, Good evening! Good afternoon! Good job!

    3. Will not match: Goodbye! G'day! Good riddance.

  3. To refine your search for a string that otherwise results in getting too many results from our standard similar match results.

  4. To find strings that have HTML markup inside them

Info: If you want to match an actual * character that is part of your text you can use \* to match exactly one * character in the filter.

Tip: You can save any filter-set used in the Strings View. For more information, read Saved Searches.

Important Considerations for Searching

  1. Search separately by text in the source string and text in the current translation.

  2. You can limit results to one specific File or URL by clicking the exact match checkbox.

  3. Search is not case-sensitive, even exact search.

  4. All filters are combined using logical “AND”; you may get zero results when combining filters, even if an individual filter would have some results.

Important Considerations for Using the History Filter

  1. The "preselected" date ranges of the History filter (e.g. last 24 hours) are dynamic. The URL for the filter (and eventually saved searches with that filter, a forthcoming feature) will use the range relative to the time the page is being loaded. So you can get different results if you run the same filter today vs. tomorrow (or even 5 minutes or one hour later) because it’s really last 24 hours from the time the page is loaded. If you want to share a search or revisit a search for a specific time range, use the Custom date range options to specify the exact time range. A saved search or shared URL with a custom range should produce the same results over time (assuming nothing else changes).

  2. The History filter has limitations for how many results can be displayed on the first page. In cases where not all search results can be shown on one page, you will receive a warning message.
    ​


    Further results may be displayed on the following pages, but the number of total search results cannot be shown reliably. To ensure that all results can be displayed correctly, please narrow down your search by adjusting the selected time range or by applying further filtering options.


Search Results and Counters

Screenshot_2021-02-05_at_12.31.16.png

The counter in the results is the count of the source strings that match your filter.

When looking at multiple target languages (the default), a source string will be repeated for each row with its current translation.

You will see more results (rows) than the number of the string counts shown if you are looking at multiple languages. Example:

Source

Translation

Language

Hello

Hola

Spanish

Hello

Bonjour

French

The count of this result is 1 string (2 words). "Hello" is one source string, listed twice for both translations (2 words).

The translation search results use dynamic pagination. When searching across multiple languages, a result will never split a single source string and its translations across multiple pages, meaning all the translations for a single string will always be shown on the same page.

As a result, the number of individual source strings that will be shown on a single page, and the number of results shown on a single page, are dynamic. They adjust automatically depending on the total result set and the number of languages selected.

Did this answer your question?