Detecting language please wait for.......
On an account, we need to check term translation compliance in Xbench. For some languages, like Croatian, due to declensions or suffixes, a lot of false positives will be reported by Xbench. This prevents linguists from spotting real errors. I want to check if it's possible for Xbench to do fuzzy match check or stem check for term translation? Please understand that the account has their own online translation system. So, Terminology Verifier in Trados Studio is not an option here.
The Key Terms check in Xbench uses a very simple heuristic that does not have stemming and lemmatization features.
It is not designed to be a full fledge terminology check but rather a check…
Josep Condal might be the best person to help here. Or maybe Riccardo Schiaffino who is very knowledgeable about Xbench.
It is not designed to be a full fledge terminology check but rather a check of the few key terms that, given its importance for the project in question, can make bearable a few false positives.
A typical use case for key terms are the few dozens of new terms coined during the project with several people working and that are more prone for inconsistencies.
In Xbench Search grammar, which is a combination of Regex and PowerSearch, the current key term check is basically the following search:
where the angle brackets mean "word boundary", and the PowerSearch minus sign means "and does not have".
You can use Xbench checklists to add fuzzyness and stemming. For example:
...could be a terminology check with stemming support if SourceT and TargetT were the stems.
These 5-minute videos are an introduction to checklists:
This 5-minute video explains PowerSearch:
To avoid hijacking this forum with Xbench questions, if you have any questions on Xbench checklists, I suggest to place your questions in the Xbench forum: forum.xbench.net
Thanks Josep Condal... agree with using the Xbench forums too.
I do not like XBench, so I have very shallow knowledge about its usage.Whatever it is, it needs a "list" just like ".sdltb"so, if it is blind to "fuzzy"you add extra items into it manually for the specific document(s), then execute XBench "QA"
abc_sc -> abc_tg (100%) listed as default abc_sc -> abc1_tg (someFuzzy) added manually into the list in order to use this item as "100%" abc_sc -> abc2_tg (Ditto)abc_sc -> abc3_tg (Ditto)
how do you extract those items from the specific document(s) ?dunnojust make it, from now on.. step by step, should be easy..
ah.. this post should move to "XBench country" not here.