Extension talk:Lingo
Contents
 First page |
 Previous page |
 Next page |
 Last page |
The mouseenter/mouseleave events don't work too well on touch devices. I've added the following to Lingo.js to solve this
/*
* Listen for mouse clicks, esp. on touch devices such as iPads. When the tooltip is visible and the mouse is clicked,
* remove the tooltip.
*/
.mousedown( function( event ){
if( $(this).find(".tooltip_tipwrapper").is(":visible") ) {
$(this).trigger('mouseleave');
} else {
$(this).trigger('mouseenter');
}
})
I will also submit this to Git.
I encountered some performance issues while using Lingo in combination with Semantic Glossary. The glossary does not change all that often, but it is still retrieved and rebuilt for every page view. This had severe impact on our loading times (we're talking about seconds here).
I added some caching logic to Lingo to LingoParser::buildLingo that solved this for us. The LingoTree is cached for 15 mins before it is rebuilt.
protected function buildLingo() {
wfProfileIn( __METHOD__ );
global $wgMemc;
// Try cache first
$cachekey = wfMemcKey( 'lingo', 'lingotree' );
$cachedLingoTree = $wgMemc->get( $cachekey );
if($cachedLingoTree != '') {
$this->mLingoTree = $cachedLingoTree;
} else {
$this->mLingoTree = new LingoTree();
$backend = &$this->mLingoBackend;
// assemble the result array
while ( $elementData = $backend->next() ) {
$this->mLingoTree->addTerm( $elementData[LingoElement::ELEMENT_TERM], $elementData );
}
$wgMemc->set($cachekey, $this->mLingoTree, 60*15);
}
wfProfileOut( __METHOD__ );
}
I'm planning to make the caching optional and the cache expiry time configurable, and to check this code in to Subversion. Any objections?
IE bug? When .tooltip_abbr overlapped by .tooltip_tip of another .tooltip, it remain visible under it
Hello, Stephan! I am using IE 9.06, mediawiki 1.17 and Lingo 0.3. The problem is on screenshot
there is no that problem in firefox
And thanks for Lingo!
Never saw this before. Then again, I am not using IE very often. I will investigate. Thanks for the report!
Cheers,
I'm also seeing formatting problems using both IE 8 & IE 9. The tooltips spread out wide over the entire page, as if they are not correctly reading the page width.
It works for me in IE9. However, there was apparently a bug in IE7 in the handling of the z-index. I checked in a patch to work around that. It could be that because of some other error your browser goes into IE7 compatibility mode. Anyway, I checked in the patch into the git repository. Would be great, if you could check it out and see, if it works now.
Hi there,
I hope anyone can help me. I have installed the current version of Lingo on my Mediawiki 1.16.2 but both ways:
;FTP:File Transfer Protocol
and
;FTP :File Transfer Protocol
result in this:
- FTPFile Transfer Protocol
Can anyone help me? 88.64.170.165 14:10, 7 May 2012 (UTC)
Hi. Thanks for your quick reply. Can you tell me what I have to do exactly?
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: <pre class="brush:c"> void James007(void) {} </pre>
Exemple - result:
void <span class="tooltip"><span class="tooltip_abbr">James007</span><span style="display: none;" class="tooltip_tipwrapper"><span class="tooltip_tip"><span>James007 is James Bond </span></span></span></span>(void) {}
Exemple - Html:
<div>
<div id="highlighter_700962" class="syntaxhighlighter nogutter c">
<table cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<td class="code">
<div class="container">
<div class="line number1 index0 alt2">
<code class="c plain">.sync_src = <span </code>
<code class="c keyword bold">class</code>
<code class="c plain">=</code>
<code class="c string">"tooltip"</code>
<code class="c plain">><span </code>
<code class="c keyword bold">class</code>
<code class="c plain">=</code>
<code class="c string">"tooltip_abbr"</code>
<code class="c plain">>James007</span><span style=</code>
<code class="c string">"display: none;"</code>
<code class="c keyword bold">class</code>
<code class="c plain">=</code>
<code class="c string">"tooltip_tipwrapper"</code>
<code class="c plain">><span </code>
<code class="c keyword bold">class</code>
<code class="c plain">=</code>
<code class="c string">"tooltip_tip"</code>
<code class="c plain">><span>James007 is James Bond</span></span></span></span>(void) {} </code>
...
Many thanks for this nice wiki extension : ) Philippe Cornucopia (talk) 12:16, 12 April 2012 (UTC)
Hi,
your second idea seems to be the best choice here. Did not test, but adding the syntaxhighlighter class to the XPath query should work. Try replacing the query in LingoParser.php (around line 167) with
"//*[not(ancestor-or-self::*[@class='noglossary'] or ancestor-or-self::*[@class='syntaxhighlighter'] or ancestor-or-self::a)][text()!=' ']/text()"
Executing Lingo after SyntaxHighlight is not possible as, as you noticed, SyntaxHighlight is based on JavaScript.
Cheers,
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)
Hi again. I have started using Semantic Mediawiki 1.7.0.2 wit Semantic Forms 2.3.2
If I have words or phrases in Field names that are on the Terminology Page then the Lingo extension is interfering with the rendering of the "Edit with Form" page. The inserted Spans are a problem.
I will have to be careful with mu terminology!
I'll investigate. Until then it should work to include the __NOGLOSSARY__ magic word into your form definitions.
Hey,
Sorry to say it is not working for me using SM Forms 2.4.2
What I should see: 
What I see: 
Curious. This is clearly not a JS, but a PHP issue. Somehow SF seems to not recognize what input type to use and so defaults to input type text. You are sure that the only difference between those two pictures is including Lingo in your LocalSettings.php or not, right? Is your wiki somehow publicly available? Or could you post your form's source code?
hi, All I am doing is adding the term "Change" on the Terminology page. Lingo is included in both examples.
I have cleared caches in IE. Is there anything I can do on the server to clear any caches? It is pretty blck an white for me however. I add the term "Change" and "Edit with Form" does not work. I remove the term and the form works. Very repeatable.
Thanks
I have noticed a slight problem. When definition text is displayed it appears to use the same font-colour as the page text it is attached to. It does not, however, use the background colour that text is against. This means that where we have white text on a coloured background the definition text is not visible. Would it be possible for Lingo to always use a black text colour? I am using v0.3 on MediaWiki 1.17.0.
Dear all: Could anyone please show an easy example of how to use Lingo extension? The problem now is I've installed both Lingo and Semantic Glossary, and edit the Special:Terminology, but I did not find somewhere with highlight words, so I think I do not quite know how to use this extension. Thanks in advance!
Hi,
Semantic Glossary turns off the Special:Terminology page. You have the choice of using Lingo alone and not installing Semantic Glossary, then the glossary is defined on Special:Terminology. Or you install Semantic Glossary in addition to Lingo, then you have to define the glossary using Semantic MediaWiki properties
Edit: Wait, there is no Special:Terminology. It's just Terminology. That's a normal page in the main namespace.
Cheers,
Hi F.troot
Thanks for your help, now I've deleted Semantic Glossary both in extensions file and LocalSetting.php, I'm trying to use Lingo. For Terminology page, yes it is just a normal page, I'm sorry I made a mistake for that!
However the case is, I follow every step of installing Lingo, and make no configureations, edit the page Terminology with ";Mo:Mo Yanzhai" , but still in the page with "Mo", nothing happened! Did I miss some steps or what?
Many thanks for that. We're trying to build a glossary with this great extension!
Hmm, if your wiki is not in English, then the name of the page could be different. A link to the terminology page is included in the credits in Special:Version.
(The documentation on the extension page should probably improved to mention that fact.)
Many thanks for that reminding
I re-installed English version, and re-install Lingo again, but still, nothing changed. I'll try tomorrow, but anyway, thanks!! I really hope I can use this extension!!
Hello,
Very nice extension. I was wondering if Lingo supports case-insensitive words? When a definition is added on the Terminology page (in lowercase) the definition is only picked up by lowercase words in the article (and not in words starting with a capital e.g. at the start of a sentence).
One could add the word starting with a capital in the Terminology, but maintenance would be a lot more work.
Hi,
Lingo currently does not support case-insensitive words. The problem is, that every transformation, every additional check results in a performance hit and thus must be very carefully considered. I will look into it, but I really am not sure if I will ever implement it.
Cheers,
Hi,
Thanks for your answer. Those sound like valid reasons. Nevertheless the extension is very helpful for our project.
Regards,
Remco
Hi, First of all thank you for this great extension!
I could also use something like a flag that specifies that the term is not case sensitive. basically I see two variants to achieve that:
- manual: permit multiple definitions for the same definition.. use a separator like "," to separate different terms. As it is now.. i have to write the same term in different casing with the same definition
- automatic: this would be much easier for the user, but heavier for the system.. I do not know how the extension is implemented, however I can see a few possible ways to achieve this:
- per word case analysis - very expensive but pretty straight forward to implement
- enhance dictionary - this would be a much more flexible way to achieve the same thing without the feature being to expensive. By default or based on a flag specified by the user of the extension, you could generate more search words (or strings in case of multi-word terms) in the dictionary based on the same word. However when generating the extra words you can take into consideration the most common cases when terms change:
- first letter both casings A/a (2 subcases: for each word and for the first word only)
- entire string both casings A/a
Thanks again for the extension! Best Regards
Hello,
at the moment i have the problem, that the words are only marked, when i save the pages again (nothing changed on the pages).
Situation: 1. Create a new entry in the Glossary template 2. Look on the pages, if the entry is now marked => nothing happend 3. Edit the page (article) and save it without any change again 4. Look again on this page and the entry is now marked.
Second question: Is it possible, to click on the ballon tip and get to the entry on the Glossary page?
thanks in advance Chris
Hmm, odd. This sounds like a cache issue. I was sure, Lingo was applied after the cache, but now I am not sure any more. If you turn off caching, does it work?
It is not currently possible to include links in the glossary.
When will Lingo support extended letters such as àéèöâ? And what about non-roman characters such as arabic, japanese, gujarati, etc... writing systems? thanks.
It should support these already. Does it not?
It works in the Terminology page but it doesn't work when you type the acronym and do a mouse hovering. Here's a screenshot : [1] I'm using MW 1.16.2, I also tried on a clean installation, same problem.
Edit : The problem was with the 0.1 version. Latest version works but it disables smoothgallery (not the case with 0.1)! Can it be fixed?
My guess is, that Lingo interferes with some JavaScript. Try wrapping the gallery in an HTML element (e.g. a span or a div) and specifying class="noglossary". Should look something like this:
<div class="noglossary"> <sgallery> Image1.jpg Image2.gif Image3.png </sgallery> </div>
Cheers,
Thanks!
I embedded the gallery in an HTML element -> works, no problem
I installed Lingo -> Smoothgallery is not disabled but pages where Smoothgallery and Lingo are, the page has a shrunken sidebar and tabs (page, discussion, remove, etc...)
Workaround -> Do not use acronyms on articles containing Smoothgallery, it seems to fix that problem, it doesn't bother me but still it should be reviewed I guess...
You can also put
<div class="noglossary">acronym</div>
between the acronym to impeach Lingo intervening.
Hello to all,
Lingo is a great extension, but it seems that there is an interaction bug between Lingo and MediaWiki:Sidebar. In fact, when, Lingo is ON, links and collapsing in the sidebar does not work anymore.
Any ideas ? Thanks
In the beginning while testing Lingo we had some trouble while Extension:UsabilityInitiative (Vector controls MediaWiki:Sidebar) was installed. This extension is abandoned and no longer compatible with MediaWiki 1.16+.
The individual components of UsabilityInitiative have been moved to their own extensions (like Extension:Vector), and those components are no longer compatible with MW 1.16. However, if you are stuck on 1.16 for the moment, Extension:UsabilityInitiative is the way you have to go. The problem is that Lingo loads JQuery itself, which conflicts with UI. I worked around this by editing LingoParser.php and commenting out lines 280 and 283 so that Lingo would not load JQuery. This allowed the sidebar to collapse again, and Lingo still works.
I solved my problem, but just in case anyone else has it, I thought I'd post the information here. The terminology page for Lingo is very finicky. When they say format it like this: ;Term1:Def1
;Term2:Def2
They mean format it EXACTLY like that. The following does not work:
;Term1
:Def1
;Term2
:Def2
This does not work either:
;Term1
;TermVar1 :Def
When it breaks, it breaks in ways that may not make the cause immediately apparent. Your list may have some tooltips, which may stop several tips above where the error is. If the problems are severe enough, it will stop working altogether.
Try the latest dev version from SVN. Both of your mentioned cases should work there.
If you think the extension does not behave as it should, please report exactly what you did, what happened, what you would have expected to happen. "If the problems are severe enough, it will stop working altogether." is not specific enough.
Cheers,
I just found a strange quirk and its appearance is so limited that you may not want to bother trying to fix it but i figured i'd let you know.
In IE 7 the space following the use of a defined term vanishes. I've tried placing multiple spaces to no avail. I can alter the code to force a space but then the ones that were showing properly have a double space after which is almost worse. I can't get it to repeat with any other browser or any other IE version. I only noticed it because my work laptop has 7 installed and I don't have admin rights on it to upgrade. When i use my personal laptop i don't see the problem and people i know using firefox haven't seen it either.
Hi Kay,
this should be fixed in the version available from SVN. Sorry, I did not have time yet to package and properly release it. You can get the SVN version from here: http://www.mediawiki.org/wiki/Special:ExtensionDistributor?extdist_extension=Lingo
Cheers,
when i clicked the link it sent me to the 'download mediawiki extension' not svn.. did i end up in the right spot?
Yes, that's exactly the right spot. It will take the SVN version, zip it up and provide it for download. One more thing, though: You need to select the development version (trunk). The other one is already deprecated.
Perfect!!! thanks so much!
just noticed something odd. not sure that anything can be done. if you use lingo. and you need to copy/paste text from a page that has an acronym that is defined.. when you paste the text.. you get the acronym AND the spelled out definition from the popup-box.
Hmm, I can see why it happens, but there is no quick fix for it. The definitions are stored in the text next to the acronym and then hidden by CSS. When you hover over the acronym, the CSS is changed to show the popup. I'll see what I can do, but to be honest, I think this could even be considered a browser bug - if an element is hidden they should not consider it as marked.
Hello!
I've just finished uploading my Wiki installation to a real server (up to now it was self hosted on my computer) and I noticed something strange: entries from the Terminology page are highlighted even if they are not a whole word but a part of another. For instance:
- entry CAR, but the word CARdiology gets a partial highlight of the "car" part.
Any idea what might be causing that?
Thanks a lot!
Just tried to reproduce it, but could not.
What version of PHP, MW and of Lingo are you using?
Is your wiki public so I could have a look?
Cheers,
Hello and thank you for taking the time to asnwer!
My Wiki, unfortunately, is closed and you would need to register in order to read the articles, so I wouldn't want to bother you this much. Besides, it's not in English...
Anyway, here's a screenshot in which you can clearly see my problem: the word from the Terminology page is "rigor", however it appears highlighted as a part of Grigoriy.
http://tinypic.com/r/14wc1sg/7
As for the versions: MediaWiki 1.17.0, PHP 5.2.17 (cgi), MySQL 5.0.92-community-log
Any ideas?
And this happens with Lingo 0.2?
Edit: Never mind, I know what the problem is. The algorithm does not properly align on word bounderies for cyrillic script. I'll try to fix it.
I think I fixed it. Could you try the latest version from SVN?
It is fixed, indeed. Thank you very much!
On another matter, is there any possibility to have links between some of the entries in the Terminology page? For example, if we have a main entry of a word, another - like the plural form, to extract the explanation from the main entry? This would be very handy, because in Bulgarian the definite article is actually formed by adding a suffix to the word, rather than a separate particle as it is in English.
Some of my wiki articles use javascript to pop open new windows. This stopped working after installing Lingo. I also use SmoothGallery (already discussed below in Support of extended alphabet letters?), which also broke. I was able to resolve both by changing line 259 in the LingoParser.php file. It appears that the saveXML function will insert a CDATA wrapper around any javascript in order to ensure properly formed XML. However, I'm not sure that XML is necessary for this output, is it? I changed it to saveHTML, and it seems to work:
$text .= $doc->saveHTML( $child );
I think it had something to do with saveHTML being fairly new and not being supported in older PHP versions, but that was some time ago. I'll look at it again.
Hi,
This does not deal with terms with a space in a phrase you may wish to refer to. I am doing some ITIL work and wish to refer to "Known Error" for instance.
I also do not get the underline when the term is in brackets.
Will these issue be addressed or am I doing something wrong.
Many thanks
JO
Since version 0.2 you should be able to use any characters in a term (including punctuation, spaces, all UTF-8 characters, but excluding the colon (:) of course).
Thanks but it does not seem to be working.
For example this code:
='''K'''= ;Known Error:An Incident or Problem for which the root cause is known and for which a Temporary Work-around or a permanent alternative has been identified.
Does not result in Known Error being underlined on any pages.
The version from the version page on my wiki is "Version 20110108"
Thanks
Jeremy
Ok, your version is the very first version of the extension. There was no real version numbering done back then, hence the date in the version string. To use special characters you will have to upgrade to the last version.
Cheers,
Thanks. That solved things that issue. I now have an issue whereby trailing spaces are stripped off and underlined terms run into the following text.
Many thanks
JO
I am using mediawiki 1.16.5 php 5.3.2(apache) and mysql 5.0.41-log
I was previously using terminology and while it "worked" pages that had html tags or used the input box or forms extension would not show up. I liked how Lingo allowed for limiting to namespace.
I tried installed as is 'out of the box' before putting in the namespace limitations.. and all of my pages show up completely blank as soon as the extension is enabled. No error message..but no page either. when i disable the extension in local settings, it all comes back. I'm not sure where to start debugging because with no error message i don't know what about the extension it's not happy with. I am going to try disabling all of my other extensions and seeing if that helps but figured i'd post here while working my way thru that in case anyone had any thoughts.
Thanks
Hi Kay,
sorry about the trouble. You are right, a blank screen is not easy to debug. To display errors include the following statements in your LocalSettings.php somewhere at the top:
error_reporting(E_ALL | E_STRICT);
ini_set("display_errors", 1);
ok i added the code segment you showed above.. saved off my localsettings.php.. uploaded it back to the server.. reloaded the page.. and nothing. i still don't get any error messages.. i simply get a http 500 error. as soon as i turn lingo back off and re upload localsettings.php my pages come back. I've checked a variety of the pages just to make sure it wasn't something that happened to be on one page.. perhaps use of an extension that conflicts.. and none of the pages in my wiki will show up, all http 500 errors.. if i hadn't be able to use terminology i'd be less confused.. but since the one worked and this is a reworking of that.. i didn't think the site would balk this much.
Hmm, not good. Do you have access to the server logs?
i don't think so. i have to upload all of my changes to a dev server that is separate from the actual real server and then use a java script to transfer them over but i'll ask .. do you know which specific files would be useful? someone else is going to have to get them to me and i want to be able to give as explicit instructions as possible to point them to what i need or they will either get something that won't help OR decide that what i am asking is too much work and they don't want to be bothered.
Difficult. This depends very much on how the server is set up. The name and location of the log file can be found in the server config file in the ErrorLog directive. On Unixes it is often named error_log and to be found in the /var/log/apache/ directory. If in doubt, if that directory exists ask for all the files in there.
Another thing that I can think of is, that for some reason you might be missing the dom module. If you want to check this first, create a php file with the following content:
<?php phpinfo();
Upload this file to your server and access it via your browser. It should give you loads of information. One of the sections should be titled "dom" and basically say that all its services are enabled (DOM/XML, HTML Support, XPath Support,...). After doing this remember to delete the file again! Making all the information public could pose a security risk.
Hi :) In a glossary entry, it is sometimes useful to add internal and/or external links.
;007:James Bond [[w:fr:007|my link]]
- 007
- James Bond my link
Do you think it is something difficult to implement (I do understand the difficulty regarding the complex computation for the size of the message, and I am sure that there are many other difficulties...) Many thanks, Philippe
I agree that it would be very useful. I just turned parsing on and did some profiling. The time spent in the relevant method went from 1.6ms to 717.5ms per request. It may be that in some future version I can figure out how to utilize the cache, but until then I will not turn on parsing.
Hi, Glossary entries in titles and sub-titles are not displayed properly (I am not talking about page names): the mouse pointer changes to the question mark but the associated definition is not displayed (Mediawiki 1.17 + Lingo 0.2... I will try the 0.2.1 version tomorrow)...
==JB007==
with in the glossary the following entry:
;JB007:James Bond
It could be a css issue but I am not yet sure. Many thanks, Philippe
It is indeed a CSS issue. Vector and Monobook skin (and probably others) set overflow:hidden for headlines. I do not know, why they would do this, it seems unnecessary to me.
To fix it find the CSS rules governing h1, h2, ... h6 in your skins CSS file and comment out or delete the overflow:hidden rule. For Monobook this is main.css around line 112, for Vector it is screen.css around line 728.
First page |
Previous page |
Next page |
Last page |
![[1]](http://img402.imageshack.us/img402/9724/doesntwork.jpg){kind=link}