Absolute versus Relative path for referenced graphic files-not working

[nadeemh34786614]

No matter how I import a referenced graphic into my book files, Framemaker always uses an absolute path traversing the topmost  level of the file directory. My graphics folder is in the same directory as the FM files. (an cen even copy a pic to the same directory as the book but  it will still create an absolute path the graphic starting at C:\...

[Bob_Niland]

Let's presume a document:
C:\UserName\Projects\MasterPlan.fm
which includes an SVG chart at:
C:\UserName\Projects\Images\TimeLine.svg

If you check the Graphics🞃Object Properties… of that import, the dialog likely displays:
Referenced File: [C:\UserName\Projects\Images\TimeLine.svg]
… but …
Save the MasterPlan.fm as MIF to MasterPlan.mif, and open it with a text editor.
Search for TimeLine.svg, see what the paths are for these markups:

‹ImportObFileDI `‹c\›Images‹c\›TimeLine.svg'›
‹ImportObFile `Images/TimeLine.svg'›
The FM user interface is showing you the absolute path (presumably so that you know where the object is supposed to be), but internally, it's using a relative path where it can.
I used to take advantage of this when I needed to have the same project on a Windows and on a Unix machine, where root directory syntax was utterly incompatible.
Are you encountering some portability problem?

[nadeemh34786614]

Hello Bob,

Thanks very much for taking the time to respond to my query.

If by "portability problems" you mean that when I send the source files to someone outside of my organization, they end up with broken links and gray boxes where some images ought to be...yes. But this only happens with some images--maybe 5%.

I will try your suggestion and look at what the mif file reveals. I guess I am just used to the old old interface where I could spot a file linked outside of my directory versus ones that were linked to the images folder by just looking at the path in properties.

Thanks again for shedding some light on this issue.

[FrameMaker-dk]

Regarding sending FrameMaker files to other people...  I always use Frameexperts "ArchiveES" script. When run, it will create a backup of the entire FrameMaker project along with two neat folders for linked graphics and text insets. The absolute beauty of this approach is that the Framemaker files can opened at the recipient with all links pointing to the two new folders. This is also an excellent method for getting a grip on a project which may have grown a little too many links to all sorts of places.

[magnificent_warmth6396]

Hi Bjørn. Thank you for recommending "ArchiveES". If creating an archive like this is not an option, I also have my "PathChanger" script which allows you to update graphic paths via an Excel spreadsheet. It also manages external cross-references and text insets.

[nadeemh34786614]

Interesting, will look int it, thanks!

[nadeemh34786614]

Thanks for the script recommendation Bjørn , I will try it out

[Bob_Niland]

nadeemh: …when I send the source files to someone outside of my organization, they end up with broken links and gray boxes where some images ought to be.

When I had that problem 15 years ago (FM7 era), I wrote {Unix} scripts to gather all the imports under local directories, re-write all the tags in the MIFs, and zip it all up for ftp by the translators. Paths were all relative — had to be, because there was no way to know anything about the file system context at the other end.

There are much handier tools now available, and running one is both a neat preparation, and a QA step, making sure all the document assets are accounted for.

[nadeemh34786614]

I recall some years ago I was somehow able to generate a list of all referenced images in the document, but have forgotten how I did it. Will take a look at what is available. Thanks again Bob.

[Winfried Reng]

Hi,

In your book click Insert | List (or Index) of References. Then select Imported Graphics.

Best regards, Winfried

[nadeemh34786614]

Thank you!