Idea Delivered

This idea has now been fully delivered with Trados Studio 2022 SR1. You now have the choice between a progress bar based on words and/or segments. See release notes for more information.

Please go back to Progress Bar focusing on words not segments

Parents
  • Oh man, this is the most annoying feature in this version. To me, the progress bar indicates the effort needed to complete the translation, and the segment count just means absolutely nothing, as I can have a 1 word or a 200 word segment. RWS, please revert back or at least give us a freedom of choice.

  •  

    "at least give us a freedom of choice"

    You already have freedom of choice.  There are several ways to see what you want.  What are your reasons for not wanting to use any of them?

  • I completely agree Algis, I absolutely hate this change and time has not helped. As a jobbing translator, I don't care about segments, I care about word counts.

  • Hi Paul, what are the several ways please? Confirmation Statistics is the only one obvious to me and it's a faff.

  •   

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

    I think the thing to keep in mind is that the majority of freelancers work on single files, or smaller projects... note I am saying the majority as there are always going to be exceptions... so the alternatives for a freelancer are far less onerus than it would be for a project manager working with hundreds or thousands of files per project, with tens or hundreds of projects a day.

    I do not disagree that having a new option to decide how you want this shown is undesirable, but I do disagree the change should be put back as it wasn't correct before.  The decision to make this change is not mine, but as I have been unsuccessful in convincing anyone to explain why the product manager should devote valuable development time to making this optional, nor has anyone taken us up on the offer to discuss this view directly with the development team (something I'm completely at a loss to understand if this is so important), I can't see why he would.

  • The change was totally unnecessary, you can write what you want.
    Why doesn't the product manager take care of inconsistencies that have been dragged through for years? The alleged improvements that come with every paid update are definitely not noticeable for me. Give me a reason why I should update to a version after 22, or I'll do without in the future.

  • Paul, you have a bunch of customers in this very thread complaining about a particular issue, and reasoning it quite well. Pretending that the problem does not exist, or basically saying that we as freelancers are too small to influence the decisions on the UI, is well, not great.

    Just like that blog post, which has this general idea: go dig deep in the radio menu and you will find your darn speed in kilometres per hourm, but we'll keep the speedometer as is.

    By the way, MemoQ is using progress bar based on words (and ignores locked segments for that) by default, just like any other usable CAT tool I know. And, it offers the choice of Segments, Words or Characters. 

Comment
  • Paul, you have a bunch of customers in this very thread complaining about a particular issue, and reasoning it quite well. Pretending that the problem does not exist, or basically saying that we as freelancers are too small to influence the decisions on the UI, is well, not great.

    Just like that blog post, which has this general idea: go dig deep in the radio menu and you will find your darn speed in kilometres per hourm, but we'll keep the speedometer as is.

    By the way, MemoQ is using progress bar based on words (and ignores locked segments for that) by default, just like any other usable CAT tool I know. And, it offers the choice of Segments, Words or Characters. 

Children
No Data