• State Verified Answer
  • Replies 6 replies
  • Subscribers 433 subscribers
  • Views 1982 views
  • Users 0 members are here
Options
Related

Studio 2017 SR1: segmentation error

Kumiko Iwaizumi

I have the latest build of Trados Studio 2017 (14.1.62846) and my source file is MIF.

When there is a variable at the beginning of a sentence, the variable tag is either omitted from the translation unit, or included in the previous translation unit at the very end (i.e. The period before the variable is not recognized). I need to either split/merge segments to correct the segmentation or translate without the variable (or when I must have the variable, I display All Contents and copy the variable tag into the target translation unit). Is SDL aware of this issue and trying to fix it in the next build?

Regards,

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

    Hi  

    Yes, we are aware of this.  It has also been fixed in CU7 which will be released next week all being well... maybe even earlier:.

    CRQ-5542

    Fix: FrameMaker MIF: Variable tags not always included in segments as expected when occurring in certain tag structures

    CRQ-4065

    Fix: Symbol tags in FrameMaker files placed at the beginning or at the end of segment not imported as translatable inline in Studio 2017

    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
    Seeing segmentation fixes being discussed - any chance that the weird segmentation behavior reported in community.sdl.com/.../46835 has been looked at?
    As I reported later in community.sdl.com/.../48428, it is caused by one of the segmentation updates in 2015 SR3 CU10. Downgrade to pure SR3 (12.3.5262.0) fixed it.
  • 0 in reply to Evzen Polenka
    Hi Evzen,

    I don't think we did anything with segmentation in this release. The focus here was on resolving some of the problems caused by SR1 itself and the new features. There are others things that got in there if they were finished and tested, but segmentation tends to be a bigger deal as even the smallest change there can have a significant impact... sometimes unwanted impact.

    If I'm honest I also didn't pick up on your details as they were not relevant to the threads you tagged them into and looked like they would take a bit if time to investigate. So best done through support... I guess you do have access through your customers to support? If not, would you mind opening a new thread specifically for this and I'll try to work through it with you and make sure we have anything we need on our backlog.

    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
    Hello to all,
    I can share the following experience with you regarding new segmentation problems with Studio 2017 SR1. I am doing support for some freelance translator and I had the following case:
    The translator had newly installed SR1 and did his first project with it. It was a word document (2016) of about 300 words, normally formatted (no hard-breaks where they shouldn't be and he hadn't changed segmentation rules either) But the xliff created had a lot of two word or one word segments - a thing impossible to translate in this state. For the first sentence the segments corresponding (about 10 of them) could be merged, the following sentences which where in the same state couldn't be merged normally. First I thought that it was a problem coming from an old template. But creating a new one didn't help. Then I investigated a little bit further the characteristics of this word document: and I saw that automatic separations where on - and I deactivated this fonction. I also deactivated lookAhead which was on in the translator's options - and miracle, when I created a new project for this translator - I got the normal xliff with NORMAL segmentations one expects from Studio.
    I think it was either the combination of LookAhead in Studio and automatic separations in Word or one of them which caused this problem. Unfortunately I didn't have the time to investigate this further, but I think you should look into this matter in order to see, if there is still a bug with one of these two features.
    Best regards
    Martha Ebermann
  • 0 in reply to Martha Ebermann
    Hi , ,

    I really want to close this thread off because otherwise how will anyone be able to find the answer to the question that was asked in the first place amidst more discussion on a topic that is not about missing variable tags in MIF files? I can mark it as answered but if I do this then your post won't be found because it'll be hidden by default unless I leave the thread open. This is why I want a new thread for these questions so we can try and manage the forum in a way that makes it easier for people to find what they're looking for

    I know the forum can be tricky to work with unless you are familiar with all it's features, but when it has no order then it's tricky to work with even when you do know all it's features ;-)

    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