Valeria Maria Tafel

A good question in fact as I'm sure you are not the only one wondering about things like this!

1. add your TM to the TM View and select it,
2. click on "Settings",
3. click on "Language Resources",
4. click on the word "Default" in the "Abbreviations" column for the source language of your TM,
5. type in your abbreviation with the full stop

What source language are you referring to because in English United Kingdom and many other languages I just checked this abbreviation is already there?

Also what version of Trados Studio as this example I shared is 2021.  It'll look different in earlier versions?

And maybe also what content is in your source file for translation? Can you share a screenshot of the segment and also show any tags that might be in there?

Paul, a million thanks!

I work with Studio 2021 and this always happens when I translate from IT into EN, with Italian source texts that mention many law articles. I always find the segments interrupted after "art." and I have to rejoin them manually.

Your scheme above is perfectly clear and actually I tried to add "art." but it was already there!! So why did I get the separated segments?

Is there any other setting to check?

And, is this a setting that must be repeated manually for EACH TM?   Can this be set for all TMs?

Valeria Maria Tafel

ok... a few questions.

Valeria Maria Tafel said:

Is there any other setting to check?

Can we see a short sample of a file where the problem occurs?  Maybe reproduce the issue in Word with a couple of sentences and share that?

Valeria Maria Tafel said:

And, is this a setting that must be repeated manually for EACH TM?   Can this be set for all TMs?

Yes, it does have to be done for all TMs... at least if you are using a file-based TM.  If you are using Cloud Resources then these settings are actually a resource that can be used by all TMs:

There is a workaround for file-based TMs though using this applyTM Template from the appstore:

https://appstore.rws.com/language/app/applytm-template/966/

That will allow you to maintain a single language resource template and then apply this to as many TMs as you like in one go.

Here is a screenshot where you can see that the segments are separated after "nr." and "art.", which are listed in the abbreviations not to be considered for segmentation

and also after "S.p.A.", which is not listed, but it is not the end of the sentence, because the sentence continues, and this is not recognised.

Can you tell me why this happens?

My TMs are all file-based, I do not work online, so I will try to study the "workaround"...

Valeria Maria Tafel

I can’t help you with this example. If I recreate it I won’t have a problem. Please provide a sample file, even a couple of sentences, where you can reproduce this problem.

Paul, I don't understand: what do you mean by "providing a sample file"?

The source file is a normal Word where there is no interruption after "art." and the other abbreviations.

What do you need exactly?

Is this ok?

Is this ok?

Valeria Maria Tafel

Thank you.  I asked for the document example in case there were hidden tags in there, or maybe even a document format that forced the segmentation.  But based on what you have provided I can achieve this:

To do this I just added these to the Italian abbreviation list:

nr.
S.r.l.
dall'art.
S.p.A.

I couldn't just add art. because there is no space between the dall' and art. so it's seen as a word in its own right.

So I guess the next things to check given the more obvious ones didn't work for you either is what TM are you applying this to, what language in your TM are you applying this to and when are you adding them?

• it must be the TM you are actually using in your project and if you have multiple TMs it must be the one at the top of the list.
• it must be the Italian language as this is your source:
  
• I made these changes to my TM before creating my project so they could take effect when the sdlxliff segmentation is effected.

I have also attached my TM so you can try it.  Given this 100% works for me a failure to work for you might give us some indication where the problem lies:

it(IT) - en(GB).zip

Paul, you are really precious!
I did all the operations you suggested. I see that the abbreviations "art." and "nr." (not case sensitive, right?) are included by default in all TMs. However, I added "dall'art." and "dell'art.", "S.p.A." and "S.r.l.", for completeness. Then I re-upgraded the TMs, as suggested by Studio, and reprocessed the files.

I even re-created a new project and reprocessed the file, but it did not work. I keep getting the separated segments...

Can there be any other setting to check?

Valeria Maria Tafel

I think the only other explanation for this is that you are simply doing one or more of these two things:

1. you are not using the TM you think you are and have applied the settings to a different TM. Hover over your TM in your project settings and see what you used.  Make sure it's what you think you're using:
   
   
   OR
   
   
2. you simply don't have your TM activate when creating your project:
   

No, Paul... this was easy   I have been working with Trados for almost 30 years and, although I am not an expert in technicalities, I know that my TMs are enabled and activated.

For this specific job I was using 2 TMs (1 general TM for financial statements and 1 specific TM for this customer), both updated after upgrading

to Studio 2021 (and upgraded again yesterday after I checked and added the abbreviations as you taught me) and, in fact, they were both being

populated and regularly searchable while I was working... so all this is really strange.

Anyway, if there is no other setting to check, I will try and try with these ones. At least now I know where to look. Maybe one day this will be resolved.

THANK YOU!!!

Valeria Maria Tafel

Valeria Maria Tafel said:

For this specific job I was using 2 TMs

Did you add the abbreviations to both TMs or did you make sure the one you added was at the top of your list before creating your project?

Valeria Maria Tafel said:

Maybe one day this will be resolved.

Well.. I don't think we have anything to fix here.  Maybe, if you have some time tomorrow morning we can take a look remotely on a call as I'm really curious to know what the problem is here?  If this could work for you ca you send me an email? - pfilkin@rws.com

Have had similar issues - and discovered as Paul mentioned that it wass essential to ensure that the first file-based TM in the list also contains the customised abbreviations. I had set up a language resource for DE-EN (my pair) and was wondering why it wasn't having the desired effect.