Moving Documents That Link to Images in Word
A .docx document stores each linked image as a full path, for example D:\Project\Images\a.png. When you move the documents and their images to another folder, drive, or computer, that path no longer exists. When ePublisher converts a document and a linked image is not at its stored path, ePublisher looks for the image relative to the document's current folder:
It looks for the end of the stored path, the folders and the file name, below the document's folder or one of the folders above it. The longest match is used.
It uses the file name alone only when the image is in the document's own folder.
For example, a document saved as D:\Project\Chapter\doc.docx links to D:\Project\Images\a.png. After you move the whole Project folder to E:\Moved\Project, ePublisher uses E:\Moved\Project\Images\a.png, and the generation log notes the substitution:
The picture linked in the document 'E:\Moved\Project\Chapter\doc.docx' was not found at 'D:\Project\Images\a.png'. Using 'E:\Moved\Project\Images\a.png' instead; the document appears to have been moved together with its images.If different files match equally well, for example two Images\a.png files at the same depth, ePublisher leaves the link unchanged, and the generation log shows a warning that names two of the files. Move or rename the extra files, or update the link in Microsoft Word.
ePublisher changes only its own copy of each document. Your source documents are not changed, and Microsoft Word shows the old links until you update them in Word.
If an image is both stored in the document and linked (Insert and Link) and ePublisher finds the linked file, the output uses the linked file, not the stored copy.
ePublisher does not look for the following images:
Images linked from a network location, such as
\\server\share\Images\a.pngImages whose relative links do not resolve from the document's folder
Images inserted with
INCLUDEPICTUREfields