Thread:Extension talk:Lingo/Looking for a tips when Lingo interferes with some JavaScript (different from NOGLOSSARY and class=noglossary)

Hi, Lingo (0.3) interferes with the Syntaxhighlighter extension javascript when there are glossary keywords in the "syntaxhighlighted" source code.

Of course __NOGLOSSARY__ and class=noglossary work fine, but I would like to offer a better solution for my wiki users, I mean, as Lingo is "automatic", I am looking for a tips (source code modifications, css...) to avoid my wiki users to add by themselves __NOGLOSSARY__ in case they are using a glossary keyword in their source code...

My questions:
 * Any idea/tips for fixing this issue?
 * LingoParser.php seems to look for the class "noglossary", I have tried to add the class "syntaxhighlighter" but without success.
 * Is there any way to execute Lingo "after" Syntaxhighlight? (not sure because Syntaxhighlight seems to use ~only Javascript)

Exemple - wiki:  void James007(void) {}

Exemple - result: void James007  James007 is James Bond   (void) {}

Exemple - Html:  ...

Many thanks for this nice wiki extension : ) Philippe Cornucopia (talk) 12:16, 12 April 2012 (UTC)