Excluding locked segments from the "Not Translated" character count in [Editor]

I would like to exclude locked segments from the "Not Translated" character count at the bottom of the [Editor] window, so that I know how much work I have left to do. How do I do this?

Parents
  • Hi David,

    This isn't possible. You can exclude from the analysis as you probably know (depending on your Studio version) but not from the count in the toolbar. Does seem like an obvious enhancement though.

    Perhaps the solution is to select all the locked segments and then set the status to "translated". This way your stats will more accurately reflect your work as you would prefer.

    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

  • I wanted the same, as including locked segments in the progress counts can make it very difficult to follow how much work has been done and how much is left to do. I have a file where everything that can be reviewed has been reviewed, but because of the many locked segments, only 3% appear as completed. It would make sense to show me that 100% of what can be done is completed.

    As for setting the status of locked segments to translated, Studio refuses to do it.
  • Hi

    Unknown said:
    As for setting the status of locked segments to translated, Studio refuses to do it.

    Could that be because they're locked and this is the expected behaviour?  Unlock them first and then set the status to translated... ideally if you want that you would do this first.

    Having said that you may be able to set the status of the locked segments if you use the SDLXLIFF Toolkit as it doesn't use Studio to effect the change and can probably add the appropriate Status to the locked segments.  I haven't tested it but I reckon that might work.

    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

  • @Paul:
    When using the SDLXLIFF Toolkit you can change any status and any locked or unlocked segment to whatever status including the locked or unlocked state. So you can change locked untranslated segments to unlocked or you can change pretranslated segments to locked and sign-off rejected and so on. This works fast even on huge files and is a big help, when processing partially translated packages from our customers, who for example refuse to pay for the pretranslated segments. You can of course do more, but this is nothing new 2U.

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

  • Thanks, Paul and Jerzy. While I'm waiting a few minutes for Studio to select 20,000 segments, I can reply here (it really is that slow).

    'Perhaps the solution is to select all the locked segments and then set the status to "translated"' is what you said on 25 April 2016, so that's what I was trying to do, but if you hadn't said that, I wouldn't have expected to be able to change the status of locked segments to "translated" either. I'm trying to see if I can unlock them, then change the status, then lock them again.

    Even if I manage to do that, the percentages shown in the lower right corner will still be wrong, as the locked segments will be included in the "Translated" counts, so this isn't much of a solution, except that I will end up with 100% completed instead of perhaps 10%.

    I'll have a look at the SDLXLIFF Toolkit later, as I'm just trying to figure out how to use Studio, and many things are very different from MemoQ, so I’m still feeling quite handicapped in Studio. I thought showing a meaningful progress rate would be part of the basic functions of a CAT tool, but apparently it isn't in Studio.

    Well, Studio hasn’t been responding for about ten minutes now, so maybe I should go and have dinner and hope it has finished selecting segments when I return. Given how long time it takes, it’s probably better not to take this any further. It is using 25% CPU, so at least it hasn’t stalled, but it could be looping. There must be some performance issues to look at here. This doesn’t look like very efficient programming.
Reply
  • Thanks, Paul and Jerzy. While I'm waiting a few minutes for Studio to select 20,000 segments, I can reply here (it really is that slow).

    'Perhaps the solution is to select all the locked segments and then set the status to "translated"' is what you said on 25 April 2016, so that's what I was trying to do, but if you hadn't said that, I wouldn't have expected to be able to change the status of locked segments to "translated" either. I'm trying to see if I can unlock them, then change the status, then lock them again.

    Even if I manage to do that, the percentages shown in the lower right corner will still be wrong, as the locked segments will be included in the "Translated" counts, so this isn't much of a solution, except that I will end up with 100% completed instead of perhaps 10%.

    I'll have a look at the SDLXLIFF Toolkit later, as I'm just trying to figure out how to use Studio, and many things are very different from MemoQ, so I’m still feeling quite handicapped in Studio. I thought showing a meaningful progress rate would be part of the basic functions of a CAT tool, but apparently it isn't in Studio.

    Well, Studio hasn’t been responding for about ten minutes now, so maybe I should go and have dinner and hope it has finished selecting segments when I return. Given how long time it takes, it’s probably better not to take this any further. It is using 25% CPU, so at least it hasn’t stalled, but it could be looping. There must be some performance issues to look at here. This doesn’t look like very efficient programming.
Children