Well, if you use both, my plugin and the Wrap plugin, then simply don't activate <span>
in order to avoid a conflict :-)
As I mentioned, the long-term target is to merge a lot of the code back into the Wrap plugin, and then change this plugin so that it depends on Wrap to work. In this situation, there is also no conflict ... however, during the development it is not really feasible to wait for a new Wrap release every time I make a little change to the shared code, so for now, this dependency does not exist (but I still need to test the behaviour of <span>
s...)
But the reason why the conflict exists is that there isn't really an alternative for <span>
. It is the most generic inline element that HTML has, and that is just what makes it so useful. I would rather avoid "inventing" a new HTML tag (that will then be rendered as <span>
to bypass the conflict with Wrap; Firstly, it will just cause more confusion and incompatibilities in the long run, and secondly this won't be an issue later anyways.
An important aspect of trying to move fast is also that I have quite an extensive body of articles which are at the moment relying on the <html>
mechanism being available. If I want to be ready for a future DokuWiki without this functionality, I need to start cleaning them up now... so I am already testing if it all works as intended, and now I have time to request new features (from myself :-) so that it all works smoothly by the time a new DW version is out. And, yes, this means I need to fix all my <span>
tags, too...
Just to give an example: this has prompted me to put a need for title
attributes on my agenda. This will be one of the next issues I plan to work at...