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

Hi and many thanks for your quick reply : )

Your source code example is exactly what I have tried before posting my question and unfortunately it does not work... but your reply confirms me I should dig somewhere there : ) After several tests, I found a "not-so-clean-but-acceptable" patch for my use case: "//*[not(ancestor-or-self::*[@class='noglossary'] or ancestor-or-self::pre or ancestor-or-self::a)][text!=' ']/text"

Note: I have also tried with the "brush" class instead of the "syntaxhighlighter" class as Lingo should see "brush" but not "syntaxhighlighter" (correct me if I am wrong), but with no success... so filtering on pre will be the "selected" patch even if it is far from perfection.

Many thanks for your very good support. Philippe 13:53, 24 April 2012 (UTC)