I suspect what's happening here is that FM won't accept the relative
path because it does not exist. If you put the file in
F:\Customer\project\translation\incoming\x\x\x\x it would probably
preserve it.

On Wed, Jan 14, 2015 at 9:39 AM, Robert Lauriston <rob...@lauriston.com> wrote:
> "FrameMaker stores relative paths whenever possible so that it can
> find an imported file even when you move both the document and the
> source file—as long as you keep the files in the same relative
> locations."
> http://help.adobe.com/en_US/FrameMaker/11.0/Using/WSd817046a44e105e21e63e3d11ab7f7960b-7eac.html
> On Wed, Jan 14, 2015 at 1:34 AM, Harro de Jong
> <harro.dej...@triviewgroup.com> wrote:
>> I recently ran into an issue: we received a set of FrameMaker files for
>> translation. After we sent the translated files back to the customer, they
>> complained that all of the image paths in their files were changed.
>> They were using relative paths that had lots  of ‘parent’ references:
>> ..\..\..\..\..\..\Graphics\etc
>> When I received these files, I placed them in a directory 4 levels deep:
>> F:\Customer\project\translation\incoming\blah.fm
>> When I opened this file Frame asked for the location of external graphics. I
>> selected ‘Ignore all missing files’ and saved the file as MIF.
>> When I inspected the MIF, the graphics paths were truncated to
>> ..\..\..\..\Graphics\etc...

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
or visit 

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

Reply via email to