I figured out that the textbox (whose content isn't exported) doesn't show 'Incopy' option in its content menu. Can anyone tell me how this can be done ?
Export to IDML and compare the IDML attributes of the textframes.
I compared the attributes for textframes. Both textframe has similar attributes. I done some more test and figured out that 'Incopy' option is not visible becuase the textframe contains tagged content bound to a xml. I was able to export this textframe as incopy document as soon as I untag the frame, though my requirements don't allow me to do so. Any ideas how to export this textbox as a Incopy (icml) without disturbing the XML structure ?
Well, this sounds like a bug, and you'll need to contact Adobe Support and get a bug filed in order to have it fixed.
If you can produce a small reproducible test case and export it as a snippet, you could paste it here and we could look at it.
You can probably generate the InCopy ICML file by hand though. Export your story as a snippet, then remove the XML, then export your story as InCopy. Then edit the ICML file in a text editor and paste in the appropriate portions of the snippet.
This is not an acceptable workflow and I don't know how far it is going to get you (perhaps InCopy will choke on the same XML for the same reasons?).
You are using the current version? 7.0.4 or 7.5.1?
I again encountered same problem a few days back and figured out what is going on.
Linked tagged textframes which are tightly bound with xml structure can not be exported to InCopy only when xml structure has missing start or end tags.
This case may arise when content xml is poured in the linked textFrames then part of the content(para or image caption) is moved into different non-linked textframe. This action leaves a placeholder tag in linked frame(used to move content back in place if, ever, newly created frame was deleted) which create inconsistency in xml structure.
Is this fixed InDesign CS6 verstion. Can you anyone tell me on this?
There were fairly few changes in XML from CS5.5 to CS6, so I would doubt it.
But we never had a really clear reproduction case for this problem from Divya Jain, so I dunno.
this issue also affect my workflow.
is have any alternative?