Graphic import > object facets problem

[Fred Ridder]

Chris Coggins wrote:


>What is happening on the problem user's computer is that the frame file he 
>generates 
>retains the object faces PDF and EPSI, and also adds a FrameImage facet after 
>going 
>through the same steps listed above. His frame files are enormous, 19 megs for 
>the same 
>file used above, and the resulting PDF files are also huge (17megs). When 
>compiled into a 
>complete book, he's generating 200meg PDFs whereas the rest of us are only 
>putting out 
>10meg books.
>
>Can someone help me understand what's happening during the import/embed 
>process 
>and why we're getting different results across our users?

Generation of a FrameImage version of imported graphics is an option that is 
enabled/
disabled from the Preferences dialog It's in the Compatibility Preferences 
section and it's
called somethng like Save FrameImage with Imported Graphics. 

FrameImage is an archaic and largely obsolete method for ensuring cross-platform
portability of graphics. The idea was that if FrameMaker stored a version of 
the graphic 
in a format that it was guaranteed to understand, it wouldn't matter whether 
the original
graphics was in a UNIX-specific, Windows-specific, or Mac-specific file format. 
But since
only the Windows version of FrameMaker is still a living product, there's no 
point to 
FrameImage. And that's doubly true if you're already usiung PDF, which is 
highly portable.

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

RE: Graphic import > object facets problem

[Fred Ridder]

Chris Coggins wrote:
 

>What is happening on the problem user's computer is that the frame file he 
>generates 
>retains the object faces PDF and EPSI, and also adds a FrameImage facet after 
>going 
>through the same steps listed above. His frame files are enormous, 19 megs for 
>the same 
>file used above, and the resulting PDF files are also huge (17megs). When 
>compiled into a 
>complete book, he's generating 200meg PDFs whereas the rest of us are only 
>putting out 
>10meg books.
>
>Can someone help me understand what's happening during the import/embed 
>process 
>and why we're getting different results across our users?

Generation of a FrameImage version of imported graphics is an option that is 
enabled/
disabled from the Preferences dialog It's in the Compatibility Preferences 
section and it's
called somethng like Save FrameImage with Imported Graphics. 
 
FrameImage is an archaic and largely obsolete method for ensuring cross-platform
portability of graphics. The idea was that if FrameMaker stored a version of 
the graphic 
in a format that it was guaranteed to understand, it wouldn't matter whether 
the original
graphics was in a UNIX-specific, Windows-specific, or Mac-specific file format. 
But since
only the Windows version of FrameMaker is still a living product, there's no 
point to 
FrameImage. And that's doubly true if you're already usiung PDF, which is 
highly portable.
 
-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.

Graphic import > object facets problem

[Chris Coggins]

Hi,

Thank you for being here. I am trying to troubleshoot a graphics import
problem with one of our frame users that is not occurring with any of our
other frame users. I don't fully understand how frame embeds graphics into
the document so I need some help determining whether these behaviors are
normal.

All are using Framemaker 10, the problem user is on Windows Vista working
across the network (Framemaker is installed on local computer, files are
hosted elsewhere), the others are on XP working on their local computers
exclusively.

This is what I discovered through experimentation on my own computer (XP,
working locally):
When importing a graphic, I use the "copy into document" setting, and
import the graphic which itself is in PDF format. I shrinkwrap it, then
save the frame file.
At this point, the objects properties pane reports a PDF facet.
I then save the frame file as PDF using the "smallest file size" filter,
and then save the frame file again.
At this point, the objects properties pane reports both a PDF and EPSI
facet.
I then close the frame file and re-open it. At this point, the objects
properties pane reports a PDF facet only.
The resulting frame filesize is approx. 400k.
I believe this is the preferred result for our needs.

What is happening on the problem user's computer is that the frame file he
generates retains the object faces PDF and EPSI, and also adds a FrameImage
facet after going through the same steps listed above. His frame files are
enormous, 19 megs for the same file used above, and the resulting PDF files
are also huge (17megs). When compiled into a complete book, he's generating
200meg PDFs whereas the rest of us are only putting out 10meg books.

Can someone help me understand what's happening during the import/embed
process and why we're getting different results across our users?

Any help would be appreciated.
Thanks,
Chris
___


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.

Graphic import > object facets problem

[Chris Coggins]

Hi,

Thank you for being here. I am trying to troubleshoot a graphics import
problem with one of our frame users that is not occurring with any of our
other frame users. I don't fully understand how frame embeds graphics into
the document so I need some help determining whether these behaviors are
normal.

All are using Framemaker 10, the problem user is on Windows Vista working
across the network (Framemaker is installed on local computer, files are
hosted elsewhere), the others are on XP working on their local computers
exclusively.

This is what I discovered through experimentation on my own computer (XP,
working locally):
When importing a graphic, I use the "copy into document" setting, and
import the graphic which itself is in PDF format. I shrinkwrap it, then
save the frame file.
At this point, the objects properties pane reports a PDF facet.
I then save the frame file as PDF using the "smallest file size" filter,
and then save the frame file again.
At this point, the objects properties pane reports both a PDF and EPSI
facet.
I then close the frame file and re-open it. At this point, the objects
properties pane reports a PDF facet only.
The resulting frame filesize is approx. 400k.
I believe this is the preferred result for our needs.

What is happening on the problem user's computer is that the frame file he
generates retains the object faces PDF and EPSI, and also adds a FrameImage
facet after going through the same steps listed above. His frame files are
enormous, 19 megs for the same file used above, and the resulting PDF files
are also huge (17megs). When compiled into a complete book, he's generating
200meg PDFs whereas the rest of us are only putting out 10meg books.

Can someone help me understand what's happening during the import/embed
process and why we're getting different results across our users?

Any help would be appreciated.
Thanks,
Chris
-- next part --
An HTML attachment was scrubbed...
URL: