🚀 go-pugleaf

Thanks for a quick answer Ole!

I'll apologize for my bad english this time. Seems like it's hard for me to get across. But at least you've tried to answer me - great!

About the missing images. The XML doesn't contain any image references (href's) at all. They're all in the document. The XML was first produced by InDesign itself (using the XML export). After the XML has been changed externally, the idea is to import it back. Is there a way to include image references in the exported XML?

Another thing is that I don't have access to the original images any longer, i.e. all the image links would break if I tried to update/relink/unlink/etc them. If this meant that all the images would get lost on XML import I'd guess that that was the main reason. But it's not like that. Some images are still there.

I'll try you comments about the copy'n'paste thing, i.e. switching documents etc.

I'd like to use the method you actually seem to prefer, i.e. placing the images once more. The problem with that is, as mentioned above, is that I don't have the original images available and don't seem to find a way of tricking InDesign to accept broken links.

Haha, with "lacking" COM support I actually primarily mean that the documentation for VB (is there any else that could be used?) isn't 100% (some things missing, like XMLElement.untagElement, others badly documented, like Rectangle.Move), but secondly and most importantly I mean that calling certain (legal) COM calls, in certain order, can make InDesign do anything from crash to freeze. Don't get me wrong, I don't think the COM support is truly bad, it's just isn't, IMHE perfect.

--
Aigars