Trados does not "see" terms with majuscule (upper-case of the first letter of a therm)

Quite strange problem without any sense...

I made a termbase from excel spreadsheet with Glossary Converter (by Gerhard Kordman - an app which Trados offers to download freely); direction iof this termbase is from English into Russian. Just to languages. Very simple. The only "complication" is synonyms.

But everything is fine, termbase is well created and contains synonyms (with "|" as a delimiter), which are also easily and properly recognized by Trados.

Direction of translation is from Russian into English.

The feature (and a problem) is that all terms are recognised properly provided only that this term is among other words in a sentence (between other words) and so has no upper-case. If it happens that this term appears at the beginning of a sentence then MultiTerm does not "see" it. But other terms are still visible...

I tried to rationalize this outcome, to figure it out somehow, but i found no logic in it: it does not depend on whether synonyms were put in termbase in some specific order (for ex., in the first place or otherwise); no witchcraft with formats of text (which is to be translated) also did not help... no logic at all.

Further experiment showed that it seems to be no problem if I switch direction of translation: now from English into Russian with this the same termbase. But it may be illusory because I used very short example. But nevertheless it may be an unpleasant answer... Can it be that the reason is in cyrillic itself? Some troubles with codes of this the very language? I have no ideas...

Finally i fall in total despair, why at all should appear such stupid problems just from nothing and with no reasonable sense...

May be I'm wrong and would be glad to hear it.

Tech specs: Trados 2024; MultiTerm 2021; Glossary Converter (by Gerhard Kordman).

emoji
Parents
  •  

    It does help to provide proper examples because otherwise anyone willing to help may waste their time, and you'll waste yours if the answer doesn't address your actual question.  It also helps to get more answers because without an example anyone willing has to try and create one before answering.

    So here's my, possible unhelpful response, it works on my machine!

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
  • Hello, mr Paul! 

    I really appreciate your answer though really unhelpful ))) But sometimes a single word is worth a lot!

    I"ve thought it over this night and this morning and finally found some key fo my situation.

    The matter is that sometimes my "terms" are not really terms - they are not in a formula "one word - one word" as in your sample, sometimes they are "three words - two words" and like that. The reason is that I try to save some sort of short established phrases such as:

    • "as amended" - "с учетом изменений";
    • "avowedly" - "по общему мнению", "открыто", "прямо";
    • "payable" - "подлежащий оплате", "причитающийся";
    • "ipso facto" - "в силу самого факта".

    So this is examples from my Excel spreadsheet converted into TermBase and which works very well if not one peculiarity. And now it seems to me I have finally discerned what works wrong, namely the following.

    As I've already said if all these "terms" appear in the middle of the sentence - Trados see it; if they appear in the beginning - Trados doen not see it.

    But sometimes it nevertheless works and I broke my brains trying to figure it out.

    After jogging this morning I guess the answer has come to me...

    The real crux is as follows: if my "term" begins with some very short word (mostly prepositions) such as "c...." ("с учетом изменений") or "по..." ("по общему мнению"r "в..." ("в силу самого факта"), ets. - then this unexplained problem appears:

    Examples:

    Screenshot showing a list of sentences in Trados. Red highlights indicate where Trados 'sees' terms, and blue highlights indicate where Trados 'does not see' terms.

    So I think I must confess all my sins so to say "I should not have inserted those strange frases into TermBase" and so on...

    But the strange fact still remains: if all those phrases appears "in between" the sentence Trados "see" them all properly. So why not to use it if it really works?

    So the real rub here is some "upper-case unvisibility" of short words as in my examples, and the roots of it must go - as far as I can imagine - right in the programme code. There must be some restriction in this regard, although without any sense...

    Well I decided that I can live with it, though it would be much better not to encounter such situations (but they will).

    Once again, Mr. Paul, thank your for participation!

    I finally unburden my heart and will live with the knowledge of this absurd programme's feature ))).

    Terms must be terms...

    emoji


    Generated Image Alt-Text
    [edited by: RWS Community AI at 3:48 AM (GMT 1) on 10 May 2025]
  •  

    Why don't you do this:

    1. create a small termbase with the appropriate terms in there
    2. create a small source file that allows me to test your case
    3. zip them up and attach them to your reply

    Then I'll happily engage with you.  I'm not going to spend more time trying to make up what you already have.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
  • Dear Mr Paul, I think that is not worth making all those exercises and engagements which you respectfully propose to do.

    The problem seems to me quite clear in the code (or some formats designated for TermBase or hell knows what else...). It's obvious that this feature (Termbase) was not created for long phrases with prepositions. Originally the formula for termbase is "one word - one word".

    The way out from this is - as I see it now - just to duplicate the russian phrases which contain short prepositions: once - with small letter, and once again (with delimiter in between) - with majuscule. It results with Trados finally see them all - in the middle and in the beginning of a sentence.

    That's finally a resolution i've come to.

    All my termbase is now remastered in this way so I'm unable (and unwilling) to re-re-master them to engage further you on top of it all )))

    Little tedious but that's fine )))

    examples:

    English word "avowedly" has three variants of translation in my termbase: "по общему признанию | прямо | открыто" (symbol of vertical pipe is a delimiter).

    If this phrase appears in the very beginning of a sentence then Trados wil not see it.

    So I added the fourth synonyme (virtually the same but with majuscule in the beginning of the preposition) in this way: "По общему признанию | по общему признанию | прямо | открыто"; now Trados see it. Happily.

    The other words are remastered in the same way. For example, the latin phrase "ipso factum" now looks like "В силу самого факта | в силу самого факта".

    Now I'm sure that my term will not fall out weather it appears in the beginning of a sentence or in the middle of it.

    Stupid resolution of a stupid problem. But there are no tasks ever existing which Bolsheviks could not overcome )))

    Sincerely!

    emoji
Reply
  • Dear Mr Paul, I think that is not worth making all those exercises and engagements which you respectfully propose to do.

    The problem seems to me quite clear in the code (or some formats designated for TermBase or hell knows what else...). It's obvious that this feature (Termbase) was not created for long phrases with prepositions. Originally the formula for termbase is "one word - one word".

    The way out from this is - as I see it now - just to duplicate the russian phrases which contain short prepositions: once - with small letter, and once again (with delimiter in between) - with majuscule. It results with Trados finally see them all - in the middle and in the beginning of a sentence.

    That's finally a resolution i've come to.

    All my termbase is now remastered in this way so I'm unable (and unwilling) to re-re-master them to engage further you on top of it all )))

    Little tedious but that's fine )))

    examples:

    English word "avowedly" has three variants of translation in my termbase: "по общему признанию | прямо | открыто" (symbol of vertical pipe is a delimiter).

    If this phrase appears in the very beginning of a sentence then Trados wil not see it.

    So I added the fourth synonyme (virtually the same but with majuscule in the beginning of the preposition) in this way: "По общему признанию | по общему признанию | прямо | открыто"; now Trados see it. Happily.

    The other words are remastered in the same way. For example, the latin phrase "ipso factum" now looks like "В силу самого факта | в силу самого факта".

    Now I'm sure that my term will not fall out weather it appears in the beginning of a sentence or in the middle of it.

    Stupid resolution of a stupid problem. But there are no tasks ever existing which Bolsheviks could not overcome )))

    Sincerely!

    emoji
Children
No Data