Since I updated Trados, the progress shown in the progress column in files view is wrong.
Is there anything I can do to have the correct progress shown?
Or is there some new algorithm that calculates the progress and can I chose somewhere the formula for it?
Thank you!
From a translator's view, I personally agree with Simona and Theodor, the word count should reflect the real effort in the progress bar instead of segments, moreover the unconfirmed tags only segments will be placed automatically into the target which is the most convenient feature used by many translators.
It seems the dev team solved a technical bugs, unfortunately only technically, indeed quite misleading in practice.
It seems the dev team solved a technical bugs, unfortunately only technically, indeed quite misleading in practice.
No one at RWS seems to care about that.
Theodor Pitsch W K Simona Weiss Bruce Campbell
Why isn't this helpful? It seems to give you exactly what you want.
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
Your specialists also have this display. Are they so stupid that you have to explain the new status bar to them?
There was no reason at all to upset the other users. This is pure willfulness - and that you don't want to row back is stubbornness.
This is pure willfulness - and that you don't want to row back is stubbornness.
No it isn't. First of all this isn't my decision. But I can see perfectly well why the decision was made. I feel as though you don't want to listen at all. If you have hundreds or thousands of files - which you probably won't have, but a project manager working on large projects will have - then the fastest way to see if something is incomplete is by quickly scrolling the files list and sorting by progress.
I don't think this conversation is going anywhere. I am perfectly happy to listen to your complaint, and I have done. I can see you got used to using something that was working incorrectly and the usecase for it being fixed is a lot stronger than the one you have to undo that change. The only stubbornness I see is your unwillingness lower your eyes a few inches and read exactly what you need for a single file in the way you see fit. You have also shown no willingness whatsoever to explain why this is so important for you and why you cannot lower your eyes a bit. You have just complained with no context, yet you expect us to spend time and money do deliver what you want. Think about that.
I think it could be possible to add a feature to allow a user to decide for themselves whether words or segments are the basis of this progress. That's up to the product manager to decide. Frankly I wouldn't waste time on that (until I had nothing else that needed development time) if it was my decision given it's already there in front of you a few inches lower. But let's see if the idea generates enough interest to warrant thinking about this at all.
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
This is pure willfulness - and that you don't want to row back is stubbornness.
No it isn't. First of all this isn't my decision. But I can see perfectly well why the decision was made. I feel as though you don't want to listen at all. If you have hundreds or thousands of files - which you probably won't have, but a project manager working on large projects will have - then the fastest way to see if something is incomplete is by quickly scrolling the files list and sorting by progress.
I don't think this conversation is going anywhere. I am perfectly happy to listen to your complaint, and I have done. I can see you got used to using something that was working incorrectly and the usecase for it being fixed is a lot stronger than the one you have to undo that change. The only stubbornness I see is your unwillingness lower your eyes a few inches and read exactly what you need for a single file in the way you see fit. You have also shown no willingness whatsoever to explain why this is so important for you and why you cannot lower your eyes a bit. You have just complained with no context, yet you expect us to spend time and money do deliver what you want. Think about that.
I think it could be possible to add a feature to allow a user to decide for themselves whether words or segments are the basis of this progress. That's up to the product manager to decide. Frankly I wouldn't waste time on that (until I had nothing else that needed development time) if it was my decision given it's already there in front of you a few inches lower. But let's see if the idea generates enough interest to warrant thinking about this at all.
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
Translate
