Special characters are missing in the target translation

I encountered a very strange issue while handling a MS Word file with special characters, and they are all missing in the generated target translation.

My Trados Studio version is 2015 SR2 (12.2.5195.7) after applying update of Studio-KB9268-7.

Here I also attached a sample file for your investigation, thank you.

It's very urgent since there are a lot of such special characters spreaded in the source file, any workaround is appreaciated.

special-char.docx

Parents
  • Hi Xiang Li, hi Paul,

    It isn't the whole font (Cambria Math) but these specific characters of the Cambria Math font that are causing the issue. I can't render them in this window, Word can but this window doesn't pick them up enough to upload them to this post. Here's an image of the 4 characters that are misbehaving:

    If one creates a document entirely written in Cambria Math and inserts these symbols manually from the Insert > Symbol list, Cambria Math (extended characters - plane 1), they are still not retained and converted to SDLXLIFF, thus it is not an authorship issue.

    There are various cases online where Cambria Math extended characters subset, unicode plane 1, has caused problems in Microsoft Office when writing equations. Their suggestions included running an online repair of Office or changing the default Windows font for Microsoft Office equations to a different font and working with that. It's not possible to change these characters in the file to a different font, they need to be found in a different font via Insert > Symbol and added manually. Or added in Studio via the Advanced tab > Insert symbol, searching for them by trial and error. Not a sensible option unless there are only a few offending characters.

    I used to get a lot of trouble with fonts that were custom-made by a particular client for their DTP documents and were 'buggy', usually because they had been incorrectly put together at a lower level, which is what this sounds like too. As they're all visually in italics I'm guessing that the italic property (maybe?) of these characters is not properly supported by the actual font properties. Word can render them correctly but Studio needs more info than Word is giving to detect the character property. How one gets around this except by manually finding and replacing the characters with ones that work, I don't know.

    What a pain!

    Ali

Reply
  • Hi Xiang Li, hi Paul,

    It isn't the whole font (Cambria Math) but these specific characters of the Cambria Math font that are causing the issue. I can't render them in this window, Word can but this window doesn't pick them up enough to upload them to this post. Here's an image of the 4 characters that are misbehaving:

    If one creates a document entirely written in Cambria Math and inserts these symbols manually from the Insert > Symbol list, Cambria Math (extended characters - plane 1), they are still not retained and converted to SDLXLIFF, thus it is not an authorship issue.

    There are various cases online where Cambria Math extended characters subset, unicode plane 1, has caused problems in Microsoft Office when writing equations. Their suggestions included running an online repair of Office or changing the default Windows font for Microsoft Office equations to a different font and working with that. It's not possible to change these characters in the file to a different font, they need to be found in a different font via Insert > Symbol and added manually. Or added in Studio via the Advanced tab > Insert symbol, searching for them by trial and error. Not a sensible option unless there are only a few offending characters.

    I used to get a lot of trouble with fonts that were custom-made by a particular client for their DTP documents and were 'buggy', usually because they had been incorrectly put together at a lower level, which is what this sounds like too. As they're all visually in italics I'm guessing that the italic property (maybe?) of these characters is not properly supported by the actual font properties. Word can render them correctly but Studio needs more info than Word is giving to detect the character property. How one gets around this except by manually finding and replacing the characters with ones that work, I don't know.

    What a pain!

    Ali

Children
No Data