Extension talk:Lingo/LQT Archive 1

I have been using the Terminology extension for about a year and have a few feature requests to address shortcomings:
 * Contextual Glossary - There is the possibility of having acronyms with dual definitions, like POST which depends on context of the article. A parser tag would solve this problem. Default functionality would work without parser tags based on the word order on the Terminology page.


 * Per-word disable - VIA parser tag, one should be able to disable the tooltip, such as when the word POST refers to HTTP POST,


 * Per-page/Per Category/Per Namespace disable - Similar to above
 * All good ideas, will implement when I get the chance

Still in development?
Hi there.

I like this extension. We use it in our company's internal Wiki. But as said above, there could be some improvments.

So I wanted to ask if this project is still alive and will be continued. Would like to see a production ready version.

Problems
The code looks nice, but this extension - breaks the html source of the page, adding and < /html > each time it's called (e.g. by templates) - preg_match_all don't recognize UTF-8 (e.g. cyrillic words) - preg_match_all offset are misplaced when 2-bit chars are in the text - should use mb_xxx functions