How can I have terms displayed when I have an Exact Match?
H
HL
started a topic
almost 6 years ago
I only see the EM:
Best Answer
I
Igor Kmitowski
said
almost 6 years ago
So what would you recommend for newbies?
It is a matter of a personal taste and past experience. As a newbie, I would definitely go for TM Fragments to focus on translation workflow rather than an advanced term-management possibly via external tools too. Editing, matching and searching TMX memory files, be it segments or fragments, in CafeTran is more than satisfactory.
Only way I know is to select an individual term and click the Glossary/TM button up above or use the glossary/TM search shortcut.
That Wdowiak
H
HL
said
almost 6 years ago
That would require some extra actions (to check several terms). One could argue: "Why do you need to see the composing terms if you got an EM?", but that's rather, hmm.
Michael Beijer
said
almost 6 years ago
oh, wait, you mean in the TM pane, right? Because any matching terms are still shown in the Glossary pane, if you have an exact (or 101%) match.
1 person likes this
H
HL
said
almost 6 years ago
I was hoping that Woorden would tune in here, he's the expert on TMs for terms after all.
Hans, are you reading this? What's your advice?
H
HL
said
almost 6 years ago
I think that a second TM is needed, that only contains terms and no segments. Right?
H
HL
said
almost 6 years ago
I hoped that these terms would be displayed in the MB, even when an EM is displayed, however, they aren't either:
Added terms:
Terms not displayed when an EM is displayed:
By the way, would it be possible and a good idea to label the terms with 'Term', instead of 'Excact'?
I
Igor Kmitowski
said
almost 6 years ago
The most common and natural is to use the exact match for the source segment and not to bother and get distracted with tens of individual fragments. If you wish to check an individual fragment anyway, just select it in the source segment and click the Translate button.
The implementation of fragments for translation memories is simple, straightforward and suitable for translators who do not care much for advanced terms management features in their workflow. They just wish to focus on the translation process itself, and may rely on other resources (e.g. online dictionaries and MT systems).
Power users who look for more term-management features should consider using CafeTran glossaries for their advanced purposes. However, this additional power comes along with the increase in some complexity which is not so obvious for new users.
H
HL
said
almost 6 years ago
Yes and I agree, apart from the scenario where you have to use the TM of another TR and want to use your own 100 terms.
H
HL
said
almost 6 years ago
And thanks for your detailed explanation. I think that I can now better compare the features of TM and gloss. Great.
w
woorden
said
almost 6 years ago
IK: Power users who look for more term-management features should consider using CafeTran glossaries for their advanced purposes.
And what is this?
H.
w
woorden
said
almost 6 years ago
IK: Power users who look for more term-management features should consider using CafeTran glossaries for their advanced purposes.
Please explain.
H.
I
Igor Kmitowski
said
almost 6 years ago
Okay, let me list a few advanced usages for glossaries:
1. Edit them easily in any simple text editor or a spreadsheet app. Yes, some translators prefer Excel cells to organize their terminology. IMO, they have been conditioned over the years to do so and it is hard to switch to other editing methods. And they are not locked to CafeTran's editing features.
2. Intuitive and searchable columns arrangement for term fields.
3. A concise term entry. Synonyms and fields for various properties (e.g. source and target synonyms, subject, notes etc.) are in one line - not hidden behind some obscured tags or closed database formats.
4. Inclusion of regular expressions to enhance matching.
With text glossaries, the user is exposed in a rather friendly way to the internals of the glossary structure giving him lots of methods (including non-CafeTran ones) to arrange it as they like. To see exactly how it looks inside. No other editing method is so versatile and so easily accessible.
In contrast, while keeping fragments in translation memories along with the segments, the user does not bother about the above or is simply not interested in it. All they wish is to use them for reference or auto-assembling in CafeTran with some editing and searching capabilities. Not much more, which is perfectly fine.
1 person likes this
w
woorden
said
almost 6 years ago
IK: Edit them easily in any simple text editor or a spreadsheet app
For TMX files, you don't need an external app, and the most important edit functions are built-in. Can't be easier.
Intuitive and searchable columns arrangement for term fields.
Same for TMX files
A concise term entry.
But not necessarily easier/faster than for TMX files, nor better in any way.
Inclusion of regular expressions to enhance matching
Now that's the only valid reason, and a tab del exclusively for regexes would be the only one I might use.
No other editing method is so versatile and so easily accessible
If the need is there (rarely), you can convert TMX>TXT, do your thing, convert back
keeping fragments in translation memories along with the segments
I'm against that, with the exception of the ProjectTM (for extra consistency check and deviant translations only). Terms should be saved separately.
H.
w
woorden
said
almost 6 years ago
And by the way, Igor, you "forgot" to mention any of the unique features of termbases and TMX files in general.
HL
I only see the EM:
So what would you recommend for newbies?
It is a matter of a personal taste and past experience. As a newbie, I would definitely go for TM Fragments to focus on translation workflow rather than an advanced term-management possibly via external tools too. Editing, matching and searching TMX memory files, be it segments or fragments, in CafeTran is more than satisfactory.
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstMichael Beijer
HL
That would require some extra actions (to check several terms). One could argue: "Why do you need to see the composing terms if you got an EM?", but that's rather, hmm.
Michael Beijer
oh, wait, you mean in the TM pane, right? Because any matching terms are still shown in the Glossary pane, if you have an exact (or 101%) match.
1 person likes this
HL
I was hoping that Woorden would tune in here, he's the expert on TMs for terms after all.
Hans, are you reading this? What's your advice?
HL
HL
I hoped that these terms would be displayed in the MB, even when an EM is displayed, however, they aren't either:
Added terms:
Terms not displayed when an EM is displayed:
By the way, would it be possible and a good idea to label the terms with 'Term', instead of 'Excact'?
Igor Kmitowski
The most common and natural is to use the exact match for the source segment and not to bother and get distracted with tens of individual fragments. If you wish to check an individual fragment anyway, just select it in the source segment and click the Translate button.
The implementation of fragments for translation memories is simple, straightforward and suitable for translators who do not care much for advanced terms management features in their workflow. They just wish to focus on the translation process itself, and may rely on other resources (e.g. online dictionaries and MT systems).
Power users who look for more term-management features should consider using CafeTran glossaries for their advanced purposes. However, this additional power comes along with the increase in some complexity which is not so obvious for new users.
HL
HL
woorden
IK: Power users who look for more term-management features should consider using CafeTran glossaries for their advanced purposes.
And what is this?
H.
woorden
IK: Power users who look for more term-management features should consider using CafeTran glossaries for their advanced purposes.
Please explain.
H.
Igor Kmitowski
Okay, let me list a few advanced usages for glossaries:
1. Edit them easily in any simple text editor or a spreadsheet app. Yes, some translators prefer Excel cells to organize their terminology. IMO, they have been conditioned over the years to do so and it is hard to switch to other editing methods. And they are not locked to CafeTran's editing features.
2. Intuitive and searchable columns arrangement for term fields.
3. A concise term entry. Synonyms and fields for various properties (e.g. source and target synonyms, subject, notes etc.) are in one line - not hidden behind some obscured tags or closed database formats.
4. Inclusion of regular expressions to enhance matching.
With text glossaries, the user is exposed in a rather friendly way to the internals of the glossary structure giving him lots of methods (including non-CafeTran ones) to arrange it as they like. To see exactly how it looks inside. No other editing method is so versatile and so easily accessible.
In contrast, while keeping fragments in translation memories along with the segments, the user does not bother about the above or is simply not interested in it. All they wish is to use them for reference or auto-assembling in CafeTran with some editing and searching capabilities. Not much more, which is perfectly fine.
1 person likes this
woorden
IK: Edit them easily in any simple text editor or a spreadsheet app
For TMX files, you don't need an external app, and the most important edit functions are built-in. Can't be easier.
Intuitive and searchable columns arrangement for term fields.
Same for TMX files
A concise term entry.
But not necessarily easier/faster than for TMX files, nor better in any way.
Inclusion of regular expressions to enhance matching
Now that's the only valid reason, and a tab del exclusively for regexes would be the only one I might use.
No other editing method is so versatile and so easily accessible
If the need is there (rarely), you can convert TMX>TXT, do your thing, convert back
keeping fragments in translation memories along with the segments
I'm against that, with the exception of the ProjectTM (for extra consistency check and deviant translations only). Terms should be saved separately.
H.
woorden
And by the way, Igor, you "forgot" to mention any of the unique features of termbases and TMX files in general.
H
-
CafeTran webinar at Proz.com (long!)
-
First look at CafeTran -- Wiki style
-
First steps with CafeTran Espresso - CATguru flavour
-
Article about CafeTran on Mac (in German)
-
Change the colours of the CafeTran interface
-
What is the best way to handle SDL Termbases?
-
memories in TMX or tab delimited?
-
Optimal workflow for 2 computers / translators
-
Glossaries> words with accents & without them
-
Glossary messed up (and I do not know why)
See all 277 topics