• State Suggested Answer
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 433 subscribers
  • Views 769 views
  • Users 0 members are here
Options
Related

PerfectMatch misses off last part of some segments (even when using workaround to this known issue)

Gemma Smith

Hi everyone,

I've had the issue before, when I prepare a new project for Manual B against a previous Studio Project of very similar (identical at most points) Manual A in Studio using PerfectMatch with formatting tags, the last part of the segment (where it combines 2 sentences into 1 segment during the segmentation process) is lost in the translated target segment.

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. All fine, what I've been doing is when creating the project, add TM and then let the TM segment the files. At this stage I also uncheck Lookup (and Concordance) so that it does not input the matches during project creation (otherwise I then have to clear all segments post Project creation before I can then run PerfectMatch in the separate step). Once the project has been created, only then do I run PerfectMatch against the sdlxliffs of the previous project.

Up until now, doing this separately has worked (at least, I'm starting to doubt that - it is always something I look out for)). I just happened to notice the issue again on the latest project I've created in this way. 

The frustrating thing is that we use PM as a cost-saver for the client - they have manuals (50-90 files between 30,000-50,000 total words) for machinery - but some of the source file are customised each time, whilst most files stay the same, and they want the full translated manual back each time. This is why PM seems handy and better than using the TM. But this issue with the PMs not being reliable is really quote frustrating, especially because we do not check the PerfectMatch and also since I thought the workaround solved it. 

I checked the Reports, in case I forgot and used PM during Project creation of this particular project, but I definitely followed the right process. In this particular project, the translator is using memoQ - might this have anything to do with it? I doubt it as the translator couldn't amend the segmentation simply by opening it in memoQ? Either that or is it the fact I disable Lookup/Concordance?

Any help would be really appreciated.

Many thanks,

Gemma 
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    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?

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul

    Hi ,

    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
Reply Children