Hi Dmitriy,

This seems to be a refresh issue, and it can normally be resolved by running a wordcount via the batch tasks.  If you can reliably cause this to happen it would be helpful if you could share the steps as we have been unable to see exactly why this happens.

So perhaps try the wordcount and let us know if this resolves it.

Hi Paul,

A new file and the same story. Run a wordcount via the batch tasks. The results are: 1) status - In Review; 2) progress - 0. However, having run "Open for Review" and then closing the progress is 100% and the status is "In Sign-Off". Weird!

I can't be 100% certain, but it seems like you've encountered one of my pet peeves there: You open a file for review, you close it and you just intuitively hit enter because when you close a document in virtually any other application, you're prompted to save. Trados, however, does not prompt you to save but instead asks if you wish to complete the review process. You hit enter, all segment statuses are changed to "reviewed",  and my colleagues never fail to get a kick out of the disgruntled noise I make when it happened again. Is this what happened with your project?

As for your original question, the file status is always based on the lowest segment status. If all segments are translated and you have but one segment that was reviewed (e.g. because it was a PM), the file status is "in review". To be honest, I don't remember anymore how this was handled in Studio 2011.

I also occasionally came across negative figures in the bottom status bar in the editor. Sometimes I cannot explain them, but most of the time this happens it's because I split or merge segments and the status bar can't seem to keep up.

Stephan

This is very similar to my case except of one thing: the file is opened for translation, not for review. When translation is over the wordcount becomes negative, the progress is 0 and the status is "In Review". The reviewing manipulations eliminate the negative count and lead to "Sign-Off". As I can see there is no any solution right now.

PS: Just in case, my files are from a package received from my customer. It happens either with files that involve splitting/merging of segments or without such manipulations.

I have experienced the same problem, both in Studio 2011 and 2014. I would love to find a solution for that! Hendrik

Hi,

Maybe we can look at this together.  This is a problem we find quite difficult to replicate reliably, so if you have a project where this behaviour is seen perhaps you can share the project and we can take a look at why this is happening.  Sometimes the problem is not what it seems... sometimes it is... but if we can reproduce it then we should be able to fix it.

Hi everyone,

Don't know what has been done with SP2 but now this issue is simply cured by running "Translation count" task. Thanks Goodness it's not a problem anymore. Hope users will be able again to split and merge segments during alignment (this is should be considered as a priority matter!) as it used to be in WinAlign.

Hi Paul,

I did this. Unlike "Translation count", running "Word Count" doesn't give any positive outcomes. It's a mystery to me. However, I am glad that I've come across that solution.