Nicholas Knutsen 

Go to File -> Options -> Editor -> AutoCorrect and check the settings for your target language.

Thanks for your reply. I have nothing checked under Autocorrect. There is nothing there that would make these replacements anyway.

Sorry I wasn't more accurate. My version: Trados Studio 2022 SR2 - 17.2.11.19134

I'm on Windows 11 23H2.

Yeah, I'm curious if anyone else can reproduce this by using the small file I posted above and choosing "Show all formatting and tags".

Nicholas Knutsen 

I just wanted to try but the file isn't available.

Nicholas Knutsen 

Unfortunately. when I click the link, I get the "not found" message. Maybe you could attach the file here in the forum. Use the "Insert" command, which you can find at the bottom of the message box when answering.

Sorry about the wrong link. I'm not able to insert any file here (I get "invalid URL"). But here is a functioning link: madforest.com/test.xlsx

Sorry about that. This should work: madforest.com/test.xlsx

Nicholas Knutsen 

Thank you for the file. This is indeed very astonishing, as when I define Polish as target and simply copy source to target I get the ligature "ti" shown (we do not have such ligatures in our language). However, the target text copied and pasted here is "til". The font in your file is Calibri. After changing the font to Arial, NO ligature is generated. Obviously, I changed the view to show formatting and no tags before. So for me the problem is really connected to this setting and the way Trados Studio shows the font Calibri...

Nicholas Knutsen 

I can repro the issue in 2022 and 2024 with Show all formatting and tags. Interestingly, there are no ligatures in the Workseet name:

And it works fine if I change the font to Times New Roman in the Excel file. I bet the issue is only with san serif fonts, such as the Calibri.

Yes, it's the font. However, Calibri is not the only font with such ligatures "embedded".

To be clear, it's not just when showing formatting and no tags; it's also when show formatting and tags. The only way to get rid of it is to choose tags but no formating.

Nicholas Knutsen 

Showing formatting (with or without tags makes no difference) means using the font from the source file, the font size and other font attributes from there. In case the font is available, it will be used directly. If the font from the source file is not available, a substitute font will be used without any warning. Exactly as in all MS Office applications. This is not good IMO, as no user is then aware of using a substitute font, making the layout in fact corrupt. I would expect any application to warn the user about missing fonts, like Adobe apps do. Unfortunately, MS seems not to care about his at all.

Possible solution for you: change the font in your source file to Arial prior to translation and replace it back with the original font after the translation.

That's a good suggestion. I think that will usually be what I will do from now on. Only when the source file have several different fonts will it be a problem, but that's usually not the case.

I don't see the problem with the font being substituted by Studio, since the translated output will still use the original font. It only has to do with how it's displayed in the editor, nothing else.

Another thing: It is a "feature" of the font (Calibri in this case) that it has these ligatures. Excel does not use them, but Word does. However, Word does so in the correct way: Ligatures are automatically replaced, but they still act as two letters, meaning you can delete one of the letters, and you can type inbetween them. Studio does it in the wrong way.

That's a good suggestion. I think that will usually be what I will do from now on. Only when the source file have several different fonts will it be a problem, but that's usually not the case.

I don't see the problem with the font being substituted by Studio, since the translated output will still use the original font. It only has to do with how it's displayed in the editor, nothing else.

Another thing: It is a "feature" of the font (Calibri in this case) that it has these ligatures. Excel does not use them, but Word does. However, Word does so in the correct way: Ligatures are automatically replaced, but they still act as two letters, meaning you can delete one of the letters, and you can type inbetween them. Studio does it in the wrong way.

Nicholas Knutsen 

Nicholas Knutsen said:

Excel does not use them, but Word does. However, Word does so in the correct way: Ligatures are automatically replaced, but they still act as two letters

Correct, and ligatures can be disabled in Word here:

Nicholas Knutsen said:

I don't see the problem with the font being substituted by Studio, since the translated output will still use the original font. It only has to do with how it's displayed in the editor, nothing else.

Well, it will, if the encoding fits. Will not in languages like Polish or other languages outside of ANSI/ASCII.