* When you convert the text selection to a <ulink url=""> (or <link
xlink:href=""> or <a href="">), you use the generic convert command.
This command, which only uses the schema of the document, does not know
what is a ulink and therefore cannot do anything special for ulinks.
* Using a specific convert command for ulinks and the generic convert
command for other elements would be very inelegant and hence expensive
to implement.
* A practical way to support what you want is by implementing a
long-delayed XXE feature: *dynamic* element templates.
The facility you want would be implemented simply by defining the
following element template in the configuration file:
---
<elementTemplate name="autoURL" selectable="override">
<ulink xmlns=""
url="{if(contains($selectedChars,'://'),$selectedChars,'???'}"
></ulink>
</elementTemplate>
---
Notice the XPath expression found in "{}" brackets.
References:
- http://www.xmlmind.com/xmleditor/_distrib/doc/commands/convert.html
-
http://www.xmlmind.com/xmleditor/_distrib/doc/configure/elementTemplate.html
The problem is that *dynamic* element templates, while potentially very
useful (e.g. automatic IDs for tables and figures), won't make us sell
more copies of XXE. Therefore if you want this feature in the near
future, then you are welcome to sponsor its development. (FYI, this kind
of feature sponsoring already happened two times: the "View > Display
Images" submenu and the "-compare" command-line option. More information
in: http://www.xmlmind.com/xmleditor/customization_service.html )
On 05/30/2013 05:03 PM, Philippe Nobili wrote:
Just a tiny suggestion for improving the Wrap Ulink/Toggle Ulink in XXE
(DocBook-4 editing),
It would be quite handy when the text selection starts with 'ftp://',
'http://', 'file://', to directly initialize also the @url attribute
with the selected text when wrapping the text within a <ulink> element
instead of doing that in a second step. This would save quit a bit of
clicks, in particular when you have a big collection of URLs addresses
in clear in your document.
Paul Vinkenoog wrote:
I would find that very practical, too. On the rare occasions where the URL
attribute should be different, you can always correct it manually (in the same
time that it takes to overwrite the '???' in the current situation).
I would also do this for the https, nntp, gopher and mailto protocols, and
possibly others.
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
