Skip to main content
K
Kenneth5FBC
Inspiring
April 22, 2021
Question

Maintaining Link Integrity When Creating PDFs and Moving Files

  • April 22, 2021
  • 2 replies
  • 441 views

Currently, I have my FrameMaker documents in separate folders (different paths) on a dev (offline) internal server.  I am creating links from one FrameMaker document to the other in my book creation.  After the books are complete, I have to create a PDFs for each book and upload these books into the SAME folder and maintain the PDF links from one book to the other.  So how would this be done?

    This topic has been closed for replies.

    2 replies

    Jeff_Coatsworth
    Community Expert
    Jeff_CoatsworthCommunity Expert
    Community Expert
    April 22, 2021

    I believe (not having cared about this for my projects) that if you had a Projects folder and had it laid out like \Projects\ProjectA\ and \Projects\ProjectB\ - if you created PDFs inside each "ProjectX" sub-folder, they would maintain their links if their final location also was in a \Projects\ structure.
    I suggest you do up a simple POC to test it.

    Jeff_Coatsworth
    Community Expert
    Jeff_CoatsworthCommunity Expert
    Community Expert
    April 22, 2021

    You'd need to maintain the FM docs and resulting PDFs in the same relative structure in relationship with each other - it would be easier if they were in the same folder (as separate folders). If that can't be done, then you may have to look at editing the links in the resulting PDFs.

      K
      kweather9122
      Inspiring
      April 22, 2021

      So, if I had all Frame files in the same folder, and both PDF's in the same folder, I should be able to transfer to any folder on the LAN with integrity?  We use a repository for LAN uploads, so I have no idea what the folder structure or name is on the LAN.  Someone else posts the files.

      Bob_Niland
      Community Expert
      Bob_NilandCommunity Expert
      Community Expert
      April 22, 2021

      kweather9122: Someone else posts the files.

      You may be doomed.

      PDF-to-PDF (or other asset) links generally need to be:

      • Fully qualified URLs
        (which could be to a portable asset ID, resolved by server code when requested)
      • Same dir ./
      • To ./child_dir/, preserved through to serving
      • Maybe ../../relative/, but never specifying a drive path (C:\), or even //root

      In a previous assignment, the location of the public documents was well known in the enterprise, and stable, but I still avoided having one PDF link to another. Even if you get IT to promise stability, mergers & acquisitions happen.

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