When you switch to 3.xx, you will need to make sure you restore this line: else $term = $args[1];
As for the other two, I'm not so sure one way or the other about whether or not to add the word boundaries. (\b). Guess it depends on whether or not you want nation to be highlighted in international. Cheers, Dan P.S. Good to see you hacking the php!!! 2009/4/7 Linly <[email protected]>: > > I've changed three lines in the highlight.php for utf output: > > <code> > <?php if (!defined('BOLTWIRE')) exit(); > > function BOLTFhighlight($args) { > global $pageLink; > if (isset($args['page'])) $page = $args['page']; > else $page = $pageLink; > $content = BOLTloadpage($page); > if (isset($args['term'])) $term = $args['term']; > else $term = $args[''][0]; > //was "else $term = $args[1];" > if (isset($args['color'])) $color = $args['color']; > else $color = 'yellow'; > $fmt = "<span style='background: $color;'>$term</span>"; > $pat = "/^(.*$term.*)$/im"; > //was "$pat = "/^(.*\b$term\b.*)$/im";" > preg_match_all($pat, $content, $match); > if (isset($args['count'])) $match[0] = array_slice($match[0], 0, $args > ['count']); > $matches = "<ul><li> " . implode("<li> ", $match[0]) . "</ul>"; > return BOLTescape(preg_replace("/$term/i", $fmt, $matches)); > //was "return BOLTescape(preg_replace("/\b$term\b/i", $fmt, > $matches));" > } > </code> > > The template.highlight is: > > <code> > [[books.{+p2}|+]] - {books.{+p2}::classification} > [(highlight "$text" count=5 page={+p})] > </code> > > Cheers, linly > > On 4月8日, 上午1時02分, The Editor <[email protected]> wrote: >> I would have to see more information. I don't know the source code >> calling the highlight template, nor how your info page is setup. As >> far as I can see, everything is working fine for me. >> >> Cheers, >> Dan >> >> 2009/4/7 Linly <[email protected]>: >> >> >> >> > Bug report: >> >> > Hi Dan, >> >> > The Highlight plugin was broken in this version. Please take a look on >> > my /jargon/ sitehttp://txtray.net/jargon/ >> > Search a word, say, tree, to see the output. >> >> > The normal is ok. >> >> > Cheers, linly >> >> > On 4月7日, 下午10時07分, The Editor <[email protected]> wrote: >> >> Just bug fixes, including a new work around for the info report >> >> problem discussed recently that does not involve any changes to >> >> existing sites. Turns out it wasn't that hard after all! >> >> >> * Bug in comm2func function, when there is no value in the command field. >> >> * A bug in how the sitemail variable is assigned its value >> >> * Slight fixes in a couple functions throwing php errors in * certain >> >> situations. >> >> * Changed order of code and /= markups to get better rendering. >> >> * Added spaces to code.snippets action list, and modified css to allow >> >> linewrapping as needed. >> >> * Fixed bug in include function when no parameters included. >> >> * Fixed bug in info report when multiple fields have the same value. >> >> >> So far I've resisted making changes and adding new features on at >> >> least a couple occasions. I'm really hoping this release will hold >> >> steady for a good loooonnnngggggg time. >> >> >> 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 -~----------~----~----~----~------~----~------~--~---
