Forum: MemoQ support
Topic: MemoQ 9.7 - How do I automatically "validate" translated segments to get an accurate cost report?
Poster: Shawn Connelly
Hello all,
I have a ticket open with MemoQ but I am still waiting for a solution after two days. Hopefully, someone in this forum can help?
We recently changed our localization .xlf file format, where the translation.xlf files previously only included English segments.
The header only has:
source-language="en"
There were no "targets" in the .xlf
The workflow was:
a) Make 3 copies of the English only translation.xlf (for 3 projects - En to Fr, En to De, and En to Es).
b) Create 3 language pair projects and upload them to the MemoQ cloud.
c) Engage MemoQ pre-translation. The pre-translation would populate the "targets" for 101% matches (previously translated segments) and 100% or less for heuristic matches. FYI, we don't use machine translation.
d) Next, we generate a cost report to give us a cost for segments of 100% and less (in cost tiers).
e) For any segments less than 101%, we engaged our translators to review or edit those segments.
f) Finally, we set the translation vendor, set a due date, and launch the projects.
The above workflow worked very well until we changed our translation.xlf format to allow us to upload pre-translated segments (translated internally). Now, our translation.xlf file headers include both the source and target: source-language="en" target-language="fr"
And the body includes "targets" with translated segments or empty targets, when there is no translation available.
Once the translation.xlf files are uploaded, I engage pre-translation to fill in any untranslated segments (where possible). And then generate a cost report for all the segments that require translation.
The problem is that I don't know how to tell MemoQ that the pre-existing translated targets should be considered translated. The 0% match rate is being interpreted by the MemoQ cost reporting as untranslated segments.
What can I do to regain an accurate cost report?
In testing, it seems that I might have a solution. Can I select MemoQ's "Confirm and Update" before our translators complete the untranslated content... that seems to correct the cost report. But can I again select "Confirm and Update" after our translators complete their translations?
Thank you and apologies for this very long post.
[Edited at 2021-05-13 19:29 GMT]
[Edited at 2021-05-14 06:33 GMT]
Topic: MemoQ 9.7 - How do I automatically "validate" translated segments to get an accurate cost report?
Poster: Shawn Connelly
Hello all,
I have a ticket open with MemoQ but I am still waiting for a solution after two days. Hopefully, someone in this forum can help?
We recently changed our localization .xlf file format, where the translation.xlf files previously only included English segments.
The header only has:
source-language="en"
There were no "targets" in the .xlf
The workflow was:
a) Make 3 copies of the English only translation.xlf (for 3 projects - En to Fr, En to De, and En to Es).
b) Create 3 language pair projects and upload them to the MemoQ cloud.
c) Engage MemoQ pre-translation. The pre-translation would populate the "targets" for 101% matches (previously translated segments) and 100% or less for heuristic matches. FYI, we don't use machine translation.
d) Next, we generate a cost report to give us a cost for segments of 100% and less (in cost tiers).
e) For any segments less than 101%, we engaged our translators to review or edit those segments.
f) Finally, we set the translation vendor, set a due date, and launch the projects.
The above workflow worked very well until we changed our translation.xlf format to allow us to upload pre-translated segments (translated internally). Now, our translation.xlf file headers include both the source and target: source-language="en" target-language="fr"
And the body includes "targets" with translated segments or empty targets, when there is no translation available.
Once the translation.xlf files are uploaded, I engage pre-translation to fill in any untranslated segments (where possible). And then generate a cost report for all the segments that require translation.
The problem is that I don't know how to tell MemoQ that the pre-existing translated targets should be considered translated. The 0% match rate is being interpreted by the MemoQ cost reporting as untranslated segments.
What can I do to regain an accurate cost report?
In testing, it seems that I might have a solution. Can I select MemoQ's "Confirm and Update" before our translators complete the untranslated content... that seems to correct the cost report. But can I again select "Confirm and Update" after our translators complete their translations?
Thank you and apologies for this very long post.
[Edited at 2021-05-13 19:29 GMT]
[Edited at 2021-05-14 06:33 GMT]