Mark Fletcher wrote: > Well, personally, I think it's silly to give users a ditabase template > with a generic topic inserted and make them convert the tag to something > else.
Well, in this case, we, at XMLmind, are silly because this approach is systematically used in XXE, not only for document templates but also for newly inserted elements. > To my mind, it's much better delivering empty dita tags and letting the > user insert the element they want--assuming that inserting that element > will turn off lenient mode. But you STILL didn't answer my question :-) > Are elementTemplates supposed to be available when in lenient mode or > not? Again, if they were available, it would solve the problem of the > first inserted child coming in invalid. The answer is obviously: *no* elementTemplates are not supposed to be available in lenient mode. You have found yourself that they are not available in lenient mode. This means that, unless you found a *bug* (in which case, I would have thanked you for finding it), elementTemplates are *not* supposed to be available in lenient mode. > Of course, the best solution to this problem (possibly avoiding the need > for lenient mode altogether) would be to prompt the user when there is a > choice of required elements. A number of other editors have this > feature. This is exactly what we have chosen *not* to do because we *hate* this behavior. The rationale of our design is obvious: - Most of the time, the simplest choice is the right choice (plus elementTemplates may override this automatic choice). - Replacing the wrong automatic choice is as tedious for the user than being prompted each time a choice is to be made. --> XMLmind XML Editor is designed as follows: if we, XMLmind people as heavy-duty XML Editor users, like to use our own product, *may* *be* other will like it too. --> XMLmind XML Editor is not designed as follows: other editors have such and such feature and therefore our product must have it too.
