• State Suggested Answer
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 432 subscribers
  • Views 1586 views
  • Users 0 members are here
Options
Related

memoQ user encountering errors importing my Studio 2015 packages

Dave Devine

Hello everyone,

One of the freelancers we work with uses memoQ. We have been sending him packages and he sends us return packages. I received an email from him today in which he mentioned several problems. One seems to stem from Studio creating empty Project-TMs.  Is there a way to prevent project TMs with 0 entries from being created?

The other, and he says this happens with nearly every package, is that MemoQ complains that "The SDLXLIFF file was not properly segmented in SDL Studio. memoQ will import and segment the text, but the segmentation may differ from that in SDL Studio." The XLIFF looks just fine to me in Studio, and it seems to me to be a memoQ issue. Has anyone else encountered this? My freelancer ultimately is able to work with the files, so the easy answer is to ignore the messages and carry on, but it would be nice to understand what is/what memoQ thinks is going on.

Thanks in advance!
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0

    Hi Dave,

    Unknown said:
    One seems to stem from Studio creating empty Project-TMs.  Is there a way to prevent project TMs with 0 entries from being created?

    Lower your match value when you use Project TMs.  If there is nothing found to match anything in your file from your main TM, and you chose to create a Project TM, then you'll end up with an empty one.  For Studio users it's no problem as they can still use this as a scratch TM, so it still serves a useful purpose.  For memoQ users... well ;-)

    Unknown said:
    The other, and he says this happens with nearly every package, is that MemoQ complains that "The SDLXLIFF file was not properly segmented in SDL Studio. memoQ will import and segment the text, but the segmentation may differ from that in SDL Studio." The XLIFF looks just fine to me in Studio, and it seems to me to be a memoQ issue.

    This is either a bug in memoQ that they will have to fix, or the user is manually unzipping the package and handling the source sdlxliffs themselves.  I have seen users doing this before... not too clever.

    Regards

    Paul

    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 Paul,

    Thanks for the quick response! Another wrinkle to the TM question: Studio creates a project TM even for TMs that are disabled in the project. We have multiple TMs, and rather than have 6 different project templates, I have 2 and activate/deactivate TMs as appropriate. Is my only option here to remove those TMs from the project rather than just disabling them?
  • 0 in reply to Dave Devine
    Hi Dave,

    I have not tested this yet, but it sounds as though it's either remove them or create the additional project templates. Wouldn't it be faster to select a different template when you create your project than it is to disable or remove TMs... seems like less clicks anyway and it would resolve your problem.

    Regards

    Paul

    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