Please use the option "Show all tags but do not show formatting" from File -> Options -> Editor.
The reason is quite simple: InDesign uses a font not present in your system. While InDesign will inform you and suggest replacing the font or ignoring the message, Studio (like all other Office apps by Microsoft) is stupid enough NOT to warn, but just to substitute the font by something what it considers to be similar. This causes only trouble and should at least result in a warning to the user. But when you switch off the formatting nonsense in Studio, all text will be shown in Arial and no formatting problems will occur.

Hi Jerzy! Thank you for your reply.

Unfortunately your suggestion did not help. Yes, now the formatting is not shown in the editor while translating. The font that should not be there in the target file (because it wasn't in the source file) is still there though.

All text has the correct font - the wrong font is used somewhere in the non-translatable content.

This is indeed strange... Unfortunately, I cannot tell you more without seeing the files. Until now I have never seen Studio adding a font specification somewhere.

Hi Jerzy,

I thought I'd added the files to my initial question but I cannot see them anymore - strange. I can send them over if you give me your details!

Jerzy Czopik, Marion Hartmann

Jerzy, I think the "Show this or that" in the editor has nothing to do with formatting written into the file, it's just for the editor. And it is useful if the document is using a font the translator does not have, so that something legible is being displayed.

There is something called "font mapping", which is defined in the file type, which changes the output font. This is not usually used when translating from one western language to another - it is necessary when translating EN->KO or the like. For each font in the source you can define which font should be used in the target. I would surely check this if you have such a puzzling problem.

Other than that, styles in InDesign can be very tricky to handle. Are you sure, sure, sure that this Minion Pro font is never defined (not taling about used) in the source files? That there is not a space or a tab or a line break which is in that font?

That Studio would add a random font is just too hard to believe.

Daniel

Hi Daniel! Thanks for your reply.

Exactly, the editor settings only relate to how the text is displayed during translation.

I checked the font mapping sections and they don't apply here as we are only translating into European languages.

To be honest, I could not believe it myself at first because surely a CAT tool is not supposed to act this way. But it is the only conclusion I was able to reach with various tests (see described above - if the source would have used the font, it would generate the same error message).

According to my DTP people (because I don't have InDesign and can't verify it myself), after translation the target file contains an empty table that is formatted in Minion Pro. I have no idea why that empty table changes formatting.

Marion Hartmann

Would be interesting to see both the source and the target file. IDML is pretty accessible, you can peek in to see what's going on, unlike INDD.

Daniel

I must disappoint you. Showing formatting and allowing any application to substitute fonts with something different leads to problems in target file. Imagine you have a font in your document, which is not present on your system. You translate into Polish, so you use diacritics. Studio uses a different font for replacing the one used in document. The font in your document does NOT support Polish diacritics and in the end of the day your target file contains a mix of either wrong diacritics or even fonts, because (what I have seen happening) Studio would use one font for replacing the Latin letters and another font for Polish letters.

You can simply experiment with bold formatting. When you show formatting and use the "Bold" button from the ribbon bar, InDesign will most certainly report a non-existing font when reimporting the document.

I must disappoint you. Showing formatting and allowing any application to substitute fonts with something different leads to problems in target file. Imagine you have a font in your document, which is not present on your system. You translate into Polish, so you use diacritics. Studio uses a different font for replacing the one used in document. The font in your document does NOT support Polish diacritics and in the end of the day your target file contains a mix of either wrong diacritics or even fonts, because (what I have seen happening) Studio would use one font for replacing the Latin letters and another font for Polish letters.

You can simply experiment with bold formatting. When you show formatting and use the "Bold" button from the ribbon bar, InDesign will most certainly report a non-existing font when reimporting the document.