Post-translation analysis (PTA) is a report of savings that you have achieved on TM and LiveDocs match rates – after translation is complete.
Post-translation analysis looks at the match rate in every segment, and groups them just like normal analysis does (101%, 100%, 95-99%, 85-94%, 75-84%, 50-74%, No match), and creates a report in the same format. But this time memoQ does not look up the segments in the translation memories. Instead, it takes the match rates that are already there in the segments:
Post-translation analysis makes most sense if the translation was done by several translators instead of just one. If there's only one translator (per target language), a simple analysis report gives an accurate estimate of the possible savings. But that does not work if two or more translators are doing the job.
Match rates come from pre-translation or automatic lookups: Segments have match rates if they are filled in through pre-translation or automatic lookup and insertion. Otherwise, the match rate is zero, and that will appear in the post-translation analysis, too.
Works if the translator is known: Post translation analysis counts segments where a translator was stored. If a segment doesn't say who confirmed it as a translator - or it wasn't confirmed by a translator -, it's not counted. This can happen if segments were translated by a user in the Reviewer 1 role rather than a Translator.
How to get here
What can you do?
In most cases, especially when you translate from English, the work is measured by the word count of the source text. But in some markets or subject fields, translation is measured by the number of characters.
In the resulting table, memoQ always gives you the character count as well as the word count. In most cases, you need to count the spaces, too.
Make sure that the Include spaces in character counts check box is checked. memoQ counts every space separately. Two spaces right after each other count as two, not one.
Check the Repetitions take precedence over 100% check box. Normally, it's checked, and there's no reason you would need to clear it.
Inserting these tags in the right places can be a lot of work. The analysis report must reflect that.
Normally, memoQ counts tags, but in a separate number. That is not easy to include in the final word count.
In the Tag weight row, type a number in the word(s) box. For example, if you type 0.25, memoQ counts one word after every four inline tags - or one-quarter word after every tag.
You can also count this with the characters. Type a number in the character(s) box. For example, if you type 2, memoQ counts two characters after every tag.
You can create several post-translation analysis reports in a project. For example, this happens if the translators deliver at very different times.
Don't use Trados 2007-like word counts: Normally, memoQ counts words like Microsoft Word does. In the past, when Trados 2007 or earlier (Trados Translator's Workbench) used to be a dominant translation tool, it was important that memoQ could produce similar word counts - so that translation companies could compare them. This is no longer the case. Use the Trados 2007-like word counts only if your client still works with an early Trados version, and they insist on using it.
When you finish
To run the analysis, and produce the report: Click OK.
To return to the Overview pane, and not generate a report: Click Cancel.
memoQ adds the analysis to the Reports tab of the Overview pane, in a new row under Post-translation analysis. The new analysis will be the first one. In the first row under Post-translation analysis, click show.
The report is grouped by translator, and not by target language or by document. Post-translation analysis is for finding out how much each translator can bill.
The user tables are followed by a summary, which shows your total savings on the entire project:
To get a new report because the project changed, click Create new report now again. The new report appears at the top of the list.