Number 2 is what I did. Yup that was it.? 

Thanks Rick.? Much appreciated.? 


-meg



________________________________
 From: Rick Quatro <rick at rickquatro.com>
To: 'meg miranda' <megmiranda at yahoo.com>; framers at lists.frameusers.com 
Sent: Friday, February 17, 2012 4:51 AM
Subject: RE: hard coded path names for imported graphics and x-refs


Hi Meg,
?
There are two ways that this can happen: 
?
1) You import images from another drive or network volume; this is unlikely in 
your case.
?
2) You Save As the FrameMaker document from one drive or volume to another. 
This will create absolute paths to the graphics. This may be what happened to 
you.
?
Please let me know if you have any questions or comments. Thank you very much.
?
Rick
?
Rick Quatro
Carmen Publishing Inc.
*** 585-283-5045 *** NEW NUMBER
rick at frameexpert.com
http://www.frameexpert.com
?
?
?
From:framers-bounces at lists.frameusers.com [mailto:framers-bounces at 
lists.frameusers.com] On Behalf Of meg miranda
Sent: Thursday, February 16, 2012 9:43 PM
To: framers at lists.frameusers.com
Subject: hard coded path names for imported graphics and x-refs
?
Hi all,
?
We're using Frame 10 and doing unstructured books.
?
We have source files out on a network drive, but we do often copy the files to 
our local machines so that we can work remotely and offline on them.
?
So now I have a book out on the network drive that somehow is referencing 
images on c:\dic\mybook\userguide\images\button.jpg instead of 
\images\button.jpg.? A similar thing has happened to some of the x-refs in 3 of 
the chapters.? We are getting specific references instead of relative 
references.
?
Does anyone have any suggestions why this behavior is happening? or how to fix 
it without having to open each chapter file and repoint the graphic directory?
?
I think I'm most conserned about understanding why it is happening, so that I 
can tell our team how to avoid this problem.
?
thanks,
meg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.frameusers.com/pipermail/framers/attachments/20120217/10c0b8ee/attachment.html>

Reply via email to