All I want is a simple analysis!

01If this title sounds familiar to you it’s probably because I wrote an article three years ago on the SDL blog with the very same title.  It’s such a good title (in my opinion ;-)) I decided to keep it and write the same article again, but refreshed and enhanced a little for SDL Trados Studio 2014.

Something I only occasionally hear these days is “When I used Workbench or SDLX it was simple to create a quick analysis of my files. Now I have to create a Project in Studio and it takes so long to do the same thing.”  I do think this is something you’re more likely to hear from experienced users of the older products because they initially find that getting a quick report out of Studio is a far more onerus process than it used to be.  What they might not think of is how you can use the Projects concept to make this easy for you once you become just as experienced with the new tools.

The basic concept behind getting a quick and simple analysis report before you take on a job is that you create a Project that you only use for analysis and then you leave this permanently in the Projects View:

Once you’ve done this the process becomes quite simple.  All you have to do is activate the Project by double clicking it whenever you want to analyse a file, or files, then drag and drop them onto the Files View.  If you prefer you can also use the Add Files button from the File Actions group in the ribbon or Right-Click from the Files View window:


The one difference between these methods is that if you select Add Files in either of the latter methods they will always be treated as translatable files as long as they are recognised filetypes.  If you drag and drop without changing to the source language first then you will be presented with an option:


If you change to the source language then you won’t get this option and they will be added as translatable files.  If you decide you want to change the purpose of a file after adding it then you can change this by selecting the files and then clicking on this icon in the ribbon:


In this example I’m just adding three files, and once they are in the list you can right click on a file (or folder), or select several files together using the ctrl key and choose the Analyze Only batch task, or select it from the Batch Task icon on the ribbon:


Once the task has completed you can select the Reports View and the reports at the top of the list will be the reports for this analysis. Note that the default Analyze Only task also produces a Translation Count report; if you have the Professional Edition you can create a custom task that only runs the analysis report:


You can set the Project up to run without a Translation memory at all, or you can set as many Analysis projects up as you need all preconfigured with your usual Translation Memories and then the time it takes to run the analysis is as fast, if not faster than it was using Workbench or SDLX.  A bigger advantage of Studio is that if you work with one source language and multiple target languages then you can analyse all the languages at the same time which is something you couldn’t do easily before and of course you can also use as many Translation Memories as you like… something else you could not do in Trados 2007.

A quick note on carrying out the analysis without a Translation Memory. “Why would I do this at all?” you may ask.  Many SDLX users made use of a feature that reported the internal repetitions.  This feature allowed you to report on what benefits you would receive from translating based on the contents of the document you are working on rather than the Translation Memory.  This allows a more realistic report on the effort required to translate and you can achieve this without a Translation Memory at all.  In Studio we have an option called Report internal fuzzy match leverage which does the same thing and this can be activated under Batch Processing -> Analyze Files.  The help guide in Studio covers this feature quite nicely, and of course you can still run with this option when using one or more Translation Memories as you see fit.  In addition you can also lock segments that you don’t want to see included in the report and these can be reported as a separate item.  This is found in the same location as the internal fuzzy match leverage:


I thought it would be handy to see the complete analysis process in one go in a video because it often takes longer to read an explanation of how to use things than it does to watch it, especially when I try to explain the various things you might come across as you go.  Certainly I think this will show the process is pretty simple and certainly doesn’t take as long as you might think!

Finally, I just want to mention the OpenExchange. There are a number of applications available now that can use the analysis in Studio to make it easier for you to prepare reports for your customer, and there are a few that can be used to create an analysis without using Studio at all… and I’m sure there will be more as time goes by.  Here’s a few examples that have been written to use the analysis in some way.  I have linked to the OpenExchange pages and used the descriptions in these pages below:

SDL Studio InQuote : SDL Studio InQuote takes an analysis from any SDL Trados Studio Project, and creates a quote.

  • The quote can be created in MS Word, MS Excel or copied to your clipboard.
  • Rates can be added as simple word analysis, standard lines or grouped analysis.
  • Client details can be saved in the app and assigned specific rates.
  • Customize your own MS Word or MS Excel template.
  • Localize the app yourself in your chosen language.

Post-Edit Compare : Post-Edit Compare is a tool designed to report translation modifications during the post-edit phases of a translation workflow.

The tool works by comparing two versions of the same SDLXLIFF file (before and after changes were applied); the files with changes are highlighted and all modifications are included in a comparison report.

The comparison report is formatted in a way that simplifies the understanding of what changes were applied from one version of the file to the other, along with a full break down of the modifications and related cost analysis.

SDL Trados Studio – Export Analysis Reports: SDL Trados Studio – Export Analysis Reports allows the user to export the SDL Trados Studio Analysis report into the CSV format.

goAnalyze: goAnalyze is a Trados 2009/2011 add-on which allows you to perform an analysis of several or even zipped files without having to open them in Trados Studio.
Before running the first analysis, you create profiles in the user interface of goAnalyze. These profiles consist of the language combination, the translation memories to be used plus optional analysis settings and even costing figures.

Free Online CAT Weighting Tool : Free Online CAT Weighting Tool used to upload the SDL Trados Studio analysis file from your computer to calculate the cost to quote.

So keep an eye on the OpenExchange because you never know who will create a tool to simplify the analysis further or use it in some clever way for added value.  I don’t think it’s difficult to use Studio for this, and I hope this article clarifies it, but there’s always room for more innovation!

  1. Anamary said:

    Thank you for helpful articles and guides!
    I’m FL french-albanian translator and occasionally from clients I receive only SDL Trados analyze file as xml file (for info about upcoming project and accordingly I prepare bid and planing my time). When I import xml analyze report into Excel, result is confusing tabele. I’m wondering if is possible to import analyze xml report into excel with some more clear results and useful for preparing a bid. I tried to ask client to export analyze report to xls or html, but apparently it’s bothering for them :( (Online CAT Weighting Tool is not best option for me, because I’m not online all the time)


    • Hi Anamarija, do you receive the full project package too? If so then you just open that and you will be able to read the analysis in Studio. I’ve never tried to use the XML in Excel outside of Studio but I imagine it would be possible with a little work… I’m just struggling with why this should even be necessary? Seems a little odd, especially when it’s not hard to save the analysis as excel in the first place.

      • Anamarija said:

        Hi Paul,

        Thank you for a quick replay.
        It is odd – I agree with you :), but scenariom is: client sends to me a xml file with analysis, and after I confirm thw job (WC and due date), he sends me a package :)

  2. So basically, if all you want is a simple analysis, the answer is: no dice. It’s a real pain to go through all this rigmarole for single documents if all the customer wants is a quote. I wish there was just some simple option to analyse a document without have to set up a project every time. Your solution is a pretty good workaround, I guess. But I’m going to try this GoAnalyze tool and see if it’s any good.

  3. Marty Nush said:

    Why do I get a set of figures when I run the analysis of a file against an empty TM (with internal analysis unchecked in Settings), and a different one when I check internal analysis and run the Analysis? Shouldn’t they be the same?

    • Hi Marty, if the difference is the internal analysis then no they should not be the same. The standard analysis is based on the contents of your TM. So if the TM is empty they should probably be all no match. The internal analysis attempts to forecast the leverage based on you translating the file, so you get some idea of the benefits of using a TM as you work.

      • Marty Nush said:

        Hello Paul, these are the steps I followed:
        -Created a new project with a pdf to translate an empty TM,. Then, batch anlaysis (unchecked show internal uanalysis). I do get matches, as follows (word counts):

        678 repetitions,
        New 369,
        Total 1121

        As I say, the TM is newly created and empty. My first issue is, aren’t repetitions and 100% the same thing here?.

        I then go to Settings, check internal analysis, batch analyze the file, and I get these:
        651 Repetitions
        2: 95-99%

        95-99: 28
        85-94: 39
        75-84: 45
        50-74; 22
        New 262
        Total: 1121

        I can’t make sense of ithis situation, can you help me?

  4. Marty said:

    Sorry about my poor explanations. I was in a rush! I found that if the TM you create for the project has ‘lookup’ enabled, the top fuzzy bands (with matches against the TM) will have some segment matches. If you disable lookup, nothing will appear there. Why is that? Also, checking or unchecking the ‘lookup’ option and checking or unchecking the ‘report internal fuzzy match leverage’ results in different repetition counts. Thanks for your help

  5. Marty said:

    There aren’t any tickets in the KB related to the issue I described above and I don’t have the Premium Software Maintenance Agreement. The analysis tool is not so simple after all! Why does SDL Trados Studio 2014 returns fuzzy matches when you analyze a text against an empty TM? I’m not talking about internal analysis. Quoting Paul: “So if the TM is empty they should probably be all no match.” Eppur si muove…

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


Get every new post delivered to your Inbox.

Join 1,959 other followers

%d bloggers like this: