On Tue, Feb 24, 2009 at 12:55 PM, Hussein Shafie <hussein at xmlmind.com> wrote:
> Why not? This is an idea. But first of all, I think we should try harder
> when attempting to convert something to an element such as DocBook 5 <link>.
True, I was just thinking that with such a facility, it would be easy
to add custom options to the wrap dialog box. These custom options
would then explicitly resolve any content model ambiguity.
> I mean, inserting a <link> works fine out of the box. This command
> automatically adds the linkend attribute (though this attribute is not
> formally required; one of linkend and xlink:href, but not both, is
> required). Why doesn't command convert do the same? We have to seriously
> check this.
Well, definitely add me to the list of users advocating for this
feature enhancement, however you end up solving the underlying
problem.
Take care,
John L. Clark
