Automated analysis report settings

Use these options to update the word counts in the project after new or changed documents are imported.

These settings are for local projects.

To learn why you need to calculate this, see the topic about creating an analysis report manually.

1. Check the Use project TMs and corpora check box. This makes sure that memoQ checks the segments in every translation memory and LiveDocs corpus in your project.
2. Check the Calculate homogeneity check box. memoQ counts internal fuzzy similarities, too. That is, memoQ predicts what matches you will get during translation while your translation memory is filled up.

   Use this only if you really work on this job alone: Don't check the Calculate homogeneity check box if others will also work on this translation.

3. Clear the Include locked rows check box: If you received documents that contain locked rows, most of the time your client means that you mustn't touch those.
4. Make sure that the Repetitions take precedence over 100% check box is checked: Use this option if a consistent translation is more important than using all possible matches from the translation memory.
5. Make sure that the Cross-file repetitions check box is checked: Since you will work on this translation on your own, you can use a segment that is repeated from another document in the project. Clear this check box only if others will work on this job, too.

Use these options to update the word counts in the project after new or changed documents are imported.

These settings are recommended for online projects.

If several translators work on a set of documents you can't predict when a translator will translate a segment or a document. You can't know who will be able to use translations from others. As a result, you can't predict what internal repetitions will be used.

Bottom line: If the translation is done by a team rather than one single translator, you can't have a precise estimate of the work in advance. To find out how much the work actually is, use Post-translation analysis after the translation is finished.

To set this up for your team in the Create analysis report window, use these options:

These settings are for an online project. Use them in a local project, too, if you are a project manager, and you plan to publish the project on a server, or to distribute the project using packages.

1. Check the Use project TMs and corpora check box. This makes sure that memoQ checks the segments in every translation memory and LiveDocs corpus in your project.
2. Clear the Calculate homogeneity check box. memoQ shouldn't count internal fuzzy similarities because we don't know the order in which segments are translated.
3. Clear the Include locked rows check box: If you received documents that contain locked rows, most of the time your client means that you mustn't touch those.
4. Make sure that the Repetitions take precedence over 100% check box is checked: Use this option if a consistent translation is more important than using all possible matches from the translation memory.
5. Make sure that the Cross-file repetitions check box is cleared: We don't know who will be able to use repetitions.

Use these options to update the word counts after translators deliver their work.

These settings are for online projects.

An editor - or proofreader - needs to work on the translation that is already there. Their work doesn't depend on translation memory matches. They will work on the entire text, so it makes no sense to analyze the work through translation memories.

1. Clear the Use project TMs and corpora check box.
2. Clear the Calculate homogeneity check box.
3. If the editor needs to review all the translation, not just the newly translated segments: Check the Include locked rows check box.
4. Check the Repetitions take precedence over 100% check box.
5. Clear the Cross-file repetitions check box.

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.

Some document formats bring along a lot of inline tags in the text. Such formats are XML, HTML, PDF, InDesign, sometimes Microsoft Word - and potentially many others.

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.

To set this up, you can count tags as words or characters.

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.

Normally, memoQ creates several analysis reports in a project - for different purposes and different reasons. Some of the reports are created automatically. For example, when a new document is added to the project, the work needs to be recalculated, because the total word counts and potentially the repetitions change.

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.

You can save the report automatically on a server in online projects. While the project is running, you can download the reports from the server, from the project file store.

Before you set this up, you need to open the eye in the Edit project template window. (Click it if it's not open.) After that, you can add the Create analysis report action to the project template.

1. Click the Export analysis to file on server tab.

   

2. Check the Export analysis report to file check box.
3. If the project has several target languages, and you need separate billing data for each target language: Check the Create a separate file for each target language check box. memoQ TMS creates as many report files as the number of target languages in the project.
4. In most cases, you use word counts: Click the Words radio button. Unless you are using character counts: Then click the Characters radio button.
5. Under Export path rules, set up the folder and name of the report files. You can use placeholders, so that memoQ TMS takes the name from the name of the project, the date or time when the report was created, the project languages, and so on. memoQ fills in the placeholders with actual details in ongoing projects that are created from this project template.

There is a fixed main folder: memoQ TMS saves the report to the project's file store. This is a folder on the server. Only a system administrator can change the location of that folder.

Normally, memoQ TMS saves the reports in a folder called Analysis reports, and the name is put together from the name of the project, and the date and time when the report is created.

You can change this: You can add folders to the path, or you can use different placeholders in the name. You can also use these placeholders in the names of the folders. Don't change Analysis reports, though.

Click to expand the list of placeholders you can use

• Project: Contents of the Project field of the project. This is not the project name.
• Client: Contents of the Client field of the project. Normally, the name of the end-user of the translation.
• Domain: Contents of the Domain field of the project. Normally, the narrower subject or the genre of the source documents.
• Subject: Contents of the Subject field of the project. Normally, the subject field of the source documents.
• ProjectName: The full name of the project. memoQ and memoQ TMS use this name to identify the project.
• SrcLangIso2: Two-letter code of the source language of the project.
• SrcLangIso3: Three-letter code of the source language of the project.
• TrgLangListIso2: List of two-letter codes of the target languages of the project.
• TrgLangListIso3: List of three-letter codes of the target languages of the project.
• YY: The year when the report is created, in two digits.
• YYYY: The year when the report is created, in four digits.
• MM: The month when the report is created, in two digits.
• DD: The day when the report is created, in two digits.
• HH: The hour when the report is created, in two digits.
• NN: The minutes when the report is created, in two digits.

1. Finally, choose the format of the report:

• To use it in financial reports, and open it in Excel: Click the CSV radio button.
• To simply file it and check it when necessary: Click the HTML radio button.