Globally changing the path to referenced files

[Menahem Rosen]

Background: I sent a FM book to a translation agency, which returned the
translated files as a FM book. They convert to mif and use Trados for
the translation, then convert back and place the files into my book.
There were no problems opening the files, displaying graphics, and the
cross-refs were good. Just as I had expected. 
 
Problem: After discovering a mistake in one of the files, I asked the
agency to re-do it. That is, just one file of the book. They sent me the
fixed file, but the references to all of the graphics (and x-refs) don't
work, because the path of the referenced file (which is still right) is
preceded by the entire path on the computer that generated the fm file.
 
One solution: I saved the problematic file as mif, opened it in Notepad,
and deleted the part of the path that I didn't need. 
 
There were a lot of graphics, so It took some time (even using "Replace
All"), and Notepad nearly hung on me. When left for a while, it
eventually came back to life and finished the job. 
 
Questions: 
1. Is there a faster, better way to do this? From within FM? 
2. I don't know how this problem was caused, but I would like to suggest
something to the translation agency so that this can be avoided in the
future. Any suggestions?
3. When experimenting in the mif (text) file, I noticed that the
referenced graphics are represented by two consecutive lines. For
example...
   <ImportObFileDI
`<c\>graphics<c\>E260<c\>Eden<c\>Photos<c\>Eden260_cropped.png'>
   <ImportObFile `graphics/E260/Eden/Photos/Eden260_cropped.png'>
What solved the problem for me was changing the first line
[ImportObFileDI `<c\>graphics...]
I did not have to change the second line. So, my question is: what is
the second line for, and should I have changed this too? (Could it be
for opening the files on Unix systems?)
 
TIA for any tips & suggestions.
 

Menahem Rosen

Senior Technical Communicator

Objet Geometries





 
 
************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************