CafeTran
How can we help you today?
Term recognition (reloaded)
tre
> It's not clear to me either. If you have two or three word phrase in the glossary, then you should expect exact matching for such multiword glossary phrases
But this is exactly the point. They are not recognized when being behind an apostrophe (as said above, the flavor of apostrophes might differ, depending on several factors)
michael
Yeah, I have been getting that too: entries in my glossary are not being highlighted if they are touching a comma, apostrophe, and a number of other characters, which is a pain in the ass.
Michael
If you wish any character to be skipped during matching add it to the "Do not match" list in Preferences. That's a fast solution to remove any characters that might interfere with the matching of words or fragments.
michael
Hmm, I checked, and the comma is in that list. I will try to see if it happens today and send in some screenshots. Here is my current list:
,.。:;!¡?¿[]"«»‘’“”„'’()
and written differently:
,
.
。
:
;
!
¡
?
¿
[
]
"
«
»
‘
’
“
”
„
'
’
(
)
tre
So any terms with the comma should be recognized and displayed in the Matchboard. They should also be highlighted in the source segment. There is only one current limitation to the highlighting. CafeTran does not highlight the phrase in the source segment if such a character is in the middle of the matched phrase. The Matchboard shows such a phrase just fine.
tre
And no, "l'Amérique du Sud" keeps being undisplayed.
tre
There are actually no more settings changed, only the default settings for "Additional space character" and "Do not match".
tre
1. Remove that apostrophe from "Do not match" list.
2. Deactivate "Prefix matching" and activate "Look up word stems" for glossaries. You may have too much fuzziness with the two options on at the same time.
3. Restart CafeTran.
"Do not match option" CafeTran removes listed characters from the matched segments to increase the chance of finding. However, the "Look up word stems" needs the apostrophe to determine the stem of the word in this case.
tre
- Do not match content: ,.。:;!¡?¿[]{}()"«»‘’“”„‚ (see also here, BTW)
- Prefix matching deactivated (it is always)
- Look up word stems activated (and French Hunspell installed)
- CT restarted
Nope.
What's the glossary word you are trying to match, and to what word in the source segment?
tre
For multiword terms, like in your example, just add the article to your term to match the same in the source segment.
tre
But then again it turns glossary work into a real pain (see here and look for acheter). I still did not test to convert the glossary into TMX - would this help?
tre
Simple detail question:
How can I make CT recognize this term?
Please note that there are different occurrences
Note the difference in the apostrophes (the 3rd case is quite seldom). It depends on programs and some other aspects, which apostrophe is being used.
If I understand correctly, I have the following options
Perhaps I oversaw something?
The handling of terms with apostrophes concerns users translating from Fench, Italian, Catalan and many more (that I might ignore here). I do not think this is an exotic problem.