Click to See Complete Forum and Search --> : Preflight font problems
smashmiester
01-19-2007, 05:38 PM
Good day all.
I seem to be having some issues when I preflight stuff from InDesign CS2. I switched all my programs from my G5 to my macBook Pro, but when I preflight files I get this message before it finishes.
The printer then has problems opening the fonts - apparently a portion of the file is missing.
I have never had this problem before, and they are all standard fonts that came with the MacBook, and I paid for my copy of CS2.
Any ideas?
D-Frag
01-19-2007, 05:44 PM
that font alert comes up with every file, so thats not what the issue is. try packaging your files File>package and read through the font list and look for any of the little yellow warning tags associated with that particular font. if you are having font issues, the packaging feature in ID will notify you about it.
smashmiester
01-19-2007, 07:09 PM
They are all good. No little yellow warnings. Hrm...
budafist
01-19-2007, 08:12 PM
Yup, the font alert comes up all the time. It's just to cover their asses.
Does the printer have trouble opening the fonts or opening the the file?
Convert to outlines perhaps? Good for a couple pages, not for heaps though.
D-Frag
01-19-2007, 08:22 PM
talk to your printer, i would suggest giving them a packaged ID file, that way they have all the fonts. I would also supply them with a postscript file to there specs, and also a press quality PDF for proofing. if you send all that, it will cover all of your steps on your end to ensure no problems.
doubting_thomas
01-19-2007, 11:46 PM
The printer then has problems opening the fonts - apparently a portion of the file is missing.
Any ideas?
That sounds odd. Are you Stuffing them? Zipping them? When somebody says
this I start to wonder if a Mac font is losing a resource or data fork (forget which
it happens to), in the compression/archiving process. It may be a figure of speech,
but might be worth looking at (it could be them damaging the fonts once they
get them too). That warning box should have nothing to do with it.
urstwile
01-20-2007, 02:26 AM
I'm wondering if this is a bug with CS2 apps on MacBook Pro's.
Have you tried it on the G5?
Harry
01-21-2007, 09:37 PM
I get that error on Indesign CS2 aswell (using a pc), I get it when i am exporting the file as a .pdf.
Is this because a font problem or my pc ?
When you switched over from the G5 - did any old fonts on your system get copied over - unknowingly? An old or unlicensed font could have been hanging around from a previous job, or embedded in a customer file. The Mac OS can find fonts anywhere...some shops keep Acrobat 4.0 to get around this very issue. The licensing capability came after 4.0.
Did you try to re-install the base fonts on your new Mac? How about searching for all instances of those families - might be a duplicate named slightly different?
doubting_thomas
01-23-2007, 03:59 PM
I get that error on Indesign CS2 aswell (using a pc), I get it when i am exporting the file as a .pdf. Is this because a font problem or my pc ?
Which error? I'm not seeing any errors in this thread. If you're getting an error
about fonts when Exporting a PDF, could you explain in more detail what it is,
or what it says? Or am I just blind?
smashmiester
01-24-2007, 01:44 AM
I didn't transfer anything over from my GF to my MacBook Pro.
I am beginning to think that it was just that printer even thogh they are a HUGE print-house. At first we thought there was a problem when I stuffed the file, so I sent it unstuffed, but it was the same thing. The guy told me that there should be 2 parts to the font file, and mine onlt had one. We ended up sending him Impact and Century Gothic from a Windows PC. Go figure...
I just sent another file off to print using just 1 of the fonts that I was having problems with "Century Gothic" and everything seems to be going fine with this new place.
smashmiester
01-24-2007, 01:46 AM
talk to your printer, i would suggest giving them a packaged ID file, that way they have all the fonts. I would also supply them with a postscript file to there specs, and also a press quality PDF for proofing. if you send all that, it will cover all of your steps on your end to ensure no problems.
How do a Packaged ID file? I always send a press PDF with my files just inacsed... one of the things tmy proff. instilled in me in college.
urstwile
01-24-2007, 01:49 AM
It's gonna depend on whether the font format is TrueType or Postscript. TrueType fonts contain all the necessary information in one file, whereas Postscript fonts have a screen font and printer font that must both be sent, and which must reside in the same folder in order to work correctly.
PrintDriver
01-24-2007, 02:50 AM
His fonts listed in post #3 both say Truetype. So it isn't missing a part unless it's a messed up data fork or the suitcase is empty.
urstwile
01-24-2007, 07:08 AM
Yup, you're right, PD, I missed that. :o
Harry
01-24-2007, 08:30 AM
This is the error i get, i can still go on with making the .PDF but it still annoys me because everytime i want to create a .PDF the same sort of error comes up.
doubting_thomas
01-24-2007, 04:18 PM
This is the error i get, i can still go on with making the .PDF but it still annoys me because everytime i want to create a .PDF the same sort of error comes up.
Do you have the correct version of Univers installed? If I recall that's one of
those fonts that have multiple versions running around that're named the
same. You should be able to Find Font and see the activated font in the
drop down menu when in that dialog box. If not, then it's either not installed
correctly, not being seen by InDesign, not being correctly activated by whatever
font manager you're using, being diabled by a conflict at the OS or application
level, corrupt... you get the idea. A tricky work around if none of the above are
the case is to throw the font into C:\Program Files\Adobe\Adobe Indesign CS2\
Fonts folder and restart the application. I don't recommend it, but it can work.
smashmiester
01-24-2007, 06:39 PM
His fonts listed in post #3 both say Truetype. So it isn't missing a part unless it's a messed up data fork or the suitcase is empty.
I am a SHE and everything seems to be going OK with this printer. I am still confused about the last printer we had. HMMMM....