acknak wrote:
Isn't this similar/same as what happens if you use linked images and send the document to someone without the images? If the (linked) image is missing, Writer displays a red frame of the same size as the image.
Yes, it is similar. This was the original reason for the InfoFrames. Someone wanted to create a PDF with frames instead of images (but like in LaTex where it shows the image filename) So that was the first idea, to simply move the folder with the images out of the way. But this of course doesn't work with embedded images. So I wrote a simple macro, that just destroys all image links, embedded as linked. The PicInfoFrames just are a nicer representation with the extra of images names and Filenames.
acknak wrote:
I assume there is a way to replace the svg placeholders with the actual images again, right?
I'm afraid not. So at the moment you must save the file as a standalone version. I had a version that could restore the original images but wasn't absolut reliable or easy to handle. In fact it was a combo with the PicExtract, because if your document has embedded images and you replace them with Infoframes they are gone
So you must at first extract them and make them linked images to be able to restore later. But then the Infoframes would show wrong information (=embedded) where as the images now were linked. Of course you can make them show the right info but as consequence InfoFrames would only make sense on documents with linked images.
I came to a point where this simple extension had to become quite complex and difficult to explain to the user.
At the moment you can use PicInfoFrames to just create a slick document or PDF. For real document exchange with reliable restore options a separate version would need to be created.
