Greater than/Equal To Font Problem

[Ken_vw@adobeforums.com]

I just recently completed a fairly large brochure. On quite a few of the tech pages I used the special char's ? and ?. In all cased they show up in my doc with a pinkish background. I know that usually means a "missing" font. When I highlite it it tells me the exact font I'm usint (Hel Neue lite). It shows up fine while in full page view (cropped view) and in all my approval pdf's that were made, I supplied a Hi-res pdf for printing along with the "live" file to the printer. The Hi-Res pdf show the chars without any problem. THEY DIDN'T PRINT IN THE BROCHURE!!! I don't know which file the printer used for printing.
ID doesn't tell me there's anything missing. Now I'm involved in a new brochure using the same characters.

Can anyone tell me what's going on here??? Please help.

Thanks in advance. :-)

[Dave_Saunders@adobeforums.com]

It also means missing glyph. The "dreaded pinkness" should never be ignored. Check the Glyphs palette to see if the glyph is present for the font you're using.

Dave

[Ken_vw@adobeforums.com]

You're right Dave, it doesn't show up in the glyph palette. How do I add it??? I only started using ID about 2 months ago. Still gettn' used to it.

Thanks

[Dave_Saunders@adobeforums.com]

You can't add glyphs to a font unless you have a font editor. Better to switch those characters to a font that does have the glyphs.

Dave

[Klaus_Scharfenstein@adobeforums.com]

The »Helvetica Neue« has no ≤ or ≥, unless you have any Pro version of that font. When creating a PDF, those characters will be replaced by those from the font »Symbol«, I'd guess. Maybe that is what you should do within your brochure - the »Symbol« should be present on almost every Mac.

Klaus

[Ken_vw@adobeforums.com]

Thanks folks... I switched to the symbol font for the glyphs.
I must say though, I never had this problem with QX (fm 4 - 6.5). Produced many different catalogs and brochures without a hitch. Unless my printer took care of problems I didn't know I had!!!!

Thanks again.

Ken