first it's funny that after 2 month someone is answering... I already thought that none is interested in a solution
From my side there was no really interest to write this Applescript because I've added the "logic" in one of my extras which will export just a whole bunch of pages at one time.
In the mean time I've experienced that I shouldn't apply the above fix for Windings. And perhaps all other fonts which have a "custom" character mapping. Because I'm not the Postscript guru I really don't know what the fix above will do (I've my thoughts but that doesn't really matter). I can only say that it worked for me with the Files I had to export.
So first we need someone who can explain what is going wrong in FH MX 11.02 and how it should fixed in a good manor.
And second we don't find this guy we need a whole bunch of files which we can compare so it becomes more clear which fonts go wrong.
For me, I'm currently working with MX11.02 with 10.6.8 in an VM-Ware image. Starting with FontagentPro and not getting all fonts everytime, I'm currently throwing all fonts in my users font folder which gave me the best results. And if some font doesn't appear I use the font finagler and restart the VM which is really fast.
For the Export itself my Workflow ist the following:
- Export as EPS without including fonts (by my extra which will fix the font problem). Others have to use the not existing Applescript or try it manually with Textedit)
- use Adobe Distiller 8 in the VM to generate a PDF
- transfer the PDF for further use to the Yosemite side of my Mac
So far, if anyone has questions or an idea how to do it better: just write