Hi Jim...
Many search programs have problems locating text within binary files ..
some will just skip binary files entirely, others will just not do a
good job at it. I've had good luck with TextPad's "Find in Files"
command. It's very basic but doesn't seem to have problems with file
types. You might want to make sure you're not doing a case sensitive
search since it's possible that this may change on Windows.
Also .. I may be wrong about this always being visible as plain text ..
in my sample files it was, but there may be situations where it's not
the case. Just for kicks, you might try opening the file that was
skipped (that you know has the inset) in Notepad and do a Find for the
inset filename (I assume you're just searching on the filename, and not
the path since FM uses its own platform independent delimiters). If you
find it, you'll know that the search tool was in error .. if you don't
find it, then that means this is not a reliable option for locating insets.
Let me know how it goes.
...scott
Pinkham, Jim wrote:
Hmm, Scott --
Quite possibly I'm missing something. I did a search in both Windows
Desktop Search (all files in the folder in question) and Windows Grep
2.3 (all .fm files and then all files *.*). For the inset in question
(JunkTrapOps.fm), I found the actual inset file in WDS and drew a total
blank in Windows Grep. At this writing, the inset is known to be in at
least six other files. Thoughts?
Jim
-----Original Message-----
From: Scott Prentice
Sent: Tuesday, November 06, 2007 3:50 PM
To: Pinkham, Jim
Cc: framers@lists.frameusers.com
Subject: Re: Tracing the Lineage of Text Insets
Hi Jim...
A quick test shows me that the name of the referenced inset is visible
as plain text within the binary FM file (FM7.2). I can't say for sure
that this is 100% reliable, but I'll bet that it is. You should be able
to do a text search (using a reliable tool .. not the default Windows
Search) of the suspect inset host files using the filename of the inset.
The only other way I know of would be with an FDK plugin or FrameScript
that would crawl the directory structure, open each file and look for
the inset .. I don't think that such a plugin/script exists, but it
would be fairly simple to create.
Good luck!
...scott
Scott Prentice
Leximation, Inc.
www.leximation.com
+1.415.485.1892
Pinkham, Jim wrote:
I've learned of an error in a text inset for one of our manuals. It
poses the obvious question of how many other manuals may carry the
same error. Is there a streamlined way to determine which manuals may
contain a particular text inset -- short of opening all 62 books and
running the archive plug-in on each?
TIA,
Jim
_______________________________________________
You are currently subscribed to Framers as [EMAIL PROTECTED]
Send list messages to [EMAIL PROTECTED]
To unsubscribe send a blank email to
[EMAIL PROTECTED]
or visit
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com
Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.
