Gemma Smith

Have you tried checking this by using a file you handled in Trados instead of memoQ?  The reason I ask is because of this:

Gemma Smith said:

I doubt it as the translator couldn't amend the segmentation simply by opening it in memoQ?

It would need checking, but I do think you can amend the segmentation simply by opening the file in memoQ.  memoQ can split/join segments in order to achieve better matches and I'm not really sure what effect this would have on an sdlxliff when you save the target later.  That part would need investigating... but you can validate by not using memoQ and see if the same problem occurs?

I'm also curious about this:

Gemma Smith said:

Due to tag/file type issues with PerfectMatch, I am aware that this is a known bug - i.e. PM should not be used to segment the files, i.e. PerfectMatch should not be run at Project creation stage, but rather after as a separate batch task.

Do you have the bug number for this?

Hi Paul,

Just returning with an update on this one.

Support have raised this issue as a defect CRQ-25143 for the development team to check and fix.

In the meanwhile, the only suggested workaround was to try and fix the original translation (i.e. old project) and then re-do PerfectMatch (for new project). Unfortunately this is not a realistic workaround for us and so instead I ended up manually re-checking all (a mere 75000 words) PerfectMatch segments this time... 

Thanks again for your help and hopefully a fix will be found soon.

Best wishes,

Gemma

Hi, Gemma.

Thanks for sharing this. In the end, this was caused by having processed the files with MemoQ or was it totally unrelated?  What fix was required in the original translation?

We don't use MemoQ but it would be good to know if we have to check the PM output.

Daniel

Hi Daniel García Magariños,

Thanks for your message. My particular case was unrelated as I did a test and found that the SDLXLIFFs have the wrong segmentation before I sent it to our memoQ-using team. 

As to the suggested fix: There was an extra CF tag in some segments. The Support team fixed the original translation by splitting the segments before the extra CF tag and fixing the target translation.

It seems to happen when there is a cf tag between 2 sentences that for some reason then get segmented wrongly into 1 combined segment. Typically in my case, the translation of the first sentence pf the segment is pulled into the target by PerfectMatch, but the translation of the second sentence is missed entirely. I am unable to share a screenshot due to client confidentiality, sorry, but I hope my explanation makes sense. 

Hope this helps.

Best wishes,

Gemma

Hi Daniel García Magariños,

Thanks for your message. My particular case was unrelated as I did a test and found that the SDLXLIFFs have the wrong segmentation before I sent it to our memoQ-using team. 

As to the suggested fix: There was an extra CF tag in some segments. The Support team fixed the original translation by splitting the segments before the extra CF tag and fixing the target translation.

It seems to happen when there is a cf tag between 2 sentences that for some reason then get segmented wrongly into 1 combined segment. Typically in my case, the translation of the first sentence pf the segment is pulled into the target by PerfectMatch, but the translation of the second sentence is missed entirely. I am unable to share a screenshot due to client confidentiality, sorry, but I hope my explanation makes sense. 

Hope this helps.

Best wishes,

Gemma