As a rule of thumb, when something feels like a hack on the markup side, I think to myself "Could/should this be handled on the processing side?" So how about having logic in the transformation that f

Here is an example usage that maybe can go into the next version of the spec.

#DITAv2-0

Some editors can be customized (relatively easily, and by you) to recognize any element as an image to be displayed while editing. XMetaL can do this. I don't know about oXygen. In XMetaL's case, with

#bookmap #images

Hi Ron, The first link you mentioned cannot be "fixed" per se. At least, that page can never be changed. It is a specification, not "documentation". FWIW, there is a newer version of the DITA specific

#admin

A challenge we all face as producers of documentation about documentation is the overloading of some of the terminology in our industry. I think we all get complacent and become guilty of carelessness

#CSS #Oxygen #PDF

Why do you think you need to specialize DITA? That sounds flippant, but isn't meant that way; I want to know what is motivating you to think that this is important. I would suggest that if your proces