Extension talk:SyntaxHighlight GeSHi/Archive 2007

From mediawiki.org

download problems

The download link doesn't exist.
IS this the correct link? http://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/SyntaxHighlight_GeSHi/
21:01, 4 April 2007 (UTC)

It was renamed a few days ago, thanks for catching this. -- Duesentrieb 23:58, 4 April 2007 (UTC)[reply]

Fatal error: Call to undefined method ParserOutput::addHeadItem

I just tried installing this extension, and I'm pretty sure I followed the directions exactly, but I'm getting the error:

[04-Apr-2007 21:01:29] PHP Fatal error:  Call to undefined method ParserOutput::addHeadItem() 
in ...\extensions\SyntaxHighlight_GeSHi\SyntaxHighlight_GeSHi.php on line 113

-- 02:09, 5 April 2007 (UTC)[reply]

yes, I'm getting this one to – just that now it's line 144. Might it be that the PHP version is not sufficient? My PHP version is 4.4.4 - what is the minimum version required for SyntaxHighlight GeSHi? --Leo141 15:05, 29 June 2007 (UTC)[reply]
Oops, how could I oversee that there are some answers on this here ... The workaround at solution for me works for me too. --Leo141 17:08, 29 June 2007 (UTC)[reply]


Fatal error: Call to undefined method ParserOutput::addHeadItem() 
in ...\wiki\extensions\SyntaxHighlight\SyntaxHighlight_GeSHi.php on line 113

I'm work with windows apache2 & php5, and i have already tried to take some older versions, but nothing changed. --IP 5 April 2007

I think ParserOutput::addHeadItem was added quite recently - so the current version of this extension only works with the current development trunk. You will have to use an older version with MW 1.9. -- Duesentrieb 11:25, 5 April 2007 (UTC)[reply]
Yea, try this version: [1] -- Duesentrieb 11:28, 5 April 2007 (UTC)[reply]

Has there been a resolution to this yet?

I was having the same issue as above:

Fatal error: Call to undefined method ParserOutput::addHeadItem() in 
...\wiki\extensions\SyntaxHighlight\SyntaxHighlight_GeSHi.php on line 113

Attempted this:

Yea, try this version: [2] -- Duesentrieb 11:28, 5 April 2007 (UTC)[reply]

which led to:

PHP Fatal error:  require_once() [<a href='function.require'>function.require</a>]: 
Failed opening required '/var/www/html/devwiki/extensions/SyntaxHighlight_GeSHi/SyntaxHighlight.i18n.php' 
in /var/www/html/devwiki/extensions/SyntaxHighlight_GeSHi/SyntaxHighlight_GeSHi.php on line 59

Is there any updates on this or am I going to have to use a different extension for this? --IP 24 April 2007

remember to download all the files here >>> http://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/SyntaxHighlight_GeSHi/ --Danny1000 21 August 2007

One Solution - rename files and variables to match calls to them

You need to rename the file "SyntaxHighlight.i18n.php" to "SyntaxHighlight_GeSHi.i18n.php"
Then inside either file make sure the names:
"efSyntaxHighlight_GeSHiMessages()" Match, pick one, and rename it and your away, not sure what version we are playing with here but its now working for me, all I care about. --IP 25 April 2007

Yes, It works for me

Thank you, who written the message above. The steps are followed

In SyntaxHighlight_GeSHi.php

First, rename the file "SyntaxHighlight.i18n.php" to "SyntaxHighlight_GeSHi.i18n.php"

Second, find this

require_once( dirname( __FILE__ ) . '/SyntaxHighlight.i18n.php' );

change to

require_once( dirname( __FILE__ ) . '/SyntaxHighlight_GeSHi.i18n.php' );
and find this
foreach( efSyntaxHighlightMessages() as $lang => $messages )

change to

foreach( efSyntaxHighlight_GeSHiMessages() as $lang => $messages )
  • Mediawiki 1.9.2
  • The AppServ Open Project - 2.5.7 for Windows
    1. Apache Web Server Version 2.2.3
    2. PHP Script Language Version 5.1.6
    3. MySQL Database Version 5.0.24a
    4. phpMyAdmin Database Manager Version

--Roc michael 03:54, 30 June 2007 (UTC)[reply]

What about further version of mediawiki?

I try it with 1.9.3 and the latest highlight-files and get an error that look similar:

Fatal error: Call to undefined method ParserOutput::addHeadItem() in
/opt/lampp/htdocs/labbook/extensions/SyntaxHighlight_GeSHi/SyntaxHighlight_GeSHi.php on line 127

Why it is so sensitive to the used version.

What is the alternative extension, to highlight bash and perl, which is more stable? --IP 14 May 2007

solution for me - Replaced the $parser

Replaced the $parser->mOutput->addHeadItem( ... )-Code with:

$out = "<style type=\"text/css\">/*<![CDATA[*/\n" .
        ".source-$lang {line-height: normal;}\n" .
	".source-$lang li {line-height: normal;}\n" .
	$geshi->get_stylesheet( false ) .

It is very VERY ugly and not valid, but FF2 and IE7 seem to show it properly. --IP 1 June 2007

Fatal error after install

I have installed the GeSHi Syntax Highlighter,

now on save an edit i got the following Error:

Fatal error: Call to undefined method ParserOutput::addHeadItem() in 
 /var/www/slr_wiki/extensions/SyntaxHighlight_GeSHi/SyntaxHighlight_GeSHi.class.php on line 66

Greetz Phillip 10 August 2007

I'm having the exact same problem... any solution?
metasim --IP 1 July 2008


I originally downloaded the current version of SyntaxHighlight_GeSHi.php pointed at by the article. I put the php into the extensions directory. I unzipped the current GeSHi. it created a GeSHI- directory with geshi directory inside of it . I then moved the geSHi directory into the extensions directory.

so we have

extensions (dir)
  geshi (dir)
    (everything under geshi)

I modified the LocalSettings.php to point to the correct location


I got a couple of errors on require so using echo i worked out directories but then i get

Fatal error: Call to undefined function efSyntaxHighlightMessages() in C:\Program Files\Apache Software
Foundation\Apache2.2\htdocs\wikiSanMar\extensions\SyntaxHighlight_GeSHi.php on line 65

I have tried both the originally posted code and then the older code noted above.

Ideas? I am sure it is something to do with where I have located it all as I doubt that this would have been posted without it working. SO fire away .. where have I gone all wrong

Thanks --Dtsig 11 April 2007

Try changing efSyntaxHighlightMessages() to efSyntaxHighlight_GeSHiMessages(). Worked for us! 10:47, 13 April 2007 (UTC)[reply]
This worked great .. thanks --Dtsig 19:02, 24 April 2007 (UTC)[reply]

I gave up

For those that just want highlighting without jumping through hoops, I ended up using this GeSHi extension on my 1.7+ wiki:

GeSHiHighlight.php --Lokal 21 April 2007

Inline usage

Is there a way to highlight a small piece of code inline, i.e. make <source> into <span>? I tried enclose=none but it doesn't work (while enclose=div does work) -- Alex Smotrov 16:54, 21 May 2007 (UTC)[reply]

References use in comments


It seems we can't use the tag <ref> in comments. (sorry for my really poor English). 00:57, 29 May 2007 (UTC)[reply]

1.9.3 and character parsing in SyntaxHighlight

This works great with the following exception.

Characters like

< >

get changed to their html equiv &lt etc

These characters are *kind of* important in source :)

I would have thought that this extension should bypass wiki/html parsing .. yes? As we see above a PRE protects the angle brackets .. shouldn't source

fyi .. This same behavior is found in 1.10.0 ..

Has anyone else seen this? Thanks --Dtsig 15:20, 5 June 2007 (UTC)[reply]

If you allow stuff like <> then you open a big hole for things like javascript ....
And what's possible with javascript is (do say it friendly) not nice (phishing, steal passwords ...).
If you need the "nacked" code use &action=raw&ctype=text/javascript&dontcountme=s example: [3]
Anyway: I don't see you're problem, because with copy&past "highlighted" sources work well.
-- MichaelFrey 15:42, 5 June 2007 (UTC)[reply]
'.. don't see you're problem .. ' I am not sure what you are saying here. What source did you copy&paste? The fact that a < becomes &lt is a problem. I will look at the link you posted. -- 20:30, 5 June 2007 (UTC)[reply]
hmmm German .. sorry I do not understand it. --Dtsig 20:33, 5 June 2007 (UTC)[reply]
Why or when is the &lt a problem for you?
I mean all actual Browsers like FF 2.0 and IE 7.0 render the source code correct.
You say, "PRE protects the angle brackets" but when I look at into the HTML source of that talk page, I see also the html equivalents of < and >.
Anyway, sorry that my link was wrong, her 2 correct examples: [4] [5]
Again: If the extension bypass things like < > it is a hole for w:Cross-site scripting and similar things.
-- MichaelFrey 15:44, 6 June 2007 (UTC)[reply]

Language that doesn't work yet


I participate in writing the Wikibook about Haskell.

GeSHi doesn't support Haskell yet, but it might in the near future (see the feature request).

In the meantime, if i try to write <syntaxhighlight lang="haskell">SOME CODE</syntaxhighlight>, it is rendered as a Big Red Error that doesn't show any code. I think that it would be better to display the source in the default black color with a small warning saying that the language is not supported. This way, when support for that language is added, the warning will go away and the coloring will just start working.

So now we are stuck with doubts whether to use tt, samp, code, pre or something else.

Is it possible to modify this extension for that?

If this is not the right place to propose it, please tell me what is the right place.

Thanks in advance. --Amir E. Aharoni 16:55, 8 June 2007 (UTC)[reply]

I entered a feature request in Bugzilla: 10201 Allow showing code in an unsupported language with a warning. Come on and vote for it if you like it :) --Amir E. Aharoni 18:27, 8 June 2007 (UTC)[reply]
It should be supported in GeSHi Can we have that updated here please? 04:37, 21 August 2007 (UTC)[reply]

Error when passing parameters from templates

As GeSHi doesn't have any functionality for in-line syntax highlighting yet, I figured I could create a template for that:

<span class="inline_code"><syntaxhighlight lang="{{{1}}}">{{{2}}}</syntaxhighlight></span>

I'm a sys-op, so I can edit the CSS files and add the .inline_code class. But the GeSHi plugin complains about not getting a lang="" parameter.

My guess is that MW runs the <syntaxhighlight></syntaxhighlight> stuff before it's passing the parameters from the template. Not sure at all, just guessing.

See the error and a brief explanation on b:no:Bruker:August/GeSHi issues ( I tried [[no:wb:Bruker:August/GeSHi issues]] but that linked to wikipedia, not sure about the syntax).

Regards, August Lilleaas, sysop @ norwegian wikibooks. 4 July 2007

Just made myself an account here, in case someone needs to contact me directly that's a bit more convenient now. --Leethal 12:39, 4 July 2007 (UTC)[reply]

I don't have an answer to your template parameter problem, but as for inline <source>:

  • block elements are not supposed to be inside <span>, so in html Mediawiki moves your <span> inside <pre>
  • Mediawiki encloses all text before and after block elements into <p> tags

So the only way so far I could make it inline requires putting the whole paragraph inside <div>:

  • CSS:
div.inline_code * {display:inline}
  • wiki:
<div class=inline_code>
 Your text 
 <source enclose=div lang=javascript>document.write()</source> 
 your text again

I think the better solution is to request inline source on bugzilla: Alex Smotrov 16:38, 5 July 2007 (UTC)[reply]

Graceful death?

When there are improper source tags the script generates a large error box, could you remove that. It should display nothing if broken. see:


--IP 13 July 2007

That is a graceful failure -- it tells you what you did wrong and how to fix it. --brion 13:43, 16 July 2007 (UTC)[reply]

Bug? The last line contains an extra space

The last line contains an extra space (e.g. XML, Lua) -- 16:18, 17 July 2007 (UTC)[reply]

Last line where? Exact steps to reproduce, please, or an example. robchurch | talk 01:19, 21 July 2007 (UTC)[reply]
peblusto asks: do you mean the last line of the resulting display in a wiki page or the last line of the support php programs? - peblusto 19:15, 18 October 2007 (UTC)[reply]

simple argument cause wiki style to be skipped?

1. Should a simple argument cause wiki style to be skipped?

  • With linenumbers
<syntaxhighlight lang="c" line="GESHI_FANCY_LINE_NUMBERS">
#include <string.h>

int main(){
    char *m;
    char n[20];



#include <string.h>

int main(){
    char *m;
    char n[20];



  • Without linenumbers
<syntaxhighlight lang="c">
#include <string.h>

int main(){
    char *m;
    char n[20];



#include <string.h>

int main(){
    char *m;
    char n[20];




2. And could someone add Estonian translation, to SyntaxHighlight_GeSHi.i18n.php

/* Estonian [[et:Kasutaja:M2s17]] */
'et' => array(
'syntaxhighlight-specify' => 'Sa pead täpsustama keelt nõnda:',
'syntaxhighlight-supported' => 'Süntaksi esiletoomise on toetatud järgnevates keeltes:',
'syntaxhighlight-err-loading' => '(toetatud keelte loetelu laadimisel esines viga)',
'syntaxhighlight-err-language' => 'antud keel on mittekehtiv',
'geshi.css' => '/* CSS mis on asetatud siia, määrab GeSHi süntaksi esiletoomise stiili */',

-- 22:42, 20 July 2007 (UTC)[reply]

Localisation added in r24296, thanks. As to the first question, I'm not sure if I understand, but I'll give it a bash.
The question, as I understand it, is why everything looks a bit different when using line numbers. As you'll spot in the HTML source, when line numbers are in use, we have to use a <div>, rather than <pre>, which means that the grey background and dashed border don't show up. If you'd like this, then you can style the surrounding <div> elements to look the same, using some CSS in MediaWiki:Monobook.css:
  div[class|="source"] {
     padding: 1em;
     border: 1px dashed #2f6fab;
     color: black;
     background-color: #f9f9f9;
     line-height: 1.1em;
Hope this helps. robchurch | talk 01:18, 21 July 2007 (UTC)[reply]

internal links within <syntaxhighlight>

I want to use internal links like

with <syntaxhighlight lang="text"> pure text
 // Request 
// Request 
usage like leads to
 <syntaxhighlight lang="text">
  // Request 
    </syntaxhighlight>[[WinSendMsg]]<syntaxhighlight lang="cpp">(hwndWnd,blabla...
  // Request

Using messages highlighting and internal links may be great thing for programmer's wiki --Evgen 11:56, 27 July 2007 (UTC)[reply]

Using internal links is possible with simply adding a keyword group in the appropriate language file and telling it the documentation URL is your Wiki. Please note the comment on external links mentioned above. -- 10:12, 26 April 2008 (UTC)[reply]
  1. There is no "external links mentioned above" easy to find.
  2. I backed out of using it on Manual:Wiki family#Ultimate_minimalist_solution as one has to ask somebody to configure something to even link to Manual:$wgLogo style names here on //www.mediawiki.org. Jidanni 01:33, 27 December 2008 (UTC)[reply]

Support for Mediawiki markup

Can we work with the GeSHi developers and add our wiki markup to the supported languages? Then we can provide examples of our own code much more easily. 00:34, 10 August 2007 (UTC)[reply]

peblusto asks: do you mean other than <nowiki>? - peblusto 19:15, 18 October 2007 (UTC)[reply]

I need an old and stable version


I need an OLD but STABLE version of this extension that works with these settings:

  • MediaWiki: 1.6.7
  • PHP: 4.3.10 (apache2handler)
  • MySQL: 4.1.10a

(I can't explain it, but) there is NO WAY to update one of these settings!!!!!!!

I did try to find the right extension-version by combining the information of the extension-page-history with the subversion repository but nearly gave it up.

Might this one be the right one for me? http://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/Highlight/?pathrev=19695

What about 20985? I can't evaluate the position :-(

Can someone help me? --IP 10 August 2007

Post-install PHP Warning: call_user_func_array()

After installing (as per the main page), when I try to test by including a some source (for example by copying any of the sample code directly) I get nothing on the screen (e.g. it does not render at all, the wiki page just skips that line). When checking /var/log/httpd/error_log I get something like:

PHP Warning:  call_user_func_array() [<a href='function.call-user-func-array'>function.call-user-func-array</a>]: 
First argument is expected to be a valid callback, 'SyntaxHighlight_GeSHi::parserHook' was given 
in /var/www/mediawiki/includes/Parser.php on line 436, referer: <url removed>

Any suggestions would be greatly appreciated. --M0nstr42 16:51, 22 August 2007 (UTC)[reply]

I am having the same issue. --Snapper67 11:09, 5 September 2007 (UTC)[reply]
I had almost the same problem. After some investigations, I found that the problem comes from some incompatibilities with PHP 4. So, if you are using php 4 like me, you need an old version of this extension.
Try getting the revision 23537 :
    svn co -r 23537 http://svn.wikimedia.org/svnroot/mediawiki/trunk/extensions/SyntaxHighlight_GeSHi
And then apply the workaround #solution for me. --omar.belkhodja 21:38, 13 October 2007 (UTC)[reply]

I have the same problem and am running php5. Any assistance? -- Robert 25 July 2008

You are probably using an old version of PHP5; try changing the 'SyntaxHighlight_GeSHi::parserHook' to array('SyntaxHighlight_GeSHi', 'parserHook') Bryan 19:12, 25 July 2008 (UTC)[reply]

I have still the same problem (MediaWiki 1.5.5/PHP 5.1.2)

PHP Warning:  call_user_func_array() [<a href='function.call-user-func-array'>function.call-user-func-array</a>]: 
First argument is expected to be a valid callback, 'SyntaxHighlight_GeSHi::parserHook' was given 
in /srv/www/htdocs/mediawiki/includes/Parser.php on line 427, referer: <url removed>

Parser.php on line 427 is

if ( $render ) {
       $ext_content[$tag][$marker] = call_user_func_array( $callback, array( $content, $params, &$this ) );;	
} else {
	$ext_content[$tag][$marker] = "$full_tag$content</$tag>";


function efSyntaxHighlight_GeSHiSetup() {
	global $wgParser;
	$wgParser->setHook( 'source', array( 'SyntaxHighlight_GeSHi', 'parserHook' ) );
	return true;

-- Michael 27 August 2008

Change the background color?

Is there a way to change the background of the rendered code table? I know that I can change it in the lang.php file but I'd expect there is a way to have a default background shared by all. I noticed that it creates a css class called "source-lang". Should I just create one myself in my wiki css file (I suppose there is one, somewhere :D) or is there some magic parameter that I can set? Thanks! -Adal 25 August 2007

If you can do it by altering the CSS class, you might find this extension useful, which allows a parser function to dynamically load a css article that is on the wiki rather than a css hard coded into the mediawiki file system --Zven 23:45, 28 August 2007 (UTC)[reply]
I now remember putting some notes up on bioperl wiki which are useful as well --Zven 04:27, 29 August 2007 (UTC)[reply]

Upgrading to 1.11.rc1

Hi, after updating to MW 1.11.rc1 i get the following error.

Detected bug in an extension! Hook syntaxHighlightLoadMessages failed to return a value; 
should return true to continue hook processing or false to abort.

--IP 10 September 2007

Installation, calls, and initial blank wiki screen of death

The text states that geshi.php is created, but the require once code talks about SyntaxHighlight_GeSHi.php, should that be geshi.php in the require once? -- 14:26, 19 September 2007 (UTC)[reply]

peblusto says:
no, there are two different calls to the two different downloaded and installed program groups.
we should have at least this directory / file structure:
then, in
put the call to the extension
and in the extension support file,
make sure there's an accurate call to the program supporting the extension
then if we get the initial blank wiki page / screen of death syndrome, try opening each php source file in a text editor and re-saving each again as text. i found that windows notepad saw no formatting inside the downloaded php files. windows wordpad did bring them on screen okay, properly formatted. so, after re-saving each of the main php files above from within wordpad as text, then notepad also saw the files formatted as text. also, most important, the wiki screens came back to life. we may have translation goofs between systems causing the source php files to loose their structure when exported and imported from system to system.
- peblusto 19:15, 18 October 2007 (UTC)[reply]

The top of the code box is getting chopped off in IE

I just installed this extension on my site, and it looks great in Firefox, but in IE the top of the code box is getting chopped off. The code is formatted correctly, but the first few lines don't have the background box, and the top border is missing. I checked your site as well, and I get the same behavior -- looks great in FF, not so much in IE. As much as I'd love to tell everyone to use FF, my site is a corporate site where IE is the standard. Any ideas? Thanks --ColinLittle 20:33, 28 September 2007 (UTC)[reply]

This is apparently not a problem in IE7. I'm using IE6 -- ColinLittle 21:15, 28 September 2007 (UTC)[reply]
For those still using IE6: It appears to be a problem with GeSHi's <pre> block element being put inside a <div> element without anything else in the div. To fix this, look for the following line in SyntaxHighlight_GeSHi.class.php:
return '<div dir="ltr" style="text-align: left;">' . $out . '</div>';

and change it into

return '<div dir="ltr" style="text-align: left;">&nbsp;' . $out . '</div>';

and the block element will render correctly. If anybody can come up with a way to insert a character without taking real space on the page, that would be nice though. Dannyh 23:20, 1 April 2008 (UTC)[reply]

Doesn't work on 1.9.2

I tried and tried to get this one to work on my wiki. I have installed several extensions and am not new to this, but I could not make this work. I even tried using some of the suggestions on this page, but nothing worked.

I tried this GeSHi extension and it worked right out of the box. Extension:GeSHiCodeTag

Just thought I would post this for others who can't get this to work for them. --IP 8 October 2007

Installation Instructions - Line does not exist

If needed, change the following line in SyntaxHighlight_GeSHi.class.php to suit the path of your geshi.php file
require_once( 'geshi/geshi.php' );

That line does not exist there ! --Arcy 19:34, 14 October 2007 (UTC)[reply]

peblusto says: i searched for "require" in my text editor and found it okay in the current version r24298 (July 21, 2007) - peblusto 19:15, 18 October 2007 (UTC)[reply]

This lines work for me (Mediawiki 1.11.0)

Just Add

 // change directory >> /usr/local/src/geshi/ << according to your geshi installation
 $languagesPath = "/usr/local/src/geshi/geshi";

to the top of SyntaxHighlight_GeSHi.php

--Arcy 18:57, 15 October 2007 (UTC)[reply]

Translating an attribute style=""

Hello, i don't know if its the right place, but... I would like to know if its possible to add a function to this extension. At fr.wikipedia.org, we use for the tag pre the style overflow:auto. It will be very nice if the tag source translate the style into is first element. With it we can easily change the height of the code, background, or border, text size...

For example, <syntaxhighlight lang="javascript" style="height:200px;">, with it we can change the height of the code, our overflow:auto add scroll if need. Thanks a lot. fr:user:bayo 14:37, 17 October 2007 (UTC)[reply]

It doesn't work for me

Hello, I tried everything I get no error messages whatsoever but I can't get any highlighting either.

my pages look like:

 <syntaxhighlight lang="php"> 
   v = "string"; 
   // sample initialization 
   html text 
    echo v; 
    // end of php code 

 <syntaxhighlight lang="csharp"> 
 // Hello World in Microsoft C# ("C-Sharp").
 using System;
 class HelloWorld { 
  public static int Main(String[] args) { 
   Console.WriteLine("Hello, World!"); 
   return 0; 

including AND showing the <syntaxhighlight> tags.

my directory structure is as follows:

extensions/SyntaxHighlight_GeSHi/geshi/geshi/ (containing many php files)

the SyntaxHighlight_GeSHi files are untouched, from the svn to my server without any modification.

the LocalSettings.php file begins as follows:



any idea on how to make it work?

thanks Giulio --IP 23:05, 12 December 2007 (GMT)

I have EXACTLY same problem :(
this one worx as a cake, tho Extension:GeSHiCodeTag
thanks starenka --IP 11 February 2008

The installation instructions on the articles page does not work. The instructions about LocalSettings.php are wrong. I downloaded the lastest stable release of the extension. There I no such file as mentioned SyntaxHighlight_GeSHi.php. Shouldn't it be more like:


anyhow with this it doesn't work neither. A pitty. My installation should work on Windows XP with an XAMPP-Server setup. Can anyone with successfull installation correct the installation instructions, though it will work? --Ollio 20:37, 2 April 2008 (UTC)[reply]

Hey guys I just spend about an hour trying to work out how to get it going. Turns out there's a couple of things you should know.
  1. Guilio: You can't start your LocalSettings.php file with a call to your extension. See Manual:Extensions#Installing_an_extension for more information. Put the require_once tag at the end of the file.
  2. Once you have followed the installation instructions you need to re-edit your page (click edit, then save) to see the changes. I kept hitting reload but MediaWiki must only parse the file when you save it.
Hope this helps. Ollio, I'm using Windows XP and xampp-lite so it should work for you. MarcT 00:02, 10 September 2008 (UTC)[reply]
@MarcT: Unfortunatly your solution won't work -.-
I'm using XP with XAMPP, went through EVERY single Step in the Installation. The Result is "nothing". I even tryed your Solution. But nothing happend.
Maybe we all have to try a little more. ;) --IP 12 November 2008

Please Add new format of Tag insertion

Hi, please let users to add source codes like this: <syntaxhighlight|lang=php>sample-source</syntaxhighlight> using space to divide parameters is not a wiki standard, the standard is dividing by | . --Tofighi 02:49, 18 December 2007

Personally, I don't see any value in this additional syntax. Besides, | is mostly used in templates, and this is a tag, not a template Alex Smotrov 22:34, 18 December 2007 (UTC)[reply]

Language Specific Tags

For a site I'm working on most of the code is in one language, so I wanted a simpler tag. I added an extra parser hook:

$wgExtensionFunctions[] = 'efPerlHighlightSetup';

function efPerlHighlightSetup() {
    global $wgParser;
    $wgParser->setHook( 'perl', 'phPerlHighlight' );

function phPerlHighlight( $text, $args = array(), $parser ) {
    $args['lang'] = 'perl';
    return SyntaxHighlight_GeSHi::parserHook($text, $args, $parser);

Which allowed me to use <perl></perl> tags. Thought someone else might find it useful. It might be nice to have an option to list languages and have it add short tags like this. --Haarg 08:16, 19 December 2007 (UTC)[reply]