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
In my case the out of memory problem was strictly related to WebSearch plug-in, or to be more precise, to Linguee resource. There's something wrong with ad display in WebSearch under SR1, making the browser consume RAM like crazy. The solution is to create an account with Linguee and then the ads disappear.
Translate
