I had this error in Studio 2015 and had hoped that by upgrading to 2019 the problem would be solved, but it is still there: A term that is flagged as 'Error: the target segment does not contain the translated term etc." is in the Termbase and is shown in the Term Recognition pane. I hope the screens are good enough to see that 'element' is in the termbase and in the target segment and is still flagged as an error.
This is really weird behavior. I am also struggling with Multiterm, which fails to recognize all terms as it should. Paul listed several conditions where a term fails to show up in the term recognition window, such as term followed by punctuation, etc. Looking at your example, I feel there is no excuse for this term not recognized properly! I am interested in hearing what SDL says about this issue you brought up.
In the meantime, I am looking for ways to complement Multiterm but so far haven't been able to find something. I tried the RyS plugin (RyS Termbase & Translation Assembler) but felt that was too complicated for me. Hopefully I will be able to find a program that would address this term recognition problem. Ideally this can be addressed by the next Multiterm version!
Chunyi
I am interested in hearing what SDL says about this issue you brought up.
Did they answer? Did they solve the problem? It is still unreliable in Studio 2021...
Hi Roger,
I don't recall getting a solution, but I have learned to live with it, as Multiterm is still easier for me to use than the other programs (such as the RyS Termbase plugin). Hopefully this issue will be addressed in one of the later versions of Studio.
Hi Roger,
I don't recall getting a solution, but I have learned to live with it, as Multiterm is still easier for me to use than the other programs (such as the RyS Termbase plugin). Hopefully this issue will be addressed in one of the later versions of Studio.
Translate
