X-translate function in memoQ: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
Tag: Undo |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 7: | Line 7: | ||
A description of the feature can be found in the [https://docs.memoq.com/current/en/Places/x-translate.html memoQ Help online]. Good practice usually dictates that after X-translate is run, a second, "normal" pre-translation should be run using selected resources (translation memories and [[LiveDocs]] corpora, etc.) | A description of the feature can be found in the [https://docs.memoq.com/current/en/Places/x-translate.html memoQ Help online]. Good practice usually dictates that after X-translate is run, a second, "normal" pre-translation should be run using selected resources (translation memories and [[LiveDocs]] corpora, etc.) | ||
<big> | <big>'''A video showing how this works is available...'''</big> [[File:60px-YT_client.png |40px|link=https://youtu.be/KbyIIllVY-M]] | ||
Latest revision as of 09:22, 14 July 2022
memoQ has a special workflow for document-based pre-translation, which is intended for two different "update" scenarios:
- A document is submitted for translation where a prior version of the document has already been completed and reviewed.
- An updated version of a document currently in a memoQ translation process is submitted and it's important to update the project in process with minimum risk to work already done.
A description of the feature can be found in the memoQ Help online. Good practice usually dictates that after X-translate is run, a second, "normal" pre-translation should be run using selected resources (translation memories and LiveDocs corpora, etc.)
A video showing how this works is available... 