Preflight / incomplete font

Preflight reports a font is incomplete. After following steps to replace it, the message continues to appear as if i was still using the font in my file.
I'm not.
How do you make it go away?

Thanks for your response. After searching more closely I realized the font
was still in the file. It was a tiny element. I changed it to a different
typeface and I think my problem is solved.
Thanks again

Similar Messages

"Incomplete font" warning when packaging a file in InDesign CS5.5?

When I package a file, any fonts that appear with an "incomplete font" warning, are not collected. But these fonts aren't incomplete at all—I have installed them from the file that I purchased from Linotype (Helvetica Neue). Can someone please tell me how to make this warning go away and have InDesign recognise that the font is in fact complete?

"Helvetica Neue" ... are you working on a Mac?
I'm asking this because Mac OS X comes with a Helvetica Neue installed -- in fact it's part of the required System set. But Apple decided the font was not good enough as it was, and made a couple of changes to it to make it work "better", and in doing so they broke a couple of things that fonts need to get printed correctly. So everyone's advice is to steer well away from using the System version of Helvetica Neue on a Mac.
Which brings me back to your assertion
jowillis79 wrote:
I have installed them from the file that I purchased from Linotype (Helvetica Neue).
as I suggest you very carefully and thouroughly double- then triple-check that you are, in fact, using your own Helvetica Neue instead of the system one.

Web sites show incomplete fonts randomly in FF 5

Same video card, turned off all extensions and hardware acceleration but FF 5 still shows incomplete fonts on web pages randomly. Any fix ?

PERFECT. Many thanks for the prompt response.

InDesign CC / Cloud Fonts - Incomplete Font warning, does not export font when Packaging?

I'm using a new font from the creative cloud. I packaged my project and the fonts showed "incomplete fonts" and then didn't export the font, into the font folder, when packaging. There is an AdobeFnt15.lst file in the fonts folder, which I'm not sure about? If this is the case, how will I deliver my project to my printer when it is finished?

If you downloaded Typekit fonts from the Creative Cloud (the ones available from the Fonts menu in the Creative Cloud Desktop app), they are not packaged. They are only licensed to Creative Cloud subscribers or Typekit subscribers. They can be embedded in a PDF file or in an EPUB file or in a DPS project.
So you have two options: (1) Given the popularity of the Creative Cloud, your printer should have at least one CC subscription, then they can download the fonts you're using. In fact, it's a relatively automatic process and I describe in the linked blog post below; or (2) you can create a PDF file they can print from.
Here's an article on how it works:
Typekit Update in InDesign CC 9.2

InDesign CC package "Incomplete" font

Ever since upgrading to Windows 8.1 and InDesign CC the package function shows all non-system fonts as "Incomplete."
For example, Minion Pro Regular shows Filename: C:\Windows\Fonts\MinionPro-regular.otf and Status: OK however my activated Univers LT Std shows Filename: NA and Status: Incomplete
I use FontAgent Pro 4.1 (latest version) for font management. All fonts, aside from default Adobe/Windows system fonts are saved in the folder C:\Users\MyUserName\AppData\FontAgent Pro Data\FontAgent Pro\Libraries\Fonts. As far as I can tell this folder cannot be changed and is created by the program when importing fonts to your library. Previous versions of InDesign while running on Windows 7 packaged fine while activating fonts with FontAgent Pro, so not sure if this is a new incompatibility with Windows 8.1, InDesign CC or FontAgent Pro.
Any known solutions or work-arounds? Thanks for any help!

According to their web page, FAP 4.1 for Windows was updated to support Windows 7 and CS5 (and there are newer versions for Mac). I'd say they aren't too interested in Windows users at this point and if you want a font manager you need to look elsewhere.

Does an "incomplete font" warning make sense for ttf?

Hi all,
we are getting "font incomplete" errors in the package dialog. According to the online help this "Lists fonts that have a screen font on the current computer but not a corresponding printer font."
Does that even make sense for true types? As far as I know there is no such thing as a separate screen and printer font in ttf.
To make things worse the fonts in question are Georgia and Times New Roman - both are system fonts.
Specs:
Windows 7 64 bit SP1
InDesign 7.04
I can't reproduce this on my machine but that's running 32 bit.
Should we ignore it?
Any hints appreciated - tried a forum search but didn't find very much.
Regards,
Mike

There is no real erro message but a warning in the package dialog (sorry but we are using the German version):
The report doesn't offer much more information:
SCHRIFTARTEN
(Nur Probleme anzeigen)
17 Schriftart(en) verwendet; 0 fehlend, 10 eingebettet, 2 unvollst., 0 geschützt
- Name: Georgia; Typ: OpenType TrueType, Status: unvollst.
Dateiname: n. zutr.
Vollständiger Name: Georgia
Zuerst verwendet auf Seite: 31
Geschützt: Nein
- Name: TimesNewRomanPSMT; Typ: OpenType TrueType, Status: unvollst.
Dateiname: n. zutr.
Vollständiger Name: Times New Roman
Zuerst verwendet auf Seite: 30
Geschützt: Nein
We actually don't even know where TimesNewRoman comes from - I suspect it's in one of the numerous linked pdf files. But then the dialog should state which files they come from.

Book panel crashes IDcs4

On Mac (Leopard) after "book panel" preflighting and getting "black circle ?" on all id cs4 files I got incompletes for 4 fonts. Preflighting all "individual" id files, no incomplete fonts. During "book panel" preflight I opened Suitcase Fusion 2 and watched temp fonts blink on and off. I then turned on all needed fonts in Suitcase and de-activated id auto activation. Same "book panel" preflight incompletes font results. Now when I try to pdf from "book panel" it crashes id. Exporting to pdf works fine from inside "individual" id files, but as I have a 100 id files divided into 14 books, Acrobat merging individual id pdfs is a challenge. I've done the usual trouble shooting hoping to revive the book panel. Nothing works. I emailed extensis. They've yet to get back to me. Suggestions on fixing id book panels? Or a batch all-individual-id files for pdf option, possibly a free plugin or a script?

I can't reproduce this on my PC, so I'm wondering if it may have to do with the Mac interface. Are you using the Application Frame?
If you are, Id suggest you try rpealcing your prefs: Replace Your Preferences

PDF/A Conversion Err :CIDset in subset font is incomplete & Character references .notdef glyphs

I was trying to convert some PDF documents to PDF/A-3b. Using Acrobat XI Pro on a Windows Vista PC, the conversion proceeded fine, but I noticed the size of the converted file increased from 1.91 Mb to 16.8 Mb (See spage usage audits below). I expected some increase in size due to the font embedding and such, but did not expect such a big jump. On Auditing the space usage, I noticed that the converted file had no embedded fonts, but the vast majority of space was being consumed by images. Turns out the "Convert to PDF/A-3b" profile in Preflight settings were set to convert all pages to images, if the regular conversion failed. I edited the profile to not do so, but fail on an error. This time when I passed the document through a "Convert to PDF/A-3b" pre-flight, it failed with the following errors.
CIDset in subset font is incomplete (font contains glyphs that are not listed). It appears to be referring to the Arial and TimesNewRoman fonts.
Character references .notdef glyph
How do I fix these errors? For the CIDset error, I noticed some folks in the InDesign forums mentioning you can locate the missing glyphs and then replace the fonts with other fonts in which these glyphs are present. I am wondering if this is the issue here and something similar can be done in Acrobat. As for the .notdef glyphs, I couldn't find anything. Any help would be much appreciated.
Thanks,
Ron
Note:
If I edit the conversion preflight profile to allow replacing the pages with images on regular conversion errors, the conversion goes through fine, but as shown below, there is a huge jump in size, which I would like to avoid. I have about 2GB worth of documents, and the conversion ends up using over 8 GB of space.
Regular PDF
Archival Ready PDF (PDF/A-3b)

What software are you using to do OCR?
Is there a way you can adjust what font is being used by the OCR software or use a different software for OCR? This is not a standard OpenType font or one the can be mapped to Unicode.
I'm not sure exactly how OCR software places fonts in PDFs. Does it show up in the PDF Properties under Fonts? If so, what is the name of the Font.
When you examine the Tagged text in the Tags Panel, if you open up a tag and look at the content does it make sense or is it nonsense (gobbledygook)?
While OCR text is not visible to the end user directly, it can be selected using the text tool and it is recognized by Acrobat for tagging purposes. The Assistive Technology, e.g., screen reader. will be reading from this text. So if it is not understandable you do not have an accessible file.
You would probably obtain better results using the Acrobat OCR feature, preferably on a Windows machine. It's been a while since I've exchanged files between Mac and Windows, and I wouldn't trust that the encodings would be the same without testing it.

Do you have to outline fonts - PDF

Hi all,
I normally outline my fonts to avoid any hassles but I have created a design that has very thin type and when I outline it makes it too fat - bleh!
So I would like to know if it is ok just to save as a PDF WITHOUT outlining the fonts if you are sending a file off to magazine, newspaper, printer and that they will not have a problem with missing fonts etc.
Thanks!

ScottWeichert wrote:
Live fonts do contain hinting which is sent to the RIP. Outlines don't contain any hinting. Hinting is exceptionally helpful at smaller type sizes. Outlines are really not the same as live type.
Every glyph in a font is a drawn character. Hinting smoothes display appearance. It could play a role in a RIP for a digital press, which relies on composite output and no separate plates for each ink. These devices treat fonts differently from dumb art, to compensate for a lower resolution output.
Let's assume that hinting for a particular glyph alters the shape of the glyph at different type sizes. To test, put the glyph on the artboard at 100 pt, and again at 2 pt. Duplicate the glyphs to a layer on top and outline. Verify that the shape of the outlines match the live font (coloring the outline something different helps).
To see if hinting affects the shape,the small shape must be enlarged proportionally to the larger glyph size, or the larger glyph shrunk proportionally to the smaller size.
Doing this, you may find that the two shapes match, or perhaps they don't. But it doesn't matter either way. When you outline fonts on output, the font doesn't get outlined, then resized - it just gets outlined. And the outline should be true to the vector shape of the glyph, no matter what the size is.
There are many arguments for and against outlining fonts. Here are both perspectives:
Advantages of live fonts in PDF output:
1. The PDF looks worlds better on screen. This is an extremely important point. The live font looking proper means less questions and concerns, less banter is time saved.
2. The font being in the PDF means that changes to the PDF are possible. Many printers prefer the fonts to be embedded whole instead of subset, and certainly not outlined. This can be a time saver. It can come down to the printer having to do one of three things - make a simple text change, try to match an outlined font to make the change, or wait on a new file. If the printer has the embedded font, the job can go to press faster.
3. File size of PDF is smaller, making file transfer faster. It can be the difference between email or FTP in some cases.
4. If something goes awry with the font in output, a simple preflight of the PDF can detect the problem. If the fonts are all outlined, you can't preflight the fonts, there aren't any - you have to hope Illy did a good job making the outlines.
5. If the designer chooses to outline the native art, he has to save a duplicate copy. If he uses the flattener to outline fonts, he's increasing his output time. Preserving live text, you avoid these issues.
Advantages of outlined fonts in PDF output:
1. Fonts are the bane of the printing industry. There are thousands upon thousands of fonts, some are good quality, some are garbage. There are many varieties of font formats. Together this adds up to a LOT of variables, and a lot of different ways text can get hosed. When you outline, the font variable is eliminated in one fell swoop.
2. Some people - printers and designers alike - subscribe to the "bullet proof PDF" solution. Such a PDF is one that is completely normalized. It goes well beyond flattening transparency, or RGB and Spot – CMYK. It includes what AI calls expansion of art. All text is outlined. All strokes become fills. Any effects, patterns and symbols are converted to dumb art. Sometimes even gradients and blends are converted into images. Overprints can also be flattened (although AI cannot do this). The result is a PDF which is a complete mess from an editing standpoint, but less likely to wig out a RIP.
3. Even if the designer does not outline, there is a good chance the printer will. He will probably not do it in Illustrator, more than likely text outlining would be an automated part of a separate workflow system. For example in the packaging industry, PDF files are often imported into Art Pro, with vectorize text enabled. So in that case, a designer who outlines his text beforehand might be choosing Illustrator's outline capability, instead of relying on the printer's outline capability.
4. If the printer uses a vector trapping engine, any traps around text will be vector art, not fonts. Sometimes fonts mixed with vector traps can be problematic. Again if the printer feels like fonts are an issue, he's probably outlining the text before trapping.
5. File integrity is an issue for some designers. Maybe they're afraid that a competing designer might snag a PDF. If the fonts are all outlined, figuring out the fonts is certainly possible, but it's harder than simply pulling up the font list in Acrobat.
6. Some printers demand PDFs with all transparency flattened. If live fonts are retained in flattened PDFs, you can end up with live glyphs that are clipping masks for images. Such a configuration is similar to a live font in Photoshop output. Anyone who deals with fonts in Photoshop output knows that the construction is pretty hopeless (Photoshop can't even embed a complete font). It is best not to have live text playing the role of a clipping mask for contone data.
Anyway, there are two sides to the argument. One thing is certain – whether the text gets outlined or not – once it's RIPped, it's nothing but pixels. A live glyph vs. a vector shape should end up having the same pixel configuration on the plate.

Cant apply superscript or subscript on opentype font (mac snow leopard/CS4)

For some reason when I try to apply the subscript or superscipt (or any style) on CS4 using snow leopard it does not seems to work properly. For some fonts, it works for some characters (mostly numbers).
Is this an issue with incomplete fonts?

Opentype fonts is a set of characters and specifications...You mentioned right. Some opentype fonts can contain for example ligatures, glyphs or adittional specifications. Some open type fonts can contain subscript or superscript as glyphs, and others do not.
To paracially solve your problem, have you already tried to set a "faux" subscript or superscript?
Gustavo..

Problem w/Optima font when exported to pdf from indesign

I'm having a problem exporting files to pdf format with the optima font. It looks okay in indesign (preflight reports font status as okay)
but when I open pdf it is misformatted. I changed it to another font but would really like to use optima. Has anyone else run into this problem and how did you solve it?
Thanks

Thanks Michael,
New to forums and having a little trouble finding my way around. I reposted
on ID forum Optima file is from Adobe and is ps file.
Thanks for your help.

Need to edit a form that was created by someone else.

Hello, I have to edit a form that was created by someone else. I made numerous changes to the text and repositioned a lot of the items, and it appeared fine on my computer. However, when I open it on my PC and other systems, the fonts are substituting and I'm getting strange characters where I changed the text. I tried embedding the fonts with the Preflight embed fonts, but it is still messed up. My client is anxious...not sure what else to check. Any help would be appreciated!

You don't need to re-do the fields. If you create a new version of the PDF
file just open the old one and use the Replace Pages command to insert the
pages from the new version over the old ones. This will give you a new
version of the file, with the existing form fields still in tact. Of
course, you might need to adjust their location and/or size, but at least
you won't have to start all over again...
On Thu, Jan 22, 2015 at 11:59 PM, Laura Holancin <[email protected]>

Dreamweaver CS6 is not displaying Helvetica i's correctly?

I have a very weird problem with Dreamweaver, and I really need this cleared up as soon as possible. For my webpage, I am using Helvetica font, but there's one problem, the lower case i's are displaying as uppercase i's when bolded. I have no clue why it is doing this, seeing as the i's function just fine in Fireworks. I should note that they also display as capitals in the browser, which can make certain words look utterly terrible. All help on this subject would be greatly appreciated, thank you.

BarakObi wrote:
A corrupted font to me means corrupted file and so it should not load at all.
Not necessarily. Corrupted could mean an incomplete font library. Fonts typically have several files in them:
uppercase normal,
lowercase normal,
uppercase bold,
lowercase bold,
uppercase italic,
lowercase italic.
Applying bold and watching it change from lower to uppercase tells me the lowercase bold file is missing or corrupted in some way.
Nancy O.

CS3 Preflight: Font incomplete

Do any of you know hat it means when preflight says there are no missing or embedded fonts, but one is incomplete?
A colleague just called to ask, and I didn't know, though I thought perhaps it meant the printer half or a T! font is missing, though there was no indication that was the case when she checked in (I think) Font Book. The font is Book Antiqua and T1, OS X 10.4.?.
Exported PDF showed "dots" where the font should be. Substituting the TT version seems to have solved the problem, but I'd like toknow what it is.
Peter

That's what she said. I'd be inclined to think that perhaps the printer half is completely missing, or it doesn't match the screen font for version or soemthing like that (I should have looked this up myself, but I'm having some issues trying to to run check disk on a laptop drive I pulled from a client machine that wouldn't boot, and every time I look at things sideways it quits and I have to restart, thought it ssems to have stabilized at this point).

Getting an error when running Preflight to embed fonts in Acrobat Pro version 9

I am running Acrobat Pro version 9.4.5 and when I am running a pre-flight for embedding fonts in my document I am getting an error message as follow: "
An unexpected error has occurred during the Fixup process ".
This is occuring at the font processing time. Anybody encountered the same issue.
One detail which has it importance, I am using TTF fonts and some specific Adobe fonts which are located in the Resource\font directory of my workstation.
Many thanks for your help.

Check all your fonts have headers that permit embedding - some commercial fonts don't. Debugging in Preflight is a nightmare, so to find the problem you may have to try the fonts one at a time against a test document until you find the one that whimpers.

Preflight / incomplete font

Similar Messages

Maybe you are looking for