Analysis calculates the character/word count in selected files and identifies repetitions, non-translatables, translation memory matches, and machine translation matches. Analysis can also show the number of revisions made by a reviewer.
Some CAT tools refer to Analysis as statistics.
Since different billing units are used in different countries, three calculation methods are available:
For languages that use spaces between words—excluding Chinese, Japanese, and Thai.
1800 characters with spaces—unrelated to the actual number of pages in a file.
Characters from CJK languages are counted as both characters and words.
To create an analysis, follow these steps:
From apage, select one or more .
The Analyze window opens.
Select afrom the dropdown list.
Provide a name if required.
Available macros for Analysis naming:
Adds source language
Adds target language. If multiple languages are analyzed, the language will be empty.
Adds username of the assigned Linguist or Vendor. If multiple Linguists are assigned, the name will be empty.
Select analysis options and click Analyze.
The analysis, or analyses are added to the list.
Click on an analysis in the list to view it.
Analysis options can be set when creating an analysis, at the project level, or globally under Setup .
Three analysis types are provided:
Default Analysis is the standard analysis run on source segments before translation. It provides the baseline analysis of a job that can be used with the Post-editing Analysis to determine how much effort was put into translating that job. This baseline is also used the basis for generating Quotes for clients.
A breakdown of segments/words/character counts is produced and if used in a project, TM matches are identified along with non-translatable matches and Machine Translation Quality Estimation (if enabled).
Running a Default Analysis after translation produces incorrect analyses.
Post-editing analysis is run on target segments and indicates editing effort; how much editing the text required from a linguist or proofreader. It is run after post-editing is complete.
When a linguist clicks on an untranslated segment, the current highest translation memory match, machine translation, and/or non-translatable match is saved for that segment and is used in post-editing analysis.
In projects with Revision in the workflow, the post-editing analysis is calculated as the difference between the translated text and the proofread text.
Memsource post-editing analysis extends the traditional translation memory analysis to include machine translation (MT) and non-translatables (NT).
Post-editing options are used for calculating the post-editing effort required for matches from the translation memory (TM), non-translatables (NT) and machine translation (MT).
Analyze TM post-editing enabled
Intended for low-quality TMs that contain high percent matches that require Linguist editing.
Indicates post-editing effort for the TM.
Contains only 100% matches in the analysis. In-context 101% matches from the TM have no effect on the calculation.
Analyze TM post-editing disabled
Intended for high-quality TM where matches should be edited as little as possible to reduce cost.
Indicates both 101% and 100%.
Indicates TM matches offered to the Linguist when the segment is opened (not the actual Linguist's post-editing effort).
Indicates post-editing effort for machine translation and non-translatables.
Analyze NT/MT post-editing enabled
If the MT or NT suggestion was accepted without further editing it is presented as a 100% match in the analysis.
If Linguist changes the MT, the match rate will be lower. The score-counting algorithm is the same as that used to calculate the score of translation memory fuzzy matches.
Editing of an NT will cause the segment to be presented as 0-49% NT.
Analyze NT/MT post-editing disabled
Entries from MT/NT without any estimated score will be considered TM 0%-49% matches. They will be indicated translated by the Linguist with the MT not considered.
MTQE and Memsource Translate matches higher than 75% will be in the MT column in their respective matches.
Team, Ultimate and Enterprise editions
Get in touch with Sales for licensing questions.
The Compare Analysis feature is available only in projects with Workflow steps. It compares two versions of a file in different Workflow steps and analyzes how the two versions differ.
A comparison between the Translation and Review steps indicates the actual effort of a Reviewer by identifying how much the translation changed during the Review step.
Analysis can be run on multiple jobs and can be grouped in two ways:
Analyze by provider
For a project with many jobs assigned to various Linguists or Vendors. Used to:
Create separate analyses containing files assigned to individual Linguists or Vendors.
Assign analyses to a provider making the analyses visible to their Linguists/Vendors.
Analyze by language
If a project contains multiple target languages, the analyses of all files can be run in a batch creating a separate analysis for each individual language.
To Analyze by language, follow these steps:
Segments, Pages, Words, Characters, and Percents columns can be displayed/hidden in the Analysis table.
To download an analysis, follow these steps:
Select a file type from the dropdown menu:
CSV (Comma Separated Values) with or without Characters and readable with spreadsheet applications.
LOG (Similar to SDL Trados format) and readable with most project management applications.
The file is downloaded.
These files can be imported into most project management software systems.
Apply a Net Rate Scheme
You can apply a discount to words/characters/pages in an analysis. A discounted translation volume is immediately calculated and displayed directly in the analysis in therow.
To remove the Net Rate Scheme from the analysis, leave the field next to the Apply Net Rate button empty.
To assign an analysis to to a provider, follow these steps:
Select an analysis from the list and click Edit.
Select a Provider from the dropdown list.
The analysis will be available to the assigned provider on the Linguist Portal.