Two-column RTF export settings

memoQ can save a Rich Text (RTF) file that contains the bilingual document in a table. This is called the Two-column RTF format.

You can send the exported file to someone who doesn't have a translation tool. They edit it in Word, and send the edited file back to you. You can import this file into the same project in memoQ: memoQ updates the document in the project.

To save a two-column Rich text file:

1. Click the Two-column RTF radio button. If you check the Open exported bilingual file in Word check box, memoQ shows you the document in Word immediately after it is saved. Click Next.
2. The second page of the wizard appears. In this page, you can fine-tune the contents, the layout, and the format of the exported bilingual file.

   

Fine-tune the columns:

• Export comments check box: Check this to make memoQ create an extra column in the table. This will contain the comments from the document. This is checked by default.
• Export segment status check box: Check this to make memoQ add an extra column that shows the segment status. The extra cells show both the color and the match rate. This is checked by default.
• Two target columns in table check box: Check this to make memoQ export the target column twice. In Word, the reviewer should leave the first target column as it is, and modify the second target column only. Normally, both target columns contain the translation. Check the Leave second target column empty check box to have an empty second target column. Both check boxes are checked by default.

  Fine-tune the formatting:

• Format tags with the "mqInternal" style check box: In the exported file, the characters in formatting tags will be formatted with the mqInternal style. Make sure this check box stays checked. For memoQ, it's easier to import or update documents that have this style. It's easier to spot formatting errors in Word, too.
• Export the full text of inline tags check box: memoQ exports every attribute in inline tags. Don't check this check box, unless you absolutely need to. This makes the document extremely difficult to read in Word.

  Set other options:

• Export all selected documents in a single RTF file check box: If you export several documents, memoQ can save them in a single RTF document. Check this check box to make memoQ create one single RTF file, with the contents of all the selected documents. The table has multiple headers, so that you can identify each memoQ document inside. This check box is cleared by default.
• Include locked segments in export check box: memoQ can omit locked segments from the exported RTF file. The reviewer won't be able to accidentally change text that should not be changed. But it's difficult to review text if you can't see the whole of it. By default, memoQ does export locked segments.

  Delicate document: The RTF file contains identifiers (long numbers) for each document and for each segment. The document ID appears below the document title. The segment IDs appear next to the segment numbers, in a font size of 1 point (unreadable). These identifiers must not be changed or deleted in Word: otherwise memoQ won't be able to update the project from the RTF file.

1. First, set a destination folder.  Normally, the document is saved in a folder called Two-column RTF files, inside your personal Documents folder. If you want to save the document elsewhere, click Custom folder. Click the ellipsis button, and find or create your folder.
2. Next, type a file name. You can use placeholders, so that memoQ can take the name from the name of the project, the date or time when the document was exported, the project languages, and so on. memoQ fills in the placeholders with actual details in ongoing projects that are created from this project template.
3. If you imported a folder structure in the project rather than single documents, and you want to have the same subfolders when the documents are exported: Check the Recreate folder structure in export folder check box.
4. To insert a placeholder, click Insert placeholder, and choose from the menu.

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.
• Template: The name of the template that was used to create the project.
• SrcLangIso2: Two-letter code of the source language of the project.
• SrcLangIso3: Three-letter code of the source language of the project.
• TrgLangIso2: Two-letter code of the target language of the document. For a document, there can be only one. For the entire project, there can be several.
• TrgLangIso3: Three-letter code of the target language of the document.
• 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.
• YYYY: The year when the document is exported, in four digits.
• MM: The month when the document is exported, in two digits.
• DD: The day when the document is exported, in two digits.
• HH-NN: The hour and minute when the document is exported, in two digits.

Under Export path rules, set up the folder and name of the two-column RTF files. You can use placeholders, so that memoQ server takes the name from the name of the project, the date or time when the document was exported, 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 server exports the document 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 server exports the documents in a folder called RTF. In that folder, memoQ server creates another folder by the name of the target language. If a folder structure was imported, memoQ server recreates the same subfolders under RTF and the target language. Then it saves the file with the same name as the original document.

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 RTF, though.

Expand this for a list of placeholders you can use.

• RelativePath: Use this if a folder structure was imported in the project. This contains the subfolder within the original folder where the document is. For example, if you import a folder called D:\Documents\ToTranslate, and the ToTranslate folder contains an ENG subfolder, then the RelativePath for the documents in the ENG folder will be ENG.
• OriginalFileNameExt: The name and extension of the original document. Example: if the original document is called ToTranslate.docx, OriginalFileNameExt is ToTranslate.docx.
• OrigFileName: The name of the original document without the extension. (It's also called a file type in Windows.) Example: if the original document is called ToTranslate.docx, OrigFileName is ToTranslate.
• OrigFileExt: The extension of the name of the original document (DOCX, HTML, XML, PDF etc.). (It's also called a file type in Windows.) Example: if the original document is called ToTranslate.docx, OrigFileExt is docx.
• 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 server use this name to identify the project.
• MajorVersion: The first version number of the document. This is the version of the source text. If the source document doesn't change during a project, it stays 1.
• MinorVersion: The second version number of the document. This is the version of the translation. This changes a lot of times during a project: When a translator or a reviewer delivers the document; when it's updated from a bilingual document; before or after the document is pre-translated or X-translated; or when someone manually creates a snapshot.
• SrcLangIso2: Two-letter code of the source language of the project.
• SrcLangIso3: Three-letter code of the source language of the project.
• DocTrgLangIso2: Two-letter code of the target language of the document. For a document, there can be only one. For the entire project, there can be several.
• DocTrgLangIso3: Three-letter code of the target language of the document.
• YYYY: The year when the document is exported, in four digits.
• MM: The month when the document is exported, in two digits.
• DD: The day when the document is exported, in two digits.
• HH: The hour when the document is exported, in two digits.
• NN: The minutes when the document is exported, in two digits.
• Translator: Name of the user who got the document in the Translator role.
• Reviewer1: Name of the user who got the document in the Reviewer 1 role. If there was no Reviewer 1, this is empty.
• Reviewer2: Name of the user who got the document in the Reviewer 2 role. If there was no Reviewer 2, this is empty.