Skip to end of metadata
Go to start of metadata

Sentiment analysis aims to determine the attitude of a source text or translation with respect to the overall contextual polarity or emotional reaction. A translation may be perfect yet lack the emotional content that you want to convey. This is why we integrate all tooling necessary to ensure accuracy of both linguistic aspects and style. This is important when translating marketing or advertisement content, web sites or other public facing material.

If we all were to like the same things how boring:

At a glance

  • Enable sentiment analysis: Activate a system in "Settings" > "Sentiment Analysis".

  • Scoring source: When marking files for translation tick the option to have the source text analysed.

  • Scoring translations: Manually from the editor's "Actions" menu or automatically by means of QA, see next.

  • Translation editor: View scores as emoticons in the translation editor. Manually edit inaccurate scores.

  • QA: Enable the sentiment analysis QA rule and thus ensure that no negative message gets out..

  • Firewall: Automatically reject negative translation work. Configure your project workflow to systematically run a QA and to ensure that no negative message gets out.

Enable automatic sentiment analysis

Obviously, you can manually assign sentiment scores such as (smile) or (sad) to each translation (or source text) in the new editor. But we recommend to have scores calculated by machine.

Go to "Settings" then "Sentiment analysis" and switch on a system:

  • Microsoft Cognitive Service: Top quality sentiment analysis in many languages
  • Polyglot (hosted by Wordbee): Over 130 languages. Less accurate for Asian or less spoken languages.
  • Random: Simply assigns random scores. For testing purposes only.

Assigning scores to translations - From the editor

Open a document, job or project in the new translation editor. Let us look at how you view and assign sentiment scores.

Score all translations in a click

Click "Actions" and choose "Sentiment Analysis".

Confirm the action. After a short time the editor displays one of 5 emoticons depending on the polarity of the sentiment.

Do you spot the grammatical error in the screenshot? Look forward to automatic grammar checks in Wordbee.

Manually adjust scores

Automatic scoring may sometimes not be as smart as us humans and miss some subtleties in sentiment.

You can manually change the sentiment by clicking the emoticon:

If no emoticon is yet shown click the "..." button of the translation box and locate the sentiment option.

Assigning scores to source texts

Why would you want to evaluate the sentiment polarity of source texts in the first place? Well, the idea here is that the polarity of the translation should ideally match that of the source. If the source text is hyper positive you would expect a hyper positive translation. If source is negative, translation should be. If source is neutral, well, we do not want any negative sentiment in the translation. Etc.

When adding new files to translate

Upload files to a project and right click to mark them for translation.

You will see a new option to automatically analyse the source text sentiment:

On demand from the editor

Open the file in the new editor and choose "Sentiment Analysis" from the "Actions" menu.

Simply make sure to select the source language!

QA - No bad scores please

By now, we know how to assign sentiment scores, manually or automatically. But wait! I want the system to verify that scores all meet my quality expectations!

Sentiment check rule

Run QA from the editor or go to a QA profile. You will find the "Sentiment Check" rule:

It lets you:

  • First off, calculate any missing scores (we listed a lot of manual options further up)
  • Check that the polarity of a translation is not below a certain level. For example, prevent negative sentiments to slip through.
  • Check that the polarity of the source matches that of the translation. Positive loves positive. Negative loves negative... so to say

Automate QA workflows

Wordbee lets you enforce the use of a QA prior to completing a job. 

A typical project workflow profile with the QA related options (available per each workflow step):

Setup your QA profile in "Settings" > "QA Profiles", enable sentiment analysis and set options:

  • The first makes the use of the specific QA profile mandatory for any translator.
  • The second runs the same or different QA prior for the work going into the next step (e.g. revision).

Access rights

Depending on the automatic sentiment analysis system you chose, it may incur costs.

Therefore, an access right exists to allow or disallow running automatic analysis. Locate this in "Settings" > "Access rights" > User profile:

This is how it works:

  • Editor "Actions" > "Sentiment Analysis" tool: Only available if user has the right enabled
  • QA: No limitation. But you can restrict access to QA settings per user profile.


  • No labels