Translation finder compact view doesn't show TM name
The translation finder compact view looks nice because it is color-coded (albeit with a code I don't understand). However, it doesn't show important information I need such as the name of the TM and the fuzzy match rate. I think it would be nice if this information also could be visible at a glance for compact view. For example, list TB if from a termbase, MM for main translation memory, MT for machine translation, PM for project memory.
Thank,
Mike
-
Official comment
Hello Mike,
Thanks for your message.
The new compact view has a new section at the bottom with the TM name and other TM segment properties. It is clickable should you need more information or wish to open the TM or TB.
The TM match rates are still displayed on the left-hand side. But note that as always, no rate will be displayed for concordance matches.
Last but not least, the color code are shown in the drop down list next to "hits". Hovering the match rate will also give you the hit category (term match,...).
This dropdown list is also where you can prioritize hits by order of relevance, or untick those you might not find relevant for your project.
-
This is a nice improvement, however, WB doesn't find all the terms that it should find in the terminology database (termbase). I'm not sure why this happens. If you open a ticket on this, I can provide a few examples. Currently, none of us (except for 1 person, perhaps) uses the new editor for the following reasons:
1. People think it is much slower, more confusing in layout than the old editor.
2. The old editor lets you see more segments on one page than the new editor.
3. When we enter new terms using the new editor, they are surrounded by the pipe symbols (vertical bars), which have to be removed manually later.
If you could improve the new editor to the point where it has none of these disadvantages and was noticeably faster, nicer in layout, and easier to use than the old editor, maybe more people would switch over to the new editor.
1
Please sign in to leave a comment.
Comments
2 comments