I am testing this app and I notice that it fails to recognize some terms. I suspect this could be to case sensitivity.
https://appstore.sdl.com/language/app/iate-real-time-terminology/950/
https://iate.europa.eu/entry/result/1545601/en-el-la-mul
With further tests, I see that a huge amount of terms is missed (despite having checked all domain fields in the settings).
There does seem to be a problem here. The termbase viewer is failing for me too. Is that the same for you?
We'll investigate and fix.
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 Paul,
Yes, I confirm that right clicking on a term, then View term details fails (no content in viewer), as it also fails in the Termbase Search.
Hi Paul,
Yes, I confirm that right clicking on a term, then View term details fails (no content in viewer), as it also fails in the Termbase Search.
Just letting you know we updated the plugin in the appstore and made two changes as noted here under the 17th December release:
Performance is even slower when using the option to search the subdomains but I think it's now delivering the missing words.
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, I ran some tests with different settings. I used the plugin + a couple of other small local termbases (under 1000 terms each).
Search all termbases sequentially = shows results from all termbases with delay
Search all termbases in parallel = shows results from all termbases with delay
Search hierarchically = shows only local termbase results (with delay) if IATE plugin is not default termbase.
Search hierarchically = does not show local termbase results if IATE plugin is the default termbase.
It is interesting that no matter the options, results are delayed, and that applies to local termbase results too. Also, the delays appear to be of equal length whether one selects 1 domain (with Search in subdomains checked), or all domains (with Search in subdomains checked).
So I think it needs to speed up in order to be usable; not sure if the bottleneck is due to the provider or the technology to get the results displayed in Studio. I guess for each segment lookup multiple queries are sent to the API, so this could account partly for the slowness.
Also, whether one leaves all term types unchecked or checked, results appear to be the same. So not sure what's the point of them being there.
Another point is that there is no unselect all subordinate text boxes functionality (by clicking Term type), so one would have to unselect each box manually or Reset to default to clear all check boxes in all categories.
Translate
