Our CMS product writes in all default DTD attribute values when persisting documents to the db. This means that our @class attributes end up having actual values. When using XXE's Convert command, the element name is switched, but the @class attribute value remains the same, which causes the new element to be misidentified during the @class-based XSL transforms.
I see that the treatment of attributes during Convert is clearly documented: "When a single element is selected, all its children (but not its attributes) are transferred to the result of the conversion." But do you see this as something that XXE should make allowances for, given the strong association between element name and @class value in DITA? For example, perhaps the configuration could let you define attributes to be stripped during Convert, or something similar.
-- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
