Community Wishlist Survey 2017/Wiktionary/Parse dumps for DICT clients

Random proposal ►◄ Wiktionary

Parse dumps for DICT clients

Problem: Wiktionary is a knowledge silo; its content is effectively unavailable to potential users except via the web-based interface. It is rather difficult to search or make additional use of the content via search engines, third-party software, or even as a spell-checker database despite its wide acclaim in the linguistic's academic community as a massive resource without peer.

Who would benefit: Readers, writers.

Proposed solutions:
- Standard dictionary dump
  
  Create DICT database output as part of regularly scheduled database dumps.
  
  Custom dictionary api
  
  Build a DICT server extension which monitors port 2628. A wide range of clients are already part of many operating systems such as MacOSX (OmniDictionary), Kdict/GNOME Dictionary/MATE Dictionary on Linux, and is even directly implemented in cURL.

More comments: Do something small, now. Parsing dumps to produce dict-style-jargon files is simple and quick. Building on that to produce DICT databases, expose a DICT server, and eventually producing standard, reliable data in formats consumable for spelling dictionaries, education dumps, translation dictionaries, and more are really just minor investments to a readily expandable pile of value-added products.
The most important element is to do something, anything, to leverage one of the more valuable WMF assets.

Phabricator tickets:
- T38881 Wiktionary needs usable API
- T31229 Extension to provide access via the dict protocol
- T986 Use structured data on Wiktionary

Proposer: Initially I think it was brion, back in 2003-ish. Never happened. -- User:Amgine

Translations: none yet

Discussion

The title is too short to be useful, shouldn't you add just 3 or 4 more words to make that "non single" short? --Liuxinyu970226 (talk) 13:55, 15 November 2017 (UTC)[reply]

You probably need to generally flesh out this proposal. It's not immediately obvious to everyone what it is, what would happen and how it would benefit readers and editors. For example, not all Wikimedians know what an API is. /Johan (WMF) (talk) 15:18, 16 November 2017 (UTC)[reply]

Moving this to Community Wishlist Survey 2017/Wiktionary/Parse dumps for DICT clients failed with "already exists" error; same with a couple other variants. - Amgine/^{meta wikt wnews blog wmf-blog goog news} 07:36, 19 November 2017 (UTC)[reply]

I've move it without any trouble. I am still not sure to understand properly the direction of this proposal, but I agree on parsing dumps to offer more exploitability! Noé (talk) 10:01, 20 November 2017 (UTC)[reply]

Voting

Support Offer pre-formated exportated dumps could give Wiktionary data much more value. Noé (talk) 18:47, 27 November 2017 (UTC)[reply]
Support VIGNERON * ^discut. 08:37, 28 November 2017 (UTC)[reply]
Support --Liuxinyu970226 (talk) 13:32, 28 November 2017 (UTC)[reply]
Support Otourly (talk) 16:40, 28 November 2017 (UTC)[reply]
Support Thomas Obermair 4 (talk) 23:29, 28 November 2017 (UTC)[reply]
Support Libcub (talk) 06:07, 29 November 2017 (UTC)[reply]
Support Donald Trung (Talk 🤳🏻) (My global lock 🔒) (My global unlock 🔓) 13:34, 29 November 2017 (UTC)[reply]
Support Maybe Wikidata will make more easy this. Giovanni Alfredo Garciliano Diaz (talk) 21:35, 29 November 2017 (UTC)[reply]
Support Pamputt (talk) 18:56, 1 December 2017 (UTC)[reply]
Support PMG (talk) 17:07, 3 December 2017 (UTC)[reply]
Support Kostas20142 (talk) 18:16, 3 December 2017 (UTC)[reply]
Support Gryllida 01:12, 4 December 2017 (UTC)[reply]
Support Lyokoï (talk) 19:00, 4 December 2017 (UTC)[reply]
Support JAn Dudík (talk) 08:01, 6 December 2017 (UTC)[reply]
Support Hector (talk) 13:33, 7 December 2017 (UTC)[reply]
Support Tacsipacsi (talk) 21:34, 9 December 2017 (UTC)[reply]
Neutral Great idea, but let's implement structured Wiktionary first, it will be much easier afterwards. Syced (talk) 05:42, 11 December 2017 (UTC)[reply]
Support Psychoslave (talk) 09:02, 11 December 2017 (UTC)[reply]