I suggest using the %select-atts; list in the DTD as possible arbitrary attributes, as this is what DITA support per default.
It would be very nice to have this.
It would be very nice to have this.
| Poster | Content |
|---|---|
nk4um User Posts: 3 | I suggest using the %select-atts; list in the DTD as possible arbitrary attributes, as this is what DITA support per default. It would be very nice to have this. |
nk4um Administrator Posts: 39 | Hi, Thanks for downloading our DITA Compare evaluation. Unfortunately it is not currently possible to add arbitrary attributes into the result of a comparison. We have only made use of standard DITA attributes in our output but we could look into adding more functionality for attribute output in future releases. I presume the attributes you mentioned are part of a DITA specialization. It should currently be possible to add either rev or status attributes (probably rev as it can take a configurable string as its value) as the output from DITA Compare and then transform them into the attributes you use in your specialization using an XSLT post-process. Let us know if you need any more help with this step. Regards, Tristan |
nk4um User Posts: 3 | Currently all changes are flagged using the attributes "rev" and "status". In our environment we have a lot more flagging relevant attributes. For example we use reviewid="<number>" to have a running reviewer change tracking. It would be nice to tell DeltaXML to use the attribute "reviewerid" instead of "rev" and/or status. Is that possible? |