Help talk:GeSHi

Suggestion

Hello.
I would suggest that any <pre> editing effect, ie.causing a <pre> pair to be inserted in the result html page, under a language header {{header|LANG_TAG}} be automatic converted to the corresponding language syntax highlight( LANG_TAG ) effect, so that any further conversion is not need. New code may still use old style editing.
Is it feasible?-badmadevil 02:36, 23 February 2008 (MST)
EXAMPLE:
{{header|C}}
<pre>
printf("Hello, World!") ;
</pre>
Result HTML page display as
{{header|C}}
<C>
printf("Hello, World!") ;
</C>

This is a good idea... saddly my PHP is non existent so I can not write the code at this point. Do you know anyone that could write this kind of filter? I also wonder if an undesirable side effect would be that <pre>date</pre> and <pre>output</pre> would get unexpectedly converted/formated as C code.

I will continue the evaluation, maybe by the end of this I will have an understanding and can do the coding easily, or... know the ramifications of why we shouldn't.

NevilleDNZ 05:43, 23 February 2008 (MST)

Suggestion x 2

Hi!
Currently, it seems D's (also others, like Java, C etc.) syntax coloring high-light a Statement keyword by color #b1b100,eg:
return new int[] ;
It may be only me, it will be looked better if a darker color is used for Statement keyword, eg. that of int keyword (#993333):
return new int[] ;
or, in similar but darker color(#666600):
return new int[] ;
Besides, the origianl <pre> tag allowed attribute modifying, eg.<pre style="background-color:#ffe">. But the syntax coloring tag will remove it, eg. <d style="background-color:#ffe"> => <pre class="d">. It seems the class is redundant as coloring is already applied. It will be nice that the syntax coloring tag can be more flexible.
Thank you. -- badmadevil 02:40, 29 February 2008 (MST)

Page error?

I saw this error message:

Warning: stristr() [function.stristr]: Empty delimiter in /home/shortcir/public_html/rosettacode.org/w/extensions/geshi/geshi.php on line 2127

Don't know if that's anything anyone can fix. --Mwn3d 13:32, 8 March 2008 (MST)

Wikipedia's version?

When you try to use an unsupported language via <source lang="lang">, you get an error that lists quite a few more supported languages. Is there a way to use the version of GeSHi that wikipedia is using?

GeSHi Error: GeSHi could not find the language forth (using path /usr/local/apache/common-local/php-1.5/lib/GeSHi-1.0.7.19-wm1/geshi/) (code 2)

You need to specify a language like this: <source lang="html">...</source>

Supported languages for syntax highlighting:

actionscript, ada, apache, applescript, asm, asp, autoit, bash, blitzbasic, bnf, c, c_mac, caddcl, cadlisp, cfdg, cfm, cpp, cpp-qt, csharp, css, d, delphi, diff, div, dos, eiffel, fortran, freebasic, gml, groovy, html4strict, idl, ini, inno, io, java, java5, javascript, latex, lisp, lua, matlab, mirc, mpasm, mysql, nsis, objc, ocaml, ocaml-brief, oobas, oracle8, pascal, perl, php, php-brief, plsql, python, qbasic, rails, reg, robots, ruby, sas, scheme, sdlbasic, smalltalk, smarty, sql, tcl, text, thinbasic, tsql, vb, vbnet, vhdl, visualfoxpro, winbatch, xml, xpp, z80