🚀 go-pugleaf

Dave, that is an interesting method, if it worked, but it doesn't seem to work for me...

The documents were in FM7 (from the translation agency), with regional fonts I think. Then they were opened in FM8. But no Unicode!

I just tried now, in FM8, with a document that had text in DIN Greek, then saved as FM7 format, then opened again in FM8. The characters were preserved as non-unicode in the original font.

Currently, on this computer, I do not have FM7, and I am not at the client who had the troublesome documents, so I can not test with "native FM7", but I might do that when I come back to the client in a few weeks or so.

But since you got it to work, I wonder what the difference is?

In the original post, I said that Trados is not compatible with FM 8, since that is what the translation agency said. Turns out, however, that the translation agency had not kept their systems up to date! Shame on them! I've had some further communication with Mats Broberg (see post above) that further clarifies that an updated and properly "patched" Trados is indeed compatible with FM8, both structured and unstructured. (The translation agency now claim they have a working unicode flow for FM8, but it is definitely "a bit late" -- the non-unicode documents are already done, so the failure can not be easily reversed!)