Actually, I hadn't realized it was no longer working. But after a good
bit of hunting around I see it has to do with how vertical spacing is
handled now. Unfortunately, there is not a simple way to fix it.
I've found this series of patches you can try. It seems to get the
result you want...
1. markups.php, line 12, add the s flag so we can pick up the `\n
MarkUp('pre', 'escape', '/\`(.){1}/se', "BOLTescape('$1')"); // `escape char
2. engine.php line 725, convert `\n to <>, we can choose another
symbol if we wish... Add second line:
if ($x == '') return;
if ($x == "\n") return '<>';
3. engine.php line 1051. Convert back to simple line break. Add second line:
$out = BOLTdomarkup($out, '', $zone, '', false);
$out = str_replace('<>', "\n", $out);
It seems to be the simplest hack/workaround to get things going.
Note there is also the <nolines> ... </nolines> tag that might work in
some cases though not as convenient for simply getting rid of one line
break.
Let me know if this works and/or causes any problems. If all is ok, we
can add to the next release.
Cheers,
Dan
.
On Wed, Jun 16, 2010 at 7:45 AM, DrunkenMonk <[email protected]> wrote:
> Seriously, what is up with the line returns not being escaped? Was
> that removed on purpose? Is there another way to escape line returns
> now?
--
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.
