Hello Ingrid Gosch ,

It would be good to hear from other users, if and how they have been able to bypass this issue.

Although MS 2013 still supports the font 'Arial Unicode MS'

MS dropped the format with the releases of Office 365/2016 as the many MS forums confirm.

Hello Ingrid Gosch ,

Could you post the full error stacks please-

This might shed some light on whether the werrors are related or something else that needs to be looked at.

Do you get the same errors if you use a different document (create a test document using a standard Arial font)?

Hello Steven,

Thanks again for your help. I tried the translation of a similar document (EU Regulation from 2015), and there was no problem with the footnotes. Strangely enough my client sees the footnotes in the problematic text in previous Studio versions. I will have to ask for new text and sdlxliff versions but I will wait until I have installed Windows 2013. Fortunately I can do the translation and somehow copy+paste the footnote numbers.

Unfortunately I don't recognise your screenshot - how do I get there? The error message I see is "Tag fn<id=20"/> entfernt" (= removed).

Before Christmas I sent a screenshot of what I see (the missing footnotes and the Overflow Exception warning) to a colleague of yours. I don't find it, but it isn't that important now.

Best regards, and thanks again

Ingrid

Hello Steven,

Thanks again for your help. I tried the translation of a similar document (EU Regulation from 2015), and there was no problem with the footnotes. Strangely enough my client sees the footnotes in the problematic text in previous Studio versions. I will have to ask for new text and sdlxliff versions but I will wait until I have installed Windows 2013. Fortunately I can do the translation and somehow copy+paste the footnote numbers.

Unfortunately I don't recognise your screenshot - how do I get there? The error message I see is "Tag fn<id=20"/> entfernt" (= removed).

Before Christmas I sent a screenshot of what I see (the missing footnotes and the Overflow Exception warning) to a colleague of yours. I don't find it, but it isn't that important now.

Best regards, and thanks again

Ingrid