I have been playing a little with the jaap variation.
3 remarks at the moment:
- (strictly technical - easy(?) fix)
In the js file on line 43 the regexp for "quoted strings" reads:
/('|"|`).*?\1/
I want to propose the following regexp for this purpose, which handled multiline quotes and embedded escaping correct in my (limited) tests (UA: FF2, IE7)
/('|"|`)(?:\\\\|[\r\n]|\\\1|.)*?\1/
- (technical (?!) - no fix for now)
while testing the above with IE7 I noticed that the "autowrap" problem can not be worked around with the display settings in this browser. (A lot of linebreaks are just ignored.) Somebody who does feel more pity than me for IE7-using perlmonks might have a look into this. I didn't test IE6 for lack of availability at the moment
- (personal opinion on usefulness)
While I'm not totally convinced if I stay with highlighting on code-blocks, I found the feature quite useful with inline-code!
To activate inlinecode highlighting add || pre.className == "inlinecode" to the if condition in line 156 at the end of the js file.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|