Confirmation of auto-propagated matches despite settings

In Options>Editor, I have explicitly de-selected the option "Auto-propagate exact matches to confirmed segments". 

I have done this several times and shut down the program and restarted it.

Still, Studio has confirmed ALL of my exact matches. I now have to manually search for them and change them to the proper translation.

 

Is there a fix for this?

 

As a side note, I would like to express my extreme dissatisfaction with this version which is astonishingly marred by bugs. As if it were a beta version. Disgusted with the purchase.

Parents
  • Unknown said:
    In Options>Editor, I have explicitly de-selected the option "Auto-propagate exact matches to confirmed segments".

    Just to confirm - do you realize that this effectively means "Do not auto-propagate to segments which already have the 'Confirmed' status set"...

    Unknown said:
    Still, Studio has confirmed ALL of my exact matches.

    ...while this seems to be a completely different situation (namely, "Studio sets the 'Confirmed' status to all segments which are exact matches")?
    This situation does not seem to have anything to do with auto-propagation, at least from your description. This seems to do with either batch task pre-translation from TM, or exact matches coming from TM during manual translation... in both these cases this is default and correct behavior.

Reply
  • Unknown said:
    In Options>Editor, I have explicitly de-selected the option "Auto-propagate exact matches to confirmed segments".

    Just to confirm - do you realize that this effectively means "Do not auto-propagate to segments which already have the 'Confirmed' status set"...

    Unknown said:
    Still, Studio has confirmed ALL of my exact matches.

    ...while this seems to be a completely different situation (namely, "Studio sets the 'Confirmed' status to all segments which are exact matches")?
    This situation does not seem to have anything to do with auto-propagation, at least from your description. This seems to do with either batch task pre-translation from TM, or exact matches coming from TM during manual translation... in both these cases this is default and correct behavior.

Children