In Studio 2021, Although "FIG." is set as an abbreviation in the segmentation rules (it's actually one of the presettings), all my English source segments are split after "FIG.". So why does this not work?

In Studio 2021, Although "FIG." is set as an abbreviation in the segmentation rules (it's actually one of the presettings), all my English source segments are split after "FIG.". So why does this not work?
is set as an abbreviation in the segmentation rules
I guess you mean is set as an abbreviation in the Language Resources.
I tool a random TM from mine, and I confirm I have 2 similar entries, fig. and Fig., but not FIG..
Coud you please confirm yu have FIG., capitalised like that and with the final period?
Yes, it's "FIG." (capitalized).
I have several TMs.
But whenever I create a project using a particular template with that particular TM, the "FIG." abbreviation is ignored.
Is that particular TM at the top? This is important, because only resouces (segmentation rules, variables, abbreviations) of the top TM are used.
Projects created with that template have only one TM that has the "FIG." abbreviation.
Is the FIG. abbreviation in the Source language? It needs to be there, regardless of Target settings. Could you confirm it’s like that?
Yes, it's in the source language.
Last thing, and I’m running out of ideas…
You need to Re-index the TM before new settings are really applied. After changing resources, always re-index the TM (or upgrade it). Then delete the old file from Studio and add it back again, so it’s re-segmented.
I’ve tested myself, with and without re-indexing, and it works as it should.
I tried. Same results. All segments are split after "FIG.". Very annoying!
This is such basic functionality there must be a more fundamental problem here. Please can you verify or comment on:
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
I actually solved the issue yesterday night. I had to create a new template from scratch with that TM.
I had been using the same template with that TM and was under the impression that any changes (such as editing the abbreviation list) to that TM are effective when using the template.
I actually solved the issue yesterday night. I had to create a new template from scratch with that TM.
I had been using the same template with that TM and was under the impression that any changes (such as editing the abbreviation list) to that TM are effective when using the template.