Skip to main content
C
Carlo Fontanesi
Known Participant
February 27, 2018
Answered

About relative paths in FM11

  • February 27, 2018
  • 2 replies
  • 880 views

Hi all,

in these last years I worked for a client with some files with images linked like something like:

..\..\..\..\Folder1\Folder2\image.jpg

The client never gives us images, but when he receives back his files the links work good and the files find their images without any other kinf of job.

Last time I worked not on a lan, but on my C: drive.

Giving bak the files to the client he found that links were corrupted.

The links look like:

..\..\..\Folder1\Folder2\image.jpg

(a "..\" was lost)

I did some test working with files on the lan and in local drive, and found that it happens: working on local drive files loose a part of the path.

Does anybody has experience of that?

Thanks

This topic has been closed for replies.
Correct answer Stefan Gentz

The reason is not the local drive, but the folder structure and nesting depth of folders. So, probably you had fewer folders between the root of your local drive and the folder which hosts the FrameMaker files. When searching for graphics on your LAN drive, FM could "go up" four levels and then "go down" into \Folder1\Folder2\. On your local drive FM could "go up" three folder levels before it reached the root of the drive.

If you put the FM file one folder "deeper" it will work again.

2 replies

A
Adobe Employee
Amitoj
Adobe Employee
March 2, 2018

We are trying to see if we could have an absolute path instead of relative path for the next release. With an absolute path, it would be much easier to manager and copy paste same onto windows explorer.

thanks,

Be.eM
Be.eM
Inspiring
June 2, 2018

Amitoj  schrieb

We are trying to see if we could have an absolute path instead of relative path for the next release. With an absolute path, it would be much easier to manager and copy paste same onto windows explorer.

thanks,

Oh no. Please don't. Never ever. This would immediately ruin perfectly working translation management for thousands of documents in dozens of languages and take me to what I absolutely *hate* on Indesign. Always referring to the wrong image folders when working on a newly translated version of a document. The relative path feature is one of the absolute highlights and essential functions of FrameMaker which needs to be maintained.

Bernd

    S
    Stefan GentzCorrect answer
    Legend
    February 27, 2018

    The reason is not the local drive, but the folder structure and nesting depth of folders. So, probably you had fewer folders between the root of your local drive and the folder which hosts the FrameMaker files. When searching for graphics on your LAN drive, FM could "go up" four levels and then "go down" into \Folder1\Folder2\. On your local drive FM could "go up" three folder levels before it reached the root of the drive.

    If you put the FM file one folder "deeper" it will work again.

    C
    Carlo FontanesiAuthor
    Known Participant
    February 27, 2018

    Thanks Stefano,

    it works (of course...)

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices