1 person found this helpful
InDesign does not export anchored images when exporting either as TXT or RTF formats. It exports text only.
It's not a bug, it's a design limitation.
I do find it odd that the RTF doc that gets created includes the encoded image information. And I find it even more odd that jpeg images work in the export. If InDesign does not support export of anchored images, why does it not just outright block it. Instead of allowing jpegs to work but not other image types. And including all encoded image text in the rtf doc?
I'm not really complaining about file size. But why bother to include encoded png or eps data if it won't properly work with the RTF format? It's just extra unusable data that inflates the file size of the RTF document. It seems logical to just block the data from ever being included. It would cut down on the file size and confusion from novice InDesign users like me.
Regardless, thanks for the information! The InDesign CS4 documentation only specified text & gave no detail on images. And since jpeg was working, I did not want to simply assume the omition in the doc about images was intentional. I had to be sure.
It's not the answer I would have liked, but it's an answer. And a quick one at that. Agian, thanks for the response!
When you say "anchored objects" you mean inline anchored images, right? If you say "anchored images" then we are more likely to think "custom-positioned anchored objects" when in fact "inline images inserted into text flow" are technically anchored objects as well.
I just ran a little test, and was surprised to find that your description was actually correct. I inserted a bunch of small images in various formats into my text flow and exported, and found that only the jpeg was included in the RTF. Is this Functioning As Designed? Or is it a bug?
Sorry, to clarify, I'm using "Inline" anchored objects. So yes, they are in the flow of the text.
And that's what I find so odd, jpeg works, others don't. Also Joel, if you open the .rtf file in a plain text editor like Notepad, you'll see the actual .rtf source code. And in fact, all those other images are in there, as big chunks of encoded data. But for whatever reason it doesn't show up.
Hence why I thought it was a bug...
I'm not an expert in RTF encoding, so I can't say what's different between the jpeg's that work & the png & eps that don't work. I'm guessing it's something with whatever RTF tags are being generated, since again, the actual encoded binary images at least "appear" to be there. But again, I'm not an RTF encoding expert.
Just tried it with .gif images and I saw something interesting. I had two different gif images, one worked. The other didn't.
The company I work for has technical support with Adobe. And their tech guys are saying that this IS a bug with InDesign. No timeline on when they'd fix it...
There is no way, even if this is a bug, it will ever get fixed in CS4.
I think I finally figured this out. I move a lot of docts back and forth between InDesign and Word, and oddly enough - some of the PNG files WERE exporting from InDesign to RTF, but not others. So I knew that it wasn't impossible! My client gives me Word docts created using screenshots, sometimes over 200 graphics in one doct. I make sure they are all inline with the text in Word, which keeps them inline when I place them in InDesign (although they are not "anchored objects" as such). All of the graphics were treated the exact same way, so why should some export to RTF and not all of them? I finally unembedded all the links to compare file properties, and there were absolutely no differences - except SIZE. I tested a few randomly, making some files bigger in Photoshop, and making others smaller, and that absolutely made the difference in whether they would export to RTF or not. The cutoff seems to be somewhere between 40-50 KB. So instead of discriminating against certain file types, that was just coincidental - since PNG files (and GIF) are generally so small.
But I'm still a little stuck as to the best workflow, given the quantity of image files I have in each doct. I tried creating an action in PS to change the image resolution from 72 to 150, applied it to the whole folder, then updated the links in InDesign. And yes, all but the very tiniest images are now exporting to RTF, but the image quality is crappy! I would love it if someone has any advice on that.
Sorry, should have mentioned - this is InDesign CS5.
If you are upsampling screen shots, use "nearest neighbor" to keep them crisp.
Thanks so much, Peter, that saved me a lot of time rambling around the forums looking for that solution!
Addendum: PNG files that are indexed will not export to RTF, regardless of size.