Pavel Tsvetkov 

Pavel Tsvetkov said:

I understand that the information is not enough as supplied but any suggestions are welcome.

Indeed.. but perhaps you noticed something about the source content, the terms maybe?  Can you create a small sample and still reproduce the problem with your sample?  If you can't can you export your termbase to multiterm XML and a definition file, then recreate it and still reproduce the issue?  I'd have a play around to try and find a reason for the problem and hopefully a way to reproduce it.

Hi Pavel,

I am having exactly the same issue as yours. Term recognition has stopped working completely since I downloaded the latest version a few days ago. I created several test files and used them on Studio, and no words were recognised.

Downloading the latest version of MultiTerm did not work either.

It would be appreciated if the RWS tech team would look into this and fix.

Kind regards,

Nami

Me too. I upgraded to the latest MultiTerm and Studio and now term recognition does not work at all. I can add a new term and find it under "Termbase Search" but nothing shows up under "Term Recognition".

Hi John,

Ditto - I can find terms under Termbase Search on Studio, but Term Recognition is not working. I created a new termbase file and tested it out on Studio, but nothing changed. Changing settings for term recognition did not work either.

It is a pain, undermining my productivity...

Regards,

Nami 

The only thing I can add is that for old projects (created before the update) term recognition still works for the same termbases but in projects created after the update term recognition only works for two-letter terms.

I hope RWS can offer a solution soon.

Pavel Tsvetkov Nami Matsumoto John Fry LYT LIU 

I spoke to our technical support team this morning to see if they were aware of any reported problems with term recognition and/or verification.  So far they have not got any reports which leads me to believe this isn't a widescale problem with the upgrade in general.  Having said that this doesn't mean you don't have a problem we need to try and get to the bottom of.

So, a good start would be for me to be able to reproduce this issue myself.  Do you have a project that you are able to share that will allow me to try?

In the meantime, what happens if you recreate the offending projects?  Do they work if you set them up again?  I don't have a solid reason for asking this, but since there has been some substantial changes in recent releases under the hood related to how we work with terminology I think it's worth checking... and when you do this don't use old project templates.  Better to create the project again using the default to make sure nothing old gets into the mix to help with troubleshooting the problem.

I have the same problem, but the project where term recognition does not work was created before the update.

 Nami Matsumoto John Fry Natalja Jampílková Pavel Tsvetkov 

Pavel sent me a project to test and I was able to reproduce this on his project.  I could also reproduce it on a new termbase I created with just two entries, and also a file with just a few sentences.  So no need to send me anything more.

I would be interested to know what language pairs you are translating with though?

Thank you for getting back to us, Paul.

I work on Japanese - English (both directions).

Pavel Pavel  Thank you for sending Paul a test project file.

Regards,

Nami

I am experiencing the exact same issue, working with Japanese to English, and it is consistent across multiple computers (two with UK English Windows, and the other with Japanese). I have also spoken to several other people who are having the issue, and know of two different companies who have apparently reported the issue (and stopped updating or rolled back to the previous version for the time being based on advice they received). So it surprises me to see that IT hadn't heard about it! 

It is heartening to see that it is being looked into now. Hopefully there will be a fix soon.