On Fri, Sep 12, 2008 at 7:25 AM, alinome.net <[EMAIL PROTECTED]> wrote:
>
>> > I know, but how can I put HTML tags inside a text link? I was using
>
>> Line 480 of markups.php says this:
>>
>> $label = BOLTtemplatemarkup($label, $pageLink, 'link',
>> 'vars,func,style');
>>
>> That is, only orders:vars, func, and style get processed. I changed
>> it tovars,func,style,fmt and my html tags get substituted properly.
Actually in the end, I left it vars,func,style and moved the html rule
from last of fmt to first of style.
> I never cease to wonder at the configurability of BoltWire!
:)
> Thank you for the clues. Instead of copying, I moved the span rule
> from block to style in my config.php:
>
> MarkUp('block', 'span','' ); // <span>
> MarkUp('style', 'span', '/([\\n]?)(<|<)([\/]{0,1})span(.*?)>/e',
> 'BOLTMstyles("$4", "span", "$1", "$3")'); // <span>
>
> That solved the problem. Now spans in variables are properly rendered
> in links!
>
> I don't know if <span> has to be in the block group anyway. I'll see
> if something strange happens...
I still plan to keep the core how it is. It seems to make more sense
semantically for span to be with div and p, though it could be argued
span belongs later, as a lower level formatting option. But either
way, glad it solved the problem. And I don't anticipate any major
issues for you.
> By the way, it seems the span rule doesn't accept no parameters, I
> mean: <span>bla bla</span> is rendered as text while <span
> blabla="blabla">bla bla</span> is rendeded as XHTML. A <span> with no
> parameters is not useless, it's used sometimes to apply styles inside
> special <div> or <p>. I'll note this in my to-do list to modify the
> rule.
Actually, and here it gets a bit complex... The html rule picks up the
<span></span> before the span markup rule, now that you've moved that
to lower in the order. And the html, if still a fmt will not get
processed in the link markup. Which is why you get the plain text back
out. If you move the html markup to style not fmt, it will catch the
simple <span></span> as process as desired, while the <span
attr></span> will get picked up by the span rule farther down.
Sounds a bit confusing, but in your case, just changing the html rule
from fmt to style should fix it. I'll be doing that in the next
release barring no unforseen problems, so you might as well change
this in markups.php, rather than a config file.
Cheers,
Dan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---
