Last modified: 2014-03-09 10:54:45 UTC
After talking with someone on #wiktionary, I had a great idea for an extension: a MediaWiki implementation of the dict protocol http://en.wikipedia.org/wiki/DICT I think this would involve writing an API client that could listen on port 2628 for dict queries, ask mediawiki to fulfill the request, and then send a reply to the dict client. Really, just a SMOP. ;)
It appears that this protocol expects responses in text/plain (unless OPTION MIME is used, in which case it could have multiple types, but the impression i get [after not very much reading, so could be wrong] is dict servers should support plain text) Converting wiktionary definitions to plain text is not exactly trivial.
Cough cough http://puszcza.gnu.org.ua/software/dico/modules.html
(In reply to comment #2) > Cough cough http://puszcza.gnu.org.ua/software/dico/modules.html Case in point: From http://dicoweb.gnu.org.ua/?q=food&db=en-wiktionary&define=1 : External links (2, '{{') projectlinks | pedia | }}commons ------ Seems as if the plugin still has something to be desired.
> Converting wiktionary definitions to plain text is not exactly > trivial. Which is why I wouldn't want the module to do it, necessarily. The output of links -dump http://en.wiktionary.org/wiki/quotidian looks at least partly usable.
How significant is the interest in this, what is the target auditory? Any use cases not covered by web interface or the API?
*** Bug 57800 has been marked as a duplicate of this bug. ***
