I'm tired of waiting when FH will become fully compatible for postscript printing.

As a Win user I used to work with FH since version 3 (there was no "Registration" swatch there) and I liked it very much for it's path editing tools. However, can anyone explain what's the point of using three (???) encoding options - ASCII, Binary(Macintosh) and Binary(Cross-platform) when they do just the same - an ASCII-coded .ps file (talking of Windows versions). A simple example - page with imported cmyk tif, printed to PS printer on file has the same file size, let say 30 Mb, no matter which encode option you choose. The same cmyk tif printed from Illustrator produce two different sized .ps files - ASCII-coded 30 Mb and Binary-coded 16 Mb.

I was waiting every new version of FH with hope things will change for better. No hopes anymore...

Now I'm using Acrobat to prepare separation files for printing house and I was thinking this could solve the problem. Yes and No. Yes - the file sizes (from FH and Illustrator) now are nearly equal, files are RIP-ed succesfully. And No - the RIP-ed separations from FH are all at 45 degrees instead applied 15-75-0-45. My Acrobat joboptions are with "Preserve halftone information" option on and there are no such problems with other apps. Now if I decide to prepare separation files from FH, I have to tell my printing house to override "my angles". Boring and unprofessional.

Why all this happened to my loved once FreeHand?

Boyan Mladenov