Last modified: 2011-01-24 10:19:49 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T28900, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 26900 - "scheme language" can't be high-lighted
"scheme language" can't be high-lighted
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
SyntaxHighlight (GeSHi) (Other open bugs)
unspecified
PC Linux
: Normal normal (vote)
: ---
Assigned To: X!
: upstream
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-01-24 09:16 UTC by NalaGinrut
Modified: 2011-01-24 10:19 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description NalaGinrut 2011-01-24 09:16:09 UTC
hi, I'm using MediaWiki.
And I can't high-light scheme language code with Syntax highlighting-GeSHi. My code attached below:
============================================================
<source lang="scheme">

(define func
   (lambda (x)
      (+ 1 x)
      (format #t "hello world~%")
      (newline)
   ))

</source>
===========================================================

This code will display only "hello world~%", that's definitely wrong.
I think my extension was installed well because I can see other language high-lighted correctly.
And when I change "scheme"  to "lisp" , it works well. But lisp is not scheme.
Comment 1 Sam Reed (reedy) 2011-01-24 09:20:53 UTC
Testing this on my dev wiki gives "Unknown modifier c on SyntaxHighlight_geshi/geshi/geshi.php on line 3403


This seems to be actually a Geshi bug...

I don't see this on other languages...
Comment 2 Niklas Laxström 2011-01-24 09:29:28 UTC
Please report this to upstream: http://qbnz.com/highlighter/geshi-doc.html#feedback
Comment 3 Sam Reed (reedy) 2011-01-24 09:35:17 UTC
I've logged it upstream.

It seems to be a duplicate bug of a couple, but needs testing on SVN head of their version

https://sourceforge.net/tracker/?func=detail&aid=3164574&group_id=114997&atid=670231

RESOLVED LATER - will be fixed when we can change the svn external we can use and it's fixed in there
Comment 4 Sam Reed (reedy) 2011-01-24 09:48:20 UTC
Just tested, this works fine on trunk geshi, ie using https://geshi.svn.sourceforge.net/svnroot/geshi/trunk/geshi-1.0.X/src/
Comment 5 NalaGinrut 2011-01-24 10:19:49 UTC
(In reply to comment #4)
> Just tested, this works fine on trunk geshi, ie using
> https://geshi.svn.sourceforge.net/svnroot/geshi/trunk/geshi-1.0.X/src/

Well, I tested this trunk with Chromium 8.0.552.237 (70801)  & firefox 3.6.13. It works well. 
Thanks!

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links