Forum: Wordfast support
Topic: Puzzled by Alt+Down behavior, WF Pro 3.4.4
Poster: Hirundo Dutch Language Services
I am puzzled by the behavior of Alt+Down in Wordfast Pro 3.4.4.
Is it intentional or am I doing something this wrong?
I am proofreading a translation using the original TM (= TM that has not yet been updated with the translation). Alt+Down (next segment TM commit) seems to do as follows, regardless whether "Perform TM Lookup automatically" is selected or not:
(1) WF commits the current segment to the TM,
(2) moves to the next segment, and then
(3) instantly overwrites the translation there with a fuzzy match from the TM.
I find automatically overwriting in step (3) unacceptable. Instead of showing the translation, WF immediately replaces it with a wrong (because fuzzy) match! Why does it do that? WF should not blindly insert from the TM if there is a translation already; it makes proofreading impossible.
Is there not one key combination to commit the current segment and move to the next one without automatically overwriting it?
Alt+End (commit current) followed by Ctrl+Down (next segment no commit = lookup in TM without inserting from TM) seems to do that, but I find two actions (four keys) for something so simple too cumbersome on long texts.
Thanks for helpful answers!
Joachim
Topic: Puzzled by Alt+Down behavior, WF Pro 3.4.4
Poster: Hirundo Dutch Language Services
I am puzzled by the behavior of Alt+Down in Wordfast Pro 3.4.4.
Is it intentional or am I doing something this wrong?
I am proofreading a translation using the original TM (= TM that has not yet been updated with the translation). Alt+Down (next segment TM commit) seems to do as follows, regardless whether "Perform TM Lookup automatically" is selected or not:
(1) WF commits the current segment to the TM,
(2) moves to the next segment, and then
(3) instantly overwrites the translation there with a fuzzy match from the TM.
I find automatically overwriting in step (3) unacceptable. Instead of showing the translation, WF immediately replaces it with a wrong (because fuzzy) match! Why does it do that? WF should not blindly insert from the TM if there is a translation already; it makes proofreading impossible.
Is there not one key combination to commit the current segment and move to the next one without automatically overwriting it?
Alt+End (commit current) followed by Ctrl+Down (next segment no commit = lookup in TM without inserting from TM) seems to do that, but I find two actions (four keys) for something so simple too cumbersome on long texts.
Thanks for helpful answers!
Joachim