blocks|key|807806|text|维基词典运行在has+an+API的MediaWiki上。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|807807|其中一个应用编程接口文档的子页是Client+code,+which+lists+some+Python+libraries。|807808|entityMap|0|LINK|mutability|MUTABLE|url|http://www.mediawiki.org/wiki/API|1|http://www.mediawiki.org/wiki/API:Client_code#Python^0|7|A|0|0|G|1A|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

Wiktionary runs on MediaWiki, which <a href="http://www.mediawiki.org/wiki/API" rel="noreferrer">has an API</a>.

One of the subpages for the API documentation is <a href="http://www.mediawiki.org/wiki/API:Client_code#Python" rel="noreferrer">Client code, which lists some Python libraries</a>.

blocks|key|807836|text|我曾经下载了一个维基词典转储，试图收集斯拉夫语言的单词和定义。我使用elementtree遍历作为转储的xml文件。我会避免尝试抓取或爬行站点，只下载wikimedia为wiktionary提供的xml转储。转到wikimedia+downloads，查找英语维基词典转储(enwiktionary)，然后转到最新的转储。您可能需要pages-articles.xml.bz2文件，它只是文章内容，没有历史记录或评论。用您喜欢的python中的任何xml处理库来解析它。我个人更喜欢elementtree。祝好运。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|807837|entityMap|0|LINK|mutability|MUTABLE|url|http://download.wikimedia.org/|1|http://download.wikimedia.org/enwiktionary/^0|2Y|J|0|3T|C|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

I had at one time downloaded a wiktionary dump, trying to gather together words and definitions for slavic languages. I approached it using elementtree to go thru the xml file that is the dump. I would avoid trying to scrape or crawl the site, and just download the xml dump that wikimedia provides for wiktionary. Go to the <a href="http://download.wikimedia.org/" rel="noreferrer">wikimedia downloads</a>, look for the english wiktionary dumps (<a href="http://download.wikimedia.org/enwiktionary/" rel="noreferrer">enwiktionary</a>) and go to the most recent dump. You'll probably want the pages-articles.xml.bz2 file, which is just the article content, no history or comments. Parse this with whatever xml processing libraries you prefer in python. I personally prefer elementtree. Good luck.

blocks|key|3991529|text|wordnik在解析定义等方面做得很好，而且他们有一个great+api|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3991530|正如其他人所提到的，wiktionary是一个格式化灾难，并且不是为计算机可读而构建的|3991531|entityMap|0|LINK|mutability|MUTABLE|url|http://wordnik.com/|1|http://api.wordnik.com/^0|0|7|0|R|9|1|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]|$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

<a href="http://wordnik.com" rel="noreferrer">wordnik</a> has done a good job parsing-out definitions, etc
and they have a <a href="http://api.wordnik.com" rel="noreferrer">great api</a>

like the others have mentioned, wiktionary is a formatting-disaster, and was not built to be computer-readable

blocks|key|810726|text|是的，很多人都解析过Wiktionary。您通常可以在Wiktionary-l+mailing+list+archives中找到过去的经验。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|810727|其他答案没有提到的一个项目是DBPedia的Wiktionary+RDF+extraction。|810728|其他几十个研究项目解析了维基词典:你可以在最近的Wiktionary+special和维基媒体研究时事通讯的other+issues中找到一些例子。|810729|Recently有人还制作了一个English+Wiktionary+REST+API，其中包括维基词典数据的一个未指明的子集；未来的计划还不清楚。|810730|entityMap|0|LINK|mutability|MUTABLE|url|https://lists.wikimedia.org/pipermail/wiktionary-l/|1|http://dbpedia.org/wiktionary-rdf-extraction|2|https://meta.wikimedia.org/wiki/Research:Newsletter/2015/September#Wiktionary_special|3|https://meta.wikimedia.org/wiki/Special:Search?search=wiktionary&prefix=Research%253ANewsletter%252F20&fulltext=Search%2Bpast%2Bissues&fulltext=Search|4|https://phabricator.wikimedia.org/T119235|5|https://en.wiktionary.org/api/rest_v1/?doc#!/Page_content/get_page_definition_term^0|R|Y|0|0|M|P|1|0|O|I|2|1I|C|3|0|0|8|4|G|R|5|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@$A|12|B|13|1|14]]|C|$]]|$1|D|3|E|5|6|7|15|8|@]|9|@$A|16|B|17|1|18]]|C|$]]|$1|F|3|G|5|6|7|19|8|@]|9|@$A|1A|B|1B|1|1C]|$A|1D|B|1E|1|1F]]|C|$]]|$1|H|3|I|5|6|7|1G|8|@]|9|@$A|1H|B|1I|1|1J]|$A|1K|B|1L|1|1M]]|C|$]]|$1|J|3|-4|5|6|7|1N|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]|R|$5|M|N|O|C|$P|S]]|T|$5|M|N|O|C|$P|U]]|V|$5|M|N|O|C|$P|W]]|X|$5|M|N|O|C|$P|Y]]|Z|$5|M|N|O|C|$P|10]]]]

Yes, many people parsed Wiktionary. You can usually find past experiences in the <a href="https://lists.wikimedia.org/pipermail/wiktionary-l/" rel="noreferrer">Wiktionary-l mailing list archives</a>.

A project not mentioned by other answers is DBPedia's <a href="http://dbpedia.org/wiktionary-rdf-extraction" rel="noreferrer">Wiktionary RDF extraction</a>.

Dozens other research projects parsed Wiktionary: you can find some examples in a recent <a href="https://meta.wikimedia.org/wiki/Research:Newsletter/2015/September#Wiktionary_special" rel="noreferrer">Wiktionary special</a> and in <a href="https://meta.wikimedia.org/wiki/Special:Search?search=wiktionary&amp;prefix=Research%3ANewsletter%2F20&amp;fulltext=Search+past+issues&amp;fulltext=Search" rel="noreferrer">other issues</a> of the Wikimedia research newsletter.

<a href="https://phabricator.wikimedia.org/T119235" rel="noreferrer">Recently</a> someone also made an <a href="https://en.wiktionary.org/api/rest_v1/?doc#!/Page_content/get_page_definition_term" rel="noreferrer">English Wiktionary REST API</a> which includes an unspecified subset of the Wiktionary data; future plans for the thing are not known yet.

blocks|key|2583226|text|我试着分析了德语维基词典。我最终把它写出来，因为太难了，但在我放弃之前，我把我的(根本没有整理过的)代码放在https://github.com/benreynwar/wiktionary-parser上。尽管有编辑使用的约定，但除了同行监督之外，它们不会被其他任何东西强制执行。所使用的模板的多样性以及页面中的所有拼写错误使得解析非常具有挑战性。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2583227|我认为问题是他们使用了与wiktionary相同的系统，这对于编辑来说很容易使用，但不适合wiktionary更结构化的内容。这是一个遗憾，因为如果wiktionary可以很容易地解析，它将是一个非常有用的资源。|2583228|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/benreynwar/wiktionary-parser^0|1I|1B|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

I had a crack at parsing the german wiktionary. I ended up writing it off as too difficult, but I put my (not at all tidied up) code up at <a href="https://github.com/benreynwar/wiktionary-parser" rel="nofollow noreferrer">https://github.com/benreynwar/wiktionary-parser</a> before I gave up. Although there are conventions used by the editors they are not enforced by anything other than peer oversight. The diversity of templates used along with all the typos in the pages makes the parsing quite challenging.

I think the problem is that they've used the same system as for wiktionary which is great for ease of use by the editors, but is not appropriate for the much more structured content of wiktionary. It's a shame because if wiktionary could be easily parsed it would be a hugely useful resource.

blocks|key|810641|text|我刚从德语垃圾场做了一个单词列表：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|810642|bzcat+pages-articles.xml.bz2+%7C+grep+'<title>[%5E[:space:][:punct:]]*</title>'+%7C+sed+'s:.*<title>$.*$</title>.*:\1:'+>+words|code-block|syntax|javascript|810643|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I just made a word list from the German dump like that:

<pre><code>bzcat pages-articles.xml.bz2 | grep '&lt;title&gt;[^[:space:][:punct:]]*&lt;/title&gt;' | sed 's:.*&lt;title&gt;$.*$&lt;/title&gt;.*:\1:' &gt; words
</code></pre>

blocks|key|3991620|text|欢迎您尝试使用MySQL解析的维基词典数据库。使用Java语言编写的解析器创建了两个数据库(英语维基字典和俄语维基字典)：http://wikokit.googlecode.com|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3991621|如果你喜欢PHP，那么欢迎你使用这个机器可读的Wiktionary+2的piwidict+-+PHP|3991622|entityMap|0|LINK|mutability|MUTABLE|url|https://code.google.com/p/wikokit/|1|https://github.com/componavt/piwidict|2^0|1P|T|0|0|Y|1|1|10|8|2|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]|$A|Y|B|Z|1|10]]|C|$]]|$1|F|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|O]]]]

You are welcome to play with the MySQL parsed Wiktionary database.
There are two databases (English Wiktionary and Russian Wiktionary) created by the parser written in Java: <a href="https://code.google.com/p/wikokit/" rel="nofollow">http://wikokit.googlecode.com</a>

If you like PHP, then you are welcome to play with <a href="https://github.com/componavt/piwidict" rel="nofollow">piwidict</a> - PHP API to this machine-readable Wiktionary <a href="https://github.com/componavt/piwidict" rel="nofollow">2</a>

blocks|key|810705|text|你可能会对dbnary项目感兴趣，虽然不是python，但很有趣。Claims支持21种语言的解析，并支持wikdict。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|810706|entityMap|0|LINK|mutability|MUTABLE|url|http://kaiko.getalp.org/about-dbnary/|1|http://www.wikdict.com/^0|5|6|0|1H|7|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

You may be interested in <a href="http://kaiko.getalp.org/about-dbnary/" rel="nofollow">dbnary</a> project, not python but interesting.
Claims support parsing for 21 languages and it powers <a href="http://www.wikdict.com/" rel="nofollow">wikdict</a>.

blocks|key|807937|text|还有JWKTL，它在解析和提取维基词典中的结构化数据方面做得很好。它是用Java编写的，支持英语、德语和俄语版本。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|807938|entityMap|0|LINK|mutability|MUTABLE|url|https://code.google.com/p/jwktl/^0|2|5|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

There is also <a href="https://code.google.com/p/jwktl/" rel="nofollow">JWKTL</a> which does a good job at parsing and extracting structured data from wiktionary. It is written in Java and has support for the English, German and Russian editions.

blocks|key|3991685|text|这取决于您需要多彻底地解析它。如果您只需要获取一种语言中某个单词的所有内容(定义、词源、发音、词形变化等)那就很简单了。我以前也这样做过，尽管in+Java+using+jsoup|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3991686|但是，如果您需要将其解析为内容的不同组成部分(例如，仅获取单词的定义)，那么它将具有更大的挑战性。语言中单词的维基词典条目没有预定义的模板，因此标题可以是从<h3>到<h6>的任何内容，部分的顺序可能混乱，它们可能是重复的，等等。|style|CODE|3991687|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/chinhodado/fr_dict/blob/master/src/chin/com/frdict/SearchWordAsyncTask.java^0|1Z|J|0|0|26|4|2B|4|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@$A|U|B|V|F|G]|$A|W|B|X|F|G]]|9|@]|C|$]]|$1|H|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

It depends on how thoroughly you need to parse it. If you just need to get all contents of a word in a language (definition, etymology, pronunciation, conjugation, etc.) then it's pretty easy. I had done this before, although <a href="https://github.com/chinhodado/fr_dict/blob/master/src/chin/com/frdict/SearchWordAsyncTask.java" rel="nofollow">in Java using jsoup</a>

However, if you need to parse it down to different components of the content (e.g. just getting the definitions of a word), then it will be much more challenging. A Wiktionary entry for a word in a language has no pre-defined template, so a header can be anything from <code>&lt;h3&gt;</code> to <code>&lt;h6&gt;</code>, the order of the sections may be jumbled, they can be repetitive, etc.

blocks|key|3991791|text|我用Java语言编写了一个原始的parser+for+the+German+Wiktionary+dump，它只提取名词及其冠词，加上它们的阿拉伯语翻译，没有任何依赖关系。执行需要很长时间，所以要注意。如果有兴趣/需要解析更多或其他数据，请告诉我，我可能会在时间允许的情况下进行研究。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3991792|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/publishing-systems/clients/tree/master/org.wiktionary/wiktionary_dump_to_xml_1^0|G|11|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I wrote a primitive <a href="https://github.com/publishing-systems/clients/tree/master/org.wiktionary/wiktionary_dump_to_xml_1" rel="nofollow noreferrer">parser for the German Wiktionary dump</a> in Java that only extracts nouns and their articles, plus their Arabic translation, without any dependencies. Execution takes a long time, so be warned. If there’s interest/need to parse more or other data, please tell me, I might look into it as time permits.

<a href="http://en.wiktionary.org" rel="noreferrer">Wiktionary</a> is a wiki dictionary that covers many languages. It even has translations. I would be interested in parsing it and playing with the data, has anyone does anything like this before? Is there any library I can use? (Preferably Python.)

Has anyone parsed Wiktionary?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

是一个涵盖多种语言的维基字典。它甚至还有翻译功能。我对解析它和处理数据很感兴趣，以前有人做过这样的事情吗？有没有我可以使用的库？(最好是Python。)

问有人解析过Wiktionary吗？
EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问有人解析过Wiktionary吗？EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问有人解析过Wiktionary吗？
EN