Hi,
Are there any advantages/disadvantages to using the SAVE AS PDF function
over printing to a postscript file and then distilling?
Thanks, Paul
___
You are currently subscribed to Framers as [EMAIL PROTECTED]
Send list messages to [EMAIL
There are numerous articles and threads on this subject in the archives,
if they are working this morning.
But, in a nutshell, Save As PDF is problematic in all versions of
FrameMaker. You may, or may not, experience problems. Using Print to
File and then Distilling eliminates all of these
You don't even need to Print to file if you use an Adobe printer
driver when printing to PDF. In versions 7.x, the printer driver is
Adobe PDF. (I forget just now which one it is in version 6.x--Acrobat
Distiller, maybe?)
When you do it this way (making sure to *clear* the Print to file
check
Now that we use Frame 7 we've never had problems with Saving as PDF.
--Doug
snipBut, in a nutshell, Save As PDF is problematic in all versions of
FrameMaker. You may, or may not, experience problems. Using Print to
File and then Distilling eliminates all of these problems.
But, in a nutshell, Save As PDF is problematic in all versions of
FrameMaker. You may, or may not, experience problems. Using Print to
File and then Distilling eliminates all of these problems.
I have not had issues since 7.0. I believe it to be finally fixed. But
yes, 6.x and earlier was
I had a few problems with FM file associations recently when I removed
my old FM7.0 version. I had both FM 7.0 and FM7.2 installed and
double-clicking a FM file opened it in FM7.0.
Once I removed FM7.0 I could no longer open my FM files from Explorer.
To rectify this, I used the fmreg.txt file
We have a similar docs payload, and have custom job options that we
just load and run on save-as. Laziness has its benefits. :-)
On 7/17/06, John Posada [EMAIL PROTECTED] wrote:
We're on 7.1 and 7.2. Out policy is to use Save As - PDF. We have 10
writers maintaining almost 100 books doing it
I never said it didn't work, only that it was problematic. Your mileage
may vary (YMMV) on the use of Save As PDF.
-Original Message-
From: Bill Swallow [mailto:[EMAIL PROTECTED]
Sent: Monday, July 17, 2006 10:36 AM
To: John Posada
Cc: Spreadbury, David; [EMAIL PROTECTED];
Is there a solution other than Rick's Table Cleaner???
Hardware: Dell 340 Workstation
OpSys:Win2K
AppWare: Frame 7.0, Acrobat 5.+, Illus 10, PShop 7.0, MSWord, MSVisualBasic
6.+
Table style change:Catalog with new table style . . .!!! Tables now
Left Indensted 18pts from column
Dunno, but I have been using the Adobe PDF driver + write to file +
distilling for nearly five years now without any problems on both
unstructured and structured FM versions 6.0 - 7.1. I haven't yet run
into a need for save as PDF.
Joe Malin
Technical Writer
(408)625-1623
[EMAIL PROTECTED]
David...And I didn't just say it worked...I said it worked 100% of
the time without problems. In your experience, how is using Save As
- PDF, in version 7.x, problematic?
In version 7.x, what problems have you experienced?
--- Spreadbury, David [EMAIL PROTECTED] wrote:
I never said it didn't
Fred, Tammy:
> Checking for unresolved x-refs with all conditions showing
> establishes that all the x-refs are good, and you should then be
> able to document that the "bad" ones that are reported in the Book
> Errors windows when you publish any given conditionalized version
> are due only to
Hi,
Are there any advantages/disadvantages to using the SAVE AS PDF function
over printing to a postscript file and then distilling?
Thanks, Paul
There are numerous articles and threads on this subject in the archives,
if they are working this morning.
But, in a nutshell, Save As PDF is problematic in all versions of
FrameMaker. You may, or may not, experience problems. Using Print to
File and then Distilling eliminates all of these
You don't even need to "Print to file" if you use an Adobe printer
driver when printing to PDF. In versions 7.x, the printer driver is
"Adobe PDF." (I forget just now which one it is in version 6.x--"Acrobat
Distiller", maybe?)
When you do it this way (making sure to *clear* the "Print to file"
Now that we use Frame 7 we've never had problems with Saving as PDF.
--Doug
> But, in a nutshell, Save As PDF is problematic in all versions of
> FrameMaker. You may, or may not, experience problems. Using Print to
> File and then Distilling eliminates all of these problems.
> But, in a nutshell, Save As PDF is problematic in all versions of
> FrameMaker. You may, or may not, experience problems. Using Print to
> File and then Distilling eliminates all of these problems.
I have not had issues since 7.0. I believe it to be finally fixed. But
yes, 6.x and earlier was
I had a few problems with FM file associations recently when I removed
my old FM7.0 version. I had both FM 7.0 and FM7.2 installed and
double-clicking a FM file opened it in FM7.0.
Once I removed FM7.0 I could no longer open my FM files from Explorer.
To rectify this, I used the fmreg.txt file
We're on 7.1 and 7.2. Out policy is to use Save As -> PDF. We have 10
writers maintaining almost 100 books doing it this way and we don't
have any problems with Save As -> PDF.
> > But, in a nutshell, Save As PDF is problematic in all versions
> > of FrameMaker. You may, or may not, experience
We have a similar docs payload, and have custom job options that we
just load and run on save-as. Laziness has its benefits. :-)
On 7/17/06, John Posada wrote:
> We're on 7.1 and 7.2. Out policy is to use Save As -> PDF. We have 10
> writers maintaining almost 100 books doing it this way and we
I never said it didn't work, only that it was problematic. Your mileage
may vary (YMMV) on the use of Save As PDF.
-Original Message-
From: Bill Swallow [mailto:techcommd...@gmail.com]
Sent: Monday, July 17, 2006 10:36 AM
To: John Posada
Cc: Spreadbury, David; framers at omsys.com;
If I was going to guess, from the limited amount of info
I'd guess that the rebuilt system was pointing z: to \\rubble rather than
\\rubble\techpubs\
Have you confirmed the paths? And while you're at it, the permissions?
Art
On 7/17/06, Brian Wesley Simmons wrote:
> Howdy, folks. I like
Is there a solution other than Rick's Table Cleaner???
Hardware: Dell 340 Workstation
OpSys:Win2K
AppWare: Frame 7.0, Acrobat 5.+, Illus 10, PShop 7.0, MSWord, MSVisualBasic
6.+
Table style change:Catalog with "new" table style . . .!!! Tables now
Left Indensted 18pts from column
Paul Grigg wrote:
> Hi,
>
> Are there any advantages/disadvantages to using the SAVE AS PDF function
> over printing to a postscript file and then distilling?
In FM 6, yup, a lot of disadvantages; somewhat fewer in later versions.
See http://www.microtype.com/FM_bugs.html
for the full story.
Dunno, but I have been using the Adobe PDF driver + write to file +
distilling for nearly five years now without any problems on both
unstructured and structured FM versions 6.0 - 7.1. I haven't yet run
into a need for "save as PDF".
Joe Malin
Technical Writer
(408)625-1623
jmalin at tuvox.com
David...And I didn't just say it worked...I said it worked 100% of
the time without problems. In your experience, how is using Save As
-> PDF, in version 7.x, problematic?
In version 7.x, what problems have you experienced?
--- "Spreadbury, David" wrote:
> I never said it didn't work, only
During the years before Frame 7.0 was released, there were many, many
messages on this list regarding using Save As PDF in FM 6.0. It worked for
a few people who happened to have the right printer driver set up but many
people complained that they were not getting the results they needed. A
27 matches
Mail list logo
