Questions?

How do we turn off the option to automatically create temporary TMs in a  memoQ project created through integration? We found that even if when the "Add Default Translation Memory if needed" option is unchecked, the temporary TM will still be created in memoQ.

I have created Selection rules for Workflow Resources, and the TMs are selected correctly in XTRF, but in memoQ, the temporary TM is always created and added as the Working/Master TM.

Any idea if creating a view of quotes and projects together in one view is on the roadmap? 

Hello, 

We have identified that the XTRF-memoQ integration is giving us wrong CAT tool analysis, and we have now to check manually each one of the word counts. 

Has anybody else experienced this issue? I have already shared a ticket with support, but was curious to see if anybody else had the same experience. 

Is is possible to create a project in memoQ first and then link it to XTRF?
We have a scenario where clients have their own MemoQ Server and want to upload projects directly to our MemoQ server.
Can a project be created in XTRF from this? 

Hi,

Is anyone using XTRF 9.2. already? Are there any critical issues we should be aware of before updating? Which memoQ version is the last stable version we can use with 9.2?

Kind regards,

Peter

Hi everyone!

We are working on implementing the integration with memoQ, but we are experiencing an issue that even though it's not a blocking one, it's extremely inconvenient.

Whenever we upload source files to a Smart Project and they are sent to the memoQ project, the analysis files take about 30 minutes to make it back to XTRF. Strange thing is that it randomly happens (sometimes the analysis make it back almost immediately).
I'm attaching a screenshot of the issue, where it took 36 minutes to retrieve 2 small files. 

Has anyone experienced this issue before? If yes, how have you solved it?

Many thanks in advance!

Best,

Lea

We have several workflows that include using memoQ to generate an analysis of files. Is there any way to have the total word count from the analysis automatically populate the project's volume field? Either using a macro in XTRF or maybe an automated action within memoQ to send the word count to the XTRF api?

Setting XTRF via API with memoQ server. Smart Projects.
PM is working heavily in memoQ preparing. It happens so often, that you do a statistics in between.
But look what happens:
The receivables are reset to standard match values ;7) and so the agreed receivable is gone.

If you made your receivables with tweaking the match values, then you have to set it over and over again. Not impressive...
Tell me what you think
Best
Juergen

We just started running some tests (in a seprate XTRF instance) of the XTRF-memoQ integration feature. So far it's working great, but I have a few questions for those already familiar with it.

• To what extent can we control what XTRF pulls from memoQ when creating a project and completing a step? XTRF is currently pulling some things we don't need (untranslated bilingual document at project creation) and not pulling things we need (translated bilingual document, QA report at every step)

• Do you handle clients (other agencies mainly) who work with Trados Studio packages and expect return packages? How do approach these projects?

• Is there a way to efficiently link usernames in external system in XTRF (as opposed to manually changing it for each vendor)? We can have a list of usernames in memoQ and a list of vendors in XTRF aligned, can we insert that back into XTRF in bulk?

• (Off-topic) A similar question, but for vendor categories. If we create a dataset of categories —and vendors in them— in an appropriate format, is there a way to update XTRF's database in one go?

• Can we modify the naming convetion for the project in memoQ?

Thanks in advance!

Can anyone confirm that there are no integration issues with XTRF 8.5 and the recently released memoQ 9.2? The changelog for memoQ 9.2 doesn't indicate that any API-related functions were updated, but I'd like to check before going ahead with the update.