This site uses cookies.
Some of these cookies are essential to the operation of the site,
while others help to improve your experience by providing insights into how the site is being used.
For more information, please see the ProZ.com privacy policy.
I had this irritating problem that auto-assembling didn't work as expected anymore. Took me a lot of time to get to the bottom of this.
Today I got a hint from the developer that a 'recently' introduced feature might be the cause. And indeed, the feature Automatic fragments adjustment was the culprit. Never understood what it was supposed to do. In CT speak, 'fragments' are something that's rather related to TMs than to glossaries.
I had this irritating problem that auto-assembling didn't work as expected anymore. Took me a lot of time to get to the bottom of this.
Today I got a hint from the developer that a 'recently' introduced feature might be the cause. And indeed, the feature Automatic fragments adjustment was the culprit. Never understood what it was supposed to do. In CT speak, 'fragments' are something that's rather related to TMs than to glossaries.
Anyway, after disabling this ominous feature, everything works as expected again: the first target translation (after the TAB character) is used by default for auto-assembling.
The relevant glossary entry: 'oder' (English: or) was auto-assembled with 'en' (English: and) instead of 'of' (or) most of the times. A potentially dangerous deviation when translating safety-related documents.
What I've learned: with a tool like CT, you really have to keep up (or don't update at all). ▲ Collapse
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
This is a very useful feature which recognises your recent usage of the term or fragment synonyms and adjusts their priority automatically to use the synonym subsequently in auto-assembling. The users who do not rely much on the set priorities for their glossary terms or TM fragments should benefit from it.
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
This is a very useful feature which recognises your recent usage of the term or fragment synonyms and adjusts their priority automatically to use the synonym subsequently in auto-assembling. The users who do not rely much on the set priorities for their glossary terms or TM fragments should benefit from it.
Perhaps it's useful to other users, but personally I found this feature an example of too much automation. It consistently translated 'or' with 'and' (oder > und) and also messed around with other short words. Perhaps it needs some polishing? I like to stay in control of AA.
Anyway, since I found where to turn this feature off, I'm ready to enjoy working with CT again.
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Manage your TMs and Terms ... and boost your translation business
Are you ready for something fresh in the industry? TM-Town is a unique new site for you -- the freelance translator -- to store, manage and share translation memories (TMs) and glossaries...and potentially meet new clients on the basis of your prior work.
The underlying LLM technology of LinguaCore offers AI translations of unprecedented quality. Quick and simple. Add a human linguistic review at the end for expert-level quality at a fraction of the cost and time.