Provide EDICT importer plugin

Bug #357461 reported by Michael Wayne Goodman on 2009-04-08
2
Affects Status Importance Assigned to Milestone
glot
High
Unassigned

Bug Description

As a first importable format, EDICT would be a good choice as it encompasses languages that both developers know. Keep in mind that this is for the original file format (eg "kanji [kana] /(general info) gloss/gloss/.../") and not the xml format. The xml (for JMdict) format will come later. Also, the CEDICT format is similar to this one, but should probably be kept separate.

The format specification is here: http://www.csse.monash.edu.au/~jwb/edict_doc.html

This depends on the plugin-architecture blueprint: https://blueprints.launchpad.net/glot/+spec/plugin-architecture

Update: apparently there are two versions of EDICT (with the second being called EDICT2). The second version has support for multiple headwords. I think we should go with that.

For the alpha milestone, this will not be a plugin. Just make it a function inside glotbase.py, then we can move it out for beta (when we have the plugin architecture)

Changed in glot:
milestone: none → alpha
status: New → Confirmed
importance: Undecided → High
description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related blueprints