Forum: MemoQ support
Topic: Pre-translation does not overwrite existing unconfirmed segments MemoQ 8.6
Poster: Laura Bergamini
[quote]Thomas T. Frost wrote:
[quote]Laura Bergamini wrote:
yes, but bullet 2 does not behave as stated. Pre-translate does NOT overwrite what is in segments (at 0%) even if a better match is found (I have some 98% that are not inserted). Is this a common behavior or a fluke in my installation?
[/quote]
As you quoted yourself,
[quote]Laura Bergamini wrote:
•Edited or confirmed segments are not overwritten. If you need to overwrite these segments, you need to clear them first using the Clear translations button on the Preparation ribbon tab.
[/quote]
[/quote]
MT segments show up as NOT CONFIRMED with a big red X and at 0%, which means translation not confirmed, and certainly not edited. They should be overwritten by default, they are not locked in any ways or haven't been touched.
This is a flaw in MemoQ in my opinion. I cannot be the only one facing this issue.
My client pays for MT output, so I cannot clear what has been applied and re-run MT myself.
The workaround to create a temporary MT memory is acceptable, and I thank you for the suggestion.
Topic: Pre-translation does not overwrite existing unconfirmed segments MemoQ 8.6
Poster: Laura Bergamini
[quote]Thomas T. Frost wrote:
[quote]Laura Bergamini wrote:
yes, but bullet 2 does not behave as stated. Pre-translate does NOT overwrite what is in segments (at 0%) even if a better match is found (I have some 98% that are not inserted). Is this a common behavior or a fluke in my installation?
[/quote]
As you quoted yourself,
[quote]Laura Bergamini wrote:
•Edited or confirmed segments are not overwritten. If you need to overwrite these segments, you need to clear them first using the Clear translations button on the Preparation ribbon tab.
[/quote]
[/quote]
MT segments show up as NOT CONFIRMED with a big red X and at 0%, which means translation not confirmed, and certainly not edited. They should be overwritten by default, they are not locked in any ways or haven't been touched.
This is a flaw in MemoQ in my opinion. I cannot be the only one facing this issue.
My client pays for MT output, so I cannot clear what has been applied and re-run MT myself.
The workaround to create a temporary MT memory is acceptable, and I thank you for the suggestion.