More re responses to can't get a pdf file from FM 10

2011-08-15 Thread Helen Borrie 
At 11:02 AM 15/08/2011, Cal Callahan wrote:
> 
>Hmmm. Thanks, Mike. I will definitely check out those possibilities, 
>especially since, whenever I print fron FM (or try to print to pdF), I get a 
>notice that "Your font information has changed." The file still prints fine 
>from FM, but maybe that's a clue to one of the situations you mention.

I had that error with FM8.  Finally I cured it by adding Adobe's font folder to 
my system path - in my case, C:\Program Files\Adobe\Acrobat 8.0\Resource\Font.  
Actually, I think I picked up that tip from someone on this list. ;-) However, 
whilst I had that error, it wasn't preventing the creation of my .ps files, 
which is the route I take for producing PDFs.  (It's the only way I have found 
to get bookmarks and proper cross-ref linkages.)

Helen

Re: More re responses to can't get a pdf file from FM 10

2011-08-14 Thread Cal Callahan 
The positive side of my problem is that I'm getting some really good info.
Your input, Fred, is illuminating and explains a previously inexplicable
behavior of Word I've noticed on occasion.

On Sun, Aug 14, 2011 at 5:30 PM, Fred Ridder  wrote:

>  Cal Callahan wrote:
>
>  > Hmmm. Thanks, Mike. I will definitely check out those possibilities,
> especially
> > since, whenever I print fron FM (or try to print to pdF), I get a notice
> that
> > "Your font information has changed." The file still prints fine from FM,
> but
> > maybe that's a clue to one of the situations you mention.
>
> This message has nothing to do with the problem you describe. You will get
> this message whenever you change to a different printer driver because
> FrameMaker relies on the Windows printer driver to provide it with the "font
> metrics"--the precise dimensions of each glyph in your document. In all
> versions of FrameMaker from 8.0 onward, the default printer driver is the
> "Adobe PDF" virtual printer, on the valid assumption that most users will
> want to produce a PDF file as their primary deliverable output. If you print
> a hard copy directly (rather than producing a PDF and printing *that* file),
> you will necessarily change to a different printer driver, and FrameMaker
> will warn you that the font information has changed.
>
> I can hear you wondering why in the world a minor change in font metric
> information matters to you. It matters because the subtle difference in
> dimensions of individual glyphs can add up to enough of a difference to make
> certain lines of text to break one word earlier or later, or to cause a line
> break inside a table. The change in line breaks can potentially make the
> paragraph a line longer (or shorter), and that can make the page breaks
> change, and that can make the page count and the page numbers in the TOC and
> index be wrong.
>
> FrameMaker is not alone in being affected this way. Most other word
> processors (including MS Word) are affected in exactly the same way. The
> difference is that other tools don't bother to warn you that anything
> changed. Word has always been notorious for having instabilities in its
> pagination, and at least some of that behavior is attributable to printer
> driver changes.
>
> -Fred Ridder
>
___


You are currently subscribed to framers as arch...@mail-archive.com.

Send list messages to framers@lists.frameusers.com.

To unsubscribe send a blank email to
framers-unsubscr...@lists.frameusers.com
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to listad...@frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.

More re responses to can't get a pdf file from FM 10

2011-08-14 Thread Cal Callahan 
The positive side of my problem is that I'm getting some really good info.
Your input, Fred, is illuminating and explains a previously inexplicable
behavior of Word I've noticed on occasion.

On Sun, Aug 14, 2011 at 5:30 PM, Fred Ridder  wrote:

>  Cal Callahan wrote:
>
>  > Hmmm. Thanks, Mike. I will definitely check out those possibilities,
> especially
> > since, whenever I print fron FM (or try to print to pdF), I get a notice
> that
> > "Your font information has changed." The file still prints fine from FM,
> but
> > maybe that's a clue to one of the situations you mention.
>
> This message has nothing to do with the problem you describe. You will get
> this message whenever you change to a different printer driver because
> FrameMaker relies on the Windows printer driver to provide it with the "font
> metrics"--the precise dimensions of each glyph in your document. In all
> versions of FrameMaker from 8.0 onward, the default printer driver is the
> "Adobe PDF" virtual printer, on the valid assumption that most users will
> want to produce a PDF file as their primary deliverable output. If you print
> a hard copy directly (rather than producing a PDF and printing *that* file),
> you will necessarily change to a different printer driver, and FrameMaker
> will warn you that the font information has changed.
>
> I can hear you wondering why in the world a minor change in font metric
> information matters to you. It matters because the subtle difference in
> dimensions of individual glyphs can add up to enough of a difference to make
> certain lines of text to break one word earlier or later, or to cause a line
> break inside a table. The change in line breaks can potentially make the
> paragraph a line longer (or shorter), and that can make the page breaks
> change, and that can make the page count and the page numbers in the TOC and
> index be wrong.
>
> FrameMaker is not alone in being affected this way. Most other word
> processors (including MS Word) are affected in exactly the same way. The
> difference is that other tools don't bother to warn you that anything
> changed. Word has always been notorious for having instabilities in its
> pagination, and at least some of that behavior is attributable to printer
> driver changes.
>
> -Fred Ridder
>
-- next part --
An HTML attachment was scrubbed...
URL:

More re responses to can't get a pdf file from FM 10

2011-08-14 Thread Fred Ridder 

Cal Callahan wrote:



> Hmmm. Thanks, Mike. I will definitely check out those possibilities, 
> especially 
> since, whenever I print fron FM (or try to print to pdF), I get a notice that 
> "Your font information has changed." The file still prints fine from FM, but 
> maybe that's a clue to one of the situations you mention.

This message has nothing to do with the problem you describe. You will get this 
message whenever you change to a different printer driver because FrameMaker 
relies on the Windows printer driver to provide it with the "font metrics"--the 
precise dimensions of each glyph in your document. In all versions of 
FrameMaker from 8.0 onward, the default printer driver is the "Adobe PDF" 
virtual printer, on the valid assumption that most users will want to produce a 
PDF file as their primary deliverable output. If you print a hard copy directly 
(rather than producing a PDF and printing *that* file), you will necessarily 
change to a different printer driver, and FrameMaker will warn you that the 
font information has changed. 

I can hear you wondering why in the world a minor change in font metric 
information matters to you. It matters because the subtle difference in 
dimensions of individual glyphs can add up to enough of a difference to make 
certain lines of text to break one word earlier or later, or to cause a line 
break inside a table. The change in line breaks can potentially make the 
paragraph a line longer (or shorter), and that can make the page breaks change, 
and that can make the page count and the page numbers in the TOC and index be 
wrong.

FrameMaker is not alone in being affected this way. Most other word processors 
(including MS Word) are affected in exactly the same way. The difference is 
that other tools don't bother to warn you that anything changed. Word has 
always been notorious for having instabilities in its pagination, and at least 
some of that behavior is attributable to printer driver changes.

-Fred Ridder  
-- next part --
An HTML attachment was scrubbed...
URL:

RE: More re responses to can't get a pdf file from FM 10

2011-08-14 Thread Fred Ridder 

Cal Callahan wrote:
 


> Hmmm. Thanks, Mike. I will definitely check out those possibilities, 
> especially 
> since, whenever I print fron FM (or try to print to pdF), I get a notice that 
> "Your font information has changed." The file still prints fine from FM, but 
> maybe that's a clue to one of the situations you mention.
 
This message has nothing to do with the problem you describe. You will get this 
message whenever you change to a different printer driver because FrameMaker 
relies on the Windows printer driver to provide it with the "font metrics"--the 
precise dimensions of each glyph in your document. In all versions of 
FrameMaker from 8.0 onward, the default printer driver is the "Adobe PDF" 
virtual printer, on the valid assumption that most users will want to produce a 
PDF file as their primary deliverable output. If you print a hard copy directly 
(rather than producing a PDF and printing *that* file), you will necessarily 
change to a different printer driver, and FrameMaker will warn you that the 
font information has changed. 
 
I can hear you wondering why in the world a minor change in font metric 
information matters to you. It matters because the subtle difference in 
dimensions of individual glyphs can add up to enough of a difference to make 
certain lines of text to break one word earlier or later, or to cause a line 
break inside a table. The change in line breaks can potentially make the 
paragraph a line longer (or shorter), and that can make the page breaks change, 
and that can make the page count and the page numbers in the TOC and index be 
wrong.
 
FrameMaker is not alone in being affected this way. Most other word processors 
(including MS Word) are affected in exactly the same way. The difference is 
that other tools don't bother to warn you that anything changed. Word has 
always been notorious for having instabilities in its pagination, and at least 
some of that behavior is attributable to printer driver changes.
 
-Fred Ridder  ___


You are currently subscribed to framers as arch...@mail-archive.com.

Send list messages to framers@lists.frameusers.com.

To unsubscribe send a blank email to
framers-unsubscr...@lists.frameusers.com
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to listad...@frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.

Re: More re responses to can't get a pdf file from FM 10

2011-08-14 Thread Helen Borrie 
At 11:02 AM 15/08/2011, Cal Callahan wrote:
> 
>Hmmm. Thanks, Mike. I will definitely check out those possibilities, 
>especially since, whenever I print fron FM (or try to print to pdF), I get a 
>notice that "Your font information has changed." The file still prints fine 
>from FM, but maybe that's a clue to one of the situations you mention.

I had that error with FM8.  Finally I cured it by adding Adobe's font folder to 
my system path - in my case, C:\Program Files\Adobe\Acrobat 8.0\Resource\Font.  
Actually, I think I picked up that tip from someone on this list. ;-) However, 
whilst I had that error, it wasn't preventing the creation of my .ps files, 
which is the route I take for producing PDFs.  (It's the only way I have found 
to get bookmarks and proper cross-ref linkages.)

Helen

___


You are currently subscribed to framers as arch...@mail-archive.com.

Send list messages to framers@lists.frameusers.com.

To unsubscribe send a blank email to
framers-unsubscr...@lists.frameusers.com
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to listad...@frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.

More re responses to can't get a pdf file from FM 10

2011-08-14 Thread Cal Callahan 
Mike Wickham wrote:

Two wild stabs at your problem:

1. I recall a time when I was getting no PDF generation. It turned out
that in File> Preferences> General, I had Cross-Platform File Naming set
to Macintosh on a Windows computer, and my file name was one character
too long for the Mac 31-character (or whatever) limit. FM actually let
me go through something like four dialog boxes toward creating the PDF,
but gave me no clue while it was failing.
2. I also had problems with Acrobat X on Windows 7 64-bit. I was getting
no PDFs. It turned out that Acrobat updates, both 10.0.1 and 10.0.2 were
trashing the port setting for the Adobe PDF printer and setting it to
COM1:! It was necessary to delete Adobe PDF printer and do a repair
install to fix the issue.

Hmmm. Thanks, Mike. I will definitely check out those possibilities,
especially since, whenever I print fron FM (or try to print to pdF), I get a
notice that "Your font information has changed." The file still prints fine
from FM, but maybe that's a clue to one of the situations you mention.

cal
___


You are currently subscribed to framers as arch...@mail-archive.com.

Send list messages to framers@lists.frameusers.com.

To unsubscribe send a blank email to
framers-unsubscr...@lists.frameusers.com
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to listad...@frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.

More re responses to can't get a pdf file from FM 10

2011-08-14 Thread Cal Callahan 
Mike Wickham wrote:

Two wild stabs at your problem:

1. I recall a time when I was getting no PDF generation. It turned out
that in File> Preferences> General, I had Cross-Platform File Naming set
to Macintosh on a Windows computer, and my file name was one character
too long for the Mac 31-character (or whatever) limit. FM actually let
me go through something like four dialog boxes toward creating the PDF,
but gave me no clue while it was failing.
2. I also had problems with Acrobat X on Windows 7 64-bit. I was getting
no PDFs. It turned out that Acrobat updates, both 10.0.1 and 10.0.2 were
trashing the port setting for the Adobe PDF printer and setting it to
COM1:! It was necessary to delete Adobe PDF printer and do a repair
install to fix the issue.

Hmmm. Thanks, Mike. I will definitely check out those possibilities,
especially since, whenever I print fron FM (or try to print to pdF), I get a
notice that "Your font information has changed." The file still prints fine
from FM, but maybe that's a clue to one of the situations you mention.

cal
-- next part --
An HTML attachment was scrubbed...
URL: