🚀 go-pugleaf

Hello,

fm-xref is defined in our EDD; it's a suboptimal element to use but supposedly the more effective conversion from basic FrameMaker crossrefs. It is associated with a number of possible formats defined in our template- in terms of support files, all 4 of the basic topic types are the same. I am also pretty confident that it is not a structure issue, since placing both fm-xref and image elements under reference elements within a document that contains a parent topic or task element still causes the problem.

I'm not sure what could cause a specific change in file handling based on the first (non dita) element in the topic. AFAIK the read-write rules are not at fault here, and ditafm.ini controls only global import/export options so I don't think it's to blame either.