Adobe Postscript Fonts and Fontbook

Many years ago, using Mac OS7, I bought some Adobe Postscript fonts and I was using Extensis Suitcase to manage the fonts. Now, I want to add some of those old fonts to my Mac Pro using Tiger 10.4.11 and Fontbook. Is there a way to get those fonts where I can use them in Fontbook? They won't open except in Suitcase - an application I haven't used in years and I no longer have. I have my old serial number but it won't accept it to open the fonts.
So, the question is: How can I use these fonts today? Is there a way? Anybody?
Thanks.

I have my old serial number but it won't accept it to open the fonts.
This number is to unlock an old Font Folio disk you purchased from Adobe? It may not work to unlock the disk because if it's that old (purchased around the same time as System 7), it would require Classic to run, which your new Macs can't do. You'll have to contact Adobe about that. I'm guessing their only solution would be to have you upgrade to Font Folio 11's OpenType fonts. But that's going to cost you full price anyway. Don't count on them to give you an alternative way to open that old disk. But it can't hurt to ask.
This is confusing. First you say:
They won't open except in Suitcase - an application I haven't used in years and I no longer have.
Then follow it later with:
Somehow Suitcase is holding them hostage where they can only be opened and used with Suitcase.
Are you, or are you not using Suitcase on your current Macs?
I'm going to guess though what your meaning is.
If your saying you DO have Suitcase on your new Macs, they have nothing to do with Font Book not being able to open the fonts. Both are font managers. Nothing more. If they open in Suitcase, but won't in Font Book, then there's something wrong with Font Book.
If you mean you DON'T have Suitcase on your current Macs, then the old version of Suitcase you previously used has absolutely nothing to do with being able, or not able to open fonts with Font Book. Again, they're both just font managers. They open and close fonts when you tell them to, that's it. They have no special ties to your fonts in any manner.
Is any of this true?
Type 1 PostScript fonts are a set. One file is a suitcase containing all of the low res bitmap screen fonts. The rest are the outline printer fonts. As an example, here's Adobe Garamond.
Adobe Garamond
AGarBol
AGarBolIta
AGarIta
AGarReg
AGarSem
AGarSemIta
The first file which I highlighted in green is the font suitcase of bitmap screen fonts. The rest are the outline printer fonts.
1) The files for a Type 1 PostScript font must have both the screen and printer fonts for a given set in order to work. They also must be in the same folder.
2) The suitcase of bitmap fonts will work alone, but output will be terrible since the system will print the fonts using the 72 dpi screen fonts in the suitcase if the outline portions are missing.
3) Having only the outline fonts will not work. You will get exactly what you are having problems with. You can see the fonts, but they will not load. That's not a problem with Font Book, Suitcase or other font manager. None of them, nor the system itself will load outline fonts from a Type 1 PostScript font without the matching suitcase of screen fonts present.
So are you simply missing the screen font suitcase for those outline fonts that Font Book can't open? If so, that's normal. You must have both in the same folder.

Similar Messages

Adobe Postscript Fonts on new iMac?

Hi,
I'm thinking of getting one of the new iMacs. But I wonder, I have some Adobe Postscript Fonts that I use with my G5 Mac; will they work with a new iMac?
Patrick

Fonts aren't dependent on a specific processor architecture to work; if they will work on one Mac OS X machine, they will work on another. Some Mac OS 9 fonts may not work in Mac OS X.
(23604)

Postscript fonts and MacBook Pro

When I had my 1.67 Powerbook, I often used an Apple Postcript font family -- ITC Garamond. When I install it on my Intel 15" MacBook Pro, however, within a short time it causes Word to hang during any save, crashes my other apps running at the time, and then when I force quit, sometimes causes the computer to forget most of the installed fonts until I restart. Happens over and over. I had hoped that 10.4.7 might fix this issue, but it still is happening. I thought OSX was supposed to run just about any fonts, and that the Intel switch didn't affect font functionality?
MacBook Pro 2Ghz Mac OS X (10.4.6)
MacBook Pro 2Ghz Mac OS X (10.4.6)

I get the same problem.
I have access (via work) to the entire Adobe OTF library. Any of those fonts that I use on the MBP + Word 2004 Mac combo = freeze on save.
I know the fonts are fine because fontbook authenticates them.
Also, Pages 2 (I'm using the trial version but I will be buying once I get back from vacation) plays very nice with the OTF fonts. To the point where it can use the ligatures (automatically) that MS Word doesn't like to at all--at least the Mac version. On PC you can use ligatures by inserting them as characters which plays havoc on spellcheck (since Word thinks it is a misspelled word). Pages 2 automatically uses the proper ligatures (if you set it) and can undo it at the click of a button.
The Word freeze + the Pages 2 ability to auto recognize when ligatures should be used (plus Pages' ability to export to Word and PDF without plugins) make it my word processing program of choice now for Mac.
Of course I'd like a working version of Word that plays nice with the OTF fonts because Word does do a better job of autocorrecting mistakes than Pages does. Ideally I'd like to do all of my WP on Word, then import into Pages and auto-insert the ligatures.
I have a feeling it's a bug w/ MS. Maybe the universal binary version of Office will fix it...

Postscript fonts and OSX 10.6 not working ..?

I've just helped a friend upgrade their new mac book pro to OSX 10.6 snow leopard, and found that a lot of fonts are now not working? (I use an imac running 10.5.8 which runs them all fine)
Some fonts I have managed to fix by just adding .otf or .ttf according to font maker, (open type etc) which seems to work ok... but I am having a nightmare with many others like postscript ones.
Can any one suggest what to do to fix this, as I dread upgrading to OSX 10.6 if it means we lose fonts! I'm not sure what apple are up to, but they seem to have overloked the problems casued by their in-build helvetica neue family as well as this ps fonts issue.
any help or advice more than welcome.

First question would be, what are you using for a font manager? For the type of work you do, Font Book should be just about your last choice. Suitcase Fusion 3 or FontExplorer X Pro are the ones I recommend.
If you already are using Suitcase or FEX Pro, then get Font Book off your Mac. Having more than one font manager on any system is a sure way to make controlling fonts difficult.
1) Open Font Book, and then its preferences. Uncheck the box for "Alert me if system fonts change". Close the preferences and shut down Font Book. Put the Font Book application in the trash and delete it.
2) Restart your Mac and immediately hold down the Shift key when you hear the startup chime to boot into Safe Mode. Keep holding it until OS X asks you to log in (you will get this screen on a Safe Mode boot even if your Mac is set to automatically log in). Let the Mac finish booting to the desktop and then restart normally.
This will reset Font Book's database and clear the cache files in your user account. Any font sets you have created will be gone. Also, all fonts in the three main Fonts folders (System, Library, your user account) will now be active, regardless of their state beforehand.
The main goal in this step is to remove the orphaned Font Book database from the hard drive. With the Font Book application no longer on the hard drive, a new one cannot be created. Which is what we want.
3) Close all running applications. From an administrator account, open the Terminal app and enter the following command. You can also copy/paste it from here into the Terminal window:
sudo atsutil databases -remove
This removes all font cache files. Both for the system and all user font cache files. After running the command, close Terminal and immediately restart your Mac.
because a lot of the displays on certain browsers and programs are not displaying like they used to.
That comes back to font cache data that no longer relates to a font still on the drive. Clearing all font cache data after manually removing any fonts is pretty much a must. As is resetting Font Book's database by doing a Safe Mode boot.
Ever since I did that, InDesign CS4 is NOT seeing any T1 fonts. Before, it was only a Helvetica Neue T1 issue.
I'd say something on the system is goofed up. When I first installed Snow Leopard to an erased partition, all fonts worked. I did my usual of removing Font Book and getting the fonts on the drive down to the minimum. I then started installing all of my third party apps. Somewhere in there, fonts simply stopped working. The only fix was to reinstall OS X and reapply the Combo updater, along with whatever else Software Update said was needed. Voila, fonts worked again as expected. Just had to remove Font Book and all the fonts I didn't want on the drive again.
It's a bit of a pain to do, but that's why I went right to "reinstall the OS" above.

Windows7 x64 and photoshop not recognising postscript fonts

The company I work for is looking to Rollout Windows7 x64 with CS5 using Universal Type Client v2.1.3.4 for our font management but have hit a snag.
When using Photoshop (both x32 and x64) and Flash, only opentype and truetype fonts are available (ie postscript fonts don't appear in the application font menus). The vast majority of our fonts are postscript so this is becoming a major issue holding back the rollout of Windows7.
We've tried turning off Hide Fonts but that made no difference.
Has anyone else seen similar or know of a fix so that postscript fonts will appear?
Many thanks in advance

Thanks for the response.
However, there are a number of problems with us dumping our postscript fonts and updating them to OT and TT.
1. We're a print media company that sends a lot of print advertisements to newspapers all over Australia. These newspapers won't accept "jobs" unless they are done using postscript fonts as their 5-10 year old RIPs are still using postscript. Unfortunately, this is beyond our control.
2, The price of re-purchasing the fonts. Many of our postscript fonts were purchased through Adobe who (in Australia) say that we need to purchase the Open Type or TrueType versions of our postscript fonts - if they exist. Given we have 200+ desktops and we're talking about 2500 fonts, combined with Adobe Australia's pricing model for fonts, we're talking about some serious money here (a few hundred thousand easily).
The postscript fonts work fine with InDesign CS5 (on Win7 x64) and with our various printers, nor any errors - it's just they don't appear in Photoshop or Flash. We can't just add them to the Windows Fonts folder as they are then all active which can have a negative impact on desktop performance.
Our Apple Macs running the same version of Creative Suite with the same version of Unversial Type Server with postscript fonts don't suffer the same issue with photoshop or flash.
Is this just a Windows 64 bit issue? Is it an Extensis issue? Is it something do with Adobe products on x64? Or a combination of the 3?

Font Book: Installed postscript Fonts don't always appear in Font Book list

Greetings,
I was helping a user the other day with Font Book. I was showing him how to add/enable fonts into Font Book when I noticed a problem I had never seen before. Before I get started, the fonts in question are from the Adobe 7 Font Folio library. There were newly installed by me from the original disk, and known not to be corrupt. I also know that that Postscript fonts are an accepted font format in Tiger.
That said, when adding.installing a particular font using Font Book, it would not "Appear" in the Font Book" list of fonts. I would attemp to, again add/enable the font (by selecting it from the Adobe Library) and still it would not appear in the Font Book list with the other installed fonts. This would happen to any font that I tried to install. Once this happenend to a specific font, I could no longer get that specific font to install.
I removed the Font Book .plist - no luck. I also rebooted - no luck.
Obviously, no application was able to recognize any of the fonts that would not install.
It was as if Font Book would not recognize any font that I was trying to add/enable.
Could this be a corrupted cache issue, or .plist problem? Could this be a permissions related issue? What did work finally was to add the font to the "Computer" set, where it would be avaialbe to all users. But I could not get the font to install into the "User" set. Weird.
Also, What is the significance of these four fonts:
HelveLTMM
Helvetica LT MM
Times LT MM
TimesLTMM
These fonts above are part of the default package that is loaded into the /System/Library/Fonts
Is it safe to replace these with Postscript version from my Adobe 7 Font Folio collection?
I have read most of the font related tutorials and articals.
thanks,
Hairfarm
G4 Mac OS X (10.4.3)
G5 Mac OS X (10.3.6)

where did
you get the information about pre-92 Adobe postscript
fonts being uncompatible?
Oh, sure, it's hard enough for me to remember things these days and now you want me to remember where I learned them from?? geez... [gone lookin' ... okay, back] It was, as I vaguely recalled, on the Adobe site, re troubleshooting in OS X, in a list of "do this to solve your problems": "Make sure that you are using the latest version of the font... If the font's creation date is prior to 1992, a new version of the font may be available." The only Type 1's that have given me any problems were, all three of them, older than 92, and in troubleshooting something here a few weeks ago, that turned out to be a problem for someone else, too.
But all of the Tiger font
research that I have done suggests that Adobe
Postscript fonts were acceptable.
Yes, well... Type 1's are supported. It seems that some older ones are a little funky (not in a design sense....)
Ideally, what fonts can be removed from Tiger from
the System/Libray/Fonts folder? I know that all four
of the MM's (Helvetica LTand Times LT), Lucida
Grande, Geneva, Keyboard, Last Resort, and Monoco
must stay, but what about the others?
You also need a real Helvetica - that is, not the MM version. You can replace the system's Helvetica with one of your own, but there must be an available Helvetica around at all times.
Then there's AquaKana (two of them, regular and bold). They're not on Apple's official "do not remove" list, but there's some anecdotal evidence of its being needed. It's "real" name begins with a period, so it doesn't appear in any menu, so it's not going to hurt anything if you leave it there.
In stripping down nonessential fonts, lots of people just remove everything from the Library/Fonts folder, but I think it's good to leave the basic most common web fonts available: Comic Sans, Georgia, Trebuchet, Verdana, Times New Roman. This keeps web pages looking the way they're supposed to - and they shouldn't conflict with anything that's being really designed!
This is assuming that the fonts
being used are not damaged and "Pass" Font Book's
validation test.
The assumption within that assumption is false: Font Book's validation is pretty iffy. I think the only reason we don't see it as REALLY iffy is because fonts, on the whole, are pretty solid in OS X (your current experience to the contrary). I've installed fonts (properly) that flew through the automatic-on-install validation but failed when I used the Validate Font command afterwards. I've had fonts that pass both the on-install and specific after-install validation but get a Bad Font warning dialog when being re-enabled after a disabling. (And I didn't use the font in between... ) Who knew Font Book did any validating when you re-enable fonts??
This is what I would do:
(Not necessarily in this order)
1. Trash Font Book .plist
2. Trash all Font Cache's from all three libraries
(System, Computer, and User folders)
3. Reboot
4. Delete problem fonts from User and Computer
Libraries and reinstall using Font Book.
Please tell me if this strategy is ill-advised, and
what the better course of action might be.
None of it is ill-advised. I would add starting up in Safe Mode to see if the problems exist there as part of the narrow-down-the-problem stage. Same goes for setting up a separate user account and see how things are behaving there. (Yikes... did you try that yet??)
In addition, there are some special things to do when it's Office apps having the problem, or something going on with Adobe's application fonts folder...
Also, Zaph Dingbats is acting up as well. I removed
the .dfont version that was in the system folder, and
replaced it with the Adobe Font Folio Postscript
version (ITC Zaph Dingbats) that I loaded into Font
Book User/Library/Fonts folder. Now that I think
about it, that specific font has been around for
along time, and may very well be pre-1992. Hmmm...
Can you further define "acting up" ? In addition to the ZD dfont from the system, I've been using/testing ITC ZD from Adobe with no problems. It's version 2.0 with copyright dates of 1985 through 1987.
A lot to respond to. My apologies.
No problem. You caught me on a night when I'm too tired for real work but not so far gone I can't do this (tho I'm soon on my way, bleary-eyed, to get a fix of Sudoku puzzles).

All Adobe PS fonts mysteriously removed from Word 2000 font library

HELP !
Operating System:     Windows 2000 Professional with Service Pack 4
Word Processor:        Office 2000 (including Word 2000) with Service Pack 3
Adobe Type Manager Deluxe:     Version 4 .1 installed May 24, 2000, Serial Number XXXXXXXXXXXXXX-XXX.
Adobe Postscript Fonts:     The entire library.
On September 12, 2010, I opened up a Word document created in 1992 on my computer using Adobe postscript font AvantGarde.
I immediately saved the document in the latest version of Word (i.e., Word 2000).
I then highlighted the bolded caption to change the font size from 12 points to 13 points.     "13" is not on the font size drop down menu, so it has to be typed in manually. I did that.
The second I pressed the "Enter" key, the following events occurred:
               The entire Adobe postscript font library disappeared from the Word 2000 drop down list of available fonts;
               The installation date of the Adobe PS fonts all changed to the date I hit the "Enter" key (i.e., 9/12/2010);
                The file size of each font changed to "OK";
                The attributes of each Adobe PS font changed to "AC";
                The file name of each Adobe PS font was broken by the insertion of an ____ in the file name; I don't know if it replaced any existing characters in the file name;
                 All the Adobe postscript fonts remain in the Master Font List of Adobe Type Manager Deluxe 4.1, as well as the Adobe folder containing all the Adobe PS fonts;
                 Every Word document ever created on our computer formatted in Adobe PS AvantGarde - about 95% of all our documents - defaulted to either Courier or Avant Guard (pronounce the same, but spelled differently); "Avant Guard" is a true type font.
Adobe Tech support personnel were unable to assist me and suggested I present this problem to the Forum.
I have the name of the engineers who developed Adobe Type Manager Deluxe 4.1, as well as its technical specifications from Help.
Adobe postscript font "Avantgarde" is practically our firm's logo. Readers recognize our work just by the font. It's one of the most beautiful and readable fonts in the entire Adobe library.
                 I have no reason to believe the document itself that I opened was corrupted.
                 I have a complete back-up of our entire Adobe postscript library on a 100 MB ZipDisk, but I don't know if simply reinstalling the font files will correct the problem.     I don't want to make things worse by blind experiment.
                 All other font types remain in our Word font library list and are fully accessible; but none are as readable or as beautiful as postscript fonts.
                 Unfortunately, I am not a computer "techie", but I can follow instructions if I understand them.
                 Sincerely appreciative of knowledgeable assistance, I remain
                 Very truly yours,
                                          NORMAN COUSINS
                                        [email protected]
                                               212-962-6460

(1)     Never post a serial number of a product you've licensed on a public forum. We have taken the responsible liberty of replacing that serial number in your post with a series of Xs.
(2)     This forum is associated with the PostScript programming language. Your problem has nothing to do with that whatsoever, but rather, with an event that somewhat mucked up fonts on your host computer system. If anyone in Adobe Technical Support told you to post on the PostScript forum, they were dead wrong. We are sorry for that bum information provided by our Technical Support organization.
(3)     Adobe Type Manager Deluxe has not been supported by Adobe in any way for well over five years.
(4)     There should be nothing that Microsoft Word or the user of same could do within Microsoft Word to cause the symptoms you describe. Neither Word nor Office do anything to uninstall fonts or modify the fonts.
(5)     Without explicitly invoking ATM, ATM has no functionality or for that matter any known bugs that would cause the symptoms you describe.
(6)     Windows' Font Control Panel likewise has no functionality or any known bugs that would cause the symptoms you describe.
Any attempt to further analyze what happened on your computer would be totally a wide-assed guess. However, I could imagine hardware problems with your disk drive causing the type of symptoms you describe. If in fact you are using a computer system that was installed in May 2000 and especially if you are using the original disk drive, I suspect your luck in terms of system longevity may just have given out. (Ten years for a computer system and especially a disk drive is pretty long). Zip Disk? You'd better back that up to something more modern. Neither the drives nor media are readily available for that format anymore.
          - Dov

Solution for Vista, missing Postscript fonts, & CS3

Just switched over 64-bit Vista (first time on Vista for me--no more ATM Lite) and found that even if I installed my old .pfm-conforming postscript fonts, they'd show up in everything but CS3.
I had followed Adobe's directions for Vista and postscript files, and installed by right clicking and selecting "install". All showed up in the Windows/Font directory, but the only PS font Photoshop saw was Myriad.
Since Myriad is Adobe's font, and was probably installed with CS3, I tried uninstalling all PS/Type 1 fonts from the Fonts directory. Myriad disappeared as well.
So I figured, no, Myriad must have been installed in the same place as the others.
Nonetheless, I tried dropping my postscript files (.pfm, .pfb. .inf for each) into Program Files (x86)/Common Files/Adobe/Fonts, and THAT worked.
Now all my postscript files function perfectly fine throughout CS3--Photoshop, Illustrator, etc.
64-bit related? Vista installs only .pfm files in the font directory but CS3 wants the .pfb or .inf files as well? No idea. But I do know Adobe's support docs were useless on this matter.

I did and got a friendly guy who apparently had never heard of the 2739 error. I was hoping to get some support here. In another thread I read something about holding the installation window until installation starts. I can try it, but I doubt I am quick enough before the error window opens.

Adobe Postscript Type 1 fonts and Windows 7

I have a disk with Adobe Postscript Type 1 fonts ("Adobe Type Basics" that I purchased in 2001). The disk includes an install program that does not work on my current computer (Windows 7, 64). Can I get those fonts installed on my current computer, and if so, how do I do it. Step by step, please. Many thanks.

Although we at Adobe certainly do recommend use of OpenType font technology going forward and especially for new publishing projects for any number of very good reasons, Adobe does continue to fully support Type 1 fonts (FWIW, TrueType and OpenType fonts are every bit as much PostScript fonts as Type 1 or Type 3 fonts are) in all our applications as well as in our Adobe PostScript and Adobe PDF Print Engine products and has committed to do so for the indefinite future.
In fact, Adobe still does license and ship Type 1 fonts in fairly high quantities. Every printer sold with Adobe PostScript 3 by Adobe's OEM partners such as Xerox, Ricoh, Canon, Océ, EFI, etc. is accompanied with host software that includes the Windows and Macintosh host versions of all the Type 1 fonts that are also printer resident.
Actually, the problem that the OP of this thread was experiencing is that apparently, the Adobe Type Basics was built without the .pfm files that normally were shipped with all Adobe type packages for Windows. When ATM was required for installation of those fonts, since ATM had the capability of building .pfm files on-the-fly, this omission wasn't noticed at the time by most users (even I wasn't aware of it until today). Otherwise, there was nothing wrong with those fonts and there was nothing about them that was “showing their age.”
Unfortunately, the Adobe Type Basics OpenType Edition is not a superset of the fonts in the original Adobe Type Basics product. Many of the font families of the original product were replaced by totally different font families. Updating to the OpenType-based product would not have solved the OP's problem without possibly needing to license a whole bunch of additional font families individually, possibly costing more than the $99 for the Adobe Type Basics OpenType Edition itself. For existing content (including templates and artwork), it is not simple to move from Type 1 to OpenType without going through existing content and globally changing all font references. The OpenType versions of Adobe's font do not have the same names as the Type 1 versions - this was not an oversight, but done for good reason since there are differences between the products in encoding and metrics that could in some cases cause layout issues.
- Dov

Using Adobe PostScript Type 1 fonts on Lion/MacBook Pro

I recently upgraded from a 5-year-old MacBook using Snow Leopard to a MacBook Pro using Lion. I also upgraded from MS Office 2004 to MS Office 2011.
On the old MacBook, as on my even-older Cube using OS 9.2 and Office 2001, I used several old Adobe PostScript Type 1 fonts with no problem. Foremost among them were Adobe Garamond and Adobe Jenson. I've dragged the six Garamond fonts, plus its font suitcase to the Fonts folder in the Library folder. Upon seeing some fleeting font installation messages, I thought all was well.
But no luck. The fonts don't appear as options on old or new documents. Any suggestions or solutions?
JohninDenver

I recently upgraded from a 5-year-old MacBook using Snow Leopard to a MacBook Pro using Lion. I also upgraded from MS Office 2004 to MS Office 2011.
On the old MacBook, as on my even-older Cube using OS 9.2 and Office 2001, I used several old Adobe PostScript Type 1 fonts with no problem. Foremost among them were Adobe Garamond and Adobe Jenson. I've dragged the six Garamond fonts, plus its font suitcase to the Fonts folder in the Library folder. Upon seeing some fleeting font installation messages, I thought all was well.
But no luck. The fonts don't appear as options on old or new documents. Any suggestions or solutions?
JohninDenver

PDF and OTF (Postscript) font issue (is there a PDF validation tool?)

Greetings all,
I am experiencing a problem uploading any documents, which include embedded OTF (Postscript) fonts, to a Cloud based collaboration tool called Crocodoc. The problem/failure appears to occur during the document conversion from PDF to HTML5. It is important to note that this problem is not specific to Crocodoc because I have tested others (i.e. Zoho).
The problem is specifically with Madcap Flare and its recent support for OTF fonts. This is how I arrived at this conclusion:
- Changing the embedded font to TTF only, the published PDF uploads to Crocodoc without incident.
- It is not the OTF font. I have also tested this particular OTF font with other publication tools, including Microsoft Word and Adobe Framemaker; there were no issues.
Other facts:
- PDF files appear to function normally. It is only when I upload to Crocodoc-like apps when the problem manifests itself.
I subscribe to the Creative Cloud but Adobe Acrobat doesn't seem to have any validation functionality.
But here are some other tests that I have done:
- Opened the malfunctioning PDF into Acrobat (no apparent issues)
> Saved as optimized with all discard options turned on plus I ran the sanitize option. The new saved PDF still failed to upload.
> Removed ALL text and saved a blank page. Still failed to upload to Crocodoc
> As a verification, I created a PDF page (from clipboard) with Acrobat and saved that (one line of font using OTF font) - This successfully uploaded to Crocodoc.
> VERY INTERESTING...using Acrobat to CONVERT the problem PDF to eps and then eps back to PDF - This PDF uploaded successfully to Crocodoc.
BUT there is something 'wrong' with Adobe Acrobat's conversion because it only converts the first page back into a PDF. WHAT?
Conclusion, as long as the PDF originated in Flare, it will fail to upload to Crocodoc. However, converting the document to .eps and then back to a PDF seems to have stripped away the 'bad' stuff.
What I am trying to learn is what exactly is causing the upload and conversion error?
Is there a PDF validation tool and might identify what is causing this conversion problem?
Sorry for the long post. Hopefully someone had the patience to read this and has an idea.
Thank you

Hello TSN,
Test Screen Name wrote:
Picking just one point: PDF -> EPS -> PDF. This could not possibly do more than one page, because EPS is absolutely by definition a single page format. Therefore you must choose a page when exporting PDF to EPS.
Thanks for your response.
I was thinking Microsoft... which has allowed multi-page eps files for years. But you're correct, this is normally an unsupported .eps format.
I solved the problem over the weekend by doing the following:
1) I removed the suspect OTF font family but despite doing so, the folder still had two 'corrupted' but unused copies of an italic font. They refused to remove so I had to boot into Win7 SAFE mode to remove.
2) After complete removal of the OTF font family. I reinstalled the OTF font *BUT* only from a different repository (oddly, this other OTF font set is slightly larger per font).
3) Once installed, I tested with Flare, published and uploaded to Crocodoc SUCCESSFULLY. Yeah!
I don't have anymore time to test but the questions remain, such as, was it one or more of the following issues:
a) Flare has a problem handling some OTF fonts or cannot error correct (the way other programs do) for marginal fonts or font errors?
b) Was it the two corrupted fonts in the Windows/fonts folder?
c) Was it the slightly different OTF fonts that I am no longer using?
Take care

When you create a PostScript file you must rely on system fonts and use document fonts

I got this error:
"When you create a PostScript file you must rely on system fonts and use document fonts. Please go to the printer properties, "Adobe PDF Settings" page and turn OFF the option "Rely on system fonts only; do not use document fonts."
This strikes me as bad practice. I only want to use system fonts and document fonts will muck me up.
That being said, I could not easily find a way to fix this with Acrobat Pro XI. I opened Control Panel (Windows 8) and found the printer and mucked around in the various ways to get to change the PDF settings (there are several ways, and some of them present the choices as bold and not just regular). I found two separate switches for "Rely on system fonts only; do not use document fonts" and turned both off, BUT that did not work.
Frustrated, I went back to FrameMaker and clicked File > Print Setup and then for the PDF printer, Printer Properties. There I found a THIRD instance of "Rely on system fonts only; do not use document fonts" that was set differently than the other two. This was the setting the error message meant. Change this one.
Thanks for the convoluted UI, Adobe. What a pain, but there is the answer for all who follow after....

> Windows 7 and Frame 7.2.
This is not a supported configuration and probably does not work, due (I'm guessing) to driver API changes from XP to Win7, which would affect generating PDF and Ps output. This would affect Save-as-PDF and Print-to-Ps+Distill (unless you have a newer version of the full Acrobat product).
As it happens, I'm going to attempt something similar: FM 7.0 on Win7 64 Pro. However, I'm going to install that old FM in "XP Mode".
XP Mode is a 32-bit virtual machine running actual Windows XP inside Win7. It is (now maybe "was") available for Windows 7 Enterprise, Professional and Ultimate (but not Basic, Home or not-so-Premium). When XP went off support life earlier this month, Mr.Bill may have taken down the ability to download XP Mode (or not, since some large enterprises are able to purchase continued support for XP at some great cost). XP Mode never was supported for Win8. There are other VMs for Windows available.
If XP Mode is still available, you also need a CPU that has hardware virtualization, which all recent 64-bit AMD processors do, but which is fused-off in many low end 64-bit Intel processors. AMD processors need a separate unobvious hot-fix patch installed before you do anything else about XP Mode.

HelveticaNeue.dfont cant be replaced by a postscript font as in 10.4 and

I have always replaced the .dfonts with postscript fonts for prepress and print design - this is vital.
Now OSX replaces it as soon as I delete it even after I replace it with a ps version.
How can I get around this "feature"?
It is a vital issue, upon which hundreds of upgrades under my watch are waiting for.
10.5 can not be deployed until designers can use postscript fonts for printing. If we are forced to use only the .dfont version we can not upgrade. Ever.
The .dfont is not acceptable as it does not contain the same number of typefaces as the adobe postscript version. Styles that are used in numerous ongoing designs, and mixing font types with one font is taboo in the print world.
I need a way to force the replacement.
(Extensis suitcase overriding system fonts is not a solution either.)

We prepress professionals don't use Font Book. I use Font Explorer here others use Suitcase. The SOP was to replace all the dFonts that are used in printing to Type one fonts, by replacing them in System/Library/Fonts. That can no longer be accomplished as the dFonts "respawn" if removed creating a font conflict because you can't have a dFont and a Type One active at the same time.
For your average user this is not an issue, just for designers and prepress monkeys.

I just bought a 13inch mac book with retina display. When Im using adobe illustrator or photoshop, the fonts and designs look pixelated! How can I fix this?

I just bought a 13inch mac book with retina display.
2.4GHz dual-core Intel Core i5 processor with 3MB shared L3 cache. Version 10.9.4 / OS X Mavericks
When Im using adobe illustrator or photoshop, the fonts and designs look pixelated!
How can I fix this?

WOW!!
That was great to hear.
I have just read this tread: https://forums.adobe.com/thread/1626784?start=0&tstart=0
So therefore I was worry about Illustrator which I use most of all programs.
Thank you !!

When opening a pdf document in Adobe Reader the font of the original document is changed....It becomes a mix of the original font and a new different font. How can i fix this

When opening a pdf document in Adobe Reader the font of the original document is changed....It becomes a mix of the original font and a new different font. How can i fix this

This issue occurs with most of the PDFs that I open up. I am using the latest version of adobe reader on my windows based machine and it is a general PDF. I saw a similar post online stating that if you look at the fonts used in the document and it doesn't say (Embedded) next to it, then Adobe Reader will try to pull the font(s) from your computer and if it doesn't find that font then it will replace it which makes it look funny.

Adobe Postscript Fonts and Fontbook

Similar Messages

Maybe you are looking for