Line width in imported graphics slightly diminishing in FMgenerated PDFs

[Dov Isaacs]

FrameMaker does not officially or fully support import
of Adobe Illustrator files directly into FrameMaker
documents.

It only "works" when Illustrator files are saved with
the "create PDF compatible file" option. In that case,
FrameMaker "sees" the .AI file as a .PDF file and 
CONVERTS the PDF portion to .EPS internally. That is
probably where the "problem" is occurring. If you created
a .AI file without that PDF option, the import would fail
as it would if you tried importing a .AI file from 
earlier versions of Illustrator that had formats that
didn't look like a PDF file internally.

I MOST STRONGLY RECOMMEND AGAINST ATTEMPTS TO IMPORT
.AI FILES DIRECTLY INTO FRAMEMAKER. Use .EPS and tell
your customer that this is the recommendation from
Adobe.

	- Dov 


 

> -----Original Message-----
> From: frameusers.com On Behalf Of Yosuke Ichikawa
> Sent: Wednesday, March 08, 2006 11:11 PM
> To: framers at FrameUsers.com
> Subject: Re: Line width in imported graphics slightly 
> diminishing in FMgenerated PDFs
> 
> Dov,
> 
> Thank you for your comments. I wanted to be accurate, and I 
> checked with our DTP person to tell me exactly what the 
> matter was; in fact, we were having Acrobat Preflight 
> problems with **.ai** files.
> 
> There were NO problems with **.eps** files (yes, they are 
> imported as eps, and they do not have borders.) I'm very 
> sorry for the mistake in my initial report.
> 
> To put it straight;
> - The graphics are .ai files with minimum line width of 0.2 pts. 
> - The PDFs of these graphics created by Illustrator do not 
> have problems when checked by Acrobat Preflight for lines 
> less than 0.2 pts. 
> - When these .ai graphics are imported to a FM doc and a PDF 
> is created by FM, this PDF does have a problem with Acrobat Preflight.
> - We also tested the same graphics saved as .eps. Neither the 
> standalone graphics nor FM docs had problems with Preflight 
> in this case.
> 
> Depending on the Acrobat version, that is. We found out that 
> this problem happens when we use Acrobat Windows versions 
> 6.0.1 to 6.0.4, but NOT in 6.0.0. I ran the preflight check 
> myself against the same PDF files, first reinstalling and 
> then updating Acrobat, so I'm sure of this. 
> 
> Our DTP person tested it on Macintosh Acrobat 6.0.0 and 
> 6.0.4, and he got similar results; i.e., no problems in 
> 6.0.0; .ai graphics imported in FM is reported as an error, 
> but not the others, in 6.0.4.
> 
> So using .eps instead of .ai would be a solution, but for 
> reasons I'm not familiar with, our client has specified using 
> .ai files instead of .eps for these particular projects, 
> whose final output is HTML converted via WWP, by the way.
> 
> 
> Yosuke
>