🚀 go-pugleaf

Pam,

I do not believe there is a DROP in conversion tables; however, you can write your conversion table so that it does not wrap specific objects (such as certain paragraph formats) in elements. The result is a structured file in which some text is outside the elements, which is not allowed in a well-formed structure. When you validate the file, Frame will find these pieces of text, at which point you can delete them. But to my knowledge, you cannot set up the conversion table to simply remove content from the file.

Your second question is not clear to me. Frame uses the same Identifier (G:) to an anchored frame, independent of whether it has Frame-created content (created with the drawing tools), inserted content, or referenced content. So, if you plan to have ONE element for all content contained in anchored frames, then you can use the conversion table to wrap the G: objects in that element. I am guess at what it is you want to do here.

Van

I handle these by wrapping them in a DELETEME element. I then write some of the rules in my conversion table to allow these to wrap into other elements that I believe will end up being their parents in the resulting structure (to avoid stopping the wrapping process too soon when Frame hits these unexpected elements).

I use this also for the M:Cross-Ref to ensure these buggers are wrapped and can easily be deleted. Otherwise, they can cause scruffy process instructions to appear during a Save As XML.

Good luck,

Kay

Scruffy PIs? The horror. :)