Skip to main content
Participating Frequently
May 13, 2010
Answered

telling from a source file what files it is imported into

  • May 13, 2010
  • 2 replies
  • 1716 views

I am using FrameMaker 9 for windows xp and I as wondering, Is there any way of telling from a source file what files it is imported into?

    This topic has been closed for replies.
    Correct answer Arnis Gubins

    Nope. No info is stored in FM files indicating where they be imported into. However, there is info indicating what files have been imported by reference or as insets.

    2 replies

    Participating Frequently
    May 20, 2010

    Yes, there is a great feature in SQUIDDS TOOLBOX for FrameMaker 7, 8 or 9 with 'Book/Dokument Transfer':

    • determine in all the book components (chapters and generated lists) the source files of referenced graphics and text modules (text insets)
    • decision for generation a report only or  transfer all components
    • adapt the paths for referencing the source files to the new directory structure ...
    • generate in the source and target directory  of the book file a report file called BookNameTRANSFER.txt

    Feature 'Server Analysis' makes a list over all referenced files of a directory of a server. Very important for repeatedly imported files ...

    - Georg

    Arnis Gubins
    Inspiring
    May 20, 2010

    Georg,

    As far as I can tell, your products do NOT specifically do what the original poster has asked in this case, i.e. directly and explicitly state what files a given inset has been imported into. They (Book Transfer and Server Analysis) list the reverse condition: what files have been imported into a given file/book. The required analysis then has to be manually done by the user, which is no better than the user generating a LOR (list of references - text insets) for all of their books and then manually compiling the same information (without the extra cost of acquiring a product).

    Please correct me if I am wrong on this!

    Also, please only reference your products when they address the specific issues stated by the user, not general (vaguely and distantly) related features of the product. The Squidds Toolbox is an excellent collection of tools that do many things very well and I do recommend it for consideration to my clients. However, if you keep plugging your product in unrelated ways, I and other hosts will consider this Forum spamming and have to deal with it according to the Forum guidelines (which could include deleting all such messages and possibly banning the poster). There is no issue when your product directly solves a problem/issue posed by a poster.

    Arnis Gubins

    FrameMaker Forum Host

    Participating Frequently
    May 20, 2010

    Arnis Gubins wrote:

    Georg,

    As far as I can tell, your products do NOT specifically do what the original poster has asked in this case, i.e. directly and explicitly state what files a given inset has been imported into. They (Book Transfer and Server Analysis) list the reverse condition: what files have been imported into a given file/book. The required analysis then has to be manually done by the user, which is no better than the user generating a LOR (list of references - text insets) for all of their books and then manually compiling the same information (without the extra cost of acquiring a product).

    Please correct me if I am wrong on this!

    Also, please only reference your products when they address the specific issues stated by the user, not general (vaguely and distantly) related features of the product. The Squidds Toolbox is an excellent collection of tools that do many things very well and I do recommend it for consideration to my clients. However, if you keep plugging your product in unrelated ways, I and other hosts will consider this Forum spamming and have to deal with it according to the Forum guidelines (which could include deleting all such messages and possibly banning the poster). There is no issue when your product directly solves a problem/issue posed by a poster.

    Arnis Gubins

    FrameMaker Forum Host

    I haven't use these tools, but Arnis' description of what they and where they doesn't fulfill the poster's need, suggests a next step or product enhancement: create a feature that extracts the information that identifies which files are referenced by container files (aka text insets,) and collate that into a separate report of referenced files and their container files.

    I'm thinking that it might be roughly possible now, depending on how LOR entries are defined. It could be possible to export the LOR-text inset reports as text files, and sort them by inset document, in a spreadsheet or other tool (the DOS Find and Sort commands performed in a Windows command-line window, for example.)

    HTH

    Regards,

    Peter

    ____________________

    Peter Gold

    KnowHow ProServices


    Peter,

    Actually, what this requirement is asking is defined by the IOR (index of references) capability. If one edits the default Reference page entry for the IOR to add system filename building block (short or full path) to the pagenum entry, it will tell you what file(s) the inset is in within each book.

    Now if one builds a super-book of all files in a user's work area or perhaps the new book-within-book capability of FM9 will allow searching all source files from a single run, then this may be the way to go. I can't test this right now, but may be tonight I can.

    Arnis

    Arnis Gubins
    Arnis GubinsCorrect answer
    Inspiring
    May 13, 2010

    Nope. No info is stored in FM files indicating where they be imported into. However, there is info indicating what files have been imported by reference or as insets.

    Participating Frequently
    May 14, 2010

    That's what I figured but I decided to ask just to make sure.

    Brainiac
    May 15, 2010

    When I was working with a lot of insets, I tried to keep to track of them with a list of markers generated from the book. I considered being more diligent about storing information in the document properties of the inset files, but didn't persist ...