I updated from WF3 to 5 this month, and the only TM / TM sub-segments it suggests are ridiculous things like after I'm done typing "the" up pop suggestions for "The", and after I'm done typing "wine" up pop suggestions for "Wine", "ready" gives "Ready", etc.
-- I have no idea where those come from (it does that to a good number of words, though not by any means all of them), or why the first letter is invariably capped, or why it thinks I'd want to change from a non-capped word to ... See more I updated from WF3 to 5 this month, and the only TM / TM sub-segments it suggests are ridiculous things like after I'm done typing "the" up pop suggestions for "The", and after I'm done typing "wine" up pop suggestions for "Wine", "ready" gives "Ready", etc.
-- I have no idea where those come from (it does that to a good number of words, though not by any means all of them), or why the first letter is invariably capped, or why it thinks I'd want to change from a non-capped word to a capped word in the middle of a sentence. Since I usually use at least 2 TMs, there are at least 2 identical irrelevant suggestions.
Even worse, if there's actually a glossary entry for the word I'm trying to type, that appears underneath any of the other, useless, ones.
I imported TMs that have 10s of thousands of TUs, so I wondered at first if WF somehow hadn't parsed them to extract suggestions that would actually be useful, and maybe it would just be a matter of time.
Then I had a segment that was exactly identical to half of a previous segment, and it offered nothing ... so as far as I can tell, the feature is a joke, and I've unchecked the "TM" and "TM sub-segment" boxes.
AFAICT, the auto-suggest feature also doesn't work for numbers, although it did in 3, and the documentation suggests it should in 5 as well.
***
FWIW, I did a really large project a few months ago using Studio for the first time (the client gave me a 1-month license). Working from a blank TM, within the first hour or so, the suggestions became useful, and within a few days, they were a huge help.
Studio would even correct simple issues on its own. EG, if the TM match wasn't bold, instead of suggesting text in a regular font, or giving you a 99% match that you then had to bold, it would go ahead and fix it to bold on its own.
I haven't ditched WF yet ... but I was very happy when I thought that they'd have something similar. Unfortunately ... ▲ Collapse
| | |
Login to reply/comment 
Translation news related to Wordfast
