Under Community Review

Include Locked Segments in the Progress count

Problem:

When translating files with locked segments you currently need to check manually if some segments to be translated have been forgotten as you will never reach a 100%-level in the Progress display, either in the file view nor in the status bar information.

When working on projects including locked segments, the completion rates will never reach 100%. This might not be a problem when projects are smalls as you might remember which issues you had und needed xxxx checks. But when having to process multiple and/or (very) large files, you might have translated everything translatable with not one rate at 100% completion.

The problem comes when the translation of a file needs to be chunked - i.e. wating for client’s answer for clarification, waiting for changes in documents, etc. - As none of the files will appaear completed and you can’t be sure the completion rate is due to locked or to untranslated segments or unconfirmed segments,

To make sure no segment as been missed, the translator must navigate through all of them and manually check the actual progression by combining filters in 2 or 3 different steps.

This is not only more work, and less productivity, but this is also something that could be avoided.

Solution:

Editor View

  1. Add a category “Locked segments” in the status bar to the already existing “Not translated/Draft/Translated” with the same units and display values, and integrate the value to the total count.
  2. Add an option to the display settings for including “Locked segments” to the status bar or not

File View:

  1. Add an option to choose to Include or exclude locked segments in the progress displayed

Expected Outcome:

This improvement will allow to see the “real” completion rate at a glance without having to perform any manual actions like filtering,

A more user-friendly interface and a gain in productivity.

Parents
  • Dear  , 

    I'll keep asking: any update on this feature?

    I understand that the forces are not equally distributed: users submitting ideas are many, your product and software development teams are limited by nature.

    That said, may I ask: Is it reasonable to collect ideas from all your users and then let them sit gathering dust in some repository for years, never to be looked at again - except by other users wishing the improvement too?

    Thanks for taking the time to answer (at least the 1st question?)

    Best regards, 

    Christine

Comment
  • Dear  , 

    I'll keep asking: any update on this feature?

    I understand that the forces are not equally distributed: users submitting ideas are many, your product and software development teams are limited by nature.

    That said, may I ask: Is it reasonable to collect ideas from all your users and then let them sit gathering dust in some repository for years, never to be looked at again - except by other users wishing the improvement too?

    Thanks for taking the time to answer (at least the 1st question?)

    Best regards, 

    Christine

Children
No Data