Create edit distance report
An edit distance report shows how much work was done on a project - by a translator or a reviewer. It doesn't show the time spent on the project. For that, there is the editing time report.
An edit distance report shows how much existing translations had to be changed.
- When the report measures the work of a translator: It shows how much change they had to make to translation memory matches.
- When the report measures the work of a reviewer: It shows how much the translator's work had to be corrected.
Only delivered documents and confirmed segments: The edit distance report gives you numbers for the entire project. But it runs on those documents only that were delivered, and on segments that were confirmed.
When memoQ calculates the edit distance report, it computes how much you need to edit the first text to get the second one. The difference appears in characters or in percent, depending on your choice:
- Levenshtein: The difference is shown in characters.
- Fuzzy: The difference is shown in percent. memoQ also groups the results by percent ranges, similarly to fuzzy ranges in analysis reports.
The distance is 100% if there was no match: If you are measuring the work of the translator, and the translation had to be written from scratch because there was no match: The edit distance will be 100% (or the number of characters in the translation).
How to get here
- In local projects (and checked-out copies of online projects): In Project home, choose Overview. Click the Reports tab. Under Edit distance report, click Create new report now.
-
In online projects: In the memoQ online project window, choose Reports. Under Edit distance report, click Create new report now.
Limited choice in online projects: You can only create the Inserted matches vs. current translations report. For other options, check out the project.
What can you do?
Set up how memoQ should count words and characters.
Measure the work of a translator
Click the Inserted matches vs. current translations radio button. For distance measurement, choose Levenshtein.
To give you an idea of how much the translator worked: This compares the translator's work to the translation memory matches that were inserted in the segments.
To get the amount of work in characters, use the Levenshtein method to measure the distance. It makes more sense to see how much a translator worked - as opposed to how much of the inserted text was changed. In an average translation job, many segments are translated from scratch, without inserting a match first.
Use Fuzzy only if the work was similar to editing: Counting in percent is useful if there was a match for most segments. This happens if you update a translation to a new version, and there is little difference. Or, when there was machine translation and you need to fix machine-translated segments.
Confirmed segments only: memoQ calculates the edit distance for those segments that are already confirmed.
Measure the work of a reviewer
Click the Calculate distance between radio button, and the choose the versions you want to compare.
Doesn't work in "normal" local projects: You can use the reviewer's edit distance report in online projects mostly, or in local projects that are distributed through packages. These are projects that have translation and review. In addition, the translation and review steps must not overlap. (You can choose this when you set up an online project.)
Normally, you would compare the reviewer's text with the translator's version, and compute - in % - how much of the translator's text was changed. More specifically, these are your choices:
- Translator > Reviewer 1: For cost analysis: Choose this if you want an estimate of the cost of the first reviewing pass. For quality assurance: Choose this if there is a Reviewer 1 in the project, and they do most of the editing.
- Translator > Reviewer 2: For cost analysis: Choose this if you need the overall cost of human editing. For quality assurance: Choose this if you want to get an overview of the quality of translation. You get a fairly reliable number if Reviewer 2 works along clearly defined guidelines, avoiding most preferential edits.
- Reviewer 2 > Reviewer 1: For cost analysis: Choose this if you need the cost of the second editing phase. For quality assurance: Choose this if you want to evaluate the work of Reviewer 1.
- Last delivery > Current text: Choose this if you're the reviewer, and need to know how much you worked.
Percent or characters? Choose Levenshtein if you need the edit distance in characters. Use this number to get an idea of the time and money needed to do appropriate editing. Choose Fuzzy to get a percentage. Look at the overall percentage only. Use this number if you want an idea about the quality of translation.
Write a description for each edit distance report
You can ask for several edit distance reports in a project - for different purposes and different reasons. For example, if a team of translators works on the job, you may want to get the edit distance of each translator separately.
When there are multiple reports, you need to know when and why each of them was created. When you create a report, make sure you always type a description in the Optional comment for report box.
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 create the edit distance report: Click OK.
To return to the Overview pane without creating the report: Click Cancel.
To view the report from the Overview pane
memoQ adds the analysis to the Reports tab of the Overview pane (or , in a new row under Edit distance report. The new analysis will be the first one. In the first row under Edit distance report, click show. It looks like this if you use Levenshtein counts:
It looks like this if you use Fuzzy counts:
To collapse the report: Click hide. To save the report in a CSV file (that you can open in Microsoft Excel): Click export. To delete the report: Click delete.
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.