The best (and for me the only) way to avoid ANY problems with fonts is simply NOT displaying any formatting, but only showing tags. This way the view in Studio will not affect any fonts due to font replacement in Windows, which is simply dumb and does not inform the user. If you use Adobe products, they will report any missing font, so you will be aware of possible problems and can react properly. Microsoft products like Word simply display text with a similar font installed on your system without even informing you. Studio does the same.

I usually use the Font Adaptation setting like this, because dealing with different font sizes and colors tires me out during translation:

Due to this, we only noticed that Trados Studio was displaying the source font size and color differently after the translation was finished and the target file saved.

I usually use the Font Adaptation setting like this, because dealing with different font sizes and colors tires me out during translation:

Due to this, we only noticed that Trados Studio was displaying the source font size and color differently after the translation was finished and the target file saved.

I am talking about a completely different phenomenon. This has nothing to do with font adaptation, which only limits the font sizes for the view in Studio Editor, but does not change the font displayed itself. What I mean is font substitution. Imagine the following situation: your customer is using a corporate font, lets say RWS Sans. You get a text in this font, open it in Word or PowerPoint and don't even notice, that RWS Sans is not installed on your system, as neither Word nor PP will tell you that. InDesign or other Adobe app would do, so you will at once notice that you don't have the necessary font and could ask the customer for it or do a proper replacement. Now you open such PPTX in Studio. It does not have access to RWS Sans, but uses a replacement font, let's say Arial. You translate and all is fine, as long you remain within the code page for RWS Sans. If that is an unicode font, it should work for all languages. But quite often fonts used are just ASCII or ANSI. And these do not support the target language. So when you add special characters which are not present in the font used, they will be displayed with again another font... To avoid all this simply do not display formatting in Studio. Then all text will be shown in Arial, but due to tags in the background in the target file the original font will be used.

In your case the translator simply did see the formatting, but did not notice, that it was applied locally and did not apply the final formatting to the translated segment... Would he/she view tags and have Studio set up not to ignore missing formatting (default setting in TAG Verifier), this would most probably not happen. The problem here is the lack of knowledge how formatting really works. People tend to rely on what they see instead of using the proper way of formatting, which in any CAT tool should be tags.

I understand what you are saying, Jerzy, and thank you for replying, but I'm not sure this was the case.

The original PowerPoint presentation used Calibri, which I believe is pretty standard.

And also it wasn't that the translator did not copy the tags. There were no formatting tags to copy (I changed my settings to display all formatting and tags and still nothing). And if you look at the screenshots in my original post, the source text has different formatting on both images, even though it's the same file on the same project.

It seems like a weird bug, as it happened just once.

In such case this is really weird. I am translating really many different formats and did not (yet) encounter such problem. Calibri is standard font, so there should't be any trouble with it.

A possible cause of the problems could be processing the file(s) either with an older version of Studio or even outside of it with one "so called" compatible tools. These can deliver proper results, but there is also a high possibility, that even a slightest error in processing may cause problems.

Lais Lewicki -  are you sure you cant send us a copy of the file. What if you did a find and replace so the content is obscured / encrypted. You know where you find a and replace with x. Likewise with any other character so the content as is will not be comprehended but the integrity of the document remains.