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.

W K said:

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.

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.

Theodor Pitsch 

Theodor Pitsch said:

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.

Theodor Pitsch W K Simona Weiss Bruce Campbell 

Hi guys,

I've been reading this thread and wondering why some or all of you seem to have taken exception to how Paul replied to your posts.

I don't find his posts at all unprofessional, wilful, stubborn or any of the other unkind words you have used to describe his participation. From my perspective, none of Paul's replies were written to 'upset other users' but rather to help them learn more about the product and how they can make it work best for them.

 Paul is totally dedicated to the job he does for us all, this is proved by the fact that he diligently works longer hours than he is contracted to do, in order to help us all use this software as knowledgeably as possible. He's always professional and honest in how he does his job. He's always happy to admit if he's made a mistake and even apologises. I see nothing in his comments that justifies such angry comments as I have read in this thread.

I've been using Trados products since several years before Studio was even created, have been an enthusiastic beta tester and voluntary help to other users right through Studio and MultiTerm's progression, and have never encountered the sort of attitudes in Trados/SDL/RWS employees that you guys are accusing Paul and the RWS 'specialists' of. They are always helpful and willing to learn from any problem arising from any clash between the complexity of Studio's current programming and the legacy stuff they have to accommodate from older versions. They do an amazing job despite the challenges they face.

All Paul has done is try answer your questions logically, I don't understand why you guys appear so angry. He only deals in facts, to try to help you and reply to your various emotional outbursts as best he can. He has been more than patient and I feel compelled to ask you to calm down because I can't see what you're all getting so angry about.

A change was made in a particular small area of Studio's functionality, to improve how it works overall. It was not done to annoy anyone; it was not 'stupid'. Most importantly, it doesn't mean you can no longer see how many words you have left to translate.

So, what's the problem?

All the best,

Ali

Theodor Pitsch W K Simona Weiss Bruce Campbell 

Hi guys,

I've been reading this thread and wondering why some or all of you seem to have taken exception to how Paul replied to your posts.

I don't find his posts at all unprofessional, wilful, stubborn or any of the other unkind words you have used to describe his participation. From my perspective, none of Paul's replies were written to 'upset other users' but rather to help them learn more about the product and how they can make it work best for them.

 Paul is totally dedicated to the job he does for us all, this is proved by the fact that he diligently works longer hours than he is contracted to do, in order to help us all use this software as knowledgeably as possible. He's always professional and honest in how he does his job. He's always happy to admit if he's made a mistake and even apologises. I see nothing in his comments that justifies such angry comments as I have read in this thread.

I've been using Trados products since several years before Studio was even created, have been an enthusiastic beta tester and voluntary help to other users right through Studio and MultiTerm's progression, and have never encountered the sort of attitudes in Trados/SDL/RWS employees that you guys are accusing Paul and the RWS 'specialists' of. They are always helpful and willing to learn from any problem arising from any clash between the complexity of Studio's current programming and the legacy stuff they have to accommodate from older versions. They do an amazing job despite the challenges they face.

All Paul has done is try answer your questions logically, I don't understand why you guys appear so angry. He only deals in facts, to try to help you and reply to your various emotional outbursts as best he can. He has been more than patient and I feel compelled to ask you to calm down because I can't see what you're all getting so angry about.

A change was made in a particular small area of Studio's functionality, to improve how it works overall. It was not done to annoy anyone; it was not 'stupid'. Most importantly, it doesn't mean you can no longer see how many words you have left to translate.

So, what's the problem?

All the best,

Ali

Alison Field said:

A change was made in a particular small area of Studio's functionality, to improve how it works overall.

Even if it is a small change, it was not necessary and affected the work of many translators.
Paul seriously recommends to consult the Confirmation Status, which supposedly contains "the same data". But only for a selected file not for all individual files at the same time. Even I, to whom Paul still ascribes beginner status after 7 years of working with Trados (isn't that insulting?), occasionally have 20, 30 or more files in a project. So far, I have been able to see at a glance where more work is needed and how much. Now only the "specialists" can see that. I can't be thankful for that and not join in the praise for Paul!

A reminder that under confirmation statistics, found at both project and file level, there is flexibility and user choice when it comes to evaluating work done/to be done in a way that hopefully appeases most 

I have been using Trados for 11 years (Studio 2009) and followed my progress toward completion and getting paid by Words and all the sudden, it is changed to segments and even worse is still incorrect as I discovered in a recent post.

 (+) TRADOS STUDIO 2022 Term Recognition NOT working correctly ? - 2. Trados Studio - Trados Studio - RWS Community (Sorry about the mismatch between the content and the title)

Please, just listen to the many people arguing and get back to a "Files" view by Words or make it selectable by the user as it is selectable in the Confirmation Statistics windows.

I have installed the lates update for Trados Studio 2022 - 17.0.4.13209, but unfortunately, the issue is still there.

On the left is a work in progress on Studio 2021 (Files View) and the numbers (Words) match perfectly the Confirmation Statistics

On the right is the same work in progress on Studio 2022 (Files View) and the numbers (Segments) are all over the place from where I want and I used to see them (Words)

Please. Do something sensible!

From the "Confirmation Statistics" windows 

One more example that should tell you how inconvenient is this change!

I started a small project today 

See the same views

On the left is a work in progress on Studio 2021 (Files View) and the numbers (Words) match perfectly the Confirmation Statistics

On the right is the same work in progress on Studio 2022 (Files View) and the numbers (Segments) are all over the place from where I want and I used to see them (Words)

                                   Why is that?

It was a file with 7 paragraphs numbered 1 to 7 and those segments with numbers where 1/3 of the segments.

See the target below

Paul Patruno 

No amount of complaining about this is going to support your case.  There are hardly any users who are upset about this... at least it seems we can count them on one hand.  Please explain why you cannot use the confirmation statistics tab at the bottom to see the details you want n the way you want them?

If there were many users upset then I'm sure the product management team would reconsider, or perhaps plan in some work to accommodate both points of view.  But given the new way is actually a more accurate view of the real completion of a file and not just the wordcount, this is unlikely to change without a very good reason to do it.

Paul Patruno said:

Please, just listen to the many people arguing

Define "many people" seeing as you have made this claim?

I absolutely consider that this statement "the new way is actually a more accurate view of the real completion of a file and not just the wordcount" is personal to you and untrue to me!

My last post earlier today demonstrates how misleading it is, when 30% or segments = 2% of words in a real case.

I can actually use and see my progress by Words on one file or on the set of files opened in the editor, but I cannot use this view to monitor my work as I have often on my docket more than one file or a set of files in the editor to work on and the Files View where it is off by a lot.

The Files view is my daily dashboard and must reflect the way I work, not something else (I call this consistency). 

I work with this software like anybody else to earn a living by the number words I translate and the progress I want to see more often are in the Files view, not in the editor.

Progress by segments is from a totally artificial view created for practical reasons and is NOT a measure of your work,

      I noticed that the Manager (beta) is (hopefully) measuring progress by Words.
      Why would the Files view not doing the same?
     This would be a very good reason, for consistency. Right?

I need consistency to keep my brain focused at work. 

I am still flabbergasted you did this change and uncredulous you would not address my request and go back to the statu quo ante bellum and give to all of us the choice to get the Files view indicator by Words we always have (for the sake of consistency)

Paul Patruno said:

I am still flabbergasted you did this change and uncredulous you would not address my request and go back to the statu quo ante bellum and give to all of us the choice to get the Files view indicator by Words we always have (for the sake of consistency)

I'm too. And I miss any approval of the stupid change (except Paul's, the other one). He can't have won much praise for it.

Paul Patruno Theodor Pitsch 

ok - given neither of you, nor anyone else, is going to answer my simple question on why you cannot use of of the other methods for seeing at a glance the wordcount... and given we seem to have three users from all of our Studio base who seem to agree with you:

I doubt you will ever see any change.

Just ranting and repeating yourself without providing any good reason why you can't use the existing features in the software for this purpose, or debating this rationally in the idea itself, means you are very unlikely to get any attention or be taken seriously.

So here's the link to the idea:

 Please go back to Progress Bar focusing on words not segments 

Here's a link to an article explaining the different ways in which you can use the software:

https://multifarious.filkin.com/2022/08/28/cant-see-the-wood-for-the-trees/

And I'm going to lock this thread for further comment.  If you want a change then please treat this seriously and do these two things:

1. use the idea where the product manager will be able to assess whether a change is needed or not
2. explain in the ideas thread why you cannot reasonably use the other mechanisms to achieve what you want