Thread View: adobe.framemaker
10 messages
10 total messages
Started by Ashton_Treadway
Tue, 03 Mar 2009 00:43
FrameMaker has correct fonts, PDFs produced with Acrobat 9 don't.
Author: Ashton_Treadway
Date: Tue, 03 Mar 2009 00:43
Date: Tue, 03 Mar 2009 00:43
7 lines
1264 bytes
1264 bytes
We're producing PDFs out of FrameMaker 9 into Acrobat 9, using the Frutiger Next font family. With the exception of a single character format, fonts are coming out correctly embedded in the PDFs. However, in this one case (Frutiger Next Pro Medium), Acrobat appears to be (for no reason we can tell) substituting Frutiger Next Pro Heavy for medium, which makes the resulting PDF look like crap. When we print from Frame, it looks correct. This only happens when we save as PDF. The fonts are installed on the machine, Frame uses and shows them correctly. This only happened after we upgraded to Frame 9 and Acrobat 9, and we're at our wit's end trying to figure out what the hell is going on.
Re: FrameMaker has correct fonts, PDFs produced with Acrobat 9 don't.
Author: Arnis_Gubins
Date: Tue, 03 Mar 2009 02:51
Date: Tue, 03 Mar 2009 02:51
20 lines
1556 bytes
1556 bytes
Is the location of the Frutiger Next Pro Medium specified in the Distiller font locations section (Settings >Font Locations)? Have you printed directly to the AdobePDF printer instance instead of using Save As PDF? If you redirect to the print to file option, check the .ps file to see if this font is actually being referenced there. Look at the following sections (of a small, few page test print) at the end of the .ps file: %%DocumentNeededResources: %%DocumentSuppliedResources: Look at the %%+ font entries. If you see the font there, then it's getting out of FM properly and something in your Distiller setup is fumbling the ball. Note: if it works fine going the manual print to postscript file and distill route, then that's probably one more thing that was fubar with the SaveAsPDF option in FM9. There are a few threads here listing other things that were broken.
Re: FrameMaker has correct fonts, PDFs produced with Acrobat 9 don't.
Author: Art Campbell
Date: Tue, 03 Mar 2009 13:49
Date: Tue, 03 Mar 2009 13:49
5 lines
929 bytes
929 bytes
You may want to try installing that family again... Make sure that the Adobe PDF printer is set as the system default, and instead of using the SaveAs PDF... is there a difference when you Print to the PDF printer? Art
Re: FrameMaker has correct fonts, PDFs produced with Acrobat 9 don't.
Author: Sheila_Carlisle
Date: Tue, 03 Mar 2009 17:53
Date: Tue, 03 Mar 2009 17:53
3 lines
1020 bytes
1020 bytes
How were the missing fonts being applied in the text -- are they applied as 1) an ad hoc character override, 2) with a named character tag, 3) at the paragraph tag level. How was the text originally created, was it entered into FM directly, was it cut-and-paste via the clipboard from somewhere else, was it imported from a different app (e.g. Word) and if so, how, exactly.
Re: FrameMaker has correct fonts, PDFs produced with Acrobat 9 don't.
Author: Ashton_Treadway
Date: Tue, 03 Mar 2009 18:00
Date: Tue, 03 Mar 2009 18:00
7 lines
1019 bytes
1019 bytes
Hi, Arnis: Thanks for your assistance: I printed to a .ps file, and those fonts are not in the DocumentNeededResources or DocumentProvidedResources. However, the resulting PDF out of the .ps file turned out looking the way it should have, so I think you're right in that this is YASAPB (Yet Another Save As PDF Bug). I'll drop it into one of the existing bugthreads.
Re: FrameMaker has correct fonts, PDFs produced with Acrobat 9 don't.
Author: Sean
Date: Wed, 04 Mar 2009 16:30
Date: Wed, 04 Mar 2009 16:30
28 lines
1666 bytes
1666 bytes
I am having this same issue with ArialMTStd-Black.otf from Monotype Imaging. 1) It displays fine in FM 8 and in a PDF created using Save as and Acrobat 9. 2) It displays fine in Word 2002 and in a PDF creating using Acrobat 9. 3) It displays fine in FrameMaker 9 but is substituted by TNR in the PDF created using Save as and Acrobat 9. Note, I tested on the same files and joboptions that work fine for FM 8. 4) Reinstalling the font has no effect. 5) Adobe PDF is my default printer. Am in Win XP all patched up. 6) The font in question is defined as part of a paragraph style (ctrl+m) and is not an override. 7) I am unsure how to read DocumentNeededResources. I see it here: %%DocumentNeededResources: %%+ font ArialMT %%+ font ArialMTStd-Black %%+ font ArialNarrow-Bold %%+ font TimesNewRomanPSMT %%+ font Arial-ItalicMT The missing font is ArialMTStd-Black. Does that mean FM is or Distiller are having issues? 8) If I print as a PS file first and then distill it, the font comes through fine, no problems. Thoughts? Sean
Re: FrameMaker has correct fonts, PDFs produced with Acrobat 9 don't.
Author: Art Campbell
Date: Wed, 04 Mar 2009 17:06
Date: Wed, 04 Mar 2009 17:06
5 lines
1022 bytes
1022 bytes
Sean, the SaveAs method should work fine, but it hasn't for a number of years and releases... including in 9. Print the book or file to the Adobe PDF logical printer and see if that changes the result. This would be the same workflow as you're using to create a PS file and then manually distill it, but it's only one step, so I expect it to solve your problem. Art
Re: FrameMaker has correct fonts, PDFs produced with Acrobat 9 don't.
Author: Arnis_Gubins
Date: Wed, 04 Mar 2009 20:03
Date: Wed, 04 Mar 2009 20:03
6 lines
916 bytes
916 bytes
Sean, In the SaveAsPDF from FM9, are you using the CMYK options or the [old]RGB option? Try the RGB option and see if it works then. If so, that's one more screw-up in the CMYK version.
Re: FrameMaker has correct fonts, PDFs produced with Acrobat 9 don't.
Author: Sean
Date: Wed, 04 Mar 2009 20:44
Date: Wed, 04 Mar 2009 20:44
5 lines
711 bytes
711 bytes
I don't know what you mean. How do I use the CMYK options? How do I use the old RGB option? Thanks, Sean
Re: FrameMaker has correct fonts, PDFs produced with Acrobat 9 don't.
Author: Sean
Date: Wed, 04 Mar 2009 21:01
Date: Wed, 04 Mar 2009 21:01
15 lines
1257 bytes
1257 bytes
What the ... heck?! When I use File > Save as PDF, there's a check box called "Convert CMYK Colors to RGB." If I leave this deselected, Distiller takes 4 seconds after printing is done and my ArialMTStd-Black.otf font is missing from my PDF. This is a 2MB PDF. If I select this, Distiller takes 3.5 minutes after printing is done and my ArialMTStd-Black.otf is present, as it should be, in my PDF. This is a 6MB PDF. Both those were done using the same joboptions. Can you tell me what the check box does, why the extra time, why the extra file size, and why it controls whether my font displays, or not? Cheers, Sean
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads