Because lookahead found a fuzzy match, the full translation from the previous segment will not get inserted. What is more, it will not even appear in the TM matches pane. Going back to the previous segment and returning to the fuzzy does not help. I believe this is a bug.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Hi Darren Ki-Fun ,
Definitely through your support contract. The integration with JIRA I mentioned would have been for Ideas. So if you have a support contract it always makes sense to use that. When we get bugs reported in the community and we are able to validate them then we do push them through support. But the process is faster if you are able to do this yourself... and you get direct feedback which may, or may not, happen in the community.
Thanks
Paul
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
I believe that LookAhead has a potential. The flaw with immediate 100% and fuzzy matches not being displayed could be dealt with by giving the user an option to choose which resources LookAhead should apply to (eg. use LookAhead for all resources except for the TM where the new translations are stored).
I think most of us use a separate TM for each project (or the project TM created by Studio), using all the Big Mama TMs for reference only. A project TM is small and it doesn't need to use LookAhead, because Studio browses it fast anyway, so everybody would win here.
There is one bug, however, with LookAhead turned on. Sometimes when I move to another segment, Studio displays matches for the previous one. I then need to press ctrl+alt+t to see proper suggestions.
I believe that LookAhead has a potential. The flaw with immediate 100% and fuzzy matches not being displayed could be dealt with by giving the user an option to choose which resources LookAhead should apply to (eg. use LookAhead for all resources except for the TM where the new translations are stored).
I think most of us use a separate TM for each project (or the project TM created by Studio), using all the Big Mama TMs for reference only. A project TM is small and it doesn't need to use LookAhead, because Studio browses it fast anyway, so everybody would win here.
There is one bug, however, with LookAhead turned on. Sometimes when I move to another segment, Studio displays matches for the previous one. I then need to press ctrl+alt+t to see proper suggestions.
Translate
