Did you find this page useful? Give us feedback.
Did you find the information
on this page useful?

Yes
Somewhat
No
  Tell us more about your choice:
Missing information
Incorrect information
Misleading information
I have a question
Other
  Enter your comment in the box below.
If you need assistance, please contact Support instead.

  Type the letters
simple PHP captcha
 

When you create a project template, you can define automated actions for frequently carried out steps such as pre-translation, analysis creation, user assignment. This saves you time when you have projects with very fast turnaround times where you need to export the completed translations and deliver them to your customer. This can take up a lot of your time. In setting up an automated export in project templates, memoQ does it for you when the workflow step is reached.

Your system administrator sets up the stored path for the Files category. This can be done in the Deployment Tool. Please read the memoQ server installation guide for further information.

How to begin

Invoke the Resource console from the Application menu or selecting the corresponding icon on the Quick Access Toolbar. Choose Project templates. Create a new template or edit an existing template.

Options

Define an export option, e.g. for All documents delivered by translator. Select this option from the Available triggers list, and then click the Add new action button (). Select an export trigger for this action. You can  export actions for source, target, bilingual documents as well as for QA and LQA reports, and resources such as a TM or TB export.

When you select an automated export option, a settings dialog is displayed, e.g. for MQXLIFF:

Define the export settings. Click OK. When the indicated workflow step (action) is reached, the trigger is executed (the files are exported and stored in the Files category).

Note: It is not possible to use the same export path settings for local and online exports.

Note: When you migrate old templates (prior to 7.8.50), you can easily add file export actions.

Note: When you create a local template and publish it on a memoQ server, the export path is set to the defaults.

Export options on memoQ server

Export source documents on server: Use this option to export the imported source file in its original file format. The exported document looks like the exported target but uses the source segments instead of the target segments. This option makes sense when translators are allowed to edit the source text (e.g. correcting typos). This export only works for monolingual files. If you imported a bilingual or multilingual file, then the document is exported with the target sides too (e.g. multilingual XML files). This option is only available for online projects. All placeholders are available.

Export MQXLIFF on server: Use this option to export a memoQ XLIFF file. The difference to the local export dialog is that the destination folder is replaced with the Export path group options. Other options like to include skeleton and preview as well as version history are available the same way. All placeholders are available.

Export two-column RTF on server: The difference to the local export dialog is that the destination folder is replaced with the Export path group options. All placeholders are available, except if you decide to export all selected documents in one single RTF file, then the placeholders OrigFileNameExt, OrigFileName, OrigFileExt, MajorVersion, MinorVersion, Translator, Reviewer 1 and Reviewer 2 placeholders are not available.

Export target documents on server: Use this option to export the translated target file(s). All placeholders are available.

Export translation memories on server: Use this option to export a TM in TMX format. The naming is done automatically by memoQ: {TMname}.tmx. The export date is appended to the file name to guarantee unique file names. If you did not specify a date, then the serial number is appended to the file name to resolve naming conflicts in projects and resources. Available placeholders are:

{Project}

{Client}

{Domain}

{Subject}

{ProjectName}

{TmName}

{SrcLangIso2}

{SrcLangIso3}

{TrgLangIso2}

{TrgLangIso3}

{YY}

{YYYY}

{MM}

{DD}

{HH}

{NN}

Export LiveDocs on server: Use this option to export a LiveDocs corpus in ZIP format. The scope is always the project. Available placeholders are:

{Project}

{Client}

{Domain}

{Subject}

{ProjectName}

{LiveDocsName}

{YY}

{YYYY}

{MM}

{DD}

{HH}

{NN}

Export term bases on server: You can choose between your highest ranked TB only or all TBs to export terminology in CSV format. the automated export of qTerm term bases is not possible, it only works for memoQ term bases. Available placeholders are:

{Project}

{Client}

{Domain}

{Subject}

{ProjectName}

{TBName}

{SrcLangIso2}

{SrcLangIso3}

{TrgLangIso2}

{TrgLangIso3}

{TrgLangListIso2}

{TrgLangListIso3}

{YY}

{YYYY}

{MM}

{DD}

{HH}

{NN}

Note: Exporting translation memories, term bases and LiveDocs corpora is only available for After project wrap-up as trigger.

Export analysis to file on server: You can export the report automatically to a file, generate the exported statistics individually for each target language and you can export as HTML or CSV format.

Available placeholders are :

o{Project}

o{Client}

o{Domain}

o{Subject}

o{ProjectName}

o{SrcLangIso2}

o{SrcLangIso3}

o{TrgLangListIso2}

o{TrgLangListIso3}

o{YY}

o{YYYY}

o{MM}

o{DD}

o{HH}

o{NN}

Similar options are available for the post-translation analysis statistics and the edit distance statistics.

Export QA report on server: Use this option to export a QA report. The settings are similar to the Run QA dialog. The scope is defined by the automated action's scope (project or document level).

Export LQA report on server: Use this option to export LQA reports. The settings are similar to the LQA reports dialog. You can only export LQA reports if your project has an LQA model attached. If you choose to export separate reports, then the file name of the report is document name + underscore + target language with the 3-letter code + LQA report.

Placeholders in file and folder names

You can include placeholders in file and folder names. memoQ recognizes the following placeholders:

{RelativePath}: the path of the original file, relative to the base folder where memoQ started to recursively parse subfolders for documents.” {RelativePath} is replicated below the project’s file storage root folder. For example, if the project file storage is \\FileServer\memoQshare\MyProjectName, and the relative path is \HTML\Chapter1\Section1, the full path will expand to \\FileServer\memoQshare\MyProjectName\HTML\Chapter1\Section1. The RelativePath placeholder makes sense only if you imported files using the Import folder structure command.

{OrigFileNameExt}: the original file name including the extension. It does not contain the path, only the file name.

{OrigFileName}: the name of original file without extension. It does not contain the path.

{OrigFileExt}: extension of the original file.

{Project}: project’s Project ID.

{Client}: project’s Client ID.

{Domain}: project’s domain.

{Subject}: project’s subject.

{ProjectName}: the name of the project.

{MajorVersion}: the major version number of the exported document.

{MinorVersion}: the minor version number of the exported document.

{SrcLangIso2}: two-letter language code (plus country name if present) of the project’s source language.

{SrcLangIso3}: three-letter language code (plus country name if present) of the project’s source language.

{TrgLangIso2}: two-letter language code (plus country name if present) of the project’s target language.

{TrgLangIso3}: three-letter language code (plus country name if present) of the project’s target language.

{TrgLangListIso2}: the list of the two-letter language codes (plus country names if present) of the project’s target languages.

{TrgLangListIso3}: the list of the three-letter language codes (plus country names if present) of the project’s target languages.

{YY}: two-digit year (when rule is applied).

{YYYY}: four-digit year (when rule is applied).

{MM}: two-digit month (when rule is applied).

{DD}: two-digit day (when rule is applied).

{HH}: 24-hour time (when rule is applied).

{NN}: two-digit minute (when rule is applied). All dates and times are local for the server computer.

{Translator}: the memoQ server account name of the assigned translator. It shows the vendor group name for subvendors and GroupSourcing for group sourced documents.

{Reviewer1}: the memoQ server account name of the assigned reviewer 1. It shows the vendor group name for subvendors and GroupSourcing for group sourced documents.

{Reviewer2}: the memoQ server account name of the assigned reviewer 2. It shows the vendor group name for subvendors and GroupSourcing for group sourced documents.

Note: The exported file's extensions depends on the export type, e.g. PDFs are exported as TXT files.

Note: The path length is restricted to 260 characters. If exceeded, the export automation fails. The export also fails when a placeholder cannot be used.

Note: The export path rules for folders behave the same way as described here.